What should a knowledge transfer plan include?

An inventory of the person's recurring tasks and responsibilities, the systems and accounts they use, the people they deal with inside and outside the company, work in progress, the unwritten rules and exceptions they apply, a named receiver for each item, the transfer method and a deadline. It should also include a check that the receiver can do each task alone.

What are the steps in a knowledge transfer plan?

Build an inventory of what the person knows on day one, prioritize each item by risk, name one receiver for every item, choose a transfer method that fits each kind of knowledge, schedule the sessions in both calendars, and check that each receiver can do the critical tasks alone before the last day.

Is there a knowledge transfer plan template?

Yes. Use one table with a row per item from the inventory and these columns: item, kind, whether only the leaver knows it, next due date, priority, receiver, method, deadline and how it was verified. A filled-in example is in the template section of this guide.

How long does knowledge transfer take?

It depends on the role. A standard two-week notice period is enough to cover the critical tasks of most roles if you start on day one and prioritize. Roles with long cycles, such as month-end or annual work, need recordings or written procedures for the tasks that will not come up before the person leaves.

How do you transfer knowledge when an employee leaves with short notice?

Prioritize hard. List only the tasks that nobody else can do and that will come up in the next 30 days, then record the person doing or talking through each one. A screen recording or voice memo takes minutes to make and can be turned into written steps after they have gone. Collect access details and key contacts before anything else.

What is the difference between knowledge transfer and offboarding?

Offboarding is the administrative exit: final pay, returning equipment, removing access and the exit interview. Knowledge transfer is about the work itself: making sure someone else can do what the leaver did. They run in parallel, and knowledge transfer should start first because it needs the most of the person's time.

How do you capture tacit knowledge?

Tacit knowledge is what a person knows but has never written down, such as how they judge an unusual case. It rarely comes out when you ask someone to write. Watch them do the task, ask them to explain each decision out loud, and ask about exceptions: when do you not follow the normal steps, and what tells you something is wrong?

Knowledge Transfer Plan: Template, Steps and Checklist

The short answer

A knowledge transfer plan is a short written plan for moving what one person knows to the people who will do the work next. It lists the tasks, contacts, access and judgment calls that person holds, who will receive each one, how it will be handed over and by what date, plus a check that the receiver can do each task alone. It is usually one table and one calendar, not a long document.

The six steps at a glance

Build the inventory on day one: list every task, system, contact and piece of work in progress.
Prioritize by risk: capture first what only this person knows and what comes up within 30 days.
Name a receiver for every item: one named owner per item, never “the team”.
Choose the transfer method: screen recording, written procedure, interview, shadowing or introductions.
Schedule it: block the sessions in both calendars across the notice period.
Check that it worked: the receiver does each critical task once before the last day.

Then copy the knowledge transfer plan template and work through the last-day handover checklist.

Why it matters

Someone good just gave notice. In two weeks they walk out with the vendor contacts, the month-end workarounds, the reason that one client gets invoiced differently and a dozen other things nobody else knows.

A knowledge transfer plan is how you keep that. This guide covers what to capture, a schedule that fits a two-week notice period, a template you can copy and a checklist for the final day.

It applies just as well to a promotion, a parental leave, a retirement or a contractor whose project is ending. The method is the same. Only the deadline changes.

What a knowledge transfer plan is

A knowledge transfer plan answers five questions for one person’s role:

What do they know or do that the business depends on?
Who receives each piece?
How will it be handed over: a written procedure, a recording, working side by side?
By when?
How will you know it worked?

It is usually one table and one calendar, not a long document. The time goes into the transfer, not into the plan.

It is also different from offboarding. Offboarding is the administrative exit: final pay, equipment, removing access. Our employee offboarding SOP template covers that side. Knowledge transfer is about the work, and it should start first because it needs the most of the leaver’s time.

The four kinds of knowledge to capture

People asked to “write down what you do” list their main duties and stop. Use these four categories to get past that.

