Field Guide
Why Technical Manual Deliverables Fail
The Short Answer
Rejected Means Nonconforming
A defense manual is accepted against the contract, not against the reviewer's taste. The CDRL line, the DID, the TMCR, and the standards they cite say what conformance means, so nearly every rejection is a gap between the delivered data and one of those documents. The eight gaps below come from the clauses, specifications, and data item descriptions that set those requirements. Your contract, not this page, controls on your program.
The Gaps
Eight Ways a Deliverable Comes Back
- 1. The wrong baseline
- The manual was built to a standard, revision, or tailoring that is not the one the contract cites. The TMCR, the data item description at the version the CDRL line names, and the CDRL remarks together define what was owed, and remarks can tailor the DID. The ground also moves: MIL-STD-40051E, dated 25 March 2025, canceled and superseded the separate -1D and -2D parts, so a team working from habit can be writing to a document the contract no longer means. See which MIL-STD applies.
- 2. Structure that fails the checks
- For S1000D deliverables, a module can be well formed and still break the project's rules. Validation tools check content against the project's BREX as well as the schema, and the business rules are tied to an issue of the specification, so the wrong issue or a stale rule set fails every module at once. Army 40051 deliverables face the same kind of gate through the government's DTDs and the viewer that must display them, covered in what IADS is.
- 3. Content that does not match the configuration
- MIL-PRF-85337B(AS), the Navy quality-assurance specification, says a manual is not validated until it reflects the configuration of the system and includes all engineering changes, and until hardware of the proper configuration was available for the validation effort. It also tells the contractor to use the most current source data. A manual written from last year's drawings, or from a variant that is not the one fielded, fails here however well it is written.
- 4. Validation that did not prove the procedures
- The same specification requires procedures to be understandable and adequate “as evidenced by actual performance,” requires data to support the approved maintenance and support plan, and makes the contractor responsible for validating what its subcontractors and vendors prepared. For an IETM it adds that content must be reachable from the table of contents and search, the viewer must behave as the approved functionality matrix says, and every hotspot and navigation link must work. Details are in TM validation and verification.
- 5. Markings that are missing or wrong
- Under DFARS 252.227-7013 (Aug 2025), a contractor asserts restrictions on the Government's rights only by marking the data, only the authorized legends count, and data delivered without restrictive markings is presumed delivered with unlimited rights. A request to add markings later has to reach the Contracting Officer within 6 months of delivery. A marking not in the authorized format is a nonconforming marking, and if the Contracting Officer gives notice and it is not fixed within 60 days, the Government may ignore it or remove or correct it at the contractor's expense. Distribution statements are a separate marking, assigned by the controlling DoD office, and export-controlled technical data raises its own handling questions. See technical data rights, distribution statements, and ITAR technical data.
- 6. A commercial manual that was never evaluated
- DI-TMSS-80527C exists to acquire sample commercial manuals for evaluation, then commercial manuals that were “evaluated and found to be acceptable,” plus any supplemental data, and it ties to MIL-PRF-32216. Delivering a vendor manual as is, where the contract requires that evaluation, skips the step that makes it an acceptable deliverable.
- 7. Format, medium, or delivery rules ignored
- DFARS 227.7103-2(c) has the contract identify the data type, quantity, format, and media, and the CDRL line carries the DID, the dates, the distribution, and the remarks. A correct manual in the wrong format, sent to the wrong list, or late is still a nonconforming deliverable. Where a contract includes FAR 52.246-2, the Government may reject supplies that are “otherwise not in conformity with contract requirements,” and acceptance is conclusive only with the exceptions the clause lists. Read your own inspection clause before relying on any of this. The CDRL mechanics are in what a CDRL is.
- 8. Comments that were not dispositioned
- Verification findings do not disappear when the manual is edited. In MIL-PRF-85337B(AS), the contractor dispositions every comment and corrects the discrepancies, the Government reviews the dispositions and concurs only if they are acceptable, and an incorporation certificate attests that everything recorded was corrected or resolved. Evaluation records must name the items in the manual each comment applies to. A disposition that says “noted” with no change, or a fix that cannot be traced to a comment, is what sends the package around again.
Review Cycles
Running the Comment Matrix
Most of the elapsed time in a rejection is not rework; it is the comment cycle around it. The Navy specification gives the pattern: the Government records comments, the contractor dispositions each one, the Government reviews and concurs, and a certificate closes the loop. Whatever your contract's forms look like, a matrix with these columns keeps the cycle short. The agreed turnaround on each side is a contract matter; see the TM contract review checklist for pinning it down before you price.
- One row per comment, numbered, with the paragraph, figure, or table it applies to. The Navy specification requires evaluation records to identify the items in the manual, and the verification discrepancy record (DI-TMSS-81820) is organized the same way.
- A disposition for every row: accepted and changed, accepted with a stated alternative, or not accepted with a reason an engineer can defend. Silence is not a disposition.
- The change itself, referenced by the revised paragraph or module, so the reviewer can find it without rereading the manual.
- An owner and a due date per row, set earlier than the contract deadline so a late engineering answer does not become a late submittal.
- A closing count: comments received, dispositioned, and closed, which is also the evidence behind the incorporation certificate.
Before You Submit
A Pre-Submittal Checklist
- The cited standards, revisions, DIDs, and CDRL remarks are written on one page, and the manual was built to that page, not to memory.
- Any government-furnished schemas, DTDs, business rules, or stylesheets are the contracted versions, and the data validates against them with a clean report attached.
- For S1000D, the BREX in force is the one the contract names, and every module declares it.
- Content is traced to the current source data and engineering changes, and the configuration it describes is stated.
- Every procedure was performed on hardware of the right configuration, or the exception is recorded for the validation certificate.
- For electronic output, a link, hotspot, and table-of-contents sweep was run on the final package, not the last build.
- Subcontractor and vendor content went through the same validation as your own.
- Commercial manuals were evaluated as the contract requires, and supplemental data is attached.
- Data rights legends match the assertions list and use only authorized wording; distribution statements and any export-control handling match what the contract and controlling office direct.
- Format, medium, naming, quantity, delivery method, and distribution list match the CDRL line, and the submittal is on time.
- Open comments from earlier reviews are all dispositioned, and the matrix is attached or ready.
- A second person who did not write the manual read the CDRL line and the DID and signed off against them.
For the delivery side, see DFARS technical data delivery clauses (deferred delivery and ordering), and MIL-STD-40051 for the standard behind most Army manuals.
FAQ
Questions We Hear
What are the most common reasons a technical manual deliverable is rejected?
The contract defines conformance, so rejection traces to a gap against it: the wrong standard, revision, or tailoring; failed structural or business-rule checks; content that does not match the configuration; procedures not proven on the equipment; missing or nonconforming markings; wrong format, medium, or distribution; and review comments that were not dispositioned. This list is drawn from the clauses, standards, and data item descriptions that set those requirements, not from a count of rejected submittals.
Why was my CDRL rejected?
Read the CDRL line and the DID it cites at the cited version, then compare the remarks, which can tailor the DID. Check format, medium, quantity, distribution, and submission date against the line, then the content against the DID. The rejection notice should name the nonconformance; if it does not, ask for the paragraph or requirement it relies on. Our CDRL explainer shows where each field sits.
Who decides whether a deliverable conforms?
The contract does, administered by the Contracting Officer and the technical reviewers the Government names. Where the contract includes an inspection clause such as FAR 52.246-2, the Government may reject or require correction of supplies that do not conform to contract requirements. Whether and when acceptance becomes final depends on the clauses in your contract, so read them rather than a summary like this one.
How should we handle government comments on a technical manual?
Log every comment against the paragraph, figure, or table it concerns, give each a disposition and a reference to the change, and return the matrix with the revised manual. In the Navy quality-assurance specification, the Government reviews the contractor's dispositions and concurs if they are acceptable, and a certificate attests that all recorded discrepancies were corrected or resolved. Your contract says what form your submittal takes and how fast each side must turn it.
Can data rights markings cause a rejection?
They can cause a problem even when nobody rejects the manual. A marking outside the authorized format is nonconforming, and after notice and 60 days the Government may ignore it or correct it at the contractor's expense. Unmarked data is presumed delivered with unlimited rights, and the window to ask to add markings is 6 months from delivery. This is educational background, not legal advice: have counsel review your assertions.
Does passing validation guarantee acceptance?
No. Validation is the contractor's proof; verification and final acceptance are separate Government steps, and acceptance follows the terms of the contract. A manual can validate cleanly and still draw findings for usability, format, markings, or a CDRL requirement. Our validation and verification guide covers the events and records.
Get In Touch
Check It Before They Do
Send us the CDRL line, the DID, and the TMCR for a deliverable. We will map the checks a reviewer is likely to run against them.