A knowledge transfer plan lists what someone knows, who takes over each part, how it will be transferred and by when, and how you will check it worked. Build it in the first days of the notice period, run it over two to four weeks, and finish with the successor doing the work while the leaver is still available.
Below is a template you can copy, followed by a week-by-week schedule and the mistakes that make most transfers fail.
What should a knowledge transfer plan include?
- Scope: the person, role, last day, successor(s) and plan owner.
- Knowledge inventory: every area of work, ranked by risk.
- Transfer method for each area: document, shadowing, walkthrough, introduction or reverse shadowing.
- Schedule: sessions booked in calendars, not "when we find time".
- Verification: proof the successor can do it.
- Output: a handover document that outlives the plan.
The template
Section 1: Scope
| Field | Detail |
|---|---|
| Person leaving or moving | |
| Role | |
| Last working day | |
| Plan owner (usually the manager) | |
| Successor(s) | |
| Interim cover if no successor yet | |
| Date plan agreed |
Section 2: Knowledge inventory
List each area of work. Rate risk as High (only this person knows it, and it matters soon), Medium, or Low.
| # | Area of knowledge | Type | Risk | Successor | Method | Target date | Done |
|---|---|---|---|---|---|---|---|
| 1 | Process / Decision / Relationship / System / Project | H/M/L | ☐ | ||||
| 2 | ☐ | ||||||
| 3 | ☐ |
Types to cover:
- Processes: recurring tasks, including those done quarterly or yearly.
- Projects: status beyond what the tracker says, next steps, risks.
- Decisions: why things are the way they are, what was tried and dropped.
- Relationships: customers, suppliers, regulators, internal approvers.
- Systems: tools, files, scripts, access (transfer through your access process, never write passwords).
- Commitments: promises made to people that are not written anywhere.
Section 3: Transfer methods
| Method | Best for | Time per area |
|---|---|---|
| Written handover | Status, contacts, where things are | 1 to 2 hours |
| Recorded walkthrough | Tool-heavy processes | 30 to 60 minutes |
| Shadowing (successor watches) | Judgment calls, customer calls | One real cycle |
| Reverse shadowing (leaver watches) | Checking the successor can do it | One real cycle |
| Introductions | Relationships | 15 to 30 minutes each |
| Structured interview | Decisions and reasoning | 30 to 45 minutes |
For the interview, use our knowledge transfer interview questions.
Section 4: Verification checklist
- Successor has done each High-risk task once, with the leaver watching
- Successor has met or been introduced to each key contact
- All access has been transferred through IT, and the leaver's access has a removal date
- Open commitments have a named new owner and the other party knows
- Handover document reviewed by the successor and the manager
- A contact plan exists for questions after the last day, if the leaver agrees
Section 5: Sign-off
| Name | Date | Comment | |
|---|---|---|---|
| Leaver | |||
| Successor | |||
| Plan owner |
A 4-week schedule
| Week | Focus | Actions |
|---|---|---|
| 1 | Inventory | Fill Sections 1 and 2. Rank by risk. Book sessions. Start the handover document. |
| 2 | High-risk areas | Interviews on decisions. Shadowing of High-risk tasks. Introductions to key contacts. |
| 3 | Reverse shadowing | Successor does the work, leaver watches. Fill the gaps found. Medium-risk areas. |
| 4 | Close | Low-risk areas. Final review of the handover document. Sign-off. Access changes scheduled. |
If the notice period is shorter, keep weeks 1 and 2 and compress the rest. If there is no successor yet, transfer to the manager or an interim owner and record everything in writing so the future hire can read it.
Why do knowledge transfers fail?
- They start too late. The last week is spent on farewells and admin.
- They only cover tasks. The reasons behind decisions are what a successor most often lacks.
- Nobody checks. A document is not proof that someone can do the job. Reverse shadowing is.
- They depend on the leaver's memory. Months of context get compressed into what one person can recall under time pressure.
The last point is the hardest to fix with a template. It is easier when decisions and commitments are written down as they happen, not reconstructed at the end. Our guide on what happens to team knowledge when someone quits goes deeper.
Where Reattend fits
Reattend keeps a running memory of decisions, commitments and meeting notes from each person's work, captured by a desktop app on their computer. When someone leaves, the transfer starts from that record. The exit interview is answered in the app and becomes a handoff document, and the dashboard shows which topics only that person holds and who is best placed to take over. You can run this plan without any software; the tool just means less depends on the final weeks.
Frequently asked questions
What is a knowledge transfer plan?
A knowledge transfer plan is a short document that lists what a departing or moving employee knows, who will take each part over, how it will be transferred (documents, shadowing, recorded walkthroughs, introductions) and by when, with a check that the successor can actually do the work.
How long should knowledge transfer take?
Plan for most of the notice period. Two to four weeks is typical for one role. Complex or long-tenure roles need longer, which is why a retirement or planned move should start months ahead.
Who is responsible for knowledge transfer?
The manager owns the plan. The leaver provides the knowledge. The successor confirms they can do the work. HR makes sure it happens for every departure, not just the senior ones.
What is the difference between a knowledge transfer plan and a handover document?
The plan is the schedule and the list of who learns what. The handover document is the main output: the written record of status, processes, decisions, contacts and risks.
What does KT mean?
KT is short for knowledge transfer. It is common in IT services and in Indian workplaces, where a KT session means a walkthrough given by the person leaving to the person taking over.