A working knowledge transfer plan has six parts: a scoped list of what only this person knows, a named receiver, structured capture sessions (not a writing assignment), successor-ready artifacts, shadowing time while the expert is still there, and a gap check before the last day. Document checklists alone miss the tacit judgment that makes the expert effective.
When a key person gives notice or sets a retirement date, someone gets asked to "put together a knowledge transfer plan." Most of what comes back is a checklist: update the wiki, record a walkthrough, list the passwords, schedule a handover meeting. Those are fine tasks, and a plan built only from them still leaves the successor without the thing that made the expert effective: the judgment.
A good plan treats the transfer as two different jobs. Explicit knowledge (documents, credentials, contacts, system access) is a collection problem, and checklists handle it well. Tacit knowledge (how decisions actually get made, what the warning signs are, why things are done this way) is an elicitation problem, and it needs structured conversation, because experts cannot simply write down what they know.
The six parts of a plan that works
- Scope: what only this person knows. Not everything they do, just the parts where they are the single point of knowledge. A free Knowledge Risk Assessment maps this in minutes and gives the plan its backbone.
- A named receiver. A specific successor, or the team lead who will hold the knowledge until one is hired. "The team" is not a receiver.
- Structured capture sessions. Guided, question-driven sessions on each scoped area. This is the core of the plan and the part checklists skip. See how to run the capture.
- Successor-ready artifacts. The output should be a briefing a successor can act on, a map of dependencies and contacts, and a view of the risks, not a folder of raw notes or recordings.
- Shadowing with the artifacts in hand. Time where the successor works through real tasks and asks follow-up questions while the expert can still answer them. The artifacts make this time far more productive because the basics are already covered.
- A gap check before the last day. Walk the successor through the scoped list and ask what they still could not handle alone. Capture those gaps while the expert is still in the building.
A document checklist transfers what was already written down. The plan exists for everything that was not.
How much time it really takes
Less than most teams fear. The scoping takes an hour. Structured capture on the areas that matter is a handful of focused sessions, not weeks of documentation duty, and it asks far less of the expert than "write up everything you know." The payoff is real: research firm APQC found that 92% of organizations see the loss of retiring employees' knowledge as a risk, yet most still rely on the informal handover this plan replaces. And with median employee tenure at 3.9 years, the plan you build for one retirement becomes the process you reuse for every departure after it.
When to start
The best window is before a departure is on the calendar, because the expert has time and no competing priorities. The practical window is the notice period: even two to four weeks is enough for scoping, capture, and a gap check if the sessions are structured rather than improvised. What does not work is starting in the final week, when the expert is wrapping up loose ends and their calendar is gone.
TacitTalks runs steps one through four for you: it scopes the risk, conducts the structured capture sessions, and produces the successor briefing, dependency map, and risk view automatically. For a single departing expert, the Continuity Pack covers the whole plan for a flat fee.
Common questions
- What should a knowledge transfer plan include?
- Six things: a scoped list of what only the departing person knows, a named receiver, structured capture sessions to elicit tacit knowledge, successor-ready artifacts (a briefing, a dependency map, a risk view), shadowing time with those artifacts in hand, and a gap check before the last day. Document and credential checklists cover the explicit knowledge but miss the judgment.
- How long does knowledge transfer take?
- With structure, the core takes days, not months: about an hour to scope, a handful of guided capture sessions on the areas where the person is the single point of knowledge, and a final gap check. Even a two-to-four-week notice period is workable. Unstructured approaches take longer and capture less.
- Is a knowledge transfer template enough?
- A template helps with the explicit items (documents, credentials, contacts) but not with tacit knowledge, because it still relies on the expert writing down judgment they use automatically and cannot articulate on a blank page. Pair any template with structured, question-driven capture sessions for the areas where the person is the only one who knows.
Sources
See your organization's knowledge risk - free
Run a free Knowledge Risk Assessment and see where hard-won expertise sits with a single person. No card required.