For consultants at the end of a project
Project Closure Report Template With Example
A project closure report for the sponsor to sign: objectives against outcomes, open items and benefits handed to client owners, plus a finished example.
Section by section
What goes in a project closure report
The summary opens the report, but write it last, in four or five sentences for the reader who stops there. Here is what to record in every other part, and a mistake to watch for in each.
| Section | What to record | Watch for |
|---|---|---|
| Objectives against outcomes | The objective as the SOW or charter worded it, its measure, what happened, a result such as Met or Partly met, and evidence a reader can check. | Marking it Met with no evidence. Point to a dated report, figure or sign-off note. |
| Scope, time and cost | Baseline against actual for the end date, budget and contingency, the approved change behind each gap, and any SOW item not delivered. | A gap put down to “scope changes” with no reference. Name each change order, who approved it and when. |
| Deliverables and acceptance | Who accepted each deliverable, when, and on what conditions, judged against the success criteria agreed at the start. | Taking use or silence as acceptance. Get each acceptance in writing from the person the SOW names. |
| Benefits | Each benefit's measure, a baseline from before the project, the target and its date, a client owner and the first review date. | A benefit with no baseline. Without a figure from before the project, nobody can show it improved. |
| Open items and handover | Every open risk, issue, action, defect and unmet requirement, with an owner who stays, a due date and the date they accepted it. Add who to call about what. | An owner like “the client” or “IT.” Until a named person accepts an item, it is still yours. |
| Lessons learned | What happened, its effect, the lesson, and who should act on it, whether it went well or badly. | Recording only what went wrong. Note what went well and why, so the next team can repeat it. |
| Records and data | Where the final documents live, whether client data was returned or deleted, and when your team's system access ended. | Client files left on your team's laptops. Return or delete them as the contract requires, and confirm it in writing. |
| Checklist and sign-off | Nine closure checks, such as the final invoice sent and system access removed, then the sponsor's decision, signature and date. | Unticked checks with no date. Give each one still open a due date, as the example report does. |
How it works
How do you write a project closure report?
To write a project closure report, start in the project's last two weeks, while your team is still there to answer questions. Collect the signed SOW or charter, every approved change, the RAID log, acceptance emails and the final cost figures. The UK government's project delivery guidance1 says closure should confirm that outputs were delivered, unmet requirements documented with how they'll be addressed, and lessons recorded. It also says responsibility for ongoing risks, issues, actions and benefits tracking should pass to an owner who accepts it.
Copy each objective word for word from the SOW or charter, then mark it Met, Partly met, Not met or Too early to tell. Use a fifth result, “Met, as changed,” only when an approved change moved the target, and name that change. Report a miss plainly: if one site of three falls short, give that site's figure rather than an average that hides it. Benefits are often Too early to tell: as the same guidance notes, a benefit is not closed2 simply because the associated work is completed.
Hand every open item, from risks to defects, to a named client owner who stays after you leave. In California's state project management framework, the transfer of open issues must be formally documented and approved3 by both the sponsor and whoever accepts ownership. Then send the report for sign-off, and list any condition the sponsor attaches as an open item rather than holding the report back. Open items often become the next project, which the consulting proposal generator can scope.
How it works
From final status to a signed closure report
Download it or open it in River
Get the report and the finished example as Word files with no account, or click Edit with AI to open both in River.
Paste your objectives first
Optional: paste your SOW objectives and final status in the box at the top. River fills a first pass and brackets every gap.
Confirm it with the client
Check every outcome, owner and date with the sponsor. If River drafted the report, start with its To confirm list.
Get it signed
Tick the nine closure checks and send the report for sign-off. River can draft the sign-off email or a follow-on proposal.
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
- Three, each with a client owner; first review 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: What is Depot 3's pick accuracy? When is the replenishment fix due? Who owns the defect after close?
Results come only from what you pasted. Anything missing goes on the list to confirm.
What lands in your doc
What's inside the project closure report template
- Project Closure Report
The Word template: a header block, then 11 numbered sections with tables or bracketed slots to fill. - Objectives against outcomes
Each objective as the SOW worded it, a result from Met to Too early to tell, and its evidence. - Scope, cost and deliverables
Baseline against actual with every approved change, and who accepted each deliverable, when and on what conditions. - Benefits and open items
Every benefit and open item, from risks to defects, handed to a client owner with dates. - Lessons, records and sign-off
Lessons with who should act, handover contacts, records and data, a nine-point checklist and the sponsor's sign-off. - Example Closure Report
A finished report for an invented three-depot warehouse system rollout, with notes on why key parts work.
Questions consultants ask
Common questions
What is a project closure report?
A project closure report is the document a sponsor signs to formally close a project. It sets each objective against what happened, records what the client accepted and what it cost, and hands every open item and benefit to an owner who stays. Write one for a canceled project too: UK government guidance says closure can happen when work is terminated early1.
What should a project closure report include?
A project closure report should include a short summary and each objective against its outcome. Add scope, time and cost against baseline, the deliverables and who accepted them, and benefits with owners and review dates. Close with open items handed to named owners, lessons learned, handover contacts, records and data, a closure checklist and sign-off.
Who signs off a project closure report?
The sponsor signs to approve closure, and the project manager signs as the author. California's state project management framework has the sponsor review the closing documents and, if satisfied, approve closing the project3. On consulting work, the sponsor is usually the client executive who approved the scope and budget. Any conditions they attach become open items with owners.
How do you report benefits that haven't happened yet?
Mark them Too early to tell, not Met, and hand each one to a client owner who will still be there to measure it. Record the measure, the baseline, the target and its date, and when the first review happens. Many benefits only show up after a new process or system has run for a while, so time the reviews to match.
Is a closure report the same as a lessons learned report?
No. A lessons learned report is for your next project, turning what happened into changes your team will make. A closure report is the client's record of this one. Even so, UK government guidance says a closure report should include a review of the lessons learned1. It also says each lesson should go to the person best placed to act on it4.
Is this project closure report template free?
Yes. Download the blank report and the finished example as Word files, free and with no signup. Edit with AI opens both in River, which is free to start. There you can edit the report, share it or ask River to change it. Paid plans add more AI use and access to the most advanced models.
What does Edit with AI do?
It opens the report and the finished example in a free River workspace. Paste your objectives and final status in the box at the top, and River fills a first pass. It copies each objective word for word, never marks one Met unless your notes show it, and brackets every missing name, date or figure. Then it lists what to confirm with the client.
Your next step