Skip to main content

Client offboarding checklist

Work through handover, closeout, and relationship tasks when a client engagement ends. Each task has an optional note field for an owner, due date, or link — check items off as you complete them, then export the whole checklist (with your notes) to a branded PDF or a CSV to keep alongside the client file.

Frequently asked questions

Why revoke your own access instead of just leaving the project as-is?

Leftover access to a former client's accounts, hosting, or repositories is a liability for both sides — if something breaks or a breach happens later, you're a lingering suspect with credentials you no longer need, and the client has no clean record of who can get in. Revoking access as a deliberate offboarding step (rather than letting it lapse) protects your reputation and gives the client a clear security boundary.

When should I ask for a testimonial or referral?

Ask while the win is still fresh — right after final deliverables are approved and before the relationship goes quiet, not weeks later when the client has moved on mentally. If the project went well, this is also the natural moment to ask if they know anyone else who could use similar work, since a satisfied client is far more likely to make an introduction immediately after delivery than months down the line.

What counts as an 'asset' I need to hand over besides the final files?

Beyond the final deliverable itself, this includes source files (design files, code repositories, editable documents), any credentials you set up during the project (hosting, domain, third-party tool accounts), and account ownership if you created accounts on the client's behalf. Missing one of these is the most common reason a former client has to email you months later asking for something you should have handed over at closeout.

Share this tool