Home About Experience Projects Case studies Resources Articles Briefs Playbook Tools FAQ How we start Security Get in touch

All tools › Project closure sheet

Saved in this browser only

The tool · project delivery

Project closure sheet

Project
Project manager
Closure date
1

Closing checklist

done means verified, not assumed
Done?ItemOwner
2

Plan versus actual

the honest table
AreaPlannedActual
3

Lessons learned

specific enough to reuse
What happenedWhat we do differently next timeApplies to
4

Sign-off

the project ends when someone says so
Approver and roleSignature or initialsDate

Why close on purpose

Unclosed projects haunt. They generate "quick asks" for months because nobody said done out loud.

Plan versus actual is the growth. The gap between the two tables is next project’s estimate, corrected.

Lessons need a destination. "Communicate better" teaches nothing; "put the content deadline in the contract" changes the next kickoff.

Release people formally. A thank-you and a clear end date beat a team that quietly evaporates.

Book the closure meeting at kickoff. It is the meeting most likely to be skipped and the cheapest hour the next project will ever buy. The lessons table feeds the kickoff checklist of whatever comes next.

Everything saves in this browser only. Print it and it is the closure report.

Prefer paper? Download the blank sheet as a PDF. The thinking behind it, and the nine tools it works with, is in The Project.

General guidance from practice, not legal, HR, or financial advice. Everything you type stays in this browser and is never sent to a server.