Account manager handover: how to transfer client knowledge without losing it

The account manager handover problem nobody talks about

When an account manager leaves, agencies focus on the wrong things. They worry about the salary replacement cost, the recruitment timeline, the onboarding. These are real problems. But the most expensive thing that happens — the thing that actually kills client relationships — is what doesn't transfer.

The knowledge.

Not the data. Any reporting tool can show you last month's numbers. The knowledge that doesn't transfer is everything else: what the client actually cares about, what was promised in the October report and never followed up on, what the CFO said on the March call that changed the entire strategy, which recommendations are still outstanding, what language the client hates.

That knowledge lives in one person's head. When they leave, it goes with them. And the incoming account manager — no matter how experienced — starts from scratch.

What "starting from scratch" actually looks like

The new AM reads the last three reports. This gives them the recent data — sessions, CPA, ROAS, what happened last month. It does not give them:

• The goal set in January that hasn't been hit yet
• The promise made in the March report to fix mobile CPCs — which was partially addressed but never formally closed
• The fact that the MD is data-literate but the CFO isn't, and reports need to lead with cost per lead in plain English
• The landing page recommendation from April that the client hasn't implemented yet but keeps asking about
• The budget cut in September that makes the year-on-year comparisons misleading

The new AM writes the first report. It's technically correct. It covers the data. But it feels disconnected — generic, like something produced by someone who doesn't know the client. Because it is.

The client notices. They don't always say anything. But they start to feel like they're not being managed. That feeling is the beginning of churn.

The handover that went differently

This is a composite scenario, but it's based on exactly the kind of situation agencies face every quarter.

An account manager had been managing a home improvement client for eight months. Strong relationship, detailed knowledge, good results. She took a role at a different agency. Two weeks' notice.

Under the old process, this would have meant a frantic handover document, a couple of calls, and a new AM trying to piece together eight months of context from a collection of reports, a Notion doc, and whatever survived in the outgoing AM's inbox.

Under the new process — using NarratorHQ — the incoming AM opened the client's Intelligence tab on day one. What they found:

The first report the new AM sent — generated automatically from this context — referenced the outstanding landing page recommendation, updated the progress toward the Q3 goal, and led with cost per lead because it knew the CFO was the decision maker. The writing framing was plain English throughout.

The client's response: "Great report as always."

They never knew the AM had changed.

Why most agency handovers fail

It's not because account managers don't care about the clients they're handing over. Most do. It's because the systems agencies use to document client knowledge are inadequate for the actual depth of what needs to be transferred.

A Google Doc handover note covers the obvious things. It doesn't capture the texture of the relationship — the things the outgoing AM knows implicitly but wouldn't think to write down because they're just part of how they talk to this client.

The most important client knowledge is the knowledge that feels so obvious to the person who has it that they don't realise it needs to be documented.

The only way to solve this is to make knowledge capture automatic — not a separate task that happens during a handover, but something that builds continuously from the work that's already being done.

What needs to be captured — and when

Most agencies think about handover documentation as something that happens at the end of a relationship, when someone is leaving. This is backwards. By the time you need it, it's too late to do it well.

Client knowledge should be captured as a byproduct of normal account management work:

• After each client call: any preference, concern, or priority the client expressed that changes how you'll approach the account
• When each report is written: any promise, recommendation, or commitment that should be tracked into the next report
• When a campaign changes: any budget, tracking, or structural change that should be flagged in future period comparisons
• When something works: the win, the specific action taken, the improvement achieved — recorded for longitudinal reference

If this happens consistently, the handover document writes itself. The incoming AM doesn't need a long brief. They need access to the accumulated context.

The real cost of knowledge loss

Agencies tend to measure account manager turnover in terms of recruitment cost and onboarding time. These are visible, quantifiable numbers. The invisible cost — the one that doesn't appear on any spreadsheet — is what happens to the client relationships during and after the transition.

A client who feels that their new account manager doesn't know them reassesses the relationship. Not dramatically, not immediately — but gradually. The questions get slightly harder. The calls feel slightly more transactional. The renewal conversation that would have been straightforward becomes a negotiation.

Over a book of business, even one or two client losses attributable to poor handovers has a compounding effect on annual revenue. The cost is real. It just doesn't show up in the line labelled "account manager turnover."

What good looks like

The goal of an account manager handover shouldn't be "the new person gets up to speed within a month." That's the floor. The goal should be: the client doesn't notice.

That's achievable. But only if the knowledge that makes an account manager good at their job for a specific client is stored somewhere outside their head — and accessible from day one to whoever picks it up next.