Email Scripts · End of engagement
Reddit Client Offboarding Template for Freelancers
A copy-paste client offboarding template for freelancers. Email scripts, support-boundary wording, and the closing messages that end an engagement kindly without opening the door to a free retainer.
Quick answer
Offboarding works when you treat it like onboarding: an intentional sequence, not a one-off farewell. The four messages below — wrap-up, support boundary, feedback request, and post-window follow-up — cover 90% of what most freelancers need. Customize the bracketed fields; leave the rest alone.
Email 1 — The wrap-up + deliverables
Send this on delivery day. It is short, complete, and forwardable to anyone on the client's team.
Subject: {CLIENT PROJECT} — final delivery and what's next
Hi {NAME},
The project is delivered. Here's the rundown:
• Deliverables: {LINKS OR ATTACHED FOLDERS}
• Source / repo access: {LINKS, ROLE, OR PERMISSIONS}
• Credentials (where applicable): {SHARED VIA PROJECT HANDOFF LINK}
(we send these through a secure handoff link — direct reply if you can't access it)
• Final invoice: {INVOICE NUMBER / LINK} (net {N} due {DATE})
What's yours now:
• Hosting/DNS/registrar accounts (you own these and the renewal dates)
• CMS access under your domain
• Brand files and any custom assets
What's mine until {SUPPORT-END DATE}:
• Bug fixes against the agreed acceptance criteria
• Up to {N} hours of clarifying questions (reply directly)
After {SUPPORT-END DATE} any change, addition, or performance work
is a new project — happy to scope it when you need.
{YOUR NAME}
{ROLE / COMPANY}Email 2 — The support window + boundary
Send this on the day support ends. It is the most important message of the engagement because it sets the precedent for every future project.
Subject: {CLIENT PROJECT} — support window has closed
Hi {NAME},
Quick heads-up: the support window for {PROJECT NAME} ended
on {SUPPORT-END DATE}. Everything inside the agreed scope
is closed.
If a question comes up that fits the original scope, reply with the
brief and I'll address it within {N} business days.
Anything new — an extra page, a copy change requiring layout work,
a new integration, a redesign — is a new project. I'm happy to scope
it on request; please send a one-line brief and I'll come back with
a fixed quote and timeline.
If you ever need to onboard a new vendor to take over ongoing work,
the final handover pack we sent on delivery day has everything they
need.
Thanks for the work — it was a good one.
{YOUR NAME}Email 3 — Feedback request (one week after sign-off)
Sent a week after sign-off so the project is fresh but settled. Keep the ask low-friction; one question is enough.
Subject: 30 seconds — a quick honest read?
Hi {NAME},
Hope the project is settling in nicely.
If you have 30 seconds, the single most useful thing you can send
back is one sentence: what was the moment we made the project easier
(or harder) for your team?
Optional, no rush — and if you'd rather skip it, no problem at all.
Thanks again,
{YOUR NAME}Email 4 — Post-window follow-up (60 days after close)
Re-opens the relationship on your terms. Useful for repeat work or referrals. Do not pitch; the message is service.
Subject: still on the books — 90-second check-in
Hi {NAME},
It's been about two months since we wrapped. No agenda — just wanted
to make sure nothing is sitting on your side unanswered.
If everything is settled, you can ignore this. If something has come
up — small update, fresh request, second project — reply with a brief
and I'll come back with a quote.
{YOUR NAME}Phrases that close gently
- "Anything inside the original scope." Frames every future ask against the original agreement.
- "A new project I'm happy to scope." Refuses the free-request without refusing the relationship.
- "Reply with a one-line brief." Lowers friction for the legitimate asks and exposes the vague asks.
- "The handover pack has everything a new vendor needs." Removes the implicit duty to stay available indefinitely.
Stop reinventing this every project
Send the same boundary. Keep the relationship.
Finalizo turns the four emails above into a structured support boundary with a timestamped sign-off step — so the closeout happens automatically and the relationship stays intact.
Automate my client offboardingRelated templates for your next project
- Client handover checklist for freelancers →The pre-delivery pass that puts these emails in motion.
- Website handover checklist for agencies →Technical ownership transfer for client builds.
- Project sign-off template for freelancers →The signed acceptance document these emails point to.
Finalizo is not affiliated with Reddit. This template was compiled from freelancer experience discussed in r/freelance and is offered as a practical reference. Finalizo is a commercial product that automates parts of this workflow.