It Was a 7: One 1940 Census Code Revealed

Post-enumeration coding of 1940 census data for marital status

Like many over-eager genealogists, I was online the morning of 02 April 2012 – the first day the 1940 census was available to the public. Within a matter of days, I had located a handful of relatives on the 1940 census by first locating their enumeration districts. It wasn’t long before I began finding information in this census that I hadn’t encountered previously despite having done extensive census research in the past. For example, why was I finding the numeral “7” in the marital status column, instead of one of the more common abbreviations of marital status, such as S[ingle], M[arried], W[idowe]d or D[ivorced]?

1940 census with marital status column 12 highlighted1940 U.S. Federal census entry for Oliver Bingaman of Shoshone County, Idaho, highlighted in yellow.

I’ve highlighted column 12 in the 1940 census in red where marital status was recorded. Note those who reported they were married (M) where the M was crossed out and a 7 penciled in. As we shall see later in this piece, instructions to enumerators were only partially followed for this household. In the case of the author’s grandfather, Oliver Bingaman, highlighted in yellow above, no obvious wife was enumerated with him, and yet there was no alteration of his marital status as originally recorded.

Fortunately, I was able to track down a blog entry by Meldon J. Wolfgang III, wherein he described this very scenario and some of the backstory behind this particular census code. Read his post here.

Mr. Wolfgang’s blog entry contains a link to a very valuable resource: the IPUMS-USA website. Wolfgang explains

“IPUMS is not a genealogy site; it is the acronym for the ‘Integrated Public Use Microdata Series’ and is part of the University of Minnesota’s Population Center. Data geeks, statisticians and epidemiologists – all of whom use census data – are the primary users of this site.”

Even though genealogists per se are not the intended audience, serious genealogists will nevertheless find a wealth of information about the decennial United States Federal census on this site.

IPUMS USA website | Census microdata for social and economic research
IPUMS-USA census data website – http://usa.ipums.org/usa/

To locate the procedural history that explains the post-enumeration coding done by the staff of the Census Bureau, navigate to this link: http://usa.ipums.org/usa/resources/voliii/enumproc1940.pdf

It is under the General Population Coding section that we find the explanation for the coding of marital status:

Source: Jenkins, Robert M. Procedural History of the 1940 Census of Population and Housing. (Madison : University of Wisconsin Press, 1983), p. 63

To summarize, if the enumerator left the marital status column blank, then the Census Bureau staff in Washington D.C. would attempt to complete the field based solely on other elements they read on the page. If no spouse or children were living in the household, the coder assumed the individual was single. If, however, the person had no spouse in the home and there were children present, then one of two codes was entered, either 1) widowed, if the individual was 55 or older, or 2) 7, if the person was under age 55. Even when a marital status of M[arried] was recorded, clerks were instructed to interline the M and replace it with 7 if no spouse was included in the household, thus resulting in this entry: M 7. This distinction with respect to age is important. In a nutshell, if you find a marital status of M crossed out and replaced with Wd, don’t assume the spouse is deceased; look for that individual in another household. If you find a 7 in the marital status column, or an M crossed out and a 7 penciled in, then look for the spouse in another household.

As Wolfgang pointed out in his post, the census coders had no special insight into any particular household. If something you’re seeing in the 1940 census doesn’t track with the research you’ve done on a family, or with your own personal knowledge of events, then having a better understanding of these codes may help explain any anomalies.

We have examined a bit of the history of census coding for a single column of data (marital status) in a single census year (1940). Imagine what additional information you may be able to glean from other entries if you read the relevant instructions or procedural history as well. The IPUMS-USA website is a great place to start.

***
Note: In his blog post, Meldon J. Wolfgang III referenced a talk he gave in the days leading up to the release of the 1940 census. Judy G. Russell, CG, (aka the Legal Genealogist) was in the audience and gave a brief synopsis of his talk, and an overview of the IPUMS-USA website, on her blog.

Three Civil War Pension Files

If you’ve reached an impasse when researching your direct-line ancestors, you’ll need to cast a wider net. Whether called “collateral research”, “whole family research”, “cluster research” or similar variants, the concept remains the same: to break down our proverbial “brick walls” we need to broaden the scope of our research to include members of our target ancestor’s extended family and larger social circle. We may need to research the lives of friends, neighbors, colleagues, comrades and the like. The more difficult the problem to be solved, the further afield we may need to go to track down records relevant to our research problem.

It is with this idea in mind that I recently ordered three United States Civil War pension files, all for the brothers or brothers-in-law of several of my direct ancestors, each of whom served in the Union Army. To order their files, I needed information from the pension index cards. There are two readily available indexes online: T288, available at Ancestry.com, and T289, available at Fold3.com. (To see the card images, you either need to be a subscriber, or go to an institution that has a subscription to one of the databases.) Both indexes were created and microfilmed by the National Archives and Records Administration (NARA) from the original index cards.

I’ve uploaded the pension index cards from T289 for each of the soldiers whose file I’ve ordered. Each card shown illustrates a different scenario with respect to Civil War pension research.

Soldier: David M. Bingaman of Companies C, D and E of the 20th Indiana Infantry, brother of my 2nd great-grandfather, Josephus Bingaman who also served in the Civil War.

Civil War Pension Card for David M. Bingaman

“Organization Index to Pension Files of Veterans Who Served Between 1861 and 1900,” digital images, Fold3.com (http://www.fold3.com : accessed 09 May 2012); David M. Bingaman (Cos. C, D & E, 20th Indiana Inf.) index card; imaged from Organization Index to Pension Files of Veterans Who Served Between 1861 and 1900, T289 (Washington, D.C.: National Archives), roll 91.

In the image above, note that David Bingaman (the “invalid”) applied for a pension 13 Aug 1892, application no. 1,125,866, certificate no. 890,449. Following his death, his widow also applied for a widow’s pension, application no. 645,202, certificate no. 464,995. The fact that the card references a certificate number beside each pension type means that both David and his widow received pensions.

Soldier: George Carson, alias George Cassner, of Company F 38th New Jersey Infantry, brother of my 3rd great-grandmother, Caroline Carson.

Civil War Pension Card George Carson

“Organization Index to Pension Files of Veterans Who Served Between 1861 and 1900,” digital images, Fold3.com (http://www.fold3.com : accessed 09 May 2012); George Carson, alias George Cassner (Co. F, 38th New Jersey Inf.) index card; imaged from Organization Index to Pension Files of Veterans Who Served Between 1861 and 1900, T289 (Washington, D.C.: National Archives), roll. 307.

George Carson applied for a pension 14 Apr 1902 less than a year before his death. His application was no. 1,283,970. His widow also applied for a widow’s pension, application no. 781,136. Applications for both George and his wife were apparently rejected, as there is no certificate number recorded for either of them in the column on the right. Perhaps there was a problem establishing his identity, especially since George seems to have also used the last name of Cassner.

Should I allow the fact that it appears that the applications were rejected to deter me from following up and ordering his pension file? Most definitely not! Even if a pension was rejected, the file will still contain, at a minimum, the application. Indeed, rejected applicants often tried multiple times to prove their claim, offering additional details and advancing more witnesses to vouch for them. On occasion, a Special Examiner was appointed to investigate the merits of the claim, in which case the file may yield a great deal of information.

Soldier: Jackson Wells of Co. D, 128th Ohio Infantry, brother-in-law of my 2nd great-grandfather, Washington R. Wallace.

Civil War Pension Card Jackson Wells

“Organization Index to Pension Files of Veterans Who Served Between 1861 and 1900,” digital images, Fold3.com (http://www.fold3.com : accessed 09 May 2012); Jackson Wells (Co. D 128th Ohio Inf.) index card; imaged from Organization Index to Pension Files of Veterans Who Served Between 1861 and 1900, T289 (Washington, D.C.: National Archives), roll 429.

In this last example, the soldier himself did not apply for a pension. Instead, his widow applied under application no. 462,465. She received a pension under certificate no. 508,610.

Widows’ applications typically provide more family information than a soldier’s application as a widow had to prove:

1. that she was married to the soldier, and the date of the marriage
2. that she remained a widow (she lost the pension if she remarried)
3. divorce or death of any previous wife or wives
4. that the soldier was deceased (if he died outside of actual service)
5. birth information for soldier’s minor children under 16

(See the full text of the pension Act of July 14, 1862 as published in the New York Times, 12 Aug 1862).

Although acquiring a Civil War Pension file isn’t cheap ($75.00 for the first 100 pages from NARA), oftentimes a pension file can contain the key to solving a brick wall problem. You can spend literally years searching for proof of a relationship only to discover the answer plainly stated within the file.

How to order a Civil War pension file
Civil War pension files are still, for the most part, textual (i.e. paper) records. They have never been microfilmed, and are only now being digitized. With the large number of pension files available, it will be years before they’re online. To access a pension file, you’ll need to do one of three things:

1. Visit the National Archives in Washington D.C. yourself
2. Order the pension file from the National Archives directly
3. Hire a private researcher to examine and copy the record for you

To order a pension file from the National Archives, go to: https://eservices.archives.gov/orderonline/start.swe#SWEApplet1

Order Military Records OnlineThe second item is the link to order the complete file (form NATF 85D).

NATF 85D online formTechnically, to order a pension file using NATF 85 you only need the following information, marked with an asterisk (*) in the above screenshot:

Veteran’s first and last name
Branch of service (Army, Navy, Marine Corps)
Kind of service (Regular, Volunteer)
War in which he served
State from which he served

However, I have found that having the pension application number and name of widow or other claimant will ensure you are getting the correct file.

Whenever possible, I recommend acquiring a complete military pension file early on in your research. If you don’t look, you won’t know what nuggets of family information may be included. I have heard tales of family bible pages and photographs being found within a pension file, although I myself haven’t been that lucky.

Stay tuned as I reveal the goldmine of family information discovered in just one of these pension files!