Data sourced from SAM.gov, USAspending, FPDS, Grants.gov. 110+ supplementary federal data feeds. View methodology →
100M+ government records · 110+ gov/news sources · Synced from live federal sources
Explore 100M+ federal records across SAM.gov, Grants.gov, USAspending, FPDS, and 110+ federal sources.
Search all opportunities →CDRLs define every piece of data a contractor must deliver under a government contract. From technical reports to test plans to status updates, CDRLs are the formal mechanism for specifying what data the government needs, when it needs it, and in what format.
Missing or late CDRL deliverables can result in payment withholding, negative CPARS ratings, and contract disputes. This guide covers everything contractors need to know about reading, responding to, and managing CDRLs.
100M+ government records · 110+ gov/news sources · Synced from live federal sources
A Contract Data Requirements List (CDRL) is a standard form (DD Form 1423) used primarily in Department of Defense contracts to identify data deliverables required from the contractor. Each CDRL item represents a specific data product the contractor must produce and deliver during contract performance.
The CDRL system was established to standardize data requirements across defense contracts. Rather than each contract inventing its own deliverable formats, CDRLs reference standardized Data Item Descriptions (DIDs) that define the content and structure of common deliverables. This creates consistency across contracts and reduces ambiguity about what the government expects.
CDRLs are listed in Section J (List of Attachments) of the contract and are cross-referenced in the Statement of Work. Each CDRL is identified by a sequence number (A001, A002, etc.) and contains the following key information:
The DD Form 1423 has a structured layout with numbered blocks. Understanding each block is essential for accurately pricing and planning your deliverables:
The unique identifier for this CDRL item (e.g., A001, A002). Used to reference the CDRL throughout the contract, SOW, and correspondence.
The name of the data item (e.g., “Systems Engineering Plan”, “Monthly Status Report”, “Test Procedures”).
The Data Item Description number that defines the content and format. DID numbers follow the pattern DI-XXXX-NNNNN (e.g., DI-MGMT-81466 for a status report).
How often the deliverable must be submitted: one-time (ONE/R), monthly (MO), quarterly (QT), annually (AN), as required (AR), or event-driven (EVAR).
When the first deliverable is due, often expressed as days after contract award (e.g., “30 DAC” means 30 days after contract award).
Contract-specific tailoring of the DID requirements. This is where the government modifies, adds, or deletes standard DID content for this specific contract. Always read Block 16 carefully — it overrides the DID.
Effective CDRL management requires a systematic approach from proposal through contract closeout. Here are the key practices:
Late or non-compliant CDRLs are a leading cause of negative CPARS ratings. The government tracks CDRL compliance rigorously, and repeated failures can lead to payment withholding under the “Withholding of Unearned Fees” clause or, in severe cases, cure notices. Invest in a robust CDRL management process — it pays for itself in contract performance ratings.
A CDRL (Contract Data Requirements List) is a formal listing of all data deliverables required under a government contract. Each CDRL item is documented on a DD Form 1423 and references a Data Item Description (DID) that defines the content, format, and preparation instructions for the deliverable. CDRLs are most common in Department of Defense (DoD) contracts but are also used by other agencies for complex acquisitions.
A CDRL (DD Form 1423) is the contract-specific form that identifies a required data deliverable, including its schedule, distribution, and any tailoring of the standard format. A DID (Data Item Description) is the standardized template that defines the content and format of a specific type of deliverable. The CDRL references the DID and may tailor it for the specific contract. For example, a DID might define the generic format for a test plan, while the CDRL specifies when that test plan is due, who receives it, and any modifications to the standard format.
The number varies widely by contract type and complexity. A simple services contract might have 5 to 10 CDRLs covering status reports, invoices, and a transition plan. A complex weapons system development contract can have 50 to 100 or more CDRLs covering design documents, test plans, test reports, training materials, technical manuals, logistics data, and safety analyses. The key is that every CDRL must be priced in your proposal — overlooking CDRLs is a common and costly mistake.
Yes, CDRLs can be added, removed, or modified through formal contract modifications. Changes to CDRLs often affect contract cost and schedule, so they typically require bilateral agreement. The Contracting Officer must approve all CDRL changes. Common modifications include adjusting delivery schedules, changing distribution lists, tailoring DID requirements, or adding new CDRLs for emerging requirements. Contractors should track CDRL modifications carefully as they affect workload and pricing.
Search active DoD solicitations, review CDRLs and SOWs, and build your pipeline. Stay on top of deliverable requirements from bid to award with Bureauify.