Client delivery · Kit & File Field Notes
How to Close Out a Client Project (Handoff, Wrap-Up, Next Step)
Handoff packet, summary note, final invoice, access cleanup, a short wrap-up call, and one honest next step. A client offboarding checklist for small firms.
Most projects don't end. They fade out, with a last file sent and a vague "let me know if you need anything." Then the client can't find the logo a few weeks later, and you're the one they email.
Build the handoff packet
The point of closing out is a client who can use the work without you. A file dump doesn't get there.
The packet:
- Final files, named so a stranger could find them.
- Editable source files, if they're in scope.
- A one-page README: what each file is, how to update it, and who to ask.
- Accounts or assets transferred to the client.
I think the README is the item people skip most, and it's the one the client will need weeks later.
README template
[Project] handoff
- [File name]: what it is, and when you'd use it.
- How to update it: [steps or the tool it opens in].
- Questions: [who to ask, and how].
Kit & File builds a handoff into each of its services, such as a 30-minute handoff at the end. Put the handoff in the scope and it never gets cut.
Write a one-page summary note and send the invoice
The summary note is the record both sides keep. Four headings:
- Scoped: what the scope of work promised.
- Delivered: what you handed over.
- Changed: anything added, swapped, or parked through out-of-scope requests.
- Recommended next steps: what the client should do now, whether or not it involves you.
Send the final invoice with the delivery, not weeks later. I'd send it the same day you ship. The terms themselves belong in your payment terms.
Clean up access
Transfer ownership of any accounts or assets you set up to the client, then remove your own access. Follow your agreement and the client's security preferences. List what you changed in the README so the client has a record.
Unglamorous. Still part of the job.
Hold a short wrap-up call and offer one next step
The wrap-up call is optional. Keep it short:
- Walk through the handoff packet.
- Cover what worked, and what to change next time.
- Give your honest recommendation for what they should do next, in or out of your scope.
Offer one next step, once. Base it on what the client needs, give it a clear scope and price, and make no an easy answer. Don't bundle it with the invoice. If nothing fits, say so and suggest a check-in date instead. Put that date in your pipeline.
What about a testimonial? Ask separately, not in the same message. The testimonial guide covers timing and wording.
When the project went badly
Still deliver a clean handoff, a factual summary, and the final invoice. Skip the testimonial and next-work asks.
The closeout checklist and email
- Deliver the final files.
- Write the README.
- Send the summary note.
- Send the final invoice with the delivery.
- Transfer access and remove your own.
- Offer a wrap-up call.
- Offer the next step once, or set a check-in date.
- Ask for a testimonial separately, if the project went well.
Hi [Name], everything for [project] is in [location], with a one-page README explaining each file. I've attached a short summary of what we scoped, delivered, and changed, plus the final invoice, due [date]. I've transferred [accounts] to you and removed my access. If useful, I'm glad to do a 20-minute walkthrough this week. Thanks for the work together.
Illustrative example (fictional)
A designer finishing a brand refresh sends the logo files with a README, a summary noting one parked request, and the final invoice, all in one email. On a short wrap-up call she recommends the client update their website next, offers that as a fixed-scope project once, and sets a check-in date when the client says not yet.
The next project starts again with onboarding. For writing the closeout email and the next-step offer, the Better Messages Kit has a guide and reusable prompts.
When the client goes looking for that logo, the README should answer before you do.
Questions
Frequently asked questions
What is client offboarding?
It's the planned end of a project: handing over final files with instructions, summarizing what was delivered, sending the final invoice, cleaning up access, and agreeing what happens next.
What should a client handoff packet include?
Final files, any in-scope source files, a one-page README explaining each file and how to update it, and any accounts or assets transferred to the client.
When should I send the final invoice?
Send it with the final delivery, under the payment terms you agreed, rather than waiting until the end of the month.
Do I need a wrap-up call at the end of a project?
It's optional but useful: a short walkthrough of the handoff, what worked, and a recommendation for what the client should do next.
How do I ask a client for more work after a project?
Recommend a next step based on what they need, offer it once with a clear scope and price, and make it easy to say no.
What should I do if a project ended badly?
Still provide a clean handoff, a factual summary, and the final invoice, but skip testimonial and new-work requests.
Put the guide to work
Better Messages Kit
The Better Messages Kit helps you write the closeout email, the next-step offer, and the check-in, with a message-writing guide, workbook, reusable prompts, and a quick-reference sheet.
See what is included →