How-to guide · Clients & workflow

How to write a project wrap-up email

By the WorkKitly Team · Last updated: November 2026 · 7 min read

A project wrap-up email is the short message sent with delivery that closes the project on purpose. It does five jobs: confirms what was delivered and where it lives, closes the loop on the agreed scope, carries the final invoice with its terms restated in one line, plants the testimonial ask without making it, and leaves one specific door open. Most freelancers send some version of "files attached, thanks!" and leave all five undone. The work was professional; the ending is an afterthought — and the ending is what the client files the whole project under. It is also the first paragraph of the next referral: the freelancer people pass on is the one whose projects visibly end. One short email, written once per project, does all of it.

1. The five jobs, in order

The order is the logic: receipt first, money in the middle, future last. That is the sequence a client reads in — where is my stuff, what do I owe, what happens next — and an email that follows it feels complete in a way a longer, wandering one never does.

Job one: confirm the delivery. Say what was delivered and where it lives — not "the files", but the thing itself and its address. The detail belongs in the project handover document, which is the receipt the client keeps: deliverables, access, how it works, the terms of the ending. The email's job is to point at that document and confirm the project is complete. A client who knows where things live stops emailing you in month three to ask.

Job two: close the loop on scope. One sentence ties the delivery back to the agreed scope: this is what was promised, and this is all of it, delivered. Anything discussed and deliberately parked mid-project gets named here too — not as an apology and not as a new quote, but as a future conversation the client can open when they are ready. Parked work named in the wrap-up is a plan; parked work never mentioned becomes, in the client's memory, something you forgot. It is the same discipline as handling scope creep while the work runs: every change was answered in writing then, so the closing sentence has something clean to point at.

Job three: the final invoice, in one line. Attach it or link it, and restate the essentials in a single line — invoice number, amount, due date, exactly as agreed. The mechanics of the invoice itself belong to our guide to how to write an invoice email, and the terms were set at the start: freelance payment terms explained covers choosing them. In the wrap-up the invoice is neither the headline nor the footnote. It is a formality riding in the middle of the message, expected and unembarrassing, because the client has known its shape since the proposal.

Job four: plant the testimonial seed — do not make the ask. One sentence does it: name the result the project produced, and say you will check in in a couple of weeks to hear how it is settling in. That is all. The actual ask belongs later, when the result has had time to prove itself and the client has something concrete to describe — our guide to getting testimonials and case studies covers the asking, the three questions and the permission. Asked at delivery, a testimonial request collects politeness. Seeded at delivery and asked at the check-in, it collects evidence.

Job five: open one specific door. End with the next thing — named concretely, from this project's evidence, not from your service menu. The site that now takes orders could grow the blog you parked; the brand refresh points at the packaging it will sit on. A specific door tells the client you were paying attention to their business, not just your deliverables. Then, once, plainly: the referral line. "If another owner asks who built it, I'd be glad of an introduction" is a line, not a campaign. The fuller ask, with its own timing, lives in how to ask clients for referrals; here the line simply keeps the door visible while the client is happiest.

2. The template

Here is the whole email, written for the bakery website that runs through our pricing guides. It is 186 words, subject line and brackets included — and every job from the list above is in it.

Subject: Your new website is live — everything in one place

Hi [Name],

It's live — the new [Bakery Name] website is finished and taking orders. Everything from the project now lives in one place: the handover document at [link], with the final files, your list of logins and the notes from our walkthrough. If you need anything from this project, it starts there.

That completes the scope we agreed: the [eight]-page site, the online ordering setup and the [training session]. The blog we discussed is parked in the handover notes as a future conversation, ready whenever you are.

The final invoice is attached: [invoice number], for [amount], due [date] — as agreed.

Thank you for trusting me with the shop window. The ordering page is already earning its keep, and I will check in in a couple of weeks to hear how the first orders feel from your side of the counter.

When you are ready, the natural next step is the blog we parked — and if another bakery owner asks who built the site, I would be glad of an introduction.

[Your name]

