Deliverables and acceptance review
Track contractor submissions and government decisions separately; review acceptance test results and request missing evidence (CT08, CT09).
COR · Contracting Officer · Technical reviewer
/pdcc/acquisitions/contracts/CT-DEMO-007/deliverablesThe deliverables register keeps submitted, reviewed and accepted as separate states. Contractual due dates require source evidence.
Deliverable row
- Deliverable
- e.g. D03 Acceptance tests.
- Submission
- Evidence version, e.g.
EV-PILOT-TESTv1. - Due
- Sourced contractual date (or an internal target, labeled).
- Decision
- Under review / Accepted / Returned.
- Reviewer
- e.g. Morgan Reed.
Review acceptance test results (CT09)
- 1
Open the deliverable
Deliverables › D03 › *Review acceptance tests*. If you were mid-review, *Resume contract review* restores your saved finding.
- 2
Assess evidence
Compare the submission with the approved test protocol.
- 3
Record review finding
e.g. *Required test results missing*. Saving a finding does not accept the deliverable.
- 4
Request missing evidence
Creates a tracked request to the contractor-facing owner.
- 5
Decide
Only the authorized acceptance official can record acceptance of the exact submission.
Deliverable monitoring
A COR can watch deliverables (/monitoring). No-change checks do not repeatedly notify or create duplicate tasks, and monitoring uses the approved assignment scope. Turning a watch into an automation needs its own approval.
Related guides
Surveillance, clauses and responsibilities
Map contract obligations to the applicable clause, QASP, observations and responsible owners (CT10).
Contract calendar, waiting and overdue work
Contract-scoped calendar lanes, waiting and overdue items, and overdue-deliverable follow-ups (G05 calendar and investigations).
Contract team assignment
How a contract is assigned to its contract specialist, contracting officer and COR — proposals, designation evidence, confirmation and what each role can then do (CT05).