How to Fire a Client as a Virtual Assistant Without Losing the Referral

Most advice about firing a client treats the conversation as the hard part. It is not. The conversation takes ten minutes and you will have rehearsed it for a week. What actually goes wrong happens in the two weeks after, when the work is winding down, nobody is quite sure what you still owe, and a final invoice is sitting in an inbox belonging to someone who has stopped caring whether you get paid.

Chasing overdue invoices was part of my own work alongside virtual assistant and BPO roles, and it teaches you what a bad ending looks like from the receiving end. The pattern barely varies. People who exit badly are almost never rude about it. They improvise the ending, and improvising is what leaves files scattered, access half returned and money uncollected.

There is one order of operations that protects both your money and your reputation, and it is the same order whether you are leaving a good client or a bad one.

Table of contents

The exit is the part people talk about

Nobody tells another business owner about the month you cleared their inbox on time. They tell them how it ended.

That is worth sitting with, because it inverts the instinct. When a relationship has gone sour the temptation is to do the minimum and get out, and the minimum is precisely what creates the story. Think about the complaints that circulate in this industry, in both directions. Nearly all of them describe an ending: a folder nobody could get into, a login still active months later, a bill that turned up long after anyone expected one.

Leaving well advertises you for free, and for a business built on people recommending you, it is the cheapest protection you can buy.

Two ways it starts, one process after that

Either the client ends it or you do. Only the first message differs. Everything after is identical, which is useful, because the version you will improvise worst is the one you least want to get wrong.

When the decision is yours, give notice on whatever terms your agreement sets. Fourteen days works for ongoing engagements, and it is the number I would write into a contract if you have not got one yet. Say three things and stop: that this is notice, which day is your last, and what carries on until then.

Hi Dan,

Treat this as my formal notice under our agreement. My last day will be Friday 3 April.

Nothing changes before then. Scheduling, the weekly invoicing run and the Monday summary all carry on as usual, and you’ll have a written handover plan from me in the next few days so nothing is waiting on me at the end.

Happy to talk it through whenever suits you.

Notice what is missing. No grievances, no apology tour, no account of what went wrong. That email is going to be kept, and at some point it will be forwarded to somebody. If they want reasons, give them on a call.

This is the hardest instruction in the whole process to follow, because by the time you are writing a notice email you usually have a case to make. Make it to a friend instead.

Pin the end date the same day

Whatever got said on a call, put the date in writing before you go to bed. One line does it: “Just to confirm in writing, Friday 3 April is my last day under the notice period.”

If the client was vague, and they often are, pin it down yourself rather than waiting for them to. “Let’s wrap up this month or so” is not an end date. Choose the specific day, state it, and let them correct you if they disagree.

Vague endings produce vague invoices, and a vague invoice is the kind that sits unpaid without anyone deciding not to pay it. Every step below hangs off that date, which is why it goes first.

Say what will not be finished, before it is obvious

Within a couple of days of setting the date, send a short list in two halves: what you will complete by the end date, and what you will not.

The second half is the one people skip, and it is the one that matters. An unfinished task you name in advance is a handover item. The same task discovered three weeks after you have gone is a story about you being unreliable.

By 3 April I’ll have March invoicing closed, the calendar cleared through to the end of April, and every weekly summary filed. What won’t be finished is the vendor reconciliation, which is roughly halfway. You’ll get the spreadsheet and my working notes so it is straightforward for whoever picks it up.

Ask for a reply confirming it. That reply is what protects you later when someone misremembers a promise you never made. You do not need it often. When you need it, nothing else substitutes.

Hand over more than they expect

Three things move across: the work itself, a written explanation of how it runs, and the keys. The test is whether a stranger could pick it up on Monday without needing to message you once.

Files belong somewhere the client already controls, not spread through folders that live under your account. Name that location when you write to them at the end. If everything sat in their systems the whole time, one sentence covers it and you are done.

Documentation is a short note on how the repeating work actually runs. Which rules sort the inbox and what they are meant to catch. Where the templates sit. What the reports look like and where the old ones are filed. It does not have to be polished. It has to exist.

This is the single strongest referral generator in the whole process, precisely because nobody expects it. A departing contractor who leaves instructions behind is rare enough to be remarked on.

Access splits in two and both halves should be spelled out. Going back to them: the mailbox seat, any admin login, the scheduling tool, every account opened on your behalf or shared with you. Coming off your side: their credentials deleted from wherever you keep them, shared folders disconnected, every device signed out. Mention that second half in your closing message. Clients seldom think to ask, and telling them before they wonder costs you a sentence and buys a lot of reassurance.

