An account manager hands in their notice, and the agency's first reaction is usually about the team: who picks up the work, whether to hire, how to cover the gap. The client comes second. That order is understandable, and it is the reason so many accounts wobble in the three months after someone leaves.
Clients rarely leave because a person left. They leave because the handover showed them how much of the relationship lived in that one person's head, and because the first few weeks with someone new felt like starting again.
What actually walks out of the door
The documents usually survive. Contracts, scopes and invoices are on a drive somewhere. What leaves is the context around them, and it is worth naming, because nobody writes down what they do not know they know.
- Preferences nobody recorded: the approver who hates emojis, the brand manager who wants to see everything before their director does, the colour the client will never accept.
- Promises in progress: the discount mentioned on a call, the extra video agreed in passing, the report format they were told would change next month.
- History: why the last campaign was pulled, which competitor the client is sensitive about, what went wrong with the previous agency.
- Relationships: who on the client side actually decides, who is friendly, who is quietly unhappy.
- Access: logins, ad accounts, pages and tools that were set up in the leaver's name or on their phone.
The last point is the one that causes the most immediate damage. A page or ad account that was set up under a personal login, or a client chat that lives on someone's personal number, does not transfer when they leave. It goes with them.
The handover checklist
Start the handover on the day the resignation is accepted, not in the final week. A notice period that ends with a handover meeting is a notice period mostly wasted. Work through each client, one at a time, and ask the leaver to write rather than tell.
- Current state of every live project: what is in production, what is waiting on the client, what is due in the next thirty days.
- Anything agreed but not yet in the scope or the contract, however small.
- Every open question with the client, and who is waiting on whom.
- Every login, account and tool, with the owner checked. Anything in the leaver's name moves to the agency or, better, to the client.
- Every conversation channel: email threads, group chats, shared folders. Anything on a personal phone number gets a replacement before they go.
- Upcoming invoices and anything overdue, with the history of any payment conversations.
- A short note on each key contact: role, what they care about, how they like to be worked with.
Review the written handover with the leaver while they are still there to answer questions. The gaps in a handover are only visible to the person reading it, not the person who wrote it.
Tell the client early, and with a plan
The worst way for a client to learn their account manager is leaving is from the account manager, in passing, a week before they go. The second worst is from an automatic email reply after they have gone.
Tell the client within a few days of the resignation being settled, and tell them with the answer to the question they will ask next: who is taking over, and when. Frame it around continuity rather than apology. The client does not need to hear why the person is leaving. They need to hear that nothing they rely on is going to be dropped.
A client hears a resignation as a risk. The agency's job in that first conversation is to show that the risk has already been handled.
Then arrange a joint call, or better, two: one where the leaver leads and the successor listens, and one where the successor leads and the leaver is there only to fill gaps. By the time the leaver goes, the client should already have had a working conversation with the new person.
Protect the promises in flight
The moment a handover becomes visible to a client is when something agreed with the old account manager is not honoured by the new one. It does not matter whether the promise was sensible. From the client's side, it was the agency's word.
Go through the list of promises in progress with the successor and decide, deliberately, which ones stand. For anything the agency cannot honour, the successor should raise it with the client directly and early, as a considered decision, not let it surface as a missed delivery.
The first month after they leave
Keep a senior person closer to the account than usual for the first month. Not running it, but reading the updates, joining one call, and making it easy for the client to say if something feels off. Most clients will not complain about a handover. They will simply become quieter.
Watch the early signs: approvals slowing, shorter replies, a new contact appearing on the client side. Those are the signals that the relationship is being re-evaluated, and they are far easier to address in week three than in month three.
Make the next handover easier
Every difficult handover is evidence that the agency's memory lives in people rather than in the record. The lasting fix is to keep the notes, approvals, contacts, files and conversations attached to the client, as the work happens, so that when someone leaves the knowledge stays behind by default.
That is the reason Wiro is built around the client record, with projects, approvals, invoices and notes in one place, and why its client portal keeps the thread with the client attached to their record rather than to one person's inbox. Whatever system you use, the aim is the same: a resignation should be a staffing question, not a client risk.
