Project Management guide · Risk, quality and control
Project Closure: Steps, Checklist and Closure Report Template
Project closure is the final phase of a project, in which the work is formally completed, deliverables are accepted and handed over, contracts and finances are closed, resources are released and lessons are recorded. It confirms the project has ended and transfers responsibility to the people who will use or support its outputs.
Key takeaways
- Project closure formally ends the project and transfers ownership.
- Use a checklist covering acceptance, handover, contracts, finance, resources and records.
- Write a closure report and get the sponsor's sign-off.
- Close cancelled projects formally too.
Why formal closure matters
- Confirms that the customer or sponsor has accepted the deliverables.
- Transfers ownership to operations or support so the project team can stop.
- Stops further spending and closes budgets and contracts.
- Releases people and equipment for other work.
- Captures lessons learned for future projects.
- Creates a complete record for audit and reference.
Projects that drift to an end without formal closure often leave open purchase orders, unclear support arrangements and unresolved disputes about whether the work is finished.
Types of project closure
| Type | When it happens | What is different |
|---|---|---|
| Normal closure | Objectives achieved and deliverables accepted | Full handover and celebration |
| Phase closure | End of a phase or stage | Formal review before authorising the next phase |
| Premature closure | Project cancelled, for example because the business case is no longer valid | Document work completed, salvage useful outputs, record reasons |
| Contract closure | A supplier contract ends | Verify deliverables, settle payments and close the agreement |
Project closure steps
- Confirm completion: check every deliverable against the scope and acceptance criteria in the project management plan.
- Obtain formal acceptance: get written sign-off from the sponsor or customer.
- Hand over: transfer deliverables, documentation, training and support arrangements to operations.
- Close contracts: confirm supplier deliverables, settle final invoices and formally close agreements.
- Close finances: reconcile actual cost against the budget, close cost codes and cancel open orders.
- Release resources: return people, equipment and facilities, and give feedback on team members' performance.
- Capture lessons learned: run a final lessons session and move lessons to the organisation's repository.
- Write the closure report: summarise performance against objectives and record outstanding items.
- Archive records: store project documents where they can be found later.
- Celebrate and communicate: thank the team and tell stakeholders the project is closed.
Project closure checklist
| Area | Checklist item | Owner | Done |
|---|---|---|---|
| Deliverables | All deliverables completed and verified against acceptance criteria | Project manager | [ ] |
| Acceptance | Formal sign-off received from sponsor or customer | Sponsor | [ ] |
| Handover | Operations or support team trained and has accepted ownership | Operations lead | [ ] |
| Handover | User guides, technical documents and warranties handed over | Project manager | [ ] |
| Issues | Open issues and defects closed or transferred with an owner | Project manager | [ ] |
| Risks | Risk register closed; ongoing risks handed to operations | Project manager | [ ] |
| Contracts | Supplier deliverables confirmed and contracts formally closed | Procurement | [ ] |
| Finance | Final costs reconciled, invoices paid, purchase orders closed | Finance | [ ] |
| Resources | Team members released and feedback provided | Project manager | [ ] |
| Access | Temporary system access and licences removed | IT | [ ] |
| Knowledge | Lessons learned session held and register updated | Project manager | [ ] |
| Benefits | Benefits measurement plan handed to the business owner | Sponsor | [ ] |
| Records | Project files archived in the agreed location | Project coordinator | [ ] |
| Communication | Closure announced to stakeholders | Project manager | [ ] |
Closure report template
| Section | What to include |
|---|---|
| Project summary | Purpose, sponsor, project manager, start and end dates |
| Objectives and results | Each objective, target and actual result |
| Scope | Delivered, changed and descoped items, with approved change requests |
| Schedule performance | Planned and actual dates for key milestones |
| Cost performance | Budget, actual cost and variance with explanation |
| Quality | Acceptance results and outstanding defects |
| Benefits | Benefits achieved so far and how the rest will be measured |
| Outstanding items | Open issues, risks and actions, each with a new owner |
| Lessons learned | Top lessons and recommendations |
| Approval | Sponsor sign-off and date |
Worked example: a payroll system upgrade had a budget of $320,000 and a planned finish of 30 June. It closed on 14 July at a cost of $334,000, a variance of $14,000 (4.4% over), caused by an approved change adding a pension interface. All 6 objectives were met. Two minor defects were transferred to the support team with agreed fix dates, and benefit tracking for reduced manual processing passed to the finance director.
Common mistakes
- Letting the team move on before handover is complete.
- No formal acceptance, so the customer keeps raising 'small' requests.
- Leaving purchase orders and contracts open.
- Skipping lessons learned because everyone is busy.
- Not handing over open risks and issues, so they are lost.
- Not closing cancelled projects formally, which wastes the learning from them.
Free templates for this topic
Frequently asked questions
What is project closure?
The final phase of a project, where deliverables are accepted and handed over, contracts and finances are closed, resources are released and lessons are recorded.
What are the steps to close a project?
Confirm completion, gain acceptance, hand over, close contracts and finances, release resources, capture lessons, write the closure report, archive records and communicate closure.
What is a project closure report?
A document that summarises results against objectives, cost and schedule performance, outstanding items and lessons learned, signed off by the sponsor.
Who approves project closure?
Usually the project sponsor or the governance board that authorised the project.
What is the difference between project closure and contract closure?
Contract closure ends a specific agreement with a supplier. Project closure ends the whole project, which may include several contracts.
How does project closure work if a project is cancelled?
It should still be closed formally: document what was completed, salvage useful outputs, close contracts and finances and record why it stopped.
What is the difference between phase closure and project closure?
Phase closure is a formal review at the end of a phase or stage, confirming its outputs and deciding whether to continue to the next phase. Project closure happens once, at the end of the whole project.
Why does project closure often go wrong?
Teams are reassigned early, closure is not planned or budgeted, and acceptance criteria were never clearly agreed.
What is the PMBOK process for project closure?
In the PMBOK Guide sixth edition it is Close project or phase, part of project integration management.
How does PRINCE2 handle project closure?
PRINCE2 has a Closing a project process, which includes handover, evaluating the project and recommending closure to the project board.
Should benefits be measured at project closure?
Some benefits can be, but many appear later. Hand a benefits measurement plan to the business owner so they are tracked after the project ends.