Define the deliverable set by milestone
List what the client or internal reviewer expects at concept, design, bid, and handoff stages. Name the required format, level of detail, owner, reviewer, due date, and controlling template.
Remove deliverables that have no stated use rather than copying a larger list from another project. Align the register with the estimate handoff checklist so the files needed downstream are planned before release day.
Track readiness with evidence
Use statuses such as not started, working, ready for review, revision required, approved, and issued. Link each status to a file revision or approval. A percentage complete is less useful when the missing item is the one document needed for a decision.
AACE guidance on the basis of estimate identifies core estimate-basis information. The project register should state the exact deliverables required for its contract and governance.
| Deliverable | Control |
|---|---|
| Estimate file | Revision and approval |
| Basis narrative | Scope and assumptions |
| Support | Takeoff, quotes, risk, reconciliation |
| Issue record | Recipients and replacement status |
Issue one controlled package
Before issue, confirm that filenames, dates, estimate revision, document references, and totals agree across the package. Record approved exceptions.
Place superseded drafts outside the issue folder and preserve them according to project retention rules. Use the revision release control to record the issued package, recipients, authorization, and later replacement.
