Module 11 · Lesson 13 of 13
Project closure checklist
Learning objectives
- Verify results, controls and governance before closure.
- Confirm finance-validated benefits and residual-risk owners.
- Capture lessons and recognition, not only numbers.
Results
- Sustained Y and CTQ across the validation window
- Guardrails held (output, safety, cost)
- Stability and capability as relevant
- Target disposition documented (met, partially met, not met with reason)
- Benefits validated by owner and finance
Process and control
- Implementation complete
- Control plan and reaction tested
- SOP and standard work current
- MSA and training refreshed
- Residual risks and CAPA owners assigned
Governance and learning
- Process owner accepts handover
- Evidence and data archived securely
- Sponsor approval and audit dates set
- Replication opportunities listed
- Actual versus plan and lessons shared
- Recognition documented
Copy-friendly closure checklist
- All rows above ticked with evidence link
- Open actions have owners and dates
- No temporary controls left in place
- Self-study disclaimer honoured — no accredited-certification claim in closure documents
Garment-factory example
A DHU project closes with three months of sustained performance, finance-signed savings, an assigned CAPA for one residual supplier risk, an audit date in the plant calendar and a replication proposal for a sister line.
Method
- Close on evidence, not calendar.
- Assign every open item an owner and date.
- Publish lessons so the next team benefits.
Common mistakes
- Closing by date despite unmet target and no reason.
- Leaving temporary controls as permanent.
- Claiming accredited certification at closure.
Knowledge check
Pick one answer per question. Explanations appear after you submit.
1. A project should be closed only when:
2. Closure documents must:
Author: Sanjeewa Dehiwalage · Last reviewed: 2026-07-21