Read it against the five jobs. Paragraph one confirms the delivery and gives the handover document as its home. Paragraph two closes the scope and names the parked blog as a future conversation. The invoice gets exactly one line. The thank-you sentence names the result and promises the check-in — the seed, not the ask. And the last paragraph names the next step and says the referral line once. Nothing else is in the email, because nothing else needs to be.

3. Timing and tone

Send it with the delivery. The wrap-up rides in the same message — or the same hour — as the finished work, while the client is opening the thing they paid for. Sent three days later it reads as admin catching up; sent with delivery, it reads as the final part of the delivery, which is what it is. If the project has a walkthrough call, the email goes first and the call walks the document it points to.

The subject line does work. From the inbox, it should tell the client the project is complete and everything is inside: "Your new website is live — everything in one place", or "[Project name] delivered: files, invoice and what's next". Honest subjects, both — no "quick question", no "just checking in", and nothing so pleased with itself that the client must open the email to learn the project ended.

Gratitude takes one line. Thank the client properly — once, specifically, for the project and what it let you build. A paragraph of thanks is not warmer; it is louder, and it pushes the invoice and the door down the page where they do less work. And never apologise — not for finishing, not for the invoice, not for the price. "Sorry to bother you with paperwork" teaches the client that the paperwork is an imposition. It is the receipt, and receipts do not apologise.

4. The mistakes

Burying the invoice. A final invoice hidden under three paragraphs of gratitude and a P.S. is an invoice hoping not to be noticed — and often it is not, until someone has to chase it, which converts a formality into a collection. Middle of the email, one line, number and date. Visible is polite.

Asking for everything at once. The delivery email that requests a testimonial, a referral, a review and an introduction is spending the client's happiest minute on your pipeline. Ask-ladder discipline: one seed now, one ask later, each at the moment it fits. A client asked for one thing at the right time usually gives it; a client handed a list gives none of it — and remembers the list.

The vague door. "Let me know if you need anything" is a door painted on a wall. It names nothing, so the client pictures nothing, and the next project goes to whoever is in front of them when the need arrives. The named next step — the parked blog, the seasonal refresh, the second location's pages — is a door with a handle: the client can see themselves opening it.

Going silent afterwards. The check-in promised in the email is a debt, and debts get calendar entries. Put it in the diary today, in the same sitting where you run the project retrospective: the retro works out what the project taught you, and the entry makes sure the client hears from you while the lesson is warm. A check-in that depends on remembering in two weeks happens in two months — or at the awkward moment you need something.

Questions

Send the shorter, factual version of the same email. Confirm what was delivered and where it lives. State the final invoice and its terms in one line. Skip the seed and the open door — warmth is optional, professionalism is not, and a clean receipt is worth having on the record even when the relationship is over. If the ending is an exit rather than a completion, our guide to firing a client professionally covers the notice and the wording; the wrap-up that follows it still does the same three factual jobs.
Link to them, at the home the handover document gives them. Attachments get downloaded once, saved wherever the downloads folder pointed that day, and quietly become the wrong version within a month. A link points at the one current copy, in the folder whose address never changes. The exception is the invoice itself: attach the PDF as well as naming it, because invoices get forwarded to whoever pays them, and the file should survive the forwarding.
Yes — with its terms restated in one line, exactly as agreed at the start. Sending it separately, a day later, reads as an ambush: the pleasant delivery email, then the money arriving like a second thought. Inside the wrap-up it is neither hidden nor headlined; it sits in the middle, one line among five jobs, a formality the client expected. Our guide to freelance payment terms covers what that one line should carry.
You don't — you plant it. The wrap-up carries one plain line saying you would be glad of an introduction, plus the named next step that reminds the client what your work looks like at its best. The real referral ask is a later, separate message, timed to a result; asking inside the delivery email spends the client's happiest minute on your pipeline instead of their project. The seed is enough: clients who were going to refer you needed the reminder, not the request.

Related: the ending, as a set

The handover document is the receipt this email points to. Testimonials and case studies is the ask this email only seeds. The project retrospective decides what the next project's wrap-up will do better. And the template above is a library citizen: it belongs in your freelance template library, blanks and all, ready for the next ending.