Kind	Examples	Best way to capture it
Tasks	Running payroll, the weekly report, renewing a license	A step-by-step procedure or a screen recording
Access and locations	Which accounts, where the files live, which inbox gets the alerts	A list, checked by the receiver logging in
Relationships	The vendor rep who answers the phone, the client who needs a call not an email	A contact list with a note on each, plus an introduction
Judgment	When to waive a fee, how to tell a job will run over, what “looks wrong” in the numbers	An interview, written up as rules and examples

Tasks are the easiest to capture and the easiest to rebuild later. Judgment is the hardest to capture and the most expensive to lose, so do not leave it for the last day.

Step 1: Build the inventory on day one

Sit down with the person for an hour as soon as you know they are leaving. The goal is a complete list, not detail. Prompts that work:

Walk me through a normal week. What do you do every day, every week?
What happens monthly, quarterly and once a year?
What do people come to you to ask?
What would break or stall in the first month if nobody picked it up?
What do you do that is not in your job description?
Which systems do you log in to that nobody else does?
Who outside the company do you deal with directly?
What is in progress right now, and what is the next step on each?

Check their calendar, their sent mail and their recurring tasks with them. Recurring calendar events are a reliable source of jobs people forget they do.

Step 2: Prioritize by risk

You will not capture everything in two weeks, so rank each item on two questions:

Does anyone else know how to do this? If yes, it can wait or be skipped.
How soon will it come up, and what happens if it goes wrong?

That gives three groups:

Capture first: only this person knows it, and it will come up within 30 days or is costly to get wrong.
Capture if time allows: only this person knows it, but it is infrequent or low stakes. A recording is usually enough.
Skip: someone else already does it, or it is already documented and current.

Be strict about the first group. A plan with forty “critical” items gets none of them done properly.

Step 3: Name a receiver for every item

Each item needs one named person who will own it afterward. “The team” does not count as a receiver.

If the replacement has not been hired, name an interim owner anyway, and capture the item in a form that outlasts both of them. A written procedure or a recording can train the eventual hire. A conversation between the leaver and a temporary cover cannot.

Spread the load if you need to. Splitting one role across three people for a few months is normal, as long as each task has one owner.

Step 4: Choose the transfer method

Match the method to the kind of knowledge.

Screen recording for anything done in software. The person does the task once for real and narrates as they go. This is the fastest method for the leaver, which matters because their time is the constraint.
Written procedure for tasks that will be repeated often or by several people. Numbered steps, one action each. See our guide to SOP format, or describe the task in a few sentences to the free AI SOP generator for a first draft of the steps.
Interview for judgment. Ask about a specific past case rather than in general: “Tell me about the last time you gave a refund outside the policy. What made that one different?”
Shadowing, then reverse shadowing for the most important tasks. First the receiver watches. Then the receiver does it while the leaver watches and says nothing unless asked. Do not skip the second half, because it shows you what did not transfer.
Introductions for relationships. A short email or call from the leaver introducing the new contact does more than a name on a list.

Do not ask the leaver to write everything. They are finishing their own work, and long writing tasks are the first thing to slip. Have them talk and demonstrate, and have the receiver or a manager turn that into the written version. Writing it up is also a good test of whether the receiver understood.

Step 5: Schedule it

A schedule that fits a two-week notice period:

When	What happens
Day 1	Inventory interview. Rank the list. Name receivers.
Days 2 to 4	Capture the first group: record or shadow each critical task. Collect access and contacts.
Days 5 to 7	Receivers write up or review the procedures. Judgment interviews.
Days 8 to 9	Reverse shadowing: receivers do the critical tasks with the leaver watching. Fix the documents where they got stuck.
Day 10	Introductions sent. Work in progress handed over with next steps. Final checklist.

Block the time in both calendars. Knowledge transfer loses to “just finishing this one thing” unless it has appointments.

For tasks that will not occur before the person leaves, such as year-end close, ask them to walk through last time’s files on a recording and explain what they did and why.

