A knowledge transfer plan for a planned departure

Start with decisions the successor will face

List the tasks that would cause a delay, a serious rework or a missed commitment if the expert were unavailable next week. Ask the expert, the successor and a customer of the work separately. A task that appears simple to its owner can contain an exception that only another team has seen.

For each task, record who makes the decision now, who will make it after the handover, the routine case and the highest-consequence exception. Prioritize tasks with frequent or serious exceptions and few people able to cover them. Start with the smallest set that will make a meaningful difference after the departure.

Put the plan on one page

Give each row a task, trigger, current owner, successor, reference, practice date, reviewer and acceptance test. A useful test describes what someone will observe. “Read the guide” is an activity. “Resolve a case with a missing carrier confirmation and tell the next shift what is still open” is a test.

Include prerequisites in the row. Ask the successor to open the current reference, find the relevant person and verify their access before the practice session. Use an approved environment for a rehearsal that involves sensitive work. Where the actual permissions or ownership will change later, assign someone to confirm the change.

A completed example from a distribution team

In a fictional distribution team, a departing lead owns the late dispatch decision. The standard tells the next shift to check the manifest. The lead also checks whether an exception is awaiting carrier confirmation, because the manifest can appear complete while the decision is open.

The plan assigns the incoming lead to run a rehearsal with one ordinary load and one missing confirmation. An operations supervisor observes whether the successor checks the source, identifies the open decision, chooses the approved escalation route and leaves a clear handover note. The reviewer records the observed steps and where the successor had to ask for help.

The rehearsal exposes an access gap. The new lead can see the manifest and cannot see the exception note. The supervisor leaves the row open, assigns the access request to the system owner and agrees a temporary route for the decision. A second rehearsal after access is granted provides better evidence than an acknowledgment that the instructions were received.

Schedule capture, practice and a second attempt

Work backward from the changeover. Early in the overlap, interview the expert about one recent case and one exception. Write down which details were known at each decision point. Ask another practitioner to review anything that could have become a personal workaround.

Ask the successor to explain and perform the task with the materials they will use after the handover. Allow time to update the reference and repeat the exercise. If the overlap is short, give priority to high-consequence tasks and assign an interim reviewer to handle open cases after departure.

Leave a record an owner can maintain

Use three states: ready, ready with a named support route, and open. Record the evidence for each decision and where the current reference lives. Put the unresolved items in the team’s normal tracking system so they have an owner and a date after the handover ends.

NASA’s knowledge continuity guide for supervisors offers a broader way to identify critical knowledge before a transition. Use the worksheet here to translate that priority into a short plan and a test someone can observe.