Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 1750 is one of those instruments: DD Form 1750, Packing List, September 1970, created to Packing List. 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.
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.
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.
For an ambiguous field, read the form's own instruction, then not stated, which controls.
Download the form
The set published here is PDF, covering 2 pages with roughly 121 fields.
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.
What the form asks for
- 5. Page number of this page.
- Total number of pages.
- a. Box number, line 1.
- b. Contents - stock number and nomenclature.
- c. Unit of issue.
- Quantities required. d. Initial Operation.
- Quantities required: e. Running Spares.
- f. Total.
- a. Box number, line 2.
- b. Contents - stock number and nomenclature.
- c. Unit of issue.
- Quantities required. d. Initial Operation.
- Quantities required: e. Running Spares.
- f. Total.
- a. Box number, line 3.
- b. Contents - stock number and nomenclature.
- c. Unit of issue.
- Quantities required. d. Initial Operation.
- Quantities required: e. Running Spares.
- f. Total.
- a. Box number, line 4.
- b. Contents - stock number and nomenclature.
- c. Unit of issue.
- Quantities required. d. Initial Operation.
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.
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 1750?
- DD Form 1750, Packing List, September 1970
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?