Consider what a Department-level form is for. DD Form 2039 — DD Form 2039, Standards Review Checklist, September 1976 — was established to Standards Review Checklist, 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.
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.
Work down the page in the printed order, and understand why the order exists. The identifying block establishes whose record this is and under what circumstances it arises. The body of the form then answers questions that are only meaningful once that context is fixed. The signature block comes last because a certification signed before the entries are complete certifies nothing.
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.
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
What you can download: PDF. The form runs 1 pages and asks for approximately 15 entries. The plurality of formats is deliberate: Defense distribution has never been able to assume one operating environment across the whole force.
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 xfdl file is a survival from an earlier phase of Defense form automation. Xfdl is the IBM Lotus Forms format, and for a long period it was the Department's standard for electronic forms — fielded broadly enough that it still appears in distribution sets today. It opens in IBM Lotus Forms Viewer or a compatible client and nowhere else; a pdf reader will report it as damaged, which is not a fault in the file.
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
- 1. Standard number.
- 2. Standard type.
- 3. Organization.
- 4. Date.
- 5. Review items accomplished: a. Methods content review with operating official (element by element check for currency). Press space bar to mark X in first box if yes, second box if no.
- b. Review of time values for engineered accuracy (maximum use of standard time data is recommended. X first box if yes, second box if no.
- c. Review of personal, fatigue, and delay (PF&D) allowance. X first box if yes, second box if no.
- d. Review of occurrence factors (tangible, dated evidence of review is required). X first box if yes, second box if no.
- e. Review of count procedures. X first box if yes, second box if no.
- f. Workload unit end item count code. X first box if yes, second box if no.
- g. Critical work unit (high earned hour). X first box if yes, second box if no.
- 5.h. Remarks. Any item a - e checked in NO column must be justified. If any item requires change, furnish explanation of change. Enter justification if standard does not meet engineered criteria.
- Approval. Signature of analyst/technician.
- Signature of work measurement supervisor.
- Press this Reset button to clear the data from all fields.
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.
When DD Form 2039 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.
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 2039?
- DD Form 2039, Standards Review Checklist, September 1976
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?