Consider what a Department-level form is for. DD Form 1423-2 — DD Form 1423-2, Contract Data Requirements List (2 data items), August 1996 — was established to Contract Data Requirements List (2 Data Items), 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.
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.
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 2 pages and asks for approximately 168 entries.
All of it downloads without charge. Where care is needed is in the reader you choose. A fillable pdf depends on field properties that desktop applications honour and browser previews frequently ignore, so work locally rather than inside a browser window.
What the form asks for
- A. Contract Line Item Number.
- B. Exhibit.
- C. CATEGORY. Press space bar to mark X if TDP - Technical Data Package.
- C. Mark X if TM - Technical Manual.
- C. Other category.
- D. System/item.
- E. Contract/ PR Number.
- F. Contractor.
- 1. Data Item Number (Item 1 of 2).
- 2. Title of Data Item.
- 3. Subtitle.
- 4. Authority.
- 5. Contract Reference.
- 6. Requiring Office.
- 7. DD 250 Requirement.
- 8. Approval code.
- 9. Distribution Statement Required.
- 10. Frequency.
- 11. As Of Date.
- 12. Date of first submission.
- 13. Date of subsequent submission.
- 14. Distribution. a. Addressee, line 1 of 3.
- 14.b. Number of Copies. Draft.
- 14.b. Number of Final copies: regular.
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 1423-2 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.
Procedures that touch both Department and service processes will cite forms from both sequences, and the coincidence of numbers between them is exactly that — coincidence. An Army proponent maintains the DA series for the Army; not stated or another Department office maintains the DD series for the whole Department. Two independent registries, two independent numbering runs, no correspondence at any value.
A form is downstream of the policy that requires it, and revision usually starts there: a directive is reissued, a collection requirement is altered, notice language is updated by statute. The form is republished as a consequence. Since none of that reaches individual users, an archived copy quietly becomes wrong, and verifying not stated each time you download is the whole remedy.
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 1423-2?
- DD Form 1423-2, Contract Data Requirements List (2 data items), August 1996
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?