Military Forms Guide

DD Form 1716 — DD Form 1716, Contract Date Package Recommendation/Deficiency Report, December 1977

Contract Data Package Recommendation/Deficiency Report

Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 1716 is one of those instruments: DD Form 1716, Contract Date Package Recommendation/Deficiency Report, December 1977, created to Contract Data Package Recommendation/Deficiency Report. 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.

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.

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 39 entries. The plurality of formats is deliberate: Defense distribution has never been able to assume one operating environment across the whole force.

The difference between a fillable and a printable pdf is a difference in what the file contains. A fillable release carries an interactive layer: each box is a defined field with a name and a data type, and what you type is stored as data inside the document. A printable release has no such layer — it is an image of the page, and the only place your answers can go is onto paper. The distinction matters downstream, because a Department record often gets scanned and forwarded several times before it reaches its final file, and typed characters survive that chain in a way pen strokes do not.

What the form asks for

  • 1. Control Number.
  • 2. Thru (Administrative Contracting Officer (ACO)).
  • 3. To (Procuring Contracting Officer (PCO)):
  • 4. From:
  • 4.a. Reporting element. Press space bar to mark X in first box if CA, second box if S&FM, third box if P, fourth box if Q, or fifth box if other.
  • 5. Priority for ACO or PCO reply. X first box if 14 day reply, second box if 30 day, third box if 45 day, or fourth box if no reply (future PCO action).
  • 6. Contract Number.
  • 7. National Stock Number.
  • 7.a. Item Noun name.
  • 8. Contractor's Name and complete address.
  • 9. Contract Data Package Problem. a. Mark X if Contract and Supporting documentation is late, missing, illegible, there are insuffiecient copies, etc
  • 9.b. Mark X if there is deficient contract data package.
  • 9.b.(1) Mark X if Item description.
  • 9.b.(2) Mark X if Point of inspection or acceptance, C O C or fast pay.
  • 9.b.(3) Mark X if Government P Q A and delegation.
  • 9.b.(4) Mark X if Code Number and/or address missing or incorrect.
  • 9.b.(5) Mark X if Preservation, packaging, packing, consignment and marking.
  • 9.b.(6) Mark X if Specifications/ Drawings.
  • 9.b.(7) Mark X if Item quantity or dollar value.
  • 9.b.(8) Mark X if Missing, improper or conflicting quality requirements.
  • 9.b.(9) Mark X if Configuration management, technical data.
  • 9.b.(10) Mark X if Appropriation or financial data.
  • 9.b.(11) Mark X if Other - Contract administration.
  • 9.b.(12) Mark X if Other- S & F M.

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.

Where a service form is cited in the same instruction, the two numbering systems should not be read across. DA numbering belongs to the Army and is administered by an Army proponent; DD numbering belongs to the Department and is administered by not stated or an equivalent Department office. The systems developed separately and were never harmonized, so identical digits in each identify two documents with nothing in common. The prefix, not the number, tells you which system you are in.

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.

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 1716?
DD Form 1716, Contract Date Package Recommendation/Deficiency Report, December 1977
Which edition is current?
Not stated by the publisher
Who is responsible for this form?
Not stated
In which formats can it be downloaded?
PDF

Other forms in the series