For consultants at the end of a project
Project Closure Report Template With Example
Two documents: a closure report covering objectives against outcomes, accepted deliverables, benefits, open items, lessons and sign-off, plus a finished example.
Project closure report
Warehouse system rollout · closed 6 Feb 2026 (example)
- Objectives
- Two met, one partly met, one too early to tell until 12 Apr
- Deliverables
- Seven of seven accepted, one with a condition
- Benefits
- Pick accuracy and labor hours, tracked by the operations director from 9 Mar
- Open items
- Four, each accepted by a named client owner
- Sign-off
- Sponsor, 6 Feb 2026, with two conditions
What you'll get
A closure report with objectives, open items, lessons and sign-off
- Each objective from the SOW against what actually happened
- Open items and benefits, each with a client owner and a date
- Lessons learned, handover contacts and a sign-off block
Before and after
Your objectives in. A closure report out.
SOW objectives: all three depots live before peak, by 31 Oct; pick accuracy 99.5% at each depot within 8 weeks of go-live. Depots 1 and 2 went live in Sep and Oct, Depot 3 on 12 Jan after the steering committee moved it. Accuracy: Depot 1 99.6%, Depot 2 99.3%. Vendor still fixing Depot 2's replenishment report.
Objectives against outcomes 1. All three depots live before peak, by 31 Oct. Met, as changed: Depot 3 went live 12 Jan after the steering committee moved it. Evidence: [evidence]. 2. Pick accuracy 99.5% at each depot within 8 weeks of go-live. Partly met: Depot 1 99.6%, Depot 2 99.3%, Depot 3 [to confirm]. Open items 1. Depot 2's replenishment report fix. Defect. Owner after close: [owner after close]. Due: [date]. To confirm with the client: Depot 3's accuracy, the fix date, who owns the defect.
Results come only from what you pasted. Anything missing goes on the list to confirm.
Why it works
What goes in a project closure report?
A project closure report records what the project set out to do, what it delivered, and who owns what's left once your team leaves. The UK government's project delivery guidance lists what closure has to confirm. That includes outputs delivered, unmet requirements documented and lessons recorded, with ongoing risks, issues, actions and benefits tracking handed over to someone who accepts them. This template gives each of those its own section, ending in sign-off.
Each objective is copied from the SOW or charter word for word, then marked Met, Partly met, Not met or Too early to tell, with the evidence beside it. Benefits get a measure, a baseline, a client owner and a date to check them. As the same guidance notes, a benefit is not closed simply because the work is done. Lessons cover what went well as well as what didn't, and each names who should act on it.
The worked example closes an invented warehouse system rollout: two of four objectives met, one partly met, one too early to tell, and four open items accepted by client owners. Paste your SOW objectives and final status report, and River fills a first pass, with brackets for anything your notes don't show. Open items often become the next project, so the consulting proposal generator can draft the follow-on. For the final weeks before close, the status report generator keeps the weekly update going.
What lands in your doc
What's inside the project closure report template
- Objectives against outcomes
Each objective as the SOW worded it, with a result from Met to Too early to tell, and the evidence. - Scope, time and cost
Baseline against actual for dates, budget and contingency, with every approved change listed. - Deliverables and acceptance
Each deliverable with its SOW reference, who accepted it, when, and any conditions. - Benefits tracking
A measure, baseline, target, client owner and first review date for every benefit. - Open items and handover
Each open risk, issue, action or defect with an owner who stays, and the contacts to call. - Lessons, checklist and sign-off
What went well and what didn't, a nine-point closure checklist, and the sponsor's sign-off.
How it works
From final status to a signed closure report
Open the template
Click Edit with AI. The closure report opens in River, with the finished example beside it in the same space.
Paste your objectives
Optional. Paste the objectives from your SOW and your final status report, and River fills a first pass.
Confirm with the client
Check each outcome, owner and date with your sponsor, and fill everything River left in brackets.
Get it signed
Send the report for sign-off, hand over the open items, and propose any follow-on work.
Questions consultants ask
Common questions
What is a project closure report?
A project closure report is the document that formally ends a project. It sets each objective against what happened, shows which deliverables the client accepted and what the work cost, and hands every open item and benefit to an owner who stays. The sponsor signs it to accept closure.
What should a project closure report include?
A summary, each objective against its outcome, scope, time and cost against baseline, deliverables and who accepted them, and benefits with how they'll be tracked. Then open items with owners, lessons learned, handover contacts, records and sign-off. This template has a section for each, in that order, with a finished example to compare against.
Who signs off a project closure report?
The sponsor, or whoever approved the project's scope and budget, signs to accept closure, and the project manager signs as author. If the client can only accept with conditions, list each condition as an open item with an owner and a date, rather than holding the whole report back.
Is a closure report the same as a lessons learned report?
No. A lessons learned report covers what to repeat or change next time. A closure report also says whether the objectives were met, what was accepted, who owns the open items and how benefits will be measured. Here, lessons sit inside the closure report, covering what went well as well as what didn't.
How do I report benefits that haven't happened yet?
Mark them Too early to tell, not Met. For each benefit, record the measure, the baseline, the target and its date, the client owner who will track it, and when the first check happens. Benefits usually arrive months after a project closes, so the owner has to be someone who stays.
What if the project didn't meet an objective?
Say so plainly, with the evidence and what happens next. Mark it Partly met or Not met, and name any approved change that moved the target. A clear account of a miss protects you better than a vague one, and the open item it leaves is often the next piece of work.
When should I write the closure report?
Start it in the last two weeks of the project, while the team is still there to answer questions, and finish it once the final deliverable is accepted. Pull the open items from your RAID log and the approved changes from your steering committee decisions and weekly status reports.
Your next step
More for your project
Close the project cleanly
Open the report with every section in place, or paste your objectives and final status for a first pass.