How to Offboard a Client
To offboard a client is to close the professional relationship formally and cleanly — issuing the final invoice, transferring assets and access, archiving the project record, and ending the engagement in a way that protects the relationship for future referrals or work. Client offboarding is not just admin; it is the last impression the client has of your business, and it shapes whether they recommend you to someone else.
The two offboarding scenarios
Planned project end. A fixed-scope project reaches its final deliverable and the engagement is naturally complete. This is the most common scenario and the easiest to handle — both sides know it is coming, which means you can prepare the offboarding steps before the final day rather than scrambling.
Retainer end. A recurring engagement concludes — either by mutual decision, client decision, or because the retainer term ran out. The offboarding checklist is the same; the conversation is slightly different because the relationship was ongoing.
A third scenario — ending a problematic relationship early — requires different handling and is out of scope for this guide. This guide covers the normal, planned close.
The client offboarding checklist
- 1
Issue the final invoice
Before any handoff begins. The final invoice covers all outstanding hours, approved extras, and reimbursable expenses. Do not transfer assets before the invoice is sent.
See the end-of-project invoice checklist for the full pre-invoice audit.
- 2
Compile all deliverables and source files
Collect every file the client is entitled to: final deliverables, source files, design assets, code repositories, content documents. Organise them into a single shared folder or transfer package rather than sending piecemeal.
- 3
Transfer access and credentials
Every account, tool, platform, or subscription you hold on behalf of the client: hosting, CMS logins, analytics, ad accounts, social profiles. Transfer ownership or revoke your access depending on what was agreed.
- 4
Remove or archive your own access
Your access to the client's tools should either be transferred out or revoked by you proactively. Leaving yourself in as a collaborator on accounts you are no longer working on is a liability for both parties.
- 5
Document what was built and why
A brief project summary — what was delivered, key decisions made, what the client should know to maintain or build on the work — is more valuable than most practitioners realise. Keep it short: one to three pages is enough for most projects.
- 6
Send the offboarding message
A short, professional note that confirms the project is complete, summarises what was handed over, and leaves the door open for future work and referrals.
- 7
Archive the client record internally
Close out the project in your own systems: log any final time, mark the project complete, and archive the record so it does not appear in your active client view.
- 8
Follow up at 30–60 days
Not to sell, but to check in. A brief "how is [the project outcome] going?" message maintains the relationship and is the right moment to ask for a referral if the engagement went well.
How to handle the final invoice at offboarding
The final invoice is the part practitioners most often rush, and the part that most often generates disputes. A few points specific to offboarding:
Send it before the handoff. The leverage for final payment is the deliverables. This is not about withholding — it is about sequencing correctly. Invoice first, hand off on payment or on an agreed payment schedule.
Make it a clean record. The final invoice at offboarding should be readable on its own: original project fee, deposits received, approved extras, final balance. A client who left your business should be able to read that invoice in two years and understand exactly what they paid for.
Include a note about what's covered. A one-line invoice description — "Design and development for [project name], inclusive of all approved scope additions per email thread dated [month/year]" — prevents future disputes about what was included.
Asset and access handoff
This is where offboarding most often breaks down in practice. The asset handoff is not complete when you say "I've sent everything" — it is complete when the client confirms they have received and can access everything they need.
- List the assets in advance. Before the handoff call or email, make a list of every file, account, and asset the client is receiving. Share the list with the handoff — it gives the client something concrete to verify against.
- Use a shared folder with organised subfolders. A single link to a Google Drive or Dropbox folder with clear subfolder names is easier for the client than a list of 30 email attachments.
- Document non-file items explicitly. For access transfers — "your Google Analytics property ID is now owned by [client email], your previous admin access has been removed" — a written confirmation prevents "but I can't log in" messages later.
- Set a handoff deadline. "Assets will be available for download until [date], after which the shared folder will be archived" gives the client a clear window and avoids indefinitely maintaining a drive folder for a closed engagement.
The closeout conversation
Most offboarding conversations are two or three sentences in an email. What they need to be:
Clear about what's closing. "The [project name] engagement is now complete" — not ambiguous.
Specific about what was handed over. "The files listed above are now in the shared folder. Access credentials are included in the last section."
Open-ended about the future. "If you need anything as you get set up with the new system, feel free to reach out. And if you know anyone who could use similar help, I'd appreciate the introduction."
The referral ask is not aggressive when it is delivered at the end of a successful engagement in a single sentence. Most practitioners never ask. Most clients never offer without being asked.
How Ascend closes the loop
The common failure mode at client offboarding is a mismatch between what was delivered and what was invoiced — either because hours were not tracked continuously, or because the time log and the invoice are in different places.
In Ascend, time is logged against the client record throughout the engagement. At offboarding, the time log is the invoice — all tracked hours are already in the same record as the client's project. The final invoice is generated from what was logged, not reconstructed from memory.
After the project closes, the record can be archived in Ascend so it stays accessible as a reference but does not appear in your active workspace.
Ascend is in early access. The free tier covers one client end to end.
Frequently asked questions
What does it mean to offboard a client?+
Offboarding a client means formally closing the professional relationship: issuing the final invoice, handing over all assets and access, documenting what was built, and ending the engagement in a way that leaves the relationship intact. It is the close process, not just the final email.
When should I start the offboarding process?+
Before the final deliverable is handed over. Ideally, the offboarding checklist — final invoice, asset list, access audit — is prepared in the last week of active work, so the close is ready when the project is ready, not two weeks later.
Should I hand over assets before or after the final invoice is paid?+
Send the invoice before the handoff. This is not about withholding work — it is about sequencing. Most professional relationships don't require leverage; most clients pay. The sequencing protects you in the minority of cases where they don't.
What access should I transfer when offboarding?+
Every account you hold on behalf of the client: hosting, CMS, analytics platforms, ad accounts, social profiles, domain registrar access. Transfer ownership where possible; in accounts where transfer isn't available, document what access the client now has and what they need to re-create.
How do I ask for a referral at the end of a project?+
One sentence, after confirming the handoff is complete: "If you know anyone who could use similar help, I'd appreciate the introduction." Delivered at the end of a successful engagement, it is not a sales pitch — it is a natural close. Most practitioners never ask; most satisfied clients never volunteer without being asked.
What if the client wants to continue the relationship after offboarding?+
If it was a project close and the client wants to continue with a retainer, treat it as a project-to-retainer conversion. If it was a retainer end and they want to restart, issue a new retainer agreement rather than retroactively extending the closed one. Clean starts are easier to manage than complicated reactivations.
Related guide
How to Transition a Client from Project to Retainer
If the relationship ended well, this is the moment to propose ongoing work. Timing, framing, and scope for the retainer conversation.
Every project close handled in one place.
Ascend tracks time throughout the engagement so the final invoice is generated from the same record. Archive the project when you're done. The free tier covers one client end to end.
Start with Ascend free