People & Exec SupportFree
Departing Employee Knowledge Transfer Plan
Reads the calendar, document ownership and system access together, then ranks the commitments and relationships none of those three lists names on its own.
River's knowledge transfer plan for a departing employee reads the calendar, document ownership and system access together, instead of one at a time. It ranks every recurring commitment, document and account by how many of those three independently confirm it. A meeting nobody else attends, a document nobody else can edit, and a login nobody else holds are three separate facts. Naming the same client twice over makes it a confirmed relationship, not a coincidence. The output is a handover document plus a task inventory with a receiving owner named on every row.
Asking someone to document their role captures what they consciously treat as their job: the live projects, the accounts on the dashboard. It rarely captures the quarterly reconciliation run four times without anyone else watching, the pricing sheet three colleagues quietly edit under her name, or the one vendor portal only she can log into. None of that reads as a task once it has become routine. Reading the underlying records instead of the memory finds it anyway, which is the same recognition-over-recall idea the exit interview programme applies after someone has already left.
Built for the manager or people ops lead handling one specific departure inside a fixed, short notice period, not an open-ended transition project. Run it the day notice arrives, before access starts getting revoked and while the person can still confirm what the data found. The role handover pack tracks what expires once the account is deleted; this is the faster read on what the person actually knows and who they actually deal with, which matters before that clock even starts running.
Most knowledge transfer plans ask the wrong question first
Every knowledge transfer template built for a departing employee starts the same way: sit the person down and ask them to walk through their role. That produces the work they think of as work, and it misses the work they stopped noticing years ago. A quarterly reconciliation run without incident since 2023 does not come up when someone asks what do you do, because by the fourth repetition it has stopped registering as a task at all. It shows up in a calendar as a recurring series whether anyone remembers to mention it or not.
The same blind spot applies to relationships, not just tasks. A customer success manager at a fictional company, Voss Analytics, was asked to name her key accounts before resigning and listed the twelve she talks about on weekly forecast calls. Reading her calendar, document activity and system access together found twenty-two accounts touched by at least one of those three signals, and nine confirmed by two or more of them at once. None of the nine were on her list, because none of them felt like an account to manage.
None of this needs a guaranteed notice period to work, and assuming two weeks is itself a mistake. California's own guidance on ending an employment relationship states plainly that unless the parties have agreed otherwise, no notice is required from either side, so whatever window actually shows up is what a plan has to fit inside. That is a sizing problem, not a checklist problem: rank what the data confirms first, and a plan built for fifteen days still works when only five are left, just shorter.
How it works
Send the exports
Calendar, document ownership and system access, in whatever format your own tools already produce them in.
Cross-reference the three
Every recurring meeting, document and account gets checked against the other two signals before anything is ranked.
Read the ranked list
Confirmed items come first, ahead of anything a single conversation would have surfaced on its own.
Assign a receiving owner
Every row in the task inventory gets a name from your list, or is marked unassigned instead.
What you get
- Cross-references calendar attendance, document ownership and system access instead of reading each list alone
- Flags recurring meetings where only the departing person is on the invite from your side
- Finds documents someone else regularly edits that only the leaver has permission to update
- Names the accounts or processes confirmed by two or three independent signals, not just one
- Builds a task inventory with a receiving owner assigned to every row, none left blank
- Sizes the priority list to the notice period you actually have, not a full audit
Common questions
What's different about this from just asking them to write a handover doc?
A self-written handover captures what someone consciously treats as their job. It rarely captures the quarterly task run for years without incident, or an account only confirmed by a meeting, a document and a login all pointing at the same name. Reading the records finds those. Asking does not, because they stopped feeling like tasks a while ago.
What if I only have one or two of the three data sources?
It runs on whatever you send. Fewer signals mean fewer items reach the two-source confirmation that pushes something to the top of the list, so the ranking leans more on what you and the receiving team already know. It states which signals were missing rather than filling the gap with a guess.
Do I need a full two-week notice period for this to work?
No. Two weeks is a workplace habit, not a requirement either side has to meet, so treating it as guaranteed is its own mistake. The output sizes to the days you actually have: confirmed items come first regardless of whether that window is fifteen days or five, and a shorter window just moves the cut line higher.
Does this replace an exit interview?
No, and the timing is why. This runs during the notice period, while the person is still reachable and the records are still current. The exit interview happens after departure and asks why people left across a team, rather than what one person needs to hand off before their last day.
How is this different from an access provisioning and deprovisioning checklist?
Access provisioning and deprovisioning revokes system access on the last day and confirms it actually happened. This runs earlier, while the person still has that access, and reads what the calendar and document activity say about commitments and relationships nobody flagged, which is a different problem solved before revocation starts.
What happens to a task nobody on the receiving list can take?
It stays on the sheet marked unassigned rather than getting attached to whichever name happens to be on the intake form. An unassigned row is a real gap a manager still has to solve. Quietly assigning it to someone who was never asked would make a handover look complete when it was not.
Departing Employee Knowledge Transfer Plan
Fill in the form and your workspace opens with the work already underway.