Consider what a Department-level form is for. DD Form 1076 — DD Form 1076, Record of Personal Effects of Believed To Be (BTB) Deceased, August 2015 — was established to Record of Personal Effects of Believed To Be (BTB) Deceased, 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.
This is why the arrangement matters to you rather than only to the archivists. not stated governs the form throughout the Department, with not stated as the responsible office, so the record you create is legible outside your own component. Joint assignments, agency details and cross-service transactions all depend on that: the paperwork does not have to be reconstructed each time it crosses a boundary.
Current edition: not stated, status not stated. Understand why that date is worth attention here. When the Department reissues a form, the replacement takes effect across every component simultaneously, so an older copy is not merely locally out of date — it is out of date in every office that might receive it.
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.
Check the edition date before you type anything, against not stated. Old blanks accumulate in shared drives for years, and the cost of one is not obvious until a reviewer cannot find a field. Because DD forms are revised centrally and replaced across the Department in a single action, there is no component still tolerating the old layout as a local practice.
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.
Understand what the Privacy Act Statement is doing on the page. It exists because collecting personal data from an individual triggers a duty to explain the collection: under what authority, for what purpose, to whom the information may routinely go, and whether you are obliged to answer. That explanation precedes the fields for the obvious reason — afterwards it is merely a notice, beforehand it is a basis for deciding.
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
Formats available: PDF, across 2 pages and about 198 fields. That several formats coexist is a consequence of scale — the Department cannot standardize the software on every desk that needs this form, so it standardizes the document instead.
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.
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.
What the form asks for
- 2. Page number of this page.
- 2. Total number of Pages.
- 7.a. Quantity, line 2.
- 7.b. Description.
- 7.c. Received.
- 7.d. Condition.
- 7.e. Disposition.
- 7.a. Quantity, line 3.
- 7.b. Description.
- 7.c. Received.
- 7.d. Condition.
- 7.e. Disposition.
- 7.a. Quantity, line 4.
- 7.b. Description.
- 7.c. Received.
- 7.d. Condition.
- 7.e. Disposition.
- 7.a. Quantity, line 5.
- 7.b. Description.
- 7.c. Received.
- 7.d. Condition.
- 7.e. Disposition.
- 7.a. Quantity, line 6.
- 7.b. Description.
Route the executed form as not stated or local guidance directs, and retain a duplicate first. Cross-component routing is ordinary for DD forms, which is precisely why a personal copy earns its keep: the receiving office may belong to an organization you have no standing to query about a missing document.
Forms referenced inside this one are located by number alone, and that simplicity is a direct product of Department-level numbering. Because the DD sequence is maintained centrally and not duplicated by service, a number is a complete address: one number, one document, throughout the Defense establishment.
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.
Understanding why editions change explains why checking them is not optional. Revision follows directive reissue, changes in what data is required, and amendments to mandatory notice text — decisions made at Department level and communicated through publication rather than notification. The file you saved does not update itself, so the edition date at download is what you rely on.
A word on what this page is. It distributes a published Department of Defense document and describes what the document contains and how it is completed. It is not the issuing authority, does not speak for one, and offers no legal advice; nothing written here determines whether a particular submission will be accepted, because that determination belongs entirely to the office receiving it. Questions of applicability, eligibility or procedure go to not stated, to your servicing personnel office, or to the office identified in not stated.
Questions and answers
- What is DD Form 1076?
- DD Form 1076, Record of Personal Effects of Believed To Be (BTB) Deceased, August 2015
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?