Deliverable (DEL)
Deliverable (DEL): a specific tangible output a federal contractor must produce under a contract, listed in the CDRL and tracked through inspection and acceptance.
What Is a Deliverable?
A Deliverable is a discrete output the contractor must produce under the contract. Each deliverable is specified by the contract through the SOW/PWS and the CDRL.
The CDRL lists each deliverable with its number, title, due date, format, distribution, and any associated Data Item Description (DID, a standard format specification for the deliverable). Common deliverable types include Program Management Plan, Risk Management Plan, Quality Assurance Plan, Monthly Progress Report, Test Plan, Test Report, Software Build, Installation Manual, Training Materials, and Final Project Report.
Each deliverable has an acceptance process: the contractor submits the deliverable, the contracting officer's technical representative reviews it against acceptance criteria, and the deliverable is either accepted, conditionally accepted with comments, or rejected. Acceptance triggers payment, contract progress, and milestone completion.
Key Characteristics
Deliverables have several defining attributes. They are specified: each deliverable is defined in the contract with description, format, and due date.
They are scheduled: each has a target submission date. They are reviewable: each has an acceptance criterion that the government applies in reviewing the submission.
They are versioned: most deliverables go through draft, review, and final versions, with formal review cycles. They are tracked: the contractor maintains a deliverable register, and the contracting officer monitors deliverable status.
They are tied to payment: in milestone-based contracts, deliverable acceptance often triggers progress payments. Each characteristic shapes how the contractor plans, produces, and manages deliverables.
How It Works in Government Contracting
Deliverables operate at a defined cycle throughout contract performance. First, during contract formation, the contracting officer and contractor agree on the deliverable list in the CDRL, with each deliverable's description, format, due date, and acceptance criteria documented.
Second, during contract execution, the contractor produces each deliverable on schedule, applying its quality assurance process and the format specified in the applicable Data Item Description (or contract-specified format). Third, the contractor submits the deliverable through the agency's specified submission method (email, secure portal, hard copy, etc.) by the due date.
Fourth, the contracting officer's technical representative reviews the deliverable against the acceptance criteria within the contract-specified review period (commonly 15 to 30 days). Fifth, the COR either accepts the deliverable, returns it with comments for revision, or rejects it.
Sixth, accepted deliverables are documented in the deliverable register and may trigger milestone completion, invoice release, or other contractual actions.
Real-World Example
A federal contractor wins a $12 million systems engineering contract with 28 deliverables listed in the CDRL: a Program Management Plan due at 30 days, Monthly Progress Reports due on the 15th of each month, a Risk Management Plan due at 60 days, a System Design Document at 120 days, a Test Plan at 180 days, and so forth. The contractor maintains a deliverable register in its project management tool, with each deliverable's status, due date, and reviewer.
The Program Management Plan is delivered at day 28, reviewed and accepted by the COR within 14 days. Monthly Progress Reports are delivered on schedule throughout the contract period.
The System Design Document is delivered at day 118, reviewed by the COR with comments, revised by the contractor, and accepted at day 142. Each accepted deliverable triggers a milestone payment per the contract's progress payment schedule. Late or rejected deliverables would impact cash flow, schedule, and CPARS rating.
Regulatory Framework
Deliverables are governed by the contract's Statement of Work or Performance Work Statement, the Contract Data Requirements List (CDRL), and the contract's general terms and conditions. For DoD contracts, the CDRL is DD Form 1423, and Data Item Descriptions provide standardized format specifications.
For civilian contracts, deliverables are typically specified in the SOW/PWS without a standard CDRL form, though many agencies have adopted similar structured formats. Acceptance criteria are governed by FAR 52.246 series (Inspection clauses), particularly FAR 52.246-2 (Inspection of Supplies-Fixed-Price), FAR 52.246-4 (Inspection of Services-Fixed-Price), and FAR 52.246-7 (Inspection of Research and Development-Fixed-Price). Deliverable failures can trigger cure notices, default terminations, CDA claims, and adverse CPARS evaluations.
Why It Matters for Contractors
Deliverables are the primary visible artifact of federal contract performance. The contracting officer's technical representative and the contracting officer largely judge contract execution by deliverable quality, timeliness, and responsiveness to comments.
Strong deliverable management produces positive CPARS ratings, smooth contract closeout, and a stronger past performance record for future proposals. Weak deliverable management produces negative CPARS, contract administration disputes, cure notices, and in extreme cases default termination.
Deliverables interact with milestones (deliverables often trigger milestone completion), with invoices (deliverable acceptance triggers payment in some contract types), with change orders (change orders can add or modify deliverables), and with past performance (deliverable quality is a major CPARS factor). Contractors that handle deliverables well treat them as the visible product of their contract performance, not as bureaucratic paperwork.
Common Misconceptions
A deliverable is anything the contractor produces during the contract.
No. A deliverable is specifically what the contract requires the contractor to submit to the government, listed in the CDRL or SOW/PWS. Internal work products, draft documents, or unrequested artifacts are not deliverables in the contractual sense.
Late deliverables can be made up later with no consequence.
Sometimes, but often not. Late deliverables can trigger cure notices, default termination, negative CPARS, and in milestone-based contracts can delay payment. The contracting officer's discretion varies; the contractor should not assume tolerance for late deliverables.
Once a deliverable is accepted, the contractor has no further obligations on it.
Not always. Some deliverables have warranty periods, error-correction obligations, or maintenance requirements that extend past acceptance. The contract terms specify post-acceptance obligations; the contractor must review and comply.
Frequently Asked Questions
What is the difference between a CDRL and a Data Item Description?
The CDRL is the list of deliverables for a specific contract (DD Form 1423 for DoD). A Data Item Description (DID) is a standard format specification for a particular type of deliverable (e.g., DI-MGMT-81650 for an Integrated Master Schedule). The CDRL line item often references a specific DID for format requirements.
What happens if a deliverable is rejected?
The contractor revises the deliverable based on the rejection comments and resubmits. The contract typically specifies the rework cycle: how many revision cycles are allowed, the review period for each, and the consequence of persistent rejection (cure notice, default, etc.).
Can a deliverable's due date be modified?
Yes, through a contract modification under FAR Part 43. The contracting officer and contractor agree on the new due date, which is documented in a bilateral modification. Unilateral changes by either party are not effective without modification.
Does deliverable acceptance trigger invoice payment?
Often yes, in milestone-based or progress-payment contracts. The contract specifies which deliverables trigger payment and the amount associated with each. In cost-reimbursement contracts, invoicing is independent of deliverable acceptance and follows the contract's invoicing schedule.
Related Government Contracting Topics
Contract Data Requirements List (CDRL): Formal list of contractual deliverables, with format, due date, and distribution for each.
Milestone: Contractual event whose completion is often tied to deliverable acceptance.
Invoice: Formal request for payment; in some contract types, triggered by deliverable acceptance.
Cure Notice: Formal notice issued when a contractor fails to meet deliverable obligations.
Past Performance: Documented contractor track record; deliverable quality is a major CPARS factor.
How LotusPetal AI Helps
LotusPetal AI's capture and proposal automation platform helps federal contractors manage deliverable scheduling, CDRL compliance, and contract execution discipline with the same discipline as the largest primes. The platform combines compliance automation, AI-assisted proposal drafting, and structured capture workflows so teams capture the right opportunities, write compliant proposals, and protect their win rate.