Consider what a Department-level form is for. DD Form 2759-TEST — DD Form 2759 Test, Report of Other Transactions for Prototype Projects. December 2000 — was established to Report of Other Transactions for Prototype Projects, 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.
That decision has consequences you will notice. Because not stated prescribes the form for the Department as a whole, and not stated maintains it on the Department's behalf, the same blank passes between the Army, the Navy, the Air Force, the Marine Corps, the Space Force, the Coast Guard when operating under Defense jurisdiction, the defense agencies and the combatant commands without translation. A clerk in one component reads a record created in another and finds the fields where they expect them.
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 form is laid out top to bottom in a sequence that reflects how the record will be read, not merely how it was drawn. Identification comes first because everything below it is understood in relation to a named person, unit or transaction; substantive entries follow; certification closes the document because certification attests to what precedes it. Filling out of order tends to produce internal inconsistencies — an entry that made sense before the header was settled and does not afterward.
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.
Leave nothing empty. Where an item genuinely does not apply, N/A is the correct entry, because the record must distinguish between a question that was answered in the negative and a question that was never reached. An empty box carries no information about which happened. Date fields deserve particular care on a Department form, since the reviewer may write dates by a convention different from yours; use the format the form itself specifies.
Where the form collects personal identifiers, a Privacy Act Statement accompanies it, and its placement is meaningful. The statute requires disclosure at the point of collection — authority, purpose, routine uses, and the consequence of declining — so that the person supplying the information does so knowing what becomes of it. Reading it after you have filled the fields inverts the arrangement entirely.
Signature is the point at which a completed form becomes a certification, and the requirement follows from that. On paper it means ink in the designated block; electronically it means a credentialed digital signature, ordinarily applied with a Common Access Card in software that supports it. A name typed into the signature field is data, not an act — it demonstrates nothing about who entered it. The date beside the signature fixes when the certification was made, which is why a signed but undated block is treated as incomplete.
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 1 pages and about 62 fields.
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
- Press this Reset button to clear the data from all fields.
- 1. Type of report: 0 = original, 1 = cancelling, 2 = correcting.
- 2. Report number.
- 3. Contracting office code.
- 4. Name of contracting office.
- 5. Agreements officer. a. Name (last, first, middle initial).
- b. Telephone number (include area code).
- 6. Procurement Instrument Identification Number (P I I N).
- 7. Modification number.
- 8. Action date. 4 digit year, 2 digit month, 2 digit day.
- 9. Completion date (4 digit year, 2 digit month, 2 digit day).
- 10. DUNS number.
- 11. CAGE code.
- 12. Consortium agreement? Y or N.
- 13. Awardee information. a. Name.
- b. Address (street, city, state, zip code).
- c. Type of entity: 1 = non-profit, 2 = traditional contractor, 3 = nontraditional defense contractor.
- 14. Significant nontraditional defense contractors. a. Name, line 1 of 7.
- b. Address (street, city, state, zip code).
- a. Name, line 2.
- b. Address.
- a. Name, line 3.
- b. Address.
- a. Name, line 4.
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.
Cross-referenced documents are found by series and number, with nothing further required. That the DD sequence is unified across the Department means a cited number identifies one form and no other, which is the practical payoff of centralizing the numbering in the first place.
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.
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 2759-TEST?
- DD Form 2759 Test, Report of Other Transactions for Prototype Projects. December 2000
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?