Process · Topic 12 of 12
Managing Project Closure
Close a project or phase by confirming acceptance, finishing procurement, capturing lessons, handing over to operations and archiving records.
- 4 min
- Closure applies to a project, a phase and each contract.
- Formal acceptance of deliverables is needed before closing.
- Procurement closure settles claims and payments and gives formal notice.
What it is
Closure formally ends a project, a phase or a contract. It confirms that the work is complete or deliberately stopped, hands the results to the people who will use them and records what the organization learned.
Skipping closure leaves loose ends: unpaid invoices, unclear ownership of the product and lessons that disappear with the team.
How it works
When a project closes
A project closes for several reasons. It may finish because objectives were met, or the project may end early because the business case no longer holds, funding or sponsorship was withdrawn, or the product is no longer needed. Cancelled or terminated projects still need closure, including documentation of the reason.
Each phase also has an end, with a review of deliverables before the next phase begins.
Closure activities
The project manager works through a checklist.
- Confirm completion. Check that all work is done, or document what remains and why, against the plan and acceptance criteria.
- Obtain formal acceptance. The customer or sponsor signs off on the final deliverables.
- Close procurement. Verify that sellers delivered, settle claims, make final payments and give formal notice that contracts are complete.
- Transition the product. Hand over to operations or support with documentation, training and a handover period.
- Transfer benefits ownership. Make sure someone owns the tracking of benefits after the project ends.
- Capture lessons learned. Hold a final review, record what went well and badly, and share the results.
- Archive records. Store project documents so they can be found later, as organizational process assets.
- Release resources. Return people and equipment, and recognize the team.
- Close financials. Complete the final accounting and close the cost accounts.
- Report. Give a final report to stakeholders and seek their feedback.
Closure in predictive projects
In a predictive project, closure is a defined step at the end of the lifecycle, supported by a final report. The report compares results with the baselines and the business case. The project manager also updates the organization's records so that future estimates can use real data.
Closure in agile projects
Agile projects deliver value in each increment, so the product may already be in use before the project ends. Closure occurs when the product vision is met, the funding ends or the remaining backlog no longer justifies cost. The team holds a final retrospective, hands over knowledge and documentation, and makes sure the product owner and support teams are ready to continue.
A hybrid project closes agile and predictive parts together. It still needs formal acceptance, contract closure and financial closure where governance requires them.
Early termination
When a project stops early, the project manager records the stage of completion, what was delivered, open commitments and the reason for stopping. Contracts must still be closed. Lessons from a cancelled project are valuable, because they show where assumptions failed.
Stakeholders and benefits
Closure is also an engagement moment. Confirm that stakeholders are satisfied or that open concerns are recorded. Benefits often appear after the project ends, so a plan for measuring them and a named owner are part of proper closure.
When a scenario asks what to do after the last deliverable is accepted, think in order: close contracts, capture lessons, archive, release the team and report.
What to remember for the exam
- Closure applies to a project, a phase and each contract.
- Formal acceptance of deliverables is needed before closing.
- Procurement closure settles claims and payments and gives formal notice.
- Transition to operations needs documentation, training and a named owner.
- Lessons learned are captured at the end and shared as organizational assets.
- Archive records so future projects can use them.
- Release resources and recognize the team's work.
- A terminated project still needs closure and documented reasons.
- A benefits owner should be named for the period after the project ends.
Common mistakes
Closing without acceptance. Without sign off, the customer may later deny that the work was complete.
Ignoring cancelled projects. An early stop still needs documentation, contract closure and lessons.
Forgetting hand over. Operations teams cannot support a product they do not understand.
Collecting lessons but not sharing them. Unshared lessons help no one.
Releasing the team before closure tasks end. Keep the people needed to finish documentation and handover.
Do not leave contracts open when the project closes, because open contracts keep legal and financial obligations alive.
Check yourself
What is needed before the project manager can close a project normally?
Formal acceptance of the final deliverables by the customer or sponsor.
What must still happen when a project is cancelled early?
Closure activities, including contract closure, documenting the reason and capturing lessons learned.
Why name a benefits owner at closure?
Benefits often appear after the project ends, and someone must track and realize them.
Topic 12 of 12 in Process
Test yourself on Process
The full PMI PMP question bank has 1,463 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by PMI. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.