A client handoff isn't a contact-info transfer. The new consultant can have the right email address, the right calendar invite, and the right file folder, and still walk into the next call knowing less than the client does about their own account. What actually breaks a handoff is everything that was never written down in the first place.
The failure mode isn't missing files — it's missing judgment
When a consultant hands off a client — going on leave, scaling up and delegating, or ending their own involvement — the instinct is to package what's easy to package: deliverables, invoices, the project plan. That's the part that was always going to transfer fine. What doesn't transfer on its own is the judgment the outgoing consultant built up over months: which stakeholder actually decides, which one needs to be copied on everything even though they never reply, what got promised verbally on a call that isn't in any document, and what topic to avoid raising until the client raises it first.
None of that lives in a deliverables folder. It lives in the outgoing consultant's head, and if the handoff doesn't deliberately extract it, it leaves with them.
Four things to transfer beyond contact info
- Stakeholder dynamics.Not just who's on the account, but how they relate to each other — who defers to whom, who's quietly skeptical, who was brought in late and still doesn't fully buy in. A new consultant treating every stakeholder as equally warm will step on a relationship that took months to build.
- Unwritten preferences.The client who hates being cc'd on internal threads. The one who wants a Friday afternoon check-in even though it's never officially on the agenda. The one who reads every word of a report but never opens an attachment. These are small, and they're exactly the kind of thing a new consultant gets wrong in week one if nobody tells them.
- Sensitive history.A missed deadline that was smoothed over. A scope disagreement that got resolved but left residue. A prior consultant on the account who was let go for cause. The new consultant doesn't need the full story dramatized, but they need to know the terrain exists so they don't accidentally walk back into it.
- What's been promised but not yet delivered.The verbal commitment from a call three weeks ago. The "we'll circle back on that next quarter" that the client is quietly still expecting. Anything owed that isn't sitting in a formal deliverables list is the single most common thing that falls through in a handoff — because it was never written anywhere to fall out of.
A worked example
Situation: A consultant is going on eight weeks of leave and handing a marketing-strategy retainer client to a colleague.
Stakeholder note:"CMO is the sponsor but rarely engages directly — all real decisions run through her Director of Brand, who was skeptical of hiring outside help and needs to see rationale, not just recommendations, or he'll push back in the next review."
Preference note:"Client prefers a written summary before any call, sent at least a day ahead — she reads on her commute and doesn't like being surprised live."
Sensitive history:"Q1 deliverable slipped two weeks due to a data-access delay on their end. It was resolved without incident, but don't reference the old timeline in writing — they've moved on and would rather not revisit it."
Open commitment:"Verbally agreed on the June call to include a competitor messaging teardown in the Q3 report. It's not in the SOW. The client is expecting it anyway."
Hand off only the deliverables list and invoice history, and the incoming consultant walks in blind to all four of these — and the client notices within the first meeting.
Write it down before you need to remember why
The honest reason most of this context never transfers is that writing it down felt unnecessary while the relationship was still in one person's head. It only becomes urgent the week someone's leaving, which is the worst possible time to reconstruct it from memory. The fix is treating this as ongoing documentation attached to the account, not a one-time handoff memo written under deadline.
A lot of this overlaps directly with stakeholder mapping — who holds power, who holds interest, and how that's shifted since the engagement started. If that map already exists and has been kept current, the handoff shrinks to filling in preferences, history, and open commitments around a structure that's already there. The free Stakeholder Mapping Tool is a fast way to build that structure before you need it, not after.