PRINCE2 Foundation v7 Closing a Project

Closing a Project (CP) is the process that confirms the project can be closed in a controlled way. Foundation questions here often test whether you understand that closure is not merely “the work seems finished.” It is a governed decision based on acceptance, handover, and review.

What to understand

Closure in PRINCE2 involves confirming product acceptance, arranging handover, assessing performance, recording lessons, and recommending project closure to the board. The stronger answer usually checks whether the agreed products have been accepted and whether closure is supported by evidence, not assumption.

This process also protects the distinction between finishing delivery work and formally closing the project. A project may be near completion operationally but still need controlled closure steps.

Example

The final product is built, but acceptance records are incomplete and operational handover is unclear. PRINCE2 would treat that as a closure-readiness problem rather than assuming the project is already closed.

Common pitfalls

• Treating completed delivery as automatic project closure.
• Forgetting to confirm acceptance and handover.
• Ignoring lessons and final performance review.
• Assuming the project manager closes the project without board decision.

Sample Exam Question

Which statement best reflects PRINCE2 Closing a Project?

A. The project closes automatically when the last task ends. B. The project closes only after acceptance, handover, and closure recommendation are properly completed. C. The delivery team closes the project once product development is finished. D. Closure should be delayed until all benefits are fully realized.

Best answer: B

Why: PRINCE2 closes projects in a controlled way, supported by acceptance, handover, evaluation, and governance decision.

Why the others are weaker: A and C skip governance and acceptance logic, while D confuses project closure with long-term benefit realization.