# Knowledge transfer plan

**Person leaving:** 
**Role:** 
**Last day:** 
**Successor (or interim owner):** 
**Plan owner:** 
**Last updated:** 

---

## 1. What only this person does

List the responsibilities that would stop, or degrade, if nobody picked them up.
Rank them: 1 = the business notices within a week.

| # | Responsibility | Who else can do it today | Risk if nobody does |
|---|---|---|---|
| 1 |  |  |  |
| 2 |  |  |  |
| 3 |  |  |  |

## 2. What has to be captured

For each item above, name the kind of knowledge you need. The written procedure is
usually the part that already exists; the rest is what leaves.

| Responsibility | Sequence and dependencies | Judgment calls | Traps | Reasons | People and places |
|---|---|---|---|---|---|
|  |  |  |  |  |  |

## 3. Schedule

Short sessions across the notice period beat one long handover at the end.

| Week | Topic | Who | Format | Done |
|---|---|---|---|---|
| 1 |  |  |  |  |
| 2 |  |  |  |  |
| 3 |  |  |  |  |
| 4 |  |  |  |  |

## 4. Who else to ask

One person's account is one person's account. Name at least one colleague per
topic who can corroborate it or disagree.

| Topic | Second person | Asked | Agreed / disagreed |
|---|---|---|---|

## 5. Where the answers land

| Topic | Document | Location | Owner after handover |
|---|---|---|---|

## 6. Still unresolved

Disagreements and unanswered questions. Do not resolve a disagreement by taking the
more senior answer — record both, and name who decides.

| Item | Positions | Who decides | By when |
|---|---|---|---|

## 7. How you will know it worked

The successor runs the task unaided, once, before the last day — with the person
leaving available but not intervening.

| Task | Dry run date | Ran unaided | What was missing |
|---|---|---|---|

---

*Template from https://nuggetz.ai/learn/knowledge-transfer-plan — copy it, fill it in, keep it in whatever your team already reads.*