Do not hold anything hostage

Sitting on files or logins until the money arrives feels like leverage. In practice it is the quickest route from a billing dispute to a review everyone can read, and it rarely even gets you paid.

What actually protects you is paperwork and sequence: a date on record, a list they replied to, and the invoice going out while you can still reach the systems. Hand everything over even when the exit is ugly. Especially then.

Send the final invoice before you are locked out

The final invoice bills finished work plus anything started and not completed by your last day. That half-done reconciliation appears on it, and it appears without a fight, because you put it in the deliverables list a fortnight earlier. Nothing on the bill is news to them.

Timing is the part most people get wrong. Send it the day before you finish, while the handover is visibly still moving, rather than once everything has landed.

The moment your access is gone and everything has been delivered, any urgency about paying you evaporates. Not through malice. You have simply stopped being a working relationship and become a line in an accounts payable queue. An invoice that arrives while you are still visibly finishing the job gets read as part of that job. One that arrives afterwards gets filed.

If you expect the invoice to be disputed, this ordering matters more, not less.

The closing message

This one goes out on your final day, once everything is handed across and the invoice has already gone.

Hi Dan,

Last day today, so here is where it all stands.

Everything sits in the shared folder on your side, labelled so you can find things without asking me: the how-to notes, the invoice templates, every working file. Your credentials are deleted from my end and I am signed out of all of it. Yesterday’s invoice was the last one, running through today, and it includes the reconciliation I flagged a fortnight ago.

Good year. I am glad the scheduling finally settled. If cover or a one-off comes up later, I am around, and if anyone you know is buried in admin I would be grateful for the introduction.

All the best,

The line about the door being open is not manners. It is the whole reason for writing carefully. Clients come back, and clients refer, and both are decided by the taste the last message leaves.

When the exit was a bad one, the closing message gets shorter, not colder. Lose the sentence about being glad how it went. Say where everything is, say thank you, and stop. No referral request either, because asking a client you have just walked away from for an introduction reads as either oblivious or sarcastic. On a bad ending, short and correct is the whole win. You are not repairing anything. You are closing it tidily enough that there is nothing worth repeating.

When you should not fire them yet

Two situations look like a client problem and are not.

You never set the boundary. If scope crept and you absorbed it silently for months, the client has no idea anything is wrong. That is worth one honest conversation before an exit, because a client who did not know is often a client who adjusts.

The real problem is the rate. Sometimes the work itself is fine and what you actually resent is being underpaid for it. Asking for more money is a smaller conversation than ending the relationship, and if the answer is no, you have learned something and can leave without wondering.

Neither applies to a client who is abusive, who does not pay, or who agreed to something and then denied it. Those you end.

The checklist

Work through it on every exit, warm or otherwise. A friendly one is an hour’s work. The difficult ones are why it is written down.

1. A specific last day, put in writing and sent
2. Both halves of the deliverables list out, with their reply on record
3. Everything gathered into a location on their side
4. A written note covering how the repeating work runs
5. Every seat, login and share given back
6. Your own side cleared: credentials gone, folders disconnected, sessions ended
7. Invoice out before you lose access, unfinished work included
8. A last-day message: where things stand, thanks, and a door left open

If you would rather not build the paperwork behind this from scratch, the client offboarding process, the service agreement that sets the notice period, and the late-payment sequence that backs the final invoice are all in the Virtual Assistant Business Operations Pack. The wider picture of where offboarding sits is in the six stages every client engagement runs through.

Frequently asked questions

How much notice should I give a client? Whatever your agreement says. If you do not have one, fourteen days is reasonable for ongoing work and gives both sides time to hand over properly. Put the specific last working day in writing the same day you give notice.

Do I have to tell the client why I am leaving? No, and the notice email is the wrong place for it. State the notice, the date, and what happens in between. If they ask why, answer on a call. Written grievances get forwarded and reread; spoken ones usually do not.

Can I bill for work I started but did not finish? Yes, if your agreement covers work in progress, and it should. The way to make that painless is to name the unfinished work in your deliverables list two weeks before the invoice, so nothing on the final bill is a surprise.

Should I withhold files until the last invoice is paid? No. It seldom gets you paid and reliably gets you complained about in public. Hand it all across, and lean instead on having the date on record, a list they replied to, and an invoice that went out while you could still reach the systems.

What if the client fires me instead? The process does not change. Confirm the end date in writing, send the deliverables list, hand over properly, invoice before you are locked out, and close warmly. A client who ends an engagement well still refers people.