7.4 Closing a Project (CP) Process
Key Takeaways
- Closing a Project (CP) is executed by the Project Manager during the final management stage of the project.
- CP applies to both planned project completion and premature project termination directed by the Project Board.
- Key activities include confirming product acceptance, securing operational/maintenance handover, and preparing the End Project Report.
- The Project Manager drafts the post-project Benefits Management Approach (Benefits Review Plan) and records final lessons learned.
- CP does NOT authorize project closure—it prepares the recommendation; the Project Board formally authorizes closure in Directing a Project (DP).
Last updated: July 2026
7.4 Closing a Project (CP) Process
Exam Focus: Closing a Project (CP) provides a controlled end to the project lifecycle. Candidates must understand that CP is executed during the final management stage, handles both planned and premature closures, ensures proper product handover to operations, and prepares the closure recommendation for the Project Board. Remember: CP prepares for closure, but Directing a Project (DP) authorizes it!
Purpose and Scope of Closing a Project
The purpose of Closing a Project (CP) is to provide a fixed point at which acceptance of the project product is confirmed, and to recognize that objectives set out in the original Project Initiation Documentation (PID) have been achieved (or that the project has no further contribution to make).
CP prevents projects from drifting endlessly into ongoing operations. It ensures that project resources are released, operational teams accept maintenance responsibility, and final performance is formally evaluated.
+-----------------------------------------------------------------------------+
| FINAL MANAGEMENT STAGE (Project Manager) |
| |
| +-----------------------------------------------------------------------+ |
| | CLOSING A PROJECT (CP) PROCESS | |
| | | |
| | +------------------+ +------------------+ +-------------------+ | |
| | | PREPARE PLANNED/ |-->| HAND OVER |-->| EVALUATE PROJECT | | |
| | | PREMATURE CLOSURE| | PRODUCTS | | (End Project Rep) | | |
| | +------------------+ +------------------+ +-------------------+ | |
| | | | |
| | v | |
| | +-------------------+ | |
| | | RECOMMEND CLOSURE | | |
| | +-------------------+ | |
| +-----------------------------------------------------------------------+ |
+-----------------------------------------------------------------------------+
|
v Submits End Project Report & Closure Recommendation
+-----------------------------------------------------------------------------+
| DIRECTING A PROJECT (Project Board) |
| Decision: Authorize Project Closure & Release Resources |
+-----------------------------------------------------------------------------+
Key Objectives of the CP Process
The CP process ensures that:
- Product Acceptance: User and customer sign-offs are secured for all delivered project products.
- Operational Handover: Products are successfully handed over to operational, support, and maintenance units.
- Post-Project Benefits Framework: The Benefits Management Approach is updated to schedule post-project reviews for benefits that can only be measured after closure.
- Performance Evaluation: Project performance is evaluated against initial baselines in an End Project Report.
- Organizational Learning: Lessons learned are captured and documented in the Lessons Report for enterprise-wide improvement.
- Controlled Shutdown: Outstanding risks, open issues, and residual assets are transferred to line management before resources are disbanded.
Planned Closure vs. Premature Closure
PRINCE2 projects close under two distinct conditions:
+-----------------------------------------------------------------------------+
| PROJECT CLOSURE MODES |
| |
| +-----------------------------------+ +-------------------------------+ |
| | PLANNED CLOSURE | | PREMATURE CLOSURE | |
| | All products delivered & accepted.| | Board orders early shutdown | |
| | Objectives met per PID baseline. | | (viability lost, strategy shift).|
| | Full handover & formal evaluation.| | Save work, secure assets, log | |
| | | | reasons, handover partial work| |
| +-----------------------------------+ +-------------------------------+ |
+-----------------------------------------------------------------------------+
| Characteristic | Planned Closure | Premature Closure |
|---|---|---|
| Primary Trigger | Final scheduled management stage completes successfully | Project Board directs early termination (e.g., Business Case no longer viable) |
| Product Status | All planned products completed, tested, and accepted | Products partially complete or abandoned; completed elements secured |
| Handover Focus | Full operational transfer of all final specialist products | Transfer of useful partial deliverables, assets, and working documentation |
| Benefits Focus | Confirm achieved benefits and schedule remaining post-project reviews | Document realized benefits to date and assess if any partial benefits can still be recovered |
| Key Action | Execute standard CP activities to wrap up final stage | Secure project environment, cancel outstanding Work Packages, log causes of failure |
Core Activities in Closing a Project
CP comprises five primary activities performed by the Project Manager:
1. Prepare Planned Closure (or Prepare Premature Closure)
- Planned: Verify that all products specified in the Project Plan are completed, approved, and accepted.
- Premature: Reclaim active Work Packages from Team Managers, secure project assets, and document the specific circumstances surrounding early shutdown.
2. Handover Products
- Transfer ownership of delivered products to the operations and maintenance organization.
- Secure formal Acceptance Records signed by the Senior User / Customer.
- Establish operational support arrangements, service level agreements (SLAs), and maintenance agreements.
3. Evaluate the Project
- Compare actual project performance (time, cost, quality, scope, benefits, risk) against original PID baselines.
- Compile the End Project Report, documenting overall achievement, variance analysis, and final financial figures.
- Write the Lessons Report (or update the Lessons Register) detailing successful practices and areas for future organizational improvement.
4. Update Benefits Management Approach
- Record benefits already realized during the project lifecycle.
- Update the Benefits Management Approach to define post-project benefit measurement schedules, responsibilities, and metrics for un-realized benefits.
5. Recommend Project Closure
- Issue a formal notification to the Project Board recommending that the project be closed.
- Prepare draft closure notifications for corporate management, suppliers, and project team members.
Key Management Products in CP
| Management Product | Author | Primary Purpose |
|---|---|---|
| End Project Report | Project Manager | Comprehensive evaluation of project performance, final budget/schedule outcomes, product achievements, and overall success against PID baselines. |
| Lessons Report | Project Manager | Documented insights, management experiences, and technical recommendations to improve future project performance. |
| Benefits Management Approach (Updated) | Project Manager | Defines how and when post-project benefits will be measured and reviewed by corporate/programme management. |
| Acceptance Records | Customer / Senior User | Formal sign-off certificates confirming that delivered products meet specified acceptance criteria. |
Roles and Responsibilities in CP
- Project Board (DP Process): Receives the PM's closure recommendation, reviews the End Project Report and Lessons Report, approves product handover, authorizes project closure, and releases project resources.
- Project Manager (CP Process): Conducts all CP activities—verifies acceptance, handovers products, drafts End Project & Lessons Reports, updates Benefits Management Approach, and recommends closure.
- Senior User: Verifies product acceptance criteria and confirms operational readiness to receive project products.
- Senior Supplier: Ensures technical documentation, warranties, and maintenance agreements are transferred to support teams.
- Executive: Recommends post-project benefit review ownership to corporate management.
High-Yield Exam Traps & Tricks
- Who authorizes project closure? The Project Board (in Directing a Project). The PM recommends closure in CP, but cannot authorize it.
- Is CP a separate stage? No! CP is a process, executed during the final management stage. It is not an independent management stage.
- When are post-project benefits measured? Post-project benefit reviews take place after project closure, managed under the updated Benefits Management Approach by corporate/programme management or operational managers.
- Does premature closure skip CP? No! Premature closure uses the CP process to ensure a clean, controlled shutdown, asset security, and lessons capture.
Test Your Knowledge
Who is responsible for formally authorizing project closure in PRINCE2?
A
B
C
D
Test Your Knowledge
What happens to the Benefits Management Approach during the Closing a Project process?
A
B
C
D
Test Your Knowledge
If a project is terminated early by the Project Board due to loss of business viability, which process is used to execute the early shutdown?
A
B
C
D