A knowledge transfer plan names what only one person knows, who needs to know it, how it will be captured, and by when. It is a schedule with owners. Most plans fail for one reason: they list responsibilities and never say who is capturing what, on which day.
Below is what goes in one, how to decide the order, and a template you can copy.
Download the template (Markdown) — seven sections, no signup.
When do you need a knowledge transfer plan?
Whenever a responsibility rests on one person. A resignation makes that urgent, not true.
The obvious trigger is someone leaving: a resignation, a retirement, an internal move. The less obvious ones matter more, because nothing forces the work. A long leave. A reorganisation. One person who has quietly become the only one who can run something. If you can name the person whose absence would stop a process, you already need the plan. Writing it while nobody is leaving is far cheaper than writing it in a notice period.
What goes in a knowledge transfer plan?
Seven sections. Each one answers a question the next person will ask.
- What only this person does. Not the job description — the responsibilities that would stop if nobody picked them up. Rank them by how quickly the business notices.
- What kind of knowledge each one holds. The sequence and its dependencies, the judgment calls, the traps, the reasons behind the rules, and the people to contact. Ask for these separately or you will get the sequence and nothing else.
- A schedule. Short sessions across the notice period, with dates and names.
- Who else to ask. At least one colleague per topic who can corroborate the account or disagree with it.
- Where the answers land. The document, its location, and who owns it afterwards.
- What is still unresolved. Disagreements and unanswered questions, listed rather than smoothed over.
- How you will know it worked. A dry run, before the last day.
How do you decide what to transfer first?
Rank by concentration, not by importance.
The instinct is to start with the most important work. That is usually the work several people already understand, precisely because it matters. Start instead with whatever rests on one person — knowledge held by one head is the knowledge that leaves. A critical process three colleagues can run is a lower risk than a minor one only the leaver knows.
Two questions rank a list quickly. How fast does the business notice if this stops? And how many people can do it today? Anything that is noticed within a week and known by one person goes first, and everything else can wait for the second pass.
Who owns the plan?
The manager. Not the person leaving.
Someone working a notice period cannot chase their own handover, and a plan owned by the departing person leaves when they do. The manager sets the schedule, books the sessions and decides when a topic is finished. The leaver’s job is to answer well, which is difficult enough.
Name a successor if you have one. If you do not, name an interim owner anyway — knowledge transferred to nobody in particular is knowledge transferred to nobody.
Why do most plans still fail?
Because they ask one person to write, and stop at one account.
Two failure modes account for most of it. The first is asking someone to document their own job. Describing work you have internalised is a different skill from doing it, and the result is a sanitised procedure without the judgment underneath. Asking questions produces better answers than requesting a document, and it takes less of their time. The handover interview questions are a starting set.
The second is stopping at one person. Ask two colleagues the same question and you learn which parts they agree on, which rest on one account, and where they quietly disagree. Two experienced people applying different thresholds, each certain they follow the same policy, is common and almost never visible until somebody asks both. That disagreement is worth more than either answer alone.
How do you know the transfer worked?
The successor runs the task unaided, once, before the last day.
Have the person leaving available but not intervening. Whatever the successor has to ask about is a gap you still have time to close. That is the point of the dry run happening a fortnight early, rather than the day after the leaver’s badge stops working. Nothing else tells you whether the transfer landed. A signed-off document proves somebody wrote it.
The template
Seven sections, in Markdown, free to copy. No signup and no email.
Download the knowledge transfer plan template
Keep it wherever your team already reads things. A plan nobody can find is a plan nobody follows, and the point of the exercise is that it outlives the person who wrote it.