Consider what a Department-level form is for. DD Form 2840 — Request for Information Regarding Deceased Debtor — was established to Request for Information Regarding Deceased Debtor, and it was placed in the DD sequence because the underlying transaction occurs throughout the Defense establishment in substantially the same shape. Standardizing the record was cheaper and more reliable than letting six services each design their own.
The practical effect of Department-level issue is interoperability. not stated establishes the requirement across the Defense enterprise; not stated keeps the document current for all of it. No service maintains its own variant, which means a completed record travels between components — service to agency, agency to joint command — and arrives in a format the receiving office already knows how to read.
You are looking for edition not stated, listed as not stated. Department-wide supersession is a single event rather than a rollout, which is what distinguishes edition currency on a DD form from the same question on a service publication: nobody anywhere is still accepting the previous version out of habit.
The sequence printed on the form is the sequence in which a reviewer will read it, and the two should agree. Header data frames every entry below it; the substantive fields depend on that frame; the certification stands at the end because its whole function is to vouch for what came before. Entries made out of sequence commonly contradict entries made earlier.
Before the first entry, compare the date printed on the form face with not stated. This is not bureaucratic fussiness. Editions change field numbering, and a receiving office working from the current layout may look for information where your copy does not put it. On a Department form the exposure is wider than usual: your record may be reviewed by an office in another service entirely, one with no reason to remember what the previous edition looked like.
Every field takes an entry, N/A included. The reason is evidentiary rather than clerical: a completed record is supposed to show what was asked and what was answered, and blank space records neither. On dates, follow the format printed beside the field. Conventions vary between components, and a joint document is read by people who do not share your habits.
The Privacy Act Statement is not boilerplate appended for legal cover; it is the mechanism by which a statutory obligation is discharged at the moment of collection. When the government asks an individual for personal information, it must state the authority under which it asks, the principal purpose, the routine uses to which the data may be put, and whether answering is voluntary or mandatory. Those four disclosures are placed ahead of the data fields deliberately, because the point of telling you is to inform a choice you have not yet made.
What the signature block asks for is an act, not a text. Ink on a printed copy performs that act; a digital signature bound to your credential performs it electronically, CAC-based in most Defense systems. Typing your name performs nothing, since anyone with the file could type the same characters. Enter the date at the same moment: the certification is a statement about a point in time and needs one recorded.
The defects that return forms are the same ones year after year: a superseded edition, required fields left blank, handwriting that fails on reproduction, dates in a convention the form did not ask for, and certification without a signature or without a date. Where a specific field is genuinely unclear, the instructions printed on the form come first and not stated governs where the two do not agree.
Download the form
The set published here is PDF, covering unknown pages with roughly unknown fields. More than one format survives because the Department serves users under very different conditions, from a desk with current software to a location where a printer is the only reliable output.
Fillable and printable are not two presentations of one file but two different objects. One holds your entries as structured data within the document; the other is a static picture meant to meet a pen. Since a DD form frequently moves outside the organization that created it, the durability of the entry matters more here than on a record that stays in one drawer. Typed text reproduces indefinitely; handwriting degrades at every copy.
If you find an xfdl file here, its presence is historical. The format belongs to IBM Lotus Forms, which the Department adopted Department-wide for electronic forms and fielded on a scale that makes wholesale removal slow. You need the matching viewer to open it; ordinary pdf software cannot read the format and will say so unhelpfully.
Nothing here is charged for. Published Defense forms are public documents and distribution carries no fee, in any format. One caution about software: fill the form in a desktop pdf application rather than a browser tab. Browser-embedded viewers implement field behaviour inconsistently, and the failure mode is silent loss of everything you entered.
Submission follows not stated and whatever local instruction supplements it. Make a copy before the original leaves. Department forms travel across organizational lines by design, and the administrative distance that makes them useful is the same distance that makes tracing a lost one difficult.
When DD Form 2840 cites another form, the citation is self-sufficient. The DD series is a single sequence administered at Department level, so the number resolves to exactly one document without any need to establish which component issued it — a convenience that exists only because the sequence was never allowed to fork.
It helps to see the DA and DD sequences as what they are: separate registries with separate custodians. One serves a single service under a service proponent, the other serves the Department under not stated or an equivalent office, and neither was ever indexed against the other. A number that appears in both systems points to two unrelated documents, which is why reading the prefix comes before reading the digits.
Editions change for reasons that originate above the form itself. The prescribing directive is reissued and the form follows; the information the Department needs to collect changes and the fields change with it; the statutory notice language is amended and every form carrying that notice is republished. None of these events announces itself to the person who downloaded a copy last year, which is why confirming not stated at the moment of download is the only reliable check available to you.
What you have here is the document and a description of it, which is a different thing from guidance. This page is not an organ of the Department, gives no legal or procedural advice, and makes no representation about the outcome of any filing; the offices that administer the requirement are the only ones positioned to answer that. Applicability, eligibility and procedural questions belong to not stated, to your servicing personnel office, or to the office designated in not stated.
Questions and answers
- What is DD Form 2840?
- Request for Information Regarding Deceased Debtor
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?