Project close-out
1 of the 16 capital-project phases
Dissolving the project into operations and capturing the lessons.
SPEQ synthesis · a practitioner on-ramp to the gated capital-project lifecycle, not any single body’s method. Each phase below carries its full 14-question grammar.
Project close-out & lessons learned
The project dissolves into operations: quality actions closed, documentation archived and retrievable, benefits realised against the business case, and the lessons captured to feed the next project’s concept phase.
- Purpose
Formally close the project, confirm benefits, archive the record, and capture lessons for the next project.
- Work performed
- Close all remaining project quality actions and punch-list items
- Archive project documentation so it is indexed and retrievable for the asset’s life
- Assess benefits realised against the business case and record variances
- Capture lessons learned and transfer residual risks and actions to operations
- Who is involved
- Project director and project management office
- Quality confirming action closure and records archival
- Operations receiving the asset, its risks, and its records
- What quality owns
- Confirmation that all project quality actions and punch items are closed
- That the documentation is archived, retrievable, and complete for its retention period
- What engineering owns
- Handover of as-built and engineering records into the site systems
- Closure of engineering punch items and open technical actions
- What operations owns
- Acceptance of the asset, its residual risks, and its open actions
- Ownership of anything carried forward from the project into routine running
- Management decisions
- Formal project close-out and benefits sign-off
- Disposition of any unrealised benefits or carried-forward risks
- Deliverables
- Project close-out report
- Documentation archival and retrievability record
- Lessons-learned register and benefits-realisation summary
- Evidence to retain
- The signed close-out report and benefits assessment
- The archival index proving records remain retrievable
- Common risks
- A project never formally closed, leaving open quality actions adrift
- Records archived but not retrievable when an inspection later needs them
- Lessons never captured, so the next project repeats the cost
- Gate criteria to advance
- All project quality actions and punch items closed
- Documentation archived, indexed, and retrievable for the asset’s life
- Benefits realised against the business case and lessons captured
- Expensive if deferred
- Records archival and retrievability — an unretrievable record is a future inspection gap
- Lessons capture — an un-mined lesson is a cost the next project pays to relearn
- Business effect
Closes the loop: a project never formally closed leaves open quality actions and an un-mined lesson that the next project pays to relearn.
- Greenfield vs brownfield
A greenfield close-out hands over a whole new asset and organisation; a brownfield close-out folds the change back into the existing operation and updates its validated-state and licence records accordingly.