The reason DA Form 2122 looks the way it does is that a file has to speak for itself. Officially RECORD OF INTERMENT/INURNMENT, it serves to record of interment/inurnment (s&i arlington national cemetery, attn: annc-a, arlington, va), and the record it produces outlasts the people and the circumstances behind it. Edition 10/01/2020, status ACTIVE, is the version published here: 4 page(s), close to 145 fields, each one present because some later reader will need that fact without being able to ask for it. Because a subsequent edition has appeared, this copy stays available — a record made under one edition is interpreted under that edition.
The form has an author and an occasion, held by different authorities. OAC owns the content and reshapes it when what is being recorded changes. PAM 290-5 governs the event that calls for the form and the route the finished document takes afterwards. Keeping those two apart is what allows a procedure to be amended without the page being rebuilt each time.
The heading blocks come first because the record is retrieved by them, not read into. Name as official records spell it, identification number, unit, date of preparation — those four are the index, and everything below them is content that only surfaces once the index has done its work. A form filed under a name written casually is not lost in principle, only in practice, which amounts to the same thing.
Much of the form's behaviour follows from its being a fixed page. Tab order was set at build time along the reading sequence, which is why tabbing catches boxes a pointer passes over. Exclusive groups release one choice when another is made because a record cannot carry two answers to a single question. Single-line fields refuse to wrap because every entry must print where the layout expects it — text beyond the width is lost at the margin, visible on screen to the end. That is what remarks areas and continuation sheets are for. Marking a field that does not apply matters for a related reason: emptiness is ambiguous, and a reviewer reading the file later cannot distinguish an omission from a decision.
A signature is what converts entries into a record, which is why it comes last and why an unsigned form remains a draft however complete it looks. Where a reviewing official, an approving authority or a witness also signs, each adds a distinct attestation, and each dates the day of signing rather than the day of preparation — the dates trace the sequence of responsibility. The recurring defects are worth knowing precisely because they defeat that purpose: an empty mandatory field leaves an obligation unmet, transposed identification digits attach the record to nobody, a date with day and month reversed puts events in the wrong order, and entries left in a reused working copy assert facts nobody intended.
Behind the Privacy Act statement is a requirement that anyone asked for personal data be told, in advance, under what authority it is sought, for what purpose, who else routinely sees it, and whether refusal is possible. Reading it after completing the fields defeats its function. And the completed form is itself a personal record from that point on, subject to the handling rules such records carry.
Download the form
Why several files for one page? Because the form has to be completed in a headquarters and in places without a workstation, and PDF, XFDL covers both. The fillable pdf holds interactive fields that fix each entry in place and remove handwriting from the equation. The printable pdf is the same layout without those fields, meant for a printer and a pen. Neither is a lesser copy of the other; each answers a condition the other cannot.
The choice of application decides whether your work survives. Browsers render pdfs as documents to be read; where a viewer shows fields without a mechanism to store them, typed text disappears when the tab closes, and nothing announces the loss. A full reader treats the file as a form and preserves entries on save. The xfdl format comes from IBM Lotus Forms, used across Army systems because of the routing and signature functions built into it, and it opens in the Lotus Forms Viewer alone.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- ADDFUDIR
- BRANCH
- CASKIN
- ContentArea1
- DAY_A
- DAY_B
- DAY_C
- DPTHGRVE
- ENLST
- GRADE
- GRVENO
- HDMRK
- INSCRPDT
- MILSTAT
- MO_A
- MO_B
- MO_C
- NAMCEM
- NAMCHAP
- NAME
- NAMOFKIN
- NICCRT
- NMADDCRE
- PLADTH
Where the signed form goes is settled by PAM 290-5 rather than by the office holding it — a named recipient, the unit administrative channel, or the individual's own file, depending on why it was raised. Retention likewise belongs to the records schedule for the series, which exists so documents are kept for as long as anyone might need them and no longer. Keep a copy before release; the original serves the file from then on, not you.
Series and number are how the DA series signals which documents belong together, and the grouping follows real process boundaries: a shared proponent or directive usually means a shared purpose. A form cited on the face of another is part of that same transaction, and continuation sheets, covers and transmittals complete it.
An edition marks the form at a point in a process that keeps moving, and the date printed on the page is what distinguishes one from another. Since a saved file never announces its own obsolescence, compare its date against the current edition before using it again. Prior executions remain valid: the change applies forward, and a record is read against the edition it was written under.
A word on where this page sits. These are reproductions of published Department of the Army documents, made available by an independent site with no official role and no authority to issue forms. The structure described above — proponent, prescribing directive, records schedule — exists apart from this site entirely, which is why nothing written here is legal advice and why acceptance by any office is not something that can be promised. Put questions of entry, requirement or eligibility to OAC or to the administrative office servicing your unit.
Questions and answers
- What is DA Form 2122?
- RECORD OF INTERMENT/INURNMENT
- Which edition is current?
- 10/01/2020
- Who is responsible for this form?
- OAC
- In which formats can it be downloaded?
- PDF, XFDL, PDF