Step 6: Check that it worked

A document existing is not proof that the knowledge moved. Before the last day, confirm for each critical item:

The receiver has done the task once themselves, or walked through it step by step.
The receiver can log in to every system the task needs.
The procedure or recording is saved where the team keeps its procedures, not in the leaver’s personal drive.
The receiver knows who to ask if something unexpected comes up after the leaver has gone.

If the departure is on good terms, ask whether the person is open to a couple of short questions by email in the first month, and agree the limits. Treat it as a courtesy, not as part of the plan.

Knowledge transfer plan template

Copy this table into a document or spreadsheet. One row per item from the inventory.

Item	Kind	Only they know it?	Next due	Priority	Receiver	Method	Deadline	Verified
Run biweekly payroll	Task	Yes	Oct 16	First	Dana	Record, then reverse shadow	Day 4	Receiver ran it alone
Supplier price negotiations	Judgment	Yes	November	First	Luis	Interview, written rules	Day 7	Reviewed with manager
Weekly sales report	Task	No	Friday	Skip	Already shared	None	None	None
Insurance broker contact	Relationship	Yes	Renewal in March	If time	Dana	Intro email, contact note	Day 10	Reply received

The names and dates are placeholders to show how a filled-in row reads.

Last-day handover checklist

Common mistakes

Starting in the last week. The first days of a notice period are the most useful. By the end, the person is wrapping up and their attention has moved on.
Asking for a brain dump. A forty-page document written in the final days is rarely read. Short procedures per task get used.
Capturing tasks and missing judgment. The steps for sending a quote are easy to rebuild. Knowing which customers always push back on price is not.
One receiver for everything. If the whole role moves to one person and that person leaves, you are back where you started. Put the knowledge in documents the team can reach.
No verification. If the receiver has only watched, you will find the gaps after the leaver has gone.

Do not wait for a resignation

The best knowledge transfer plan is the one you barely need, because the role was already documented. Two habits get you most of the way there:

Document as you go. When someone does a task that only they know, they record it once. Over a few months the single points of failure shrink.
Cross-train on the critical few. For each task that would hurt within a week if its owner were out sick, make sure a second person has done it at least once. Our guide to cross-training employees shows how to map that cover with a skills matrix.

Vacations are a free test. If someone cannot take a week off without being called, that is the knowledge transfer plan you should write this month. Our guide to getting the business out of the owner’s head applies the same idea to the person who usually holds the most.

How SOPCompass helps

You can run everything above with a spreadsheet, a screen recorder and a shared folder. The slow part is turning what the leaver says and shows into procedures someone else can follow, and that is the part SOPCompass speeds up.

Talk instead of write. The AI assistant interviews the person by text or voice and drafts a step-by-step SOP from their answers. Nothing is saved until a person approves it.
Record the task once. Record your screen or upload a video and SOPCompass drafts the steps with screenshots and keeps the video in the SOP, so each step can play its moment. For work in a web app, the Capture extension writes a step for each click as the person works.
Bring in what already exists. Import Word, PDF and Markdown files, or an audio recording of someone explaining a process. Imports run one document at a time so each draft gets reviewed.
Hand it to the receiver. Assign each SOP to the person taking it over with a due date, and add a quiz on the ones where a mistake is costly.
Keep it findable afterward. SOPs live under pillars and departments, and Ask answers a plain-English question from your own SOPs with a citation to the source. If your SOPs do not cover it, it says so.

What it will not do: it cannot know what the person does not say, so the inventory interview and the questions about exceptions are still yours to run. It does not store passwords, so use a password manager for those. And a draft is only as good as its review, so have the leaver read each one before their last day.

Where to start today

If someone has already given notice, book the inventory hour for tomorrow and rank the list before you capture anything. If nobody is leaving, pick the one person whose absence would hurt most and ask them to record the single task only they know how to do. That is one fewer thing to lose when a resignation does come.

Knowledge Transfer Plan: How to Keep What an Employee Knows