Virtual Assistant Client Offboarding Checklist: How to End a Retainer Without Burning the Bridge

A virtual assistant client offboarding checklist is the thing you do not have until the first time a retainer ends badly. The client says they are "pausing for a while," you stop getting tasks, and three weeks later you realize you still have admin access to their inbox, an unpaid final invoice, and a half-finished project nobody owns.

Most VAs have an onboarding process. Very few have the reverse. That gap costs real money and, worse, it costs the reference you would have gotten if the ending had been tidy. Here is the sequence that works, in the order it should happen.

Start with the notice, not the exit

Offboarding begins the moment either side says the retainer is ending. Your contract should already say how much notice is required, usually 14 or 30 days. If it does not, write down the agreed end date in an email the same day and ask the client to reply "confirmed." That one reply settles most later arguments about whether the last two weeks were billable.

Then ask what the client wants from the remaining time. Some want a full handoff to a new VA. Some want you to wind down quietly. Some want nothing and will ghost you. Knowing which one you have decides how much of the rest of this list you need.

Close out the hours before you close out the work

Reconcile the retainer. Pull the logged hours for the current period and compare them against what the retainer covers. If the client prepaid for 20 hours and you logged 14, decide now what happens to the 6. Refund, credit toward the notice period, or forfeit under your rollover policy. Do not leave it to be discovered. Clients remember an unexpected refund fondly and an unexpected "that's non-refundable" email for years.

If you have been tracking time loosely, this is where it hurts. Rebuilding a month from calendar entries and sent mail is miserable, and you will undercount. A clean time log makes this step a five-minute job instead of an evening.

Send the final invoice early. Do not wait until your last day. Invoice for work completed through the end date as soon as you can total it, with the reconciliation above attached. Final invoices have the worst collection rate of any invoice you will send, because the client no longer has an ongoing reason to keep you happy. Net-7 terms and a clear line item list help. Chasing a former client for $340 is a bad use of your week, so make it easy to pay in one click.

Hand back access in a specific order

This is the part that gets forgotten, and it is the part with actual liability attached. Make a list of every system you can touch for this client: email, calendar, CRM, social accounts, the shared drive, the password manager, the payment processor if you ever had view access, the project board. Then go through them one at a time.

For each one, do one of three things. Transfer ownership to the client, remove yourself, or confirm in writing that the client wants you to stay. Staying is a legitimate choice. A client who keeps you as a calendar delegate for a month while their new hire ramps up is fine. A client who has simply forgotten you are still in their Google Workspace is a security question they will not thank you for raising later.

Anything you created on your own accounts for them also belongs on this list. Templates in your own Notion, automations running on your Zapier plan, a scheduling link tied to your calendar. If it stops working the day you leave, say so out loud and either export it or give them a date.

If you subcontract any of this work to other VAs, tell them the end date too and close out their access in the same pass. A subcontractor with leftover login access to a client you no longer work for is your problem, not theirs.

Write the handoff document

One page. Not a manual. It should say what recurring tasks you were running and on what schedule, where the files live, which logins exist and who owns them now, which tasks are mid-flight, and who the contact is for each vendor or tool. A new VA, or the client themselves, should be able to read it in ten minutes and know what to do on Monday.

The temptation is to skip this because the client is leaving anyway. Do it. It is the single most visible piece of evidence of how you work, and a good handoff document gets forwarded. Several VAs I know have picked up referrals from the person who inherited their handoff doc, not from the client who left.

Decide what you want after the end date

Retainers end for boring reasons far more often than bad ones. Budget cuts, a hire, a pivot, a founder who wants to try doing it themselves for a quarter. A good chunk of those clients come back. Make that easy.

Say so plainly in your closing email. Something like: "If you want to restart, the same rate holds for 90 days and I can usually pick up within a week." Do not write a paragraph about how much you enjoyed working together. One sentence is enough. Then ask for a short testimonial or a LinkedIn recommendation, once, and only if the work went well. If it did not, skip it and move on.

What the checklist looks like in practice

Compressed, the order is: confirm the end date in writing, reconcile hours, send the final invoice, list and transfer access, write the handoff page, tell any subcontractors, send the closing email, set a calendar reminder 60 days out to check in. That is eight items. None are hard. The reason they get skipped is that nobody sits down to do them while a client is leaving, because leaving feels like a non-event until it is a problem.

The weak point of any checklist is that you have to remember it exists. Keep it as a reusable template somewhere you will actually open, not buried in a folder from 2024. And be honest with yourself about the 60-day check-in. Most people write it down and never do it. If you will not, delete it and do not pretend.

If you want the hours, the final invoice, and the client's shared files to live in one place so the reconciliation step stops being archaeology, that is what FocalVA for virtual assistants is built around. It will not write the handoff doc for you, but it does make the numbers behind it easy to pull.