Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 3076-5 is one of those instruments: Military Working Dog (MWD) Covenant Not to Sue with Indemnity Agreement (Adoption), created to Military Working Dog (MWD) Covenant Not to Sue with Indemnity Agreement (Adoption). The reason it carries a DD number rather than a service designation is structural — the Department maintains a single body of forms for matters that arise identically in every service, so that a record created in one component remains intelligible in another.
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.
The edition in force is not stated, carried by the publisher as not stated, and edition discipline is stricter on a Department form than most people expect, precisely because supersession happens everywhere at once. There is no interval during which one service still works from the previous layout while another has moved on.
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.
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.
Two states of the same page circulate, and the reason is worth knowing. In the fillable pdf, the boxes are real fields holding real data; in the printable pdf, the boxes are drawings. Where a record will cross components — as Department records regularly do — the typed version is the safer artifact. Each scan, each forwarding, each reproduction costs handwriting a little legibility, and the office that finally files the record is rarely the office that received it first.
The completed form goes to the office named in not stated or in local implementing procedure, and it is worth keeping a copy before it goes. On a Department form the destination is frequently outside your own chain — another service, a defense agency, a joint staff — and recovering a document that has crossed an organizational boundary is a slower business than retrieving one from a file down the hall.
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 3076-5?
- Military Working Dog (MWD) Covenant Not to Sue with Indemnity Agreement (Adoption)
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?