Exam objective 3.8 asks you to explain the purpose, objectives, and key activities of the closing a project process, including project evaluation and handover. This concept solves the problem of how to properly end a project so that nothing is left undone, the customer accepts the final product, and the organisation captures valuable lessons for future work. For someone studying PRINCE2F, understanding this process is critical because it is the formal step that ensures a project is truly finished, not just abandoned, and that all stakeholders are satisfied.
Jump to a section
Your rental lease is ending, so you must formally close the tenancy. This leads to a final walkthrough with the landlord to confirm everything is in order.
First, you hand over the keys, return parking permits, and cancel utilities. The landlord inspects each room, checks for damage, and compares the flat's condition against the inventory made when you first moved in. Any missing lightbulbs or scuffed walls are noted, and you agree on a fair deduction from your deposit.
Next, you finalise the paperwork: a signed statement that the property is vacated, a forwarding address for any post, and a receipt for the returned deposit. The landlord must store your tenancy records securely for a set period in case of future disputes.
Finally, you reflect on what went well and what you'd do differently next time. Did you budget for cleaning? Would you choose a different agent? This reflection improves your next move. Just like closing a project, the move-out isn't finished until all obligations are met, the property is signed off, and lessons are recorded for your next tenancy.
Closing a Project is the last of the seven PRINCE2 processes. Its purpose is to provide a fixed point at which the project is formally dissolved. This means that after this process, the project team disbands, the project manager is released, and the ongoing responsibility for the product's benefits is handed over to the operational teams. Without a formal closure, projects can drift into 'maintenance mode' without clear ownership, leading to extra costs and confusion.
In PRINCE2, a project is a temporary organisation created to deliver one or more business products according to a business case. A 'business case' is the justification for starting the project, describing the costs, benefits, and risks. The 'project plan' is the detailed schedule and budget. The 'benefits review plan' outlines how and when the project's expected benefits—such as increased sales or reduced costs—will be measured after the project ends. These benefits are often realised months after closure.
The Closing a Project process has five key objectives:
Verify that the project has delivered everything agreed in the project initiation documentation (PID). The PID is the master document that defines the project scope, objectives, and constraints.
Confirm that the customer (the person or group who will use the final product) has accepted the product. This is often done through a formal handover and sign-off.
Ensure that the project's products are transitioned into operational use. For example, if the project built a new software system, the IT support team must be trained and ready to maintain it.
Evaluate the project's performance against its original plans and the business case. This is called the 'project evaluation' and includes assessing whether the project was on time and on budget.
Recommend any follow-up actions, such as repairs, enhancements, or corrective actions still needed after closure.
The process starts when the project manager triggers it, usually after the final product has been delivered and accepted, or earlier if the project is prematurely closed (for example, because the business case is no longer viable). The project manager prepares two key documents: the End Project Report and the Lessons Report.
The End Project Report is a summary of how the project performed. It covers what was achieved, how actual costs and time compared to the planned costs and time, any deviations from the original plan, and an evaluation of the business case. It also includes a review of the benefits that have already been realised and a plan for measuring the remaining benefits.
The Lessons Report captures what went well, what went wrong, and what should be done differently in future projects. This document is sent to the organisation's central 'lessons repository'—a database or file where all project teams can access it. This is how PRINCE2 supports organisational learning, preventing the same mistakes from being repeated.
Before closure, the project manager must also ensure that any outstanding risks or issues are resolved or transferred to the operational teams. 'Risks' are uncertain events that could affect the project, and 'issues' are problems that have already occurred. For example, if a software bug is found during closure, it must be logged as a 'follow-on action recommendation' and assigned to the team that will support the product.
The project board, which is the group of key stakeholders—including the executive (the person ultimately accountable for the project), the senior user (who represents the users' interests), and the senior supplier (who represents the team building the product)—must formally approve the closure. The executive reviews the End Project Report and gives permission to close the project. This is called 'authorising project closure'.
Finally, the project manager hands over all project files, including plans, reports, contracts, and technical documentation, to the organisation's archives. The project team is then disbanded, and any remaining project resources (like equipment or software licences) are returned or reassigned.
The Closing a Project process replaces the informal 'finish when we run out of budget' approach. It ensures that every project ends in a controlled, auditable way. For the PRINCE2 Foundation exam, you must remember that this process is not optional—it is a mandatory step that every project must go through, even if the project is cancelled early.
Prepare for closure
The project manager checks that all products are completed and accepted. They gather any outstanding issues or risks and prepare to write the key closure documents.
Prepare the End Project Report
This report summarises the project's performance against the original plan, budget, and business case. It includes an evaluation of benefits already realised and a plan for future reviews.
Prepare the Lessons Report
The project manager consolidates all lessons from the lesson log into a final report. This is sent to the organisation's lessons repository to help future projects.
Hand over the product
The project manager formally transfers the product to the operational team. This includes documentation, training, and sign-off from the customer that the product meets their needs.
Request authorisation to close
The project manager submits the End Project Report and Lessons Report to the project board. The executive reviews and formally authorises closure, releasing the team and archiving the documents.
Archive and disband
All project files are stored in the corporate archive. The project team is disbanded, and resources are reassigned. The project manager notifies stakeholders that the project is officially closed.
An IT professional working for a retail company has just finished building a new e-commerce website. The developer delivered the code, the testers confirmed it works, and the marketing team is ready to launch. But the project manager does not simply say 'job done' and walk away.
Instead, they begin the Closing a Project process. First, they schedule a handover meeting with the IT operations team—the group that will keep the website running day-to-day. During this meeting, they transfer the server login details, database passwords, and the deployment scripts used to push updates. They also provide the operations team with a runbook, which is a step-by-step guide for common tasks like restarting the server or rolling back a bad update. This handover is documented in a 'product handover document'.
Next, the project manager gathers all stakeholders from the project board for a closure review. The senior user from the marketing department confirms that the website meets all requirements: it loads in under three seconds, accepts credit card payments, and displays products correctly on mobile phones. The senior supplier, the lead developer, confirms that all technical documentation has been completed and that there are no known critical bugs. The executive wants to know whether the projected £500,000 in annual extra revenue still looks achievable. The project manager presents the benefits review plan, which schedules a benefits evaluation six months after launch.
The project manager then writes the End Project Report. This report shows that the project finished two weeks late and ten percent over budget due to an unexpected database migration. The lessons learned section details that future projects should allocate more time for data migration. This report is submitted to the executive for approval.
Once the executive signs off, the project manager creates the Lessons Report and sends it to the company's project management office (PMO), which maintains the central lessons database.
Finally, the project manager distributes all project files—including meeting minutes, design documents, and supplier contracts—to a secure shared drive. They archive the project site. The team members are then reassigned to other projects. The project manager follows up on any 'follow-on action recommendations', such as a planned security penetration test that must happen after the website goes live.
In a real scenario, the project manager also ensures that any third-party licences, such as the SSL certificate for the website, are renewed and that the billing for the cloud hosting service is transferred from the project budget to the operations budget. Without this step, the operations team might find the website suddenly offline because the payment method expired.
The PRINCE2 Foundation exam tests your ability to recall the purpose, objectives, and key activities of the Closing a Project process. You will not be asked to write an essay—instead, expect multiple-choice questions that ask you to identify the correct statement or the correct order of activities. The exam loves to test the difference between the Closing a Project process and the Managing a Stage Boundary process. Remember that Closing a Project occurs at the very end, while Managing a Stage Boundary happens between stages during the project.
Here are the specific concepts you must memorise for the exam:
The purpose of Closing a Project: to provide a fixed point for project dissolution and product handover.
The five objectives: deliver final product acceptance, confirm product transition, evaluate project performance, assess benefits realisation, and recommend follow-on actions.
The key documents: End Project Report, Lessons Report, Benefits Review Plan, Follow-on Action Recommendations.
The roles involved: project manager prepares the reports, project board authorises closure. The executive gives the final sign-off.
The triggers for this process: the final product has been approved by the customer, or the project is prematurely closed.
The relationship to the business case: the project manager must evaluate how well the project performed against the business case and assess the potential for benefits realisation.
Common traps in the exam:
They might present a question where a project is cancelled early and ask which process applies. The answer is still Closing a Project, even for a premature closure.
They might confuse the End Project Report with the End Stage Report. The End Project Report covers the whole project, while the End Stage Report covers only one stage. Both contain lessons, but the End Project Report is the final one.
They might suggest that the project board does not need to be involved in closure. This is wrong—the project board must authorise closure.
They might list 'creating the project plan' as an activity in Closing a Project. The project plan is created during the Initiating a Project process, not during closure.
They might test whether 'lesson log' is the same as 'lessons report'. The lesson log is a live document updated throughout the project, while the lessons report is the final summary produced during closure.
Key definitions to memorise:
End Project Report: a summary of project performance against the PID, including a review of the business case.
Lessons Report: a description of what went well and what went wrong, shared with the organisation.
Benefits Review Plan: a plan for when and how the project's benefits will be reviewed after closure.
Follow-on Action Recommendations: any work still needed after the project ends, such as ongoing maintenance or future enhancements.
Project closure notification: a formal communication that the project is closed and the project manager is relieved of responsibilities.
For the exam, focus on the key activities in order:
Prepare the End Project Report and Lessons Report.
Evaluate the project against the business case.
Prepare the benefits review plan.
Obtain acceptance of the final product from the customer.
Hand over the product to the operational team.
Recommend follow-on actions.
Request authorisation to close the project from the project board.
Archive all project documentation.
Closing a Project is a mandatory PRINCE2 process that must be performed even if the project is cancelled early.
The purpose of Closing a Project is to provide a fixed point for dissolving the project and handing over the product to operations.
The End Project Report summarises how the project performed against the original plans and business case.
The Lessons Report captures what went well and what went wrong, and is shared with the organisation to improve future projects.
Only the project board, led by the executive, can authorise project closure.
Product handover includes formal acceptance, transfer of ownership, and training for the operational support team.
The benefits review plan is created during closing, but actual benefits are measured after the project ends.
Follow-on action recommendations list any work still needed after closure, such as repairs or future enhancements.
These come up on the exam all the time. Here's how to tell them apart.
Closing a Project
Occurs only once at the very end of the project
Produces the End Project Report and Lessons Report
Hands over the final product to operations
Managing a Stage Boundary
Occurs at the end of each management stage (multiple times)
Produces the End Stage Report and updated project plan
Does not hand over the final product—only plans for the next stage
End Project Report
Covers the entire project from start to finish
Includes an evaluation of the full business case
Produced only once during Closing a Project
End Stage Report
Covers only one management stage
Focuses on stage performance and next stage plan
Produced multiple times, once per stage
Lessons Report
Produced at the end of the project during Closing a Project
A single summary document sent to the organisational lessons repository
Summarises all lessons from the entire project
Lesson Log
Maintained continuously throughout the project
A live working document updated by the project manager
Contains individual lessons as they are identified
Benefits Review Plan
Created during Closing a Project to plan future benefit evaluations
Specifies when and how benefits will be measured after closure
Focuses on benefit realisation timing
Business Case
Created during Initiating a Project to justify the project
Contains cost, benefit, and risk estimates before the project starts
Focuses on justifying the investment
Mistake
Closing a Project is only necessary when the project is successful and all deliverables are complete.
Correct
Closing a Project must be performed even if the project is cancelled early. The process handles both successful and premature closures.
Beginners think closure is a celebration, but PRINCE2 mandates a formal closure to capture lessons and hand over any incomplete work, not just to celebrate success.
Mistake
The project manager can authorise project closure on their own.
Correct
Only the project board, specifically the executive, can authorise project closure. The project manager prepares the reports but does not have the authority to close the project.
People assume the person leading the day-to-day work has the final say, but in PRINCE2 the executive owns the business case and must confirm the project is no longer needed.
Mistake
The Lessons Report is only produced once, at the very end of the project.
Correct
Lessons are captured throughout the project in a lesson log, and the Lessons Report is a summary produced during Closing a Project. The lesson log is updated continuously.
The exam tests that lessons are an ongoing activity, not a one-off event. Beginners often lump all lessons work into the final process.
Mistake
During Closing a Project, you evaluate whether the project's benefits have been fully achieved.
Correct
You evaluate the potential for benefits, but actual benefits realisation often happens after the project ends. The benefits review plan schedules these evaluations later.
Many people think benefits must be proven at closure, but in reality benefits (like increased sales) take time to appear. The process plans for future review, not immediate measurement.
Mistake
The product handover is a simple email saying 'the product is ready'.
Correct
Product handover is a formal activity documented in the product handover document, with acceptance sign-off from the customer and training for operational teams.
Beginners underestimate the formality of handover. The exam tests that handover includes acceptance, transfer of ownership, and operational readiness.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Yes, you must still perform Closing a Project. Even for a cancelled project, you need to capture lessons, hand over any completed work, and formally end the project.
The End Project Report covers the entire project from start to finish, while the End Stage Report covers only one management stage within the project. Both report on performance and lessons.
The executive of the project board gives the final approval. The project manager prepares the documents but cannot authorise closure without the board's permission.
It is a suggestion for work that still needs to be done after the project ends, such as fixing minor bugs, performing ongoing maintenance, or conducting future upgrades.
No, you only plan how and when benefits will be measured after closure. This plan is called the benefits review plan. Actual benefits are evaluated later by operational teams.
The key documents are the End Project Report, Lessons Report, Follow-on Action Recommendations, and the Benefits Review Plan.
You've finished Closing a Project Process. Continue through the PRINCE2F study guide to build a complete picture of the exam.
Done with this chapter?