My Employee is LeavingRead the story
What a firm loses when the person the client trusted resigns.
When Consultants Leave, Relationships and Context Disappear
When key details slip through the cracks, project chaos follows.
Lost insights lead to missed deadlines and eroded client trust.
Inconsistent billing practices lead to financial losses.
Everything that mattered lived in one person's spreadsheets, and nobody else has them.
In brief: what happens when a senior consultant or account lead leaves?
In professional services, the deliverables live in shared drives — but the client goes to a person. When that person resigns, the relationship history, the unwritten preferences, and the 'how we really run this account' leave too. A structured interview captures it, confirmed by the person leaving.
- Client relationship depth: who trusts whom, and why.
- Commitments made verbally that never reached a statement of work.
- Engagement history: the decisions and near-misses behind the current plan.
What should a firm capture first when an account lead resigns?
The client-by-client picture, starting with the accounts where the relationship is the reason the work continues.
- Who the real decision-maker is on each account.
- What was promised outside the paperwork.
- Where each engagement stands right now.
Which client knowledge never made it into the shared drive?
The soft edges — preferences, sensitivities, and the history that explains why a client reacts the way they do.
- How each client likes to be communicated with.
- Old friction that still shapes the relationship.
- Internal favours and unofficial arrangements.
What do the first two weeks look like for the accounts at risk?
Get the account context out first, while there is still time to make an introduction.
- Book sessions before the diary fills with farewells.
- Prioritise the top accounts.
- Give every open question in the report an owner.
When the Relationship Walks Out With the Person
The notice lands. Every file is where it should be, which is exactly why nobody panics early enough.
Trust doesn't transfer with a folder
The client called them, not the firm. The next person inherits an email address and a rate card.
Corridor commitments
Something was promised on a call. It shapes the client's expectations and appears in no document.
Engagement memory
Why the scope changed. Which deliverable was quietly rewritten. What almost ended the relationship in year two.
What Client Files Don't Contain
Timesheets and deliverables record output. They don't record the relationship.
- Stakeholder map: who decides, who influences, who blocks.
- Commitments: what was said beyond the paperwork.
- Communication preferences: how each client wants to be handled.
- History: past friction and how it was resolved.
- Open threads: proposals, renewals, unresolved issues.
A guided offboarding interview goes after that layer, voice or text, the employee's choice. They confirm, edit, or reject every fact before it reaches a report.
Running Sessions Through a Billable Notice Period
A departing consultant is usually still billing. Multi-session by design: up to 10 structured topics, voice or text, pause and resume anytime, with a total time budget of up to roughly 300 minutes. Time is budgeted, not promised.
Short sessions between client calls, resumed the next day. Designed for real departures, not for a quiet week that never arrives.
What the Incoming Account Lead Receives
A structured handover report, manager-ready, in three parts. Illustrative lines below — what a report looks like, not a customer's report.
Confirmed facts
“The client's finance director signs off, not the programme manager; send figures a week early.”
Open questions and gaps
“Unclear whether the discount on the renewal was agreed in writing. Confirm with the client.” Gaps are an intended output; naming them reduces risk.
What was not covered
“Two smaller accounts were not discussed — no session reached them.” Stated plainly, so nobody assumes otherwise.
Five questions the interview asks
Open questions first, then follow-ups where the answer thins out.
-
✓
For each key client, who actually makes decisions — and who quietly influences them?
The map behind the org chart.
-
✓
What have you promised that isn't in a statement of work?
Commitments the client remembers regardless.
-
✓
How does each client prefer to be communicated with?
Cadence, tone, and what irritates them.
-
✓
What history explains how this relationship works today?
Old friction, resolved and unresolved.
-
✓
What's open right now — proposals, renewals, unresolved issues?
The threads someone has to pick up.
How a client handover runs
1
Notice lands
You book the first session before the diary fills up.
2
Sessions between client calls
Up to 10 topics, voice or text, paused when work needs them.
3
They confirm every fact
Each fact is confirmed, edited, or rejected by the consultant.
4
Report reaches the manager
Confirmed facts, open questions, what was not covered.
5
You assign the gaps
Every open question goes to a name.
Frequently Asked Questions
What do professional services firms lose most often in a departure?
Relationship context. Files and deliverables stay; the stakeholder map, the verbal commitments, and the history behind the engagement leave unless somebody asks in time.
Is this a fit when client matters are privileged?
Fit is decided by the role's knowledge, not the matters around it — client relationship history, delivery rhythms, and escalation paths are in scope, while privileged material and client records stay out of it.
The person is billing until their last day — is this realistic?
Multi-session by design: up to 10 structured topics, voice or text, pause and resume anytime, with a total time budget of up to roughly 300 minutes. Time is budgeted, not promised. Sessions sit between client calls rather than competing with them.
What does the incoming account lead get?
A structured handover report: confirmed facts in plain language, explicit open questions and gaps, and a section naming what was not covered. It reduces transition risk; it doesn't claim to cover everything.
See if this is a fit.
See if this is a fit.Explore More
Knowledge Transfer for Customer Success Managers
Document operational knowledge through our knowledge transfer checklist and interview questions for Customer Success Managers. Avoid operational loss.
When the Founder Hands Off Operations
Explore a detailed guide on handling knowledge transfer when your founder hands off operations, including crucial documentation strategies.
Knowledge Transfer for Quality Assurance Managers
A QA manager's real value is knowing which defect matters. A guided interview captures that judgment before they leave, confirmed by them.
Knowledge Transfer After a Sudden Resignation
Discover strategies for knowledge transfer after a sudden resignation, ensuring critical operational continuity and relationship preservation.
Knowledge Transfer for IT / Systems Admin
When your IT or systems admin leaves, the setup reasoning and vendor contacts go too. A guided interview captures that context, never the secrets.
Knowledge Transfer for Operations Managers
Secure critical knowledge from your departing Operations Manager using our comprehensive checklist and insights.