PRINCE2 7 Foundation · Study lesson 35
Prepare a responsible finish
Confirm acceptance, transfer ownership and make the unfinished obligations visible.
11 minute study lesson · Processes · Original learning material
What you will understand
- Identify the purpose and main preparations of Closing a project.
- Distinguish product acceptance, operational handover and closure authorisation.
- Explain how follow-on actions and benefits reviews continue beyond delivery.
The idea
A team packing away its equipment is not enough to show that a project has ended responsibly. Closing a project establishes a clear final position and prepares the recommendation that the board should authorise closure. It is used for a planned finish and for controlled premature closure. The aim is to leave ownership and obligations clear rather than let the project fade away.
Confirm the status of the project product against agreed acceptance criteria and obtain the relevant acceptance evidence. Users need to understand what has been delivered and any formally agreed limitations. A product being built is different from its being accepted, and acceptance is different from operational readiness. Avoid assuming that a supplier’s completion notice alone satisfies every user, contract or project acceptance requirement.
Arrange handover to the people who will operate, maintain and use the products. They may need documentation, training, support arrangements, access rights and agreed responsibilities. Check that necessary operational arrangements have owners. A project can deliver the intended output while leaving adoption work that must continue under clear business ownership. Handover should make that position explicit rather than claim that delivery automatically creates all expected benefits.
Identify outstanding issues, residual risks and follow-on actions, with responsible owners and suitable communication. Closure does not mean every future action or uncertainty has vanished. It means the remaining matters are understood and have been transferred appropriately. Update the benefits management arrangements for reviews that occur after the project. The business remains responsible for realising and evaluating benefits after the temporary project organisation has been disbanded.
Evaluate the project against the agreed baseline and later authorised changes. An end project report summarises performance and the final position. Capture and share useful lessons with people who can apply them elsewhere, including an honest account of difficult decisions and unexpected effects. A concise, actionable lessons report is more useful than a ceremonial list that leaves no one responsible for applying its findings.
Prepare the closure recommendation and bring it to the board through Directing a project. The board authorises closure, confirms the relevant notifications and release of resources, and ensures that remaining business arrangements are understood. Premature closure uses proportionate versions of these checks: record what was delivered, what was not, why work is stopping and what needs safeguarding. Do not continue a project solely to wait for benefits that are intended to be measured later.
Controlled closure protects the result
| Check | Reason |
|---|---|
| Acceptance and handover | Confirm responsibility for using and supporting the products. |
| Outstanding items | Assign follow-on actions rather than quietly forgetting them. |
| Performance and lessons | Give a useful account of what happened and what can improve. |
| Future benefits reviews | Keep post-project measurement and ownership clear. |
| Recommend closure | Allow the board to authorise the end. |
An original fictional example
Fictional case: a local history archive
An archive digitisation project has delivered the accepted catalogue and trained library staff. A small set of fragile documents will be digitised later under an agreed follow-on action. Usage benefits will be reviewed after six months.
The decision
The project manager confirms acceptance and operational ownership, assigns the follow-on action, updates the benefits review arrangements and submits the end project report and closure recommendation to the board.
Why it makes sense
Responsible closure records and transfers remaining obligations. Waiting six months with the whole project team retained would confuse a later benefits review with a condition for completing the temporary project.
A common confusion
The mistaken idea: A project must stay open until every expected benefit has been measured.
The distinction: Some benefits arise later; closure should establish clear owners and review arrangements for them.
Finish the temporary project; preserve the continuing business responsibilities.
Points to remember
- The manager prepares closure; the board authorises it.
- Acceptance, operational handover and business benefit realisation are distinct.
- Premature closure still needs proportionate evaluation and follow-on arrangements.
Your takeaway
Close with evidence of the final position, accepted handover and named owners for remaining actions and benefits reviews. The board’s decision completes a controlled transition to continuing business ownership.
This independently written explanation is supplementary study material. It is not official examination content. Read about our content and its limitations.