How to Write a Project Closure Report: A Practical Guide
A project closure report is the final record of a project: what was delivered, what it cost, how it went, and what happens next. It formally ends the project, hands the results over to whoever runs them day to day, and preserves the story for future teams. Projects that never officially close tend to linger, a few “quick fixes” in month seven, an unpaid invoice in month nine.
When to Use This
Write it when the project has delivered its objectives, or when it is being stopped early. Both endings need a report: a cancelled project still spent money and taught lessons, and its record should say so. Typical timing: within two to four weeks of the final deliverable being accepted. Do not wait until every loose end is tied; write the report, list the loose ends in it, and assign them. The report is what turns “the project is basically done” into “the project is closed.”
How to Fill It Out
Section 1: Project overview. Summarise the project in a short paragraph: what it set out to do, when it ran, who sponsored and managed it. “The Riverside store refit (sponsor: Maria Chen; project manager: David Park) ran from 6 January to 28 June 2027, modernising the shop floor, till systems, and staff areas.” A future reader with no background should understand the basics from this section alone.
Section 2: Objectives vs. achievements. List each original objective from the charter alongside what was actually achieved. “Objective: complete refit by 30 May 2027. Achieved: completed 28 June, four weeks late, delay caused by the till-system testing issue (see lessons learned). Objective: stay within £120,000. Achieved: final cost £126,400, 5.3% over.” Be honest about misses; the closure report is a record, not a sales pitch. Unexplained gaps between plan and reality will be noticed, explain them yourself.
Section 3: Deliverables and acceptance. List every deliverable and its acceptance status: accepted, accepted with conditions, or not accepted. “New till system, accepted 25 June (signed by store manager). Staff training materials, accepted with conditions: refresher session due August.” Attach or reference the signed acceptance documents. Anything not accepted needs an owner and a date for resolution, the report does not close open items, it assigns them.
Section 4: Financial summary. Give the final numbers: original budget, approved changes, total spent, and variance. “Budget: £120,000. Approved changes: +£4,000 (CR-004, extra electrical work). Total spent: £126,400. Variance: +£2,400 over revised budget (1.9%).” Confirm all invoices are paid or list the outstanding ones with expected dates. Unpaid invoices discovered months later are a classic symptom of a project that was never properly closed.
Section 5: Handover. Describe what is being handed to the ongoing operations team: systems, documents, warranties, support contacts, and any remaining work. “Till system support contract with TechServe Ltd (reference TS-8841, expires June 2028). Operations manual stored in the shared drive. Outstanding: staff refresher training, owner Sarah Lowe, due 31 August 2027.” Name the person accepting each handover item. The project team disbands after closure, anything not handed over falls through the cracks.
Section 6: Lessons learned summary. Include the top five to eight lessons (or reference the full lessons-learned document). “Key lesson: confirm supplier test-environment availability in writing eight weeks ahead, the till delay cost four weeks.” This ensures the project’s hard-won knowledge travels with the closure report instead of living in a separate file nobody opens.
Section 7: Formal sign-off. The sponsor signs to confirm the project is closed, the deliverables are accepted (or exceptions noted), and remaining items have owners. This signature releases the project team and closes the budget. Keep the signed report on file, it is the definitive record if questions arise later.
Common Mistakes
1. Closing the project before the deliverables are accepted. “Basically finished” is not finished. Every deliverable needs a clear accepted/not-accepted status with evidence. Teams that skip this step inherit disputes: the client who claims the work was never signed off, the invoice that cannot be paid because acceptance was never recorded.
2. Fudging the final numbers. Rounding £126,400 down to “about £120,000” or burying the overrun in vague language destroys the report’s value. Future estimates depend on honest history. Record the real figures, explain the variance in one paragraph, and move on, an explained overrun is information; a hidden one is a lie that compounds.
3. No real handover. The project team walks away and the operations team inherits a system nobody explained. Document every handover item, name the receiver, and hold a handover meeting, thirty minutes where the project manager walks the operations lead through the systems, documents, and outstanding items. Projects do not end when the team leaves; they end when someone else can run what was built.
4. Skipping closure for cancelled projects. A project stopped halfway still needs a report: what was spent, what was delivered, why it stopped, and what to salvage. Without it, the next team rediscovers the same dead end. “Project stopped 14 May: market conditions changed; £18,000 spent; supplier contracts cancelled with no penalty; design work archived for potential reuse.” Ten lines now save a future team weeks.
Who Needs to Sign Off
The project manager writes the report and confirms the facts. The sponsor signs to formally close the project and release the team and budget. The operations lead (whoever receives the handover) signs to confirm they accept the deliverables and outstanding items. For client projects, the client signs acceptance of the deliverables. Four signatures close a project properly.
How Often to Review and Update
The closure report is written once, it is a final record, not a living document. But it should be revisited in two ways: first, at the three- or six-month mark, check that the handover items were actually completed and the benefits are materialising (a short post-project review). Second, at the kickoff of the next similar project, the project manager should read the closure reports and lessons of the last one, that is the moment the whole exercise pays off.
Download the free Project Closure Report.