Hand off a client without the client feeling handed off
When an account manager leaves or changes, the client's experience is the test. This is the checklist for a handoff that reads as continuity, not disruption.
Overview
This is a checklist for transferring a client relationship from one team member to another — because someone left, changed roles, or the account was reassigned. It covers what context needs to move (not just tasks, but the unwritten stuff: how the client likes to communicate, what's sensitive, what's already been promised), how to introduce the new point of contact, and what not to say to the client during the transition.
Why it matters
Clients don't judge a handoff by whether the work continues — they judge it by whether they feel like they have to re-explain themselves. A handoff that only transfers task lists loses the informal context that made the relationship work: the client's actual preferences, the small commitments made in passing, the history of what's already been tried. Losing that context is what makes clients feel like they've been dropped, even when deliverables are still on time.
Who should use it
- Agencies where an account manager or project lead is leaving, changing roles, or going on leave
- Team leads reassigning accounts as the team grows or client load rebalances
- Anyone managing a handoff where the outgoing person has more context than exists in written notes
How to use it
- 1
Have the outgoing owner do a context dump first
Capture the unwritten details — communication style, sensitivities, informal promises — before anything else happens.
- 2
Introduce the new contact while the old one is still involved
A joint call or a warm email introduction reads as continuity; a cold handoff reads as disruption.
- 3
Watch the first two client interactions closely
The first response time and first deliverable under the new owner are what set the client's impression of the transition.
What's inside
1. Document the client's communication preferences and quirks
2. List any informal commitments not captured in the project record
3. Flag anything sensitive: past complaints, near-misses, pricing history
4. Introduce the new contact before the old one disappears
5. Confirm the client knows who to reach and how
6. Avoid phrases that suggest instability or apology
7. Check in after the first deliverable under the new owner
Get it free
- A context-transfer worksheet covering both formal history and informal preferences
- An introduction email template for the new point of contact
- A list of phrases to avoid saying to the client during the transition
- A first-two-weeks checklist for the incoming owner
Common questions
Should the client be told why the handoff is happening?
A brief, neutral reason is enough — "[Name] is moving into a new role and [Name] will be your main contact going forward." Avoid over-explaining or apologizing, which reads as instability.
What context matters most beyond the project file?
The things that never get written down: how the client likes to be communicated with, what's been promised informally, and what topics are sensitive. This is usually the difference between a smooth and a rocky handoff.
Should the outgoing team member still be reachable for a while?
A short overlap window, even just for questions, reduces client anxiety. But keep it time-boxed — an indefinite overlap undermines the new owner's authority with the client.
What's the biggest mistake agencies make in a handoff?
Treating it as an internal admin task instead of a client-facing moment. The handoff itself is part of the client's experience of the agency, not background logistics.
Run the rest of your agency from one place
This resource is free. Sarion is where the day-to-day client work happens next.