A CDRL schedule should show more than a list of contract due dates. The integrated master schedule (IMS) should include the work required to produce each significant deliverable, a logic-driven submission milestone and any review or approval cycle that affects downstream work.
The contract remains the source of the requirement. The scheduler’s job is to translate that requirement into an executable network without replacing the contractual date with an unsupported scheduling convention. When the forecast moves later than the required date, the IMS should expose the variance rather than hide it with a hard constraint.
The Contract Defines the Deliverable Requirement
A Contract Data Requirements List (CDRL) identifies data that the contractor must deliver under the contract. If you need a refresher on the document itself, see what a Contract Data Requirements List contains.
Defense Federal Acquisition Regulation Supplement 215.470 directs contracting officers to include DD Form 1423 when data must be delivered under a DoD contract. In addition, Federal Acquisition Regulation Subpart 11.4 explains that delivery or performance time is an essential contract element and may be expressed as a calendar date or a period measured from another event.
However, neither statement creates a universal rule for how every CDRL must appear in every IMS. The controlling requirements may vary based on the contract, tailored Data Item Description (DID), statement of work, agency guidance and program-specific IMS instructions.
Therefore, review the complete contractual package before building the schedule. At a minimum, examine:
- The CDRL item number and data item title.
- The governing DID and any contract tailoring.
- DD Form 1423 Blocks 10 through 13 for frequency, as-of date and submission timing.
- Block 8 for an approval requirement.
- Block 16 for review periods, event-based timing and special instructions.
- The Statement of Work (SOW) or Performance Work Statement (PWS) reference.
- Applicable Contract Line Item Number (CLIN), Work Breakdown Structure (WBS) and acceptance provisions.
- Contract modifications that changed the requirement or delivery date.
The DoD IPMDAR Implementation Guide illustrates how DD Form 1423 timing and approval instructions can be tailored through Block 16. Those instructions matter because a delivery labeled “monthly” may still have a specific number of working days after the accounting period.
How a CDRL Schedule Entry Should Be Structured
For a significant deliverable, the IMS should normally show a short chain of activities rather than one isolated milestone. The chain should explain how the team plans to reach the contractual submission.
1. Plan the work that produces the data item
Start with the technical or management work needed to create the deliverable. For example, a test report may depend on test completion, data reduction, anomaly resolution and engineering analysis. A design document may depend on requirements maturity, trade studies and internal reviews.
These activities should reside under the WBS element and work package responsible for the effort. That approach preserves the relationship among scope, schedule and budget. See how the WBS connects to the Statement of Work for the broader traceability model.
2. Include internal review and release steps
A credible schedule accounts for the contractor’s own review process. Depending on the deliverable, that process may include peer review, Integrated Product Team review, configuration control, security review or authorized release.
Do not bury a two-week approval cycle inside a single writing task if the review controls the delivery date. Separate activities improve status visibility and identify the organization that owns the remaining work.
3. Use a zero-duration submission milestone
The delivery event itself should usually appear as a zero-duration milestone with a clear name, such as:
- Submit CDRL A005 Draft Systems Engineering Plan
- Deliver CDRL A012 Monthly Schedule Dataset
- Submit CDRL B003 Final Qualification Test Report
Include the CDRL identifier in the name or a dedicated field. Avoid vague milestone names such as “Report Due” or “Document Complete.” The task name should remain understandable when filtered out of its summary-task context.
The milestone should have valid predecessor logic from the activities that produce and authorize the submission. If later work depends on the deliverable, the milestone should also have appropriate successors.
Separate Submission, Government Review and Final Acceptance
Submission does not always equal approval or acceptance. The schedule should preserve those distinctions when the contract establishes them or when they affect execution.
For example, a tailored CDRL may require an advance draft, Government review, comment resolution and final delivery. In that case, model separate events:
- Prepare and internally review the draft.
- Submit the draft CDRL.
- Perform Government review.
- Receive consolidated comments.
- Resolve and incorporate comments.
- Submit the final CDRL.
- Record approval or acceptance if it controls successor work.
Represent a defined Government review period as a task with duration, not as a zero-duration milestone. Identify it as an external or Government-owned activity according to the program’s coding conventions. Then link it to the contractor’s comment-resolution work.
Do not invent a Government review duration. Use the period in the contract, CDRL remarks or formal program direction. If the contract does not state a duration, document the planning assumption and seek clarification through the appropriate contractual channel.
Approval codes also require careful interpretation. An approval requirement on DD Form 1423 may call for Government action before final distribution. It does not automatically mean that every downstream engineering activity must wait for approval. The technical plan and contract determine which work depends on that event.
Preserve Both the Contractual Date and the Forecast Date
A strong CDRL schedule preserves two different pieces of information:
- Required date: The date or event-based timing established by the contract.
- Forecast date: The date calculated by current durations, status and network logic.
These dates may match at baseline. However, they serve different purposes. The contractual date states the commitment, while the forecast shows when the current plan predicts delivery.
Avoid applying a Must Finish On constraint merely to keep the milestone displayed on the required date. That practice can override logic, distort float and conceal a late forecast. Instead, let the delivery milestone remain logic-driven and store the required date in a deadline, target-date or designated contractual-date field.
For Microsoft Project schedules, Microsoft explains that a deadline can identify a target date without normally controlling task scheduling. In contrast, inflexible constraints anchor tasks to specified dates and can override dependencies. The related guide on using deadlines without hard constraints provides a practical implementation method.
A hard constraint may still be appropriate when an event truly cannot occur outside a fixed window. Examples may include a Government-furnished facility date or a contractually fixed test range. Even then, document the basis and verify that the constraint reflects the actual restriction rather than a desired finish date.
Model Recurring CDRL Deliveries Deliberately
Recurring reports need enough visibility to support execution without turning the IMS into an administrative calendar. The contract and tailored IMS requirement determine the necessary level of detail.
Individually model recurring submissions when they:
- Require measurable preparation effort.
- Drive payment, acceptance or fee determination.
- Support major reviews or customer decisions.
- Create predecessor or successor relationships with technical work.
- Have changing content or resource demand.
- Need monthly performance visibility under the reporting requirement.
For example, each Integrated Program Management Data and Analysis Report (IPMDAR) submission may need its own milestone because the reporting cycle repeats monthly and each occurrence has a defined data date and delivery timing. See what an IPMDAR schedule dataset contains for more detail.
Low-effort recurring administrative submissions may be managed in a supporting schedule if the contract and IMS instructions allow that approach. However, do not omit them merely because they are repetitive. First confirm the required schedule content and customer expectations.
Avoid using a single milestone named “Monthly Reports” across several years. That milestone cannot show which submission is late, complete or driving another event. Instead, create uniquely named occurrences or use a controlled near-term planning horizon with documented rolling-wave procedures.
Build CDRL Traceability Into the IMS
A reviewer should be able to filter the IMS and reconcile scheduled deliverables to the contract. Useful schedule fields include:
- CDRL item number.
- Data item title.
- DID number and revision.
- Draft, interim or final designation.
- Required delivery date.
- Submission frequency.
- SOW or PWS reference.
- WBS and control account.
- Responsible organization or control account manager.
- CLIN or exhibit reference when useful.
- Government review duration.
- Approval or acceptance indicator.
The task name does not need to contain every code. Use structured fields so the program-controls team can produce a CDRL schedule report without parsing text manually. This also supports reconciliation during baseline reviews, customer deliveries and contract modifications.
As a program-specific example, the NAVAIR IMS Guide includes standard IMS CDRL language and emphasizes traceable, networked schedule content. Treat such agency guidance as applicable only when incorporated into the solicitation, contract or program direction.
Fictional Example: A005 Engineering Plan
Assume the fictional Falcon Ridge Sensor Upgrade contract includes CDRL A005, an engineering management plan. The contract requires a draft 45 calendar days after contract award. It also provides a 10-working-day Government review period, followed by final delivery within five working days after receipt of comments.
The scheduler should not create one constrained milestone on Day 45. A more useful network would include:
- Develop engineering plan content — 15 working days.
- Conduct functional lead review — 5 working days.
- Resolve internal comments — 3 working days.
- Perform configuration and release review — 2 working days.
- Submit CDRL A005 draft — milestone with the contractual deadline recorded.
- Government review of CDRL A005 draft — 10 working days.
- Receive consolidated Government comments — milestone.
- Incorporate Government comments — 5 working days.
- Submit CDRL A005 final — milestone.
If the Preliminary Design Review depends on an approved plan, the applicable approval event should drive the review-preparation path. For an explanation of those technical gates, see SRR, PDR, CDR, TRR and PRR explained.
During status, the draft submission milestone may forecast three days late because the internal review took longer than planned. The IMS should show that late forecast and the resulting impact. Moving the milestone back to Day 45 with a hard constraint would hide the execution problem.
Earned Value and Proposal Considerations
The work that produces a CDRL should align with the responsible work package when an Earned Value Management System (EVMS) applies. However, a zero-duration submission milestone does not carry effort by itself. The supporting activities contain the planned work and resources.
Also, do not assume that submitting or obtaining acceptance of a CDRL automatically earns value. The approved control account plan and earned value technique determine when budgeted value is earned. The IMS must remain consistent with that plan, as explained in how the IMS supports earned value management.
During a proposal, load the CDRL requirements before finalizing the schedule basis of estimate. Drafting, review, configuration management and recurring reporting consume real resources. Missing that effort can produce an understated price and an unexecutable post-award baseline.
Common CDRL Schedule Failure Modes
- Using one milestone with no predecessors: The schedule shows the due date but not the work needed to meet it.
- Constraining every delivery to its contract date: The IMS cannot provide an honest forecast or meaningful float.
- Treating submission as acceptance: Review and comment-resolution cycles disappear from the network.
- Omitting recurring instances: The team cannot status individual monthly or quarterly deliveries.
- Using vague names: Reviewers cannot reconcile milestones to DD Form 1423.
- Ignoring contract modifications: The schedule retains obsolete dates or deliverables.
- Loading all effort on the milestone: A zero-duration event cannot represent document development and review work.
- Inventing review durations: An unsupported assumption appears to be a contractual requirement.
- Leaving milestones open-ended: A deliverable without successors may fail to show its effect on reviews, acceptance or downstream execution.
CDRL Schedule Review Checklist
- Reconcile every applicable scheduled delivery to the current contract.
- Confirm the CDRL identifier, title, frequency and required timing.
- Verify that significant deliverables have preparation and internal review activities.
- Use a logic-driven submission milestone.
- Store the contractual date separately from the calculated forecast when possible.
- Model Government review and contractor comment resolution when they affect the plan.
- Distinguish draft submission, final submission, approval and acceptance.
- Check predecessor and successor logic.
- Confirm WBS, control account and SOW traceability.
- Review recurring submissions individually at the required level of detail.
- Verify that contract modifications are reflected through controlled schedule changes.
- Confirm consistency among the IMS, work package plan and earned value technique.
Frequently Asked Questions
Should every CDRL be a milestone in the IMS?
Follow the contract and tailored IMS requirement. Significant CDRLs should normally be visible, especially when they require material effort, support customer decisions or drive downstream work. Some low-level administrative deliveries may reside in a supporting schedule if the contractual framework permits it.
Should the CDRL due date use a hard constraint?
Usually not. A hard constraint can hide the current forecast and distort float. Preserve the contractual date in a designated field or deadline while allowing predecessor logic to calculate the forecast. Use a constraint only when it represents a real scheduling restriction.
Is Government approval the same as CDRL delivery?
No. Delivery records the contractor’s submission. Approval or acceptance represents a separate Government action when required by the contract. Model both events if the distinction affects execution.
What happens when a CDRL date changes?
Confirm that an authorized contract modification or other valid contractual direction changed the requirement. Then process the schedule update through the program’s baseline change-control procedure. Do not revise the baseline commitment solely because the current forecast slipped.