My Employee is LeavingRead the story
The relationships and history that never make it into a handover document.
When Someone Is Promoted, Who Inherits the Old Work?
A promotion is a real transition — it just does not look like one.
The old work is split three ways, and the reasoning that held it together is not.
Still in the building, and already out of reach.
The exception arrives, and nobody knows the rule that used to cover it.
In brief: what happens when someone is promoted internally?
The person stays but their old work loses its owner, and everyone assumes the context is still available because the person is.
- Access is mistaken for availability — until the new role fills the calendar.
- The old work is split across several people and the reasoning is not.
- Exception handling and escalation instincts were never on any checklist.
Who should sit the interview?
The person leaving the role, not the successor — the successor uses the report as their starting point.
- Captured while the old work is still fresh.
- The successor reviews and asks follow-ups against a written baseline.
Why do it if the person has not left the company?
Because attention moves on the first day of the new role, and the reasoning behind the old work goes with it.
- Still reachable is not the same as still responsible.
- Personal logins and permissions should not follow someone into a new role.
What should the manager do before the new role starts?
Treat the promotion date as a handover deadline, not just a start date.
- Book the sessions before the new role fills the calendar.
- Decide who inherits each piece of the old work, and tell them.
- Move personal logins and shared access off the individual.
What Breaks When Someone Is Promoted Internally?
The person stays, but their old work loses its owner the day the new role starts.
Three risks when someone moves internally
- Everyone assumes access equals availability. The person is still reachable, so nothing gets written down — until their new role leaves no time to answer.
- The old work is split, not handed over. Pieces land with three people and the reasoning that held them together is lost.
- Judgment leaves quietly. Exception handling, escalation instincts, and vendor history are never part of a promotion checklist.
What the Person Leaving the Role Actually Knows
Most of it has never been written down, because the person has always been at the next desk.
The context worth capturing
- What in the current role has no documented owner. The task done because nobody else knows it exists.
- The judgment calls a checklist would get wrong. Name the exception and how it was decided.
- Systems and permissions tied to the person. Accounts, dashboards, and shared logins that should not follow them into the new role.
- Who calls them directly instead of using the process. Internal and external — those calls will keep coming.
- What is half-finished, and what the plan was. State of play plus the reasoning behind the next step.
What the Interview Asks Before a Role Change
An internal promotion is a real transition, and the transition date is already confirmed.
How the session is run
- A structured voice interview while access is still live. The old work is captured before the permissions and the attention move.
- Facts the employee confirms or corrects. Nothing is recorded as context until the person who owns it agrees with it.
- A manager-reviewed report scored for completeness. The manager sees what was covered and what was not.
- Booked before the new role fills the calendar. The promotion date is the handover deadline.
What the Handover Report Delivers to the Successor
The deliverable is a structured handoff report the receiving manager can actually review.
What lands with the successor
- Completeness-scored, with open questions listed. It reduces surprises rather than pretending there are none.
- Handed to whoever inherits each piece. Split work still gets a named owner per part.
- A written baseline for follow-up questions. The successor asks against a document, not from memory.
- Reviewable before you commit. See a sample report and judge the depth first.
Five questions the person changing roles should answer
Ground to cover before the new role takes over their calendar.
-
✓
What in your current role has no documented owner?
The task you do because nobody else knows it exists.
-
✓
Which judgment calls did you make that a checklist would get wrong?
Name the exception and how you decided.
-
✓
Which systems and permissions are tied to you personally?
Accounts, dashboards, and shared logins that should not follow you into the new role.
-
✓
Who calls you directly instead of using the process?
Internal and external — those calls will keep coming.
-
✓
What is half-finished right now, and what was the plan?
State of play plus the reasoning behind the next step.
-
✓
Which relationships should be introduced rather than handed over?
The contacts who will keep calling you unless someone else is put in front of them.
How an internal handover runs
1
Promotion Confirmed
The start date for the new role sets the deadline for the old one's handover.
2
Sessions Scheduled
Booked before the new role takes over the calendar.
3
Context Captured
Undocumented ownership, judgment calls a checklist would get wrong, personal access, and work in flight.
4
Employee Confirms
The person confirms or corrects each extracted fact while the detail is still fresh.
5
Successor Reviews
A completeness-scored report with open questions listed, handed to whoever inherits each piece.
Frequently Asked Questions
Why bother when the person is still in the company?
Because their attention moves on the day the new role starts. The interview captures the reasoning while the old work is still fresh.
Who should sit the interview — the person promoted or their successor?
The person leaving the role. Their successor uses the report as the starting point for review.
Does this cost the same as a departure?
Yes — one $1,000 credit covers one transition, including the multi-session interview and the final report.
Will the report be complete?
It is scored for completeness and lists the questions still open. It reduces surprises; it does not promise there are none.
Is this a fit when the person is not leaving the company?
Fit is decided by what the vacated role knows, not how senior the promotion is. It's designed for operational knowledge — undocumented ownership, informal decision rules, and the escalation order people actually use; regulated records and controlled data stay out of scope.
Move the person without losing the context
Secure this transitionExplore More
Knowledge Transfer for Logistics & Distribution
Access a structured checklist and actionable insights for effective knowledge transfer in logistics when a key member departs.
Knowledge Transfer for Maintenance Managers
Maintenance managers carry an unwritten service history. A guided interview captures the equipment quirks and vendor reality before they go.
Step-by-Step Employee Knowledge Transfer During Offboarding
Stop the brain drain. Learn how our structured system captures critical tribal knowledge and reduces operational regret before they leave
Knowledge Transfer for Customer Success Managers
Document operational knowledge through our knowledge transfer checklist and interview questions for Customer Success Managers. Avoid operational loss.
Knowledge Transfer for Security Engineers
Learn essential knowledge transfer steps for Security Engineers to avoid operational disruptions during their departure.
Knowledge Transfer for Construction Superintendents
Access a comprehensive checklist for capturing critical knowledge when a Construction Superintendent leaves, ensuring smooth project continuity.