Contract Deliverable Requirements List (CDRL)
This is a dual‑purpose document — for both the planning and the execution stage of a project.
Use the CDRL to identify and evaluate the correct CDID’s to use, identify missing CDID’s which need to be developed, and to assess the cost/benefit of having the document or artefact at all.
The purpose of the CDID “key codes” is to identify the high‑profile data elements and to prevent their redundant creation if possible. Ideally, critical data elements have one control point and are not calculated again and again by different sources (and usually with different values as a result.)
The CDRL is the “go‑to” document to identify what project artefacts have been deemed worthy of being produced (and hence — paid for), what their status is, who’s responsible for it, where to find them, etc.
note: replaces km4
The pm02c CDRL is used by project managers, technical leads, and contract administrators to maintain a single authoritative list of all deliverables associated with a project. It is referenced during planning, kickoff, stage‑gates, audits, and close‑out.
Usage includes:
Selecting appropriate CDIDs for each deliverable
Tracking deliverable maturity (draft, review, approved, archived)
Ensuring contractual compliance
Providing visibility to stakeholders
Preventing uncontrolled or duplicate artefact creation
Updated at every major project milestone, or whenever a deliverable is added, removed, or changes status. Minimum update frequency: monthly.
KM01b — CDID Master Structure
ddILS — Data Dictionary for Integrated Logistics Support
pm01 — Project Charter
pm03 — Project Schedule
ils91t — Technical Data Package (TDP)
ops01 — Work Instructions / SOPs
Primary: Project Manager (PM)
Secondary: Technical Lead(s), Document Control, Contract Administrator
PM ensures completeness; Document Control ensures accuracy and version integrity.
Owned by the Project Management Office (PMO). Custodian: Document Control.
Initial creation: 2–4 hours depending on project complexity.
Maintenance: 15–30 minutes per update cycle.
If not maintained:
Deliverables may be missed or duplicated
Contractual obligations may be violated
Cost overruns due to uncontrolled artefact creation
Loss of configuration control
Audit findings and compliance issues
The pm02c CDRL contains:
List of all deliverables (CDID‑coded)
Deliverable description
Responsible owner
Due date / milestone
Status (draft, review, approved, archived)
Storage location (URL, folder, repository)
Dependencies (other CDIDs, upstream data sources)
Cost category (if applicable)
pm02c‑CDRL‑\<project\>‑v\<revision\>.xlsx
pm02c‑CDRL‑\<project\>‑v\<revision\>.xml (metadata export)
pm02c‑CDRL‑\<project\>‑v\<revision\>.pdf (client‑facing)
Required metadata fields:
CDID key code
Deliverable ID
Revision
Owner
Creation date
Last updated
Approval authority
Storage location
Security classification (if applicable)
All pm02c files must be stored in the project’s controlled repository.
Versioning must follow KM01b revision rules.
No uncontrolled copies permitted.
Client‑facing versions must be exported to PDF and locked.
13.1 Create initial CDRL during project planning.
13.2 Identify required CDIDs for each deliverable.
13.3 Add missing CDIDs to the development backlog.
13.4 Update deliverable status at each milestone.
13.5 Review CDRL during audits and stage‑gates.
13.6 Archive final CDRL at project close‑out.
14.1 How to select the correct CDID for a deliverable
14.2 How to evaluate cost/benefit of producing a deliverable
14.3 How to maintain metadata integrity
14.4 How to link deliverables to upstream/downstream artefacts
A standard CDID template (KM01b) is used to define each deliverable referenced in the CDRL. The template includes sections 1.0–14.0, metadata, file handling, procedures, and tutorials.