WWI Classification Lists Part 1: How to Order

blog banner - WWI Classification Lists Part 1: How to Order

Thanks to Classification Lists, I now know about events during several days in my grandfather’s life.

Why you might want this record: to learn more about the process between an ancestor’s registration for the draft and induction, which might include indication that an appeal or deferment was made.

What you need to know before ordering: the draftee’s name and local draft board identification number, which can be found on the WWI Draft Registration Card for your ancestor.

Groups of men who registered for the draft and were determined to be in the Classification I category (based on filling in a questionnaire), were called in for physical examinations.

Classification Lists show the results of the examination of the draftees, as well as where they were to be sent. These lists are found in NARA’s RG163, and as of this blog post being published, the Classification Lists at NARA are not online.

I searched FamilySearch.org for Joseph McMahon’s WWI Draft Registration Card at https://www.familysearch.org/en/search/collection/1968530

The identification code for Joseph McMahon’s local draft board is circled. This number is used by the NARA archivist to identify the book for the Classification List containing Joseph McMahon’s entry.

WWI example draft card (back)

Courtesy of FamilySearch.org

I emailed this information with an attached image of his draft card to the NARA branch in Atlanta at: atlanta.archives@nara.gov

Data sent to NARA Atlanta

An automated response was sent to my email in reply. Shortly after that, a response from an archivist followed with confirmation that the record had been found, and how to pay for it. The cost was $20. The scanned record was emailed to me after the archivist confirmed the payment.

Human archivists are involved in the process of lookup, scanning, and communicating. That means the timeline for responses may vary based on archivists’ workload. Also know that payment must be verified before the record is emailed.

In the next blog post, we will take a look at the Classification List itself.

Special thanks to Peggy Ash and Michael Strauss for their informative, detailed, and motivating presentations about the US Drafts.


Fatal error: Uncaught GuzzleHttp\Exception\ClientException: Client error: `POST https://api.aspose.cloud/connect/token` resulted in a `429 Too Many Requests` response in /home/aweegpsr/public_html/wp-content/plugins/aspose-doc-exporter/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/aweegpsr/public_html/wp-content/plugins/aspose-doc-exporter/vendor/guzzlehttp/guzzle/src/Middleware.php(69): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response), NULL, Array, NULL) #1 /home/aweegpsr/public_html/wp-content/plugins/aspose-doc-exporter/vendor/guzzlehttp/promises/src/Promise.php(204): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/aweegpsr/public_html/wp-content/plugins/aspose-doc-exporter/vendor/guzzlehttp/promises/src/Promise.php(153): GuzzleHttp\Promise\Promise::callHandler(1, Object(GuzzleHttp\Psr7\Response), NULL) #3 /home/aweegpsr/public_html/wp-content/plugins/aspose-doc-exporter/vendor/g in /home/aweegpsr/public_html/wp-content/plugins/aspose-doc-exporter/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113