Administrative documents are written for readers who were not present, and DA Form 2385 is no exception. Titled TEMPORARY GRAVE/NICHE MARKER, it is used to temporary grave/niche marker (s&i arlington national cemetery, attn: annc-a, arlington, va) — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date 10/01/2020 and the status ACTIVE. Its 1 page(s) and roughly 116 fields are sized to what the record must prove years later, which is always more than the moment appears to need. A newer edition exists. This one is retained because the documents completed on it were completed under its terms and are read under them.
Behind any Army form sit two separate decisions. What the document asks is settled by OAC, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by PAM 290-5. That division is the reason a form can outlive several changes in the process it serves.
Retrieval governs the order of entry. The head of the form takes name, identification number, unit and date, and those values become the handles by which the record is found later — the substantive blocks are never searched on. This is why the spelling must match official records exactly rather than approximately.
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.
The signature is the point at which entries become an assertion someone stands behind, so it follows everything else and its absence leaves a draft. Countersignatures by reviewing, approving or witnessing officials each carry their own weight and are dated at signing, which is how the file preserves the order of responsibility. Seen that way, the familiar errors are not clerical trivia: an unanswered mandatory field, digits transposed in an identification number, day and month reversed, and residue from a reused file each put something false or unresolved into a document that will be relied upon.
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
The published formats — PDF, XFDL — reflect the range of places a form gets filled in. Where there is a computer, the fillable pdf supplies live fields that keep entries positioned and readable. Where there is not, the printable pdf gives the identical page as flat artwork for pen entry. The distinction is one of setting rather than of authority; the page is the same document in both.
Software determines whether an entry lasts. A browser viewer is designed for reading, and several will take typed input into fields without any means of writing it back — the text is simply absent when you reopen. A standalone reader handles the form structure properly. The xfdl file is IBM Lotus Forms, carried in Army systems for the routing and signature support it provides, which is why the Lotus Forms Viewer is its only reader.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- BRNSER
- CHANGES
- ContentArea1
- DATE
- DAY_A
- DAY_B
- DAY_C
- DENOMIN
- GRADE
- GRAVENO
- Group1
- MO_A
- MO_B
- MO_C
- NAME
- NICCRT
- NUMBER
- PVTMON
- Page1
- R100
- R101
- R102
- R103
- R104
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.
Editions change because the process changes, and the printed edition date is the only marker of which version a page belongs to. A copy saved locally cannot know it has been superseded, so the date on it is compared against the edition in force before reuse. Records already executed under an earlier edition are left alone — a document is read under the terms it was made, and reopening completed files to match a later form would falsify the account.
One boundary should be stated clearly. What is distributed here are copies of published Department of the Army forms; the site is independent, issues nothing of its own, and holds no position in the system it describes. Proponency, prescribing directives and retention schedules operate without reference to it. Consequently nothing here is legal advice and no assurance about acceptance is possible. Questions about a particular entry, a requirement or eligibility belong with OAC or your servicing administrative office.
Questions and answers
- What is DA Form 2385?
- TEMPORARY GRAVE/NICHE MARKER
- Which edition is current?
- 10/01/2020
- Who is responsible for this form?
- OAC
- In which formats can it be downloaded?
- PDF, XFDL, PDF