Working with others
Close out a project out loud
A simple exercise to end a project clearly, so nothing is left hanging and the work gets seen
When something ships, tell everyone involved that it's done, what's left, and who owns each follow-up.
- 10 minutes
- You and everyone involved
- When something ships
- Quick
Why this can work
A short close-out tells people they can stop holding a project, and puts a name next to every loose end. Without one, projects tend to fade rather than finish, and the small leftover items quietly become nobody's job. It's also a natural moment for the work, and the people who did it, to be seen.
Read moreHow to write a project close-out note
You’ll come away with a short close-out note that ends the project and gives every loose end an owner.
- List what's done and what isn't.
What shipped, and what didn't make it: open bugs, promised follow-ups, the doc nobody finished. Be honest; this list is the point.
- Put a name and a date next to each loose end.
Check with each person before you name them. If something has no owner yet, say so, and say who will decide.
Tip: It's fine for something to be dropped on purpose. Say that too, so nobody keeps waiting for it.
- Thank people specifically.
One line each for what someone did that made a difference. A specific line means more than a general thanks to the team.
- Send it to everyone involved.
Include the people who were waiting on it, not only the people who built it. They're often the ones who most need to hear it's done.
To: everyone involvedProject name is done. What shipped, in brief.
Still open, and who's on it: loose end, owner, by date. Anything dropped on purpose, and why.
Thank you to name for specific thing, and to name for specific thing.
Anything I've missed? Let me know and I'll make sure it gets an owner.
Swap the highlighted parts for your thing. Works on Slack, in email, or said out loud. - Keep a copy for yourself.
Save it with your own notes. It's a ready-made record of what you delivered, written while you still remember the details.
Good times to repeat it: when something shipswhen a project is paused or cancelledwhen you hand work off to someone else
Making it work for you
Every workplace is different. Here’s what to think about before you start, and what might get in the way.
Things to think about
For you it may mean shipped. For the person waiting, it may mean they can use it, and for your manager, that they can report it. Say which done you mean.
What might make this harder
Close it out anyway, honestly: what's done, what isn't, and what you'd do differently.
Questions people ask
How do I announce that a project is complete?
Send one short note to everyone involved: what shipped, what's still open with an owner and a date for each, and specific thanks.
What should a project close-out email include?
What was delivered, open items with owners and dates, anything dropped on purpose, and thanks to the people who made it happen.
What's the difference between a close-out and a retrospective?
A close-out tells people it's done and who owns what's left. A retrospective looks back at how it went. Both are useful, and the close-out is the quicker one.
Why this works, and where it comes from
Most projects don't end, they fade. The launch happens, everyone moves on to the next thing, and a handful of small items sit in limbo: the bug someone meant to fix, the doc someone meant to update, the customer someone meant to call back. Nobody decided to drop them. They just never got a name next to them. A few months later someone asks, and nobody remembers whose they were.
A close-out is an expectation, set out loud. It tells people they can stop keeping this project in their heads, a small relief most of them won't mention. It tells the people waiting on it that it's ready to use. And it turns every loose end into something with an owner and a date, or something dropped on purpose, which is almost as good. Either way, nobody is left waiting for a thing that isn't coming.
It's also one of the few natural moments to make good work visible. The people who did the hard, quiet parts of a project often go unmentioned, simply because nobody paused to mention them. A line each, specific about what they did, costs you a minute. For you, the note is a ready-made record of what you delivered, written while you still remember what it took, which is exactly what's hard to reconstruct at review time.
Many teams hold a retrospective after a project, and that's worth doing too. The close-out is smaller and faster. It asks not how did it go, but is it done, and what's left. It's worth sending even when the ending was messy or the project was cancelled. A clear end is kinder than a slow fade.
Other simple things to consider
What to do next
More in Working with others
Never lose the proof of your work
Do it with Truest and it goes on your permanent record, in a Career Vault your employer doesn’t own.
See how Truest worksAlready a member? Log in- Kept with the thing it was aboutSave what comes back in your Vault, next to the work it was about.
- Lands in your closeoutFriday's closeout asks for progress, priorities, and proud moments; this is one.
- On your recordWhen it's done, it goes on your record with your priorities and progress.
Read this alongside your role page
Tell Truest what you’re dealing with
We read every one, and we write guides for the things that come up most. Leave your email if you’d like to hear when we do.
An exercise written by Truest, based on our experience. Last updated September 25, 2026. We sell a career membership; where that’s relevant above, we say so.