danielpradilla PRINCE2 Closure Pack
For detailed management product definitions, read ../../references/prince2-management-products.md when the user needs a complete PRINCE2 document set or asks what each artifact is for.
Use this workflow when the project is ready for planned or premature closure.
Inputs To Ask For
- Project initiation documentation
- Latest business case
- Product acceptance evidence
- Product status
- Open risks, issues, and changes
- Benefits evidence and measurement plan
- Lessons log
- Handover requirements
Output Structure
1. Closure Recommendation
- Close as planned, close with exceptions, or close prematurely
- Rationale
- Conditions before closure
2. Product Acceptance
- Final product
- Acceptance criteria
- Acceptance evidence
- Approver
- Outstanding defects or limitations
3. End Project Report
- Original objectives
- Final result
- Performance against targets and tolerances
- Benefits achieved or expected
- Unresolved risks and issues
- Follow-on action recommendations
4. Lessons Report
- What worked
- What did not work
- Root causes
- Recommendations for future projects
- Evidence or examples
5. Benefits Review Plan
- Benefits to measure after closure
- Owner
- Metric
- Baseline
- Review date
- Data source
6. Handover And Closeout
- Operational owner
- Support model
- Documentation location
- Contracts or suppliers
- Archived records
- Project team release
Quality Bar
- Closure must confirm acceptance or clearly state why acceptance is incomplete.
- Benefits do not need to be fully realized at closure, but ownership must be clear.
- Follow-on actions should have owners.
- Premature closure still needs evidence, lessons, and handover decisions.