Why offboarding matters
The end of a project is the part clients remember. A tidy handover, a clear final invoice and a thank-you call leave a better impression than a great project that fizzles out with an unanswered email. It is also practical: unclear endings cause disputes over what was delivered, unpaid final invoices, and security problems when old logins keep working.
Offboarding is the mirror of onboarding a new client. If you write it down once as a checklist, or better an SOP, every project ends the same way, whoever on the team runs it.
The offboarding checklist
Work through these in order. Most take a few minutes each.
1. Final delivery and sign-off
- Check every deliverable in the statement of work against what was delivered.
- Get written sign-off on the final deliverables.
- List anything still open, with an owner and a date, or agree it is out of scope.
- Confirm the warranty or support period, if your contract includes one.
2. Handover of files and accounts
- Send final files in agreed formats, plus source files if the contract includes them.
- Transfer ownership of domains, hosting, ad accounts, analytics and social profiles to the client.
- Hand over documentation: logins list, how-to notes, brand guidelines, a short training video if useful.
- Confirm the client can log in to everything without you.
3. Access cleanup
- Remove your team from the client's systems, or ask the client to.
- Remove the client from your internal tools, shared drives and chat channels.
- Rotate any passwords or API keys you created or knew, and tell the client.
- Cancel tools or subscriptions you were paying for on the client's behalf, after transferring what they need.
4. Finance
- Send the final invoice, including approved change requests and expenses.
- Settle deposits, prepaid retainer hours or credits.
- Stop recurring invoices and scheduled payment reminders for the ended work.
- Send a receipt or statement showing the account is fully paid.
5. Data and legal
- Confirm intellectual property has passed to the client, as the contract says.
- Agree what client data you keep, for how long, and delete the rest.
- Keep invoices and contracts for as long as your tax rules require.
- Note any ongoing confidentiality obligations from the contract or NDA.
6. Relationship
- Hold a short wrap-up call to review results and next steps.
- Ask for feedback, a testimonial and permission to use the work in your portfolio.
- Ask for a referral if the project went well.
- Set a reminder to check in after three to six months.
7. Internal wrap-up
- Run a short retrospective: hours versus estimate, what went well, what to change.
- Update your templates, pricing and SOPs with what you learned.
- Archive the project so the record is kept but out of the way.
Order matters in one place: transfer ownership of accounts to the client before you remove your own access, and confirm they can log in. Otherwise you risk locking everyone out of a domain or ad account.
Wrap-up email template
Send this after the final delivery, with the links filled in.
Hi [first name], Thank you for working with us on [project]. It's been a pleasure. Here's a summary of the handover: - Final files: [link] - Accounts transferred to you: [domain, hosting, analytics, ...] - Documentation and logins guide: [link] - Final invoice [INV-0057]: [paid / due on date] We've removed our access to [systems] and rotated the passwords we set up. If you'd like us to keep any access for support, just let me know. Two small asks: 1. Would you be happy to share a sentence or two about working with us? We'd love to use it on our site. 2. If you know anyone who needs help with [service], we'd be grateful for an introduction. I'll check in around [month] to see how things are going. In the meantime, you can reach me any time at [email]. Thanks again, [your name]
Data, records and ownership
Three things need a clear answer at the end of every engagement: who owns the work, what data you keep, and which records you must retain.
- Ownership. Many contracts pass rights in the final deliverables to the client once they have paid in full. Check what yours says and confirm it in the wrap-up. Our service agreement template uses this approach.
- Client data. Data protection laws such as the GDPR in the EU and UK GDPR say personal data should not be kept longer than needed. Other regions have their own rules. Agree what you will delete, such as customer lists, exports and access logs, and do it.
- Business records. Invoices and contracts usually have to be kept for several years for tax purposes, and the period varies by country. Keep them, and keep them separate from client working files you are deleting.
- Confidentiality. Obligations under an NDA or confidentiality clause often continue after the project ends. Make sure the team knows.
When the relationship ended badly
Not every project ends with a thank-you. When it does not, the checklist matters even more. Keep communication short and factual, confirm in writing what was delivered and what is owed, and follow the contract on handover and payment. Remove access on both sides promptly.
If the final invoice is unpaid, our payment reminder email templates cover the follow-up sequence. Be careful about withholding work or accounts the client has already paid for; get advice first if there is a real dispute.
Ending a retainer
Retainers need a couple of extra steps. Check the notice period in your agreement and confirm the last billing date in writing. Decide how unused hours are handled, whether they lapse, roll into a final month or are refunded, according to the contract. Then stop the recurring invoice so the client is not billed after the end date. A short summary of what the retainer achieved makes a strong close and a useful case study.
Loose ends across five tools, or one place to close the project
Offboarding usually means hunting through drives, chat channels, password managers and the invoicing app. In Arpixa, the client's files, deliverables, invoices and contract sit together, so the handover is a checklist rather than a search.
Final files
Source files
Client channel
Project tasks
Final invoice
ArpixaAll of it, connectedOffboarding in Arpixa
In Arpixa, a client's files, deliverables, signed contract and invoices live on the same client record, so you can check what was delivered, what was approved and what is still unpaid from one place. Deliverables approved through the client portal give you a written sign-off trail.
Automations can react when a project is marked completed, for example to send a thank-you note, assign a follow-up, or archive the project. Team and client access is managed in members and roles, which makes the access cleanup step easier to check.
Close every project cleanly
Start free in minutes, or log in to your Arpixa workspace. See pricing for plan details.
Data retention and ownership rules vary by country and contract. This checklist is general guidance, not legal advice. The pricing page is the source of truth for current Arpixa plan limits.
Frequently asked questions
What is client offboarding?
Client offboarding is the structured process of ending a project or client relationship: confirming the final deliverables, handing over files and accounts, removing access, sending the final invoice, deciding what data to keep, and closing the relationship on good terms. It is the mirror image of onboarding, and it matters just as much, because it shapes what the client remembers and says about you.
Why is client offboarding important?
A clean offboarding protects you and keeps the door open. It reduces security risk from leftover access, avoids disputes about what was delivered or owed, and makes sure you get paid in full. It is also the best moment to ask for a testimonial or referral, because the results are fresh. Clients who leave with a clear handover are far more likely to come back or recommend you.
How long should I keep client data after a project ends?
Keep what you need for legal and tax reasons, and delete the rest once it is no longer needed. Tax records such as invoices often have to be kept for several years; the period depends on the country, for example six years in the UK for many businesses. Under data protection laws like the GDPR and UK GDPR, personal data should not be kept longer than necessary for the purpose it was collected. Agree the approach with the client and write it into your contract.
How do you offboard a client when the relationship ended badly?
Keep it factual and follow the contract. Confirm in writing what was delivered and what is owed, hand over what the client has paid for, remove access on both sides, and send the final invoice. Avoid arguing in email. If there is a dispute about payment or ownership, keep records of the agreement, deliverables and correspondence, and get advice before withholding anything.
Should I give clients their source files?
It depends on what your contract says. Many agencies include final files by default and treat editable source files as an extra or as part of a full rights transfer. Whatever you decide, state it in the proposal or statement of work so it is not debated at the end. Handing over files usually happens after the final invoice is paid.