Client offboarding checklist: the exit that feeds the pipeline

Every client relationship ends in one of three ways — the work completes, the retainer pauses, or someone calls it quits — and almost every small team treats all three the same way: a final invoice, an awkward goodbye, and a folder everyone is afraid to delete. Six months later the same client emails a "quick question" that is not in scope, you answer it because the files are still on your server and the story of who-owes-what is unwritten, and the exit quietly costs you support hours, access risk, and the referral the relationship should have produced.

This is the checklist: money before feelings, a handover pack with a defined shape, access cut off in the right order, the referral ask made at the moment goodwill peaks, and a keep-warm file that turns ended clients into the cheapest pipeline you will ever have.

1. The three exits, and why the exit type sets the checklist

Before anything else, write one sentence in the client's file: which exit is this?

• The completion exit — the project shipped, the goal hit, the contract's final milestone closed. Offboarding here is a celebration with paperwork: the final invoice and the handover pack, plus the referral ask at its most natural moment ("now that it's live, who else needs this?").
• The pause exit — budget freeze, hiring change, reorganization: the relationship isn't dead, it's sleeping. This is the pause-not-lapse path from the renewal checklist: agree the pause terms in writing (duration, holding rate, restart trigger), skip the hard access cut-off, and keep the keep-warm cadence running. Half of paused clients restart within a year — if you didn't make the exit feel final.
• The ended exit — fired, outgrown, or drifted away. This is the full checklist below: everything gets a date, every access gets cut, and the goodbye is scripted so it can't be skipped.

• Write the exit type down before doing anything else. The single most expensive offboarding mistake is running the full cut-off on a pause (killing a sleeping relationship) or a soft goodbye on an end (leaving zombie access and open invoices).
• The exit type decides who leads. Completions lead with delivery ("here's everything, it's yours"); ends lead with closure ("here's what happens after Friday"); pauses lead with continuity ("here's exactly how this resumes").

2. Money before feelings: the final invoice

The final invoice goes out within 48 hours of the exit conversation — not "when we wrap up the last bits," not "end of month." Every day between the goodbye and the invoice converts billed work into a favor, and favors don't survive a client's finance department.

• The final invoice names itself. "Final invoice — engagement complete 30 Sep" on the face of it. An invoice that looks like every other invoice gets paid on the normal cycle; an invoice that says FINAL gets prioritized, and it closes the account in their AP system instead of leaving it open.
• Hold-backs get resolved, not discovered. Any outstanding change orders, pass-through costs, or unused retainer hours are listed on the final invoice or explicitly waived in writing. A $90 pass-through discovered in November on a September exit reads as sloppiness, not arithmetic.
• Refunds and credits are decisions, not defaults. If unused hours or prepaid months are refundable under the contract, issue the credit memo in the same 48-hour window. Paying what you owe fast is the cheapest trust you will ever buy — and the exit is when the client tells colleagues what you're like.
• Payment terms stay the same terms. A final invoice is not an apology invoice. If the engagement was net 14, the final invoice is net 14, chased by the same dunning ladder as any other invoice. Bending terms at the exit teaches clients that the terms were negotiable all along.

3. The handover pack: one folder, four things

The handover pack is what turns "we can't leave, they'll be lost without us" into "here is everything, in one folder, yours." It also ends the zombie support: a client with a complete pack has no reason to email you, and a client without one has every reason.

• One folder, four things, no more. (1) The files — every deliverable, final versions only, named by the same convention you promised in the SOW. (2) The credentials — domains, hosting, ad accounts, analytics, all transferred to ownership the client controls, passwords handed through a password manager share, never in the pack itself. (3) The one-page map — what everything is, where it lives, who hosts it, when things renew. (4) The maintenance reality — one honest paragraph: what breaks without attention, and how often.
• The map is the difference between offboarding and abandonment. Dumping 300 files in a folder is abandonment. The same 300 files with a one-page index that says "the site lives on X, renews in March, the person to call is Y" is a professional exit — and it's the page that gets forwarded when someone asks the client "who built this?"
• Transfer ownership, not access. Wherever a contract allows, domains, ad accounts, and analytics move to accounts the client owns, with you removed afterward — not the reverse. "You access our stuff" is the root of every post-exit hostage story on both sides.
• Send it once, marked final. "Attached is the complete handover pack. This folder is everything; nothing lives outside it on our side." One send, one archive stamp, and the pack itself sets the boundary you'd otherwise have to enforce in conversation.

4. Access cut-off order: last in, first out

Access gets revoked on a schedule with an order, not in a cleanup mood weeks later. The rule is last in, first out: whatever you touched most recently (and therefore could still act on) gets revoked first; what you only ever read gets cut last.

• The cut-off date is in the exit conversation. "Our access ends 14 days from Friday" — said once, on the record, kills the slow-motion access drift where your agency is quietly still an admin of a client's Google Analytics in March.
• Order of revocation: payment and billing access first (nobody should be able to spend the client's money after the last invoice), then publishing and admin rights, then write access, then read-only last. Each removal gets a one-line log entry: account, role removed, date.
• Shared secrets rotate the same day. Any password the client's team knew, the client rotates. Any password only you knew dies with the transfer. This is the same discipline as the secrets rotation checklist — the exit is just the rotation with a witness.
• Confirm in writing, both directions. The pack send and the access cut-off each get a two-line confirmation email. "Access removed as of the 14th, per our conversation" is the sentence that prevents both the security audit finding and the awkward "can you just look at one thing" email.

5. The exit conversation that isn't a goodbye

The end of an engagement is the highest-goodwill, lowest-stakes moment in the whole relationship — no live work to judge, no invoice anxiety, no proposal pressure. It is the best referral window you will ever get, and most teams spend it mumbling "let's keep in touch."

• Ask while it's still warm, not in a "staying in touch" email later. The ask rides the handover send: the work is delivered, the gratitude is genuine, and the three-part referral ask (thanks tied to a real outcome, one named person, an easy exit) fits in the same email as the pack. An offboarding referral ask converts two to three times better than the same ask six weeks later, when the engagement has gone cold.
• The testimonial ask is one sentence with an out. "If you'd send two lines I could quote, that would genuinely help — no worries if not." Two lines is a two-minute job; a blank-page "write us a testimonial" is a never.
• The end-of-call script, thirty seconds: "Everything's in the pack, access is cut as of the 14th, and the final invoice is with your finance team. One last thing — you mentioned [peer company] was going through something similar. Want me to intro myself, or would you rather forward the note I've drafted?" Either answer produces a pipeline event; neither costs you anything.
• Leave the door open in one specific sentence, not a vague one. "If [the thing you know is coming — the migration, the launch, the audit] lands next quarter, the fastest version of this is a two-week refresher" is a door. "Let's definitely work together again" is noise.

6. The keep-warm file: the 90-day return path

An ended client is not a lost client; they are a prospect who already trusts you and hasn't been marketed to in months. The keep-warm file is a single row per offboarded client, reviewed in the same weekly block as the win-back sequence.

• The row has five columns: exit date, exit type (completion / pause / ended), the one thing they'd need next (written during the exit conversation — "they'll hire in-house," "the replatform lands in spring," "budget returns in Q3"), last-touch date, next scheduled touch.
• Two touches a year, both worth opening: the "this reminded me of you" note (a genuine artifact — a benchmark, a change in their space, a piece of the old work in a new context) and the anniversary check-in. Fourteen months after a clean handover, "how's the new setup holding up?" reads as care; anything resembling a newsletter reads as marketing.
• The trigger column does the selling. When the thing you predicted happens — the replatform ships, the in-house hire leaves, the audit lands — that's not a cold outreach, that's the follow-up you promised. Clients who return this way come back for projects, not rate negotiations.
• Pause rows get a heartbeat instead of a pitch. For paused clients, the touch is a two-line "still fine to stay paused, here's the restart link" at the pause midpoint. The pause survives on feeling held, not on being chased.

7. Worked example: the nine-client consultancy

A nine-client product consultancy, four exits a year, offboarding handled the old way: final invoice whenever the owner got to it, files in a shared folder named "FINAL_final_v2", access cut whenever someone noticed, goodbye email optional. The visible costs: roughly eleven hours a month of out-of-scope "quick question" support from former clients, two domains the agency still technically held a year after exit, and one referral in three years.

One year after the checklist went live:

• Exit support fell from ~11 hours a month to under 2. The handover pack's one-page map answered the questions that used to arrive as emails; the marked-final send set the boundary the owner used to have to defend in conversation.
• The referral ask at handover produced four introductions in a year — from four exits. The same ask, previously made never or too late, had produced one lead in three years.
• One ended client came back as a $14k project when the predicted replatform landed, five months after a "how's the new setup holding up?" touch that cost ninety seconds to send.
• The zero-dangling-access audit passed first time: the one-line revocation log meant the annual security review took an afternoon instead of an archaeology dig.

Nothing about the delivery changed. The only change: the exit became a designed event with a money step, a handover shape, a cut-off, an ask, and a return path — instead of a fade-out that cost a little every month.

8. Five weekly numbers

• Final invoice within 48h (exits invoiced inside two business days / all exits — target: 100%; every late final invoice is a favor you didn't mean to give).
• Handover completeness (exits with the four-part pack sent / all exits — the pack is the difference between offboarding and abandonment; below 100% means exits are being improvised).
• Dangling access age (days from exit date to confirmed cut-off, oldest open item — target: under 14 days; this number is your security audit finding in waiting).
• Exit referral rate (introductions received / exits — healthy band 30–50%; near zero means the ask is being skipped in the exit conversation).
• Return rate at 12 months (ended or paused clients with a paid engagement within a year / all exits — 10–20% is a pipeline; zero means the keep-warm file is a graveyard).

Keep reading

The offboard is the last path of the retainer renewal checklist (decide it in week one of the renewal runway, not in the last week of the term), and the referral ask it rides on is engineered in the referral request sequence. For clients who left badly or silently, the win-back sequence for churned customers is the second-chance ladder the keep-warm file hands off to. And the mirror image — cutting off a vendor instead of a client — lives in the vendor offboarding and data-deletion checklist.

This checklist is part of the kit line

This checklist is part of the Hive80 Lab ops kit line — field-tested, instantly downloadable:

• The First 30 Minutes — free incident quick-start
• Ops Field Cards — 12 printable incident checklists — $4
• Ops Starter Kit — full incident-response kit for small teams — $14
• Ops Mega Bundle — all 5 kits in one download — $29