A knowledge transfer plan is a short document that lists the work one person does that others will need to keep doing, who takes over each task, how it will be handed over, by when, and how you will know it worked. You write one when someone gives notice, retires, moves to another role or goes on long leave, so their work keeps running after their last day. This page explains what goes in a plan, gives you a free knowledge transfer plan template in Word and PDF with a filled-in example, and walks through the eight steps to run one.
What is a knowledge transfer plan?
A knowledge transfer plan is a working document, usually owned by the manager, that turns one person's know-how into tasks someone else can do. For each task it records the receiver, the method of handover, a deadline and the proof that the receiver can now do the work. It runs from the day notice is given to a check after the last day.
The word that matters is tasks. A common handover goes like this: the person leaving sends a folder of files and a page of notes, and the receiver finds out in month two which parts nobody wrote down. A plan avoids that by starting from what the person actually does each week, month and year, and by ending only when the receiver has done the important tasks themselves.
When do you need one?
- Someone resigns. The notice period is the whole window, so the plan starts the same week.
- Someone retires. You usually know months ahead, which is time to move yearly tasks and long relationships properly.
- Someone moves to another role or team. They stay reachable, so questions after the move are cheap, but their old work still needs a new owner.
- Someone goes on parental or long leave. The handover is temporary, so the plan also says what comes back to them on return.
- A contractor, agency or vendor contract ends. The knowledge often sits outside the company, which makes the inventory harder and more important.
- A project hands over to the team that will run it. The builders move on, and the people who keep it running need the same tasks, access and contacts.
You may also see the term knowledge transition. In IT outsourcing it usually means moving a whole service from one provider or team to another, in planned phases with formal exit checks. The parts are the same as in this plan, at a larger scale: an inventory of what the service does, a method and proof for each part, access, contacts and open work.
What should a knowledge transfer plan include?
A knowledge transfer plan should include eight parts: a short summary, an inventory of tasks with a priority, how each task moves with its proof, a week-by-week schedule, access and accounts, contacts, open work and upcoming dates, and a sign-off. The free template below has exactly these eight sections.
| Section | What goes in it | Why it is there |
|---|---|---|
| Header | The role, the reason, who is leaving, who receives, the plan owner, the dates and where the handover files are kept | Anyone can see in ten seconds whose plan it is and when it ends |
| 1. Handover summary | What the role is for, what must keep running after the last day, and who signs off | It sets the bar the sign-off is measured against |
| 2. Knowledge inventory | Every task, how often it happens, what happens if it stops, who else can do it, and a priority from 1 to 3 | It decides what moves first when time runs short |
| 3. How each task moves | For each task: the receiver, the method, a due date and the proof it moved | This is the plan itself; the other sections support it |
| 4. Week-by-week schedule | What the leaver, the receiver and the plan owner each do in each week | It stops everything being left to the last few days |
| 5. Access, accounts and tools | Each system or account, what it is used for, who it moves to, how, and when it was done | Access moves by a different route from know-how, and it is easy to miss |
| 6. Contacts and relationships | The people who rely on the role, why they matter, and who introduces the receiver | A relationship cannot be written down; it has to be passed on in person |
| 7. Open work and upcoming dates | Work in progress, promises made, and dates in the next twelve months, each with a new owner | Half-finished work is what goes wrong first after the last day |
| 8. Sign-off and after the last day | Five checks, who answers questions afterwards, a check-in date, what is still open, and signatures | It ends the plan on proof rather than on a date |
Sections 2 and 3 do most of the work. The inventory makes the leaver and the manager agree on what the job really involves, which is rarely what the job description says. The transfer table then gives each task a person, a method and a test. If you only have time for two sections, fill in those two.
Download the free knowledge transfer plan template
There are two versions of the same eight sections, and a filled-in example of each. Take the Word file if you will keep the plan up to date on a computer. Take the PDF if you want to print it and fill it in by hand at the first meeting with the leaver and the receiver.
- Knowledge transfer plan template, Word (.docx): blank, with a short instruction in grey under every heading. It opens in Microsoft Word and Apple Pages, and in Google Docs if you upload it to Drive and choose Open with Google Docs.
- Knowledge transfer plan template, PDF: the same blank template laid out for printing, with ruled tables to write in.
- Filled-in example, Word and as a PDF: a complete plan for an accounts payable specialist who leaves with four weeks' notice. It is the sample further down this page.
The links go straight to the files, with no email address, form or account. Copy them, change them and share them inside your company however you like. The sign-off checks are already filled in on the blank, because they are the same for every plan.
How do you create a knowledge transfer plan?
To create a knowledge transfer plan, set the deadline and name the people, list the leaver's real tasks, rank them, choose how each one moves, capture the screen work while it is still being done, move access and contacts, let the receiver do the work under supervision, and sign off on proof. Here are the eight steps in order.
- 1
Set the deadline and name the people
Write down the last day, the receiver for each area of work, and the plan owner. The owner is usually the leaver's manager, not the leaver: the person leaving supplies the knowledge, but someone who stays has to decide when the handover is done. If there is no receiver yet, name an interim owner and say so in the header.
- 2
List the tasks, not the job description
Sit with the leaver and go through the last three months of their calendar, sent email, tickets and recurring reminders, then the last twelve months for anything yearly. Ask what would break in the first month if they were gone tomorrow. Write each item as a task with a verb, such as Run the weekly supplier payments, and note how often it happens.
- 3
Rank each task
Give each task a priority from two questions: what happens if it stops, and how many other people can do it today. Priority 1 is high impact with nobody else able to do it; those tasks move first and each one needs proof. Priority 3 is low impact or already shared, and a short note may be enough.
- 4
Choose how each task moves
Match the method to the kind of knowledge, using the table in the next section: a recording for work done on a screen, shadowing and real cases for judgment, a walk-through for rare tasks, introductions for relationships. Then write the proof you will accept, in words the plan owner can check.
- 5
Capture the screen work while it is still being done
Record each recurring task the next time the leaver does it for real, with them explaining what they check and why. A real run shows the odd cases and the shortcuts a staged demo leaves out. Do this in the first week, because the last week is full of meetings and goodbyes.
- 6
Move access, contacts and open work
Request the receiver's own access through each system's normal process, and never hand over passwords. Introduce the receiver to each contact in section 6, in person or by email, before the last day. Give every open item in section 7 a new owner and a date.
- 7
Let the receiver do the work
For each priority 1 task, the receiver first watches, then does the task with the leaver watching, then does it alone. The middle stage, sometimes called reverse shadowing, is where gaps tend to show up, because the receiver stops and asks about the things nobody thought to mention. Write each answer into the plan or the task's guide.
- 8
Sign off on proof, then check again later
On or before the last day, the plan owner goes through section 8. A task counts as transferred when its proof is met, not when the date arrives. Anything that cannot be proven yet, such as a yearly task, gets an owner and a check date. Hold a check-in about 30 days after the last day.
For documenting a single task properly once it has moved, see how to document a process and the free SOP template. For a one-page reminder the receiver keeps beside the work, see job aids.
How do you choose the transfer method for each task?
Choose the method from the kind of knowledge the task depends on. Steps done on a screen can be recorded and repeated; judgment has to be seen on real cases; relationships have to be introduced; access has to be granted. Most roles need all four, which is why one method for the whole handover rarely works.
| Kind of knowledge | Example | How it moves | Proof it moved |
|---|---|---|---|
| Repeatable steps on a screen | Run the weekly payments in the accounting system | Record a real run with the leaver explaining each check; keep the written steps | The receiver does the task alone and the result is right |
| Judgment and exceptions | Which supplier queries need the manager | Shadowing on real cases, worked examples, a decision table | The receiver handles a week of real cases, checked by the leaver |
| Rare or yearly tasks | Year-end supplier tax forms | A recorded walk-through of last time's files, plus a dated checklist | Checklist reviewed, date in the calendar, checked when the task comes round |
| Relationships | A key supplier's credit controller | An introduction in person or by email, with the context | The contact has dealt with the receiver at least once |
| Facts and locations | Where the contracts and statements are filed | A one-page reference sheet with links | The receiver finds each item without asking |
| Access | The bank portal's payment role | Each system's own process, to the receiver's own account | The receiver signs in with their own account; the leaver's access ends |
Questions that bring out what nobody wrote down
The hardest knowledge to move is the part the leaver no longer notices they use. General questions such as "what should I know?" get general answers. Ask about specific moments instead:
- What do you check that is not written down anywhere?
- Tell me about the last time this went wrong. What did you notice first, and what did you do?
- Which cases do you handle differently from the usual way, and why?
- Who do you go to when you are stuck, and for what?
- What happens once a quarter or once a year that we have not listed?
- What have you promised anyone that is not finished yet?
- If you could warn the receiver about one thing, what would it be?
Write the answers into the task's row in section 3 or into its written steps, not into a separate notes file. For a wider view of interviews, shadowing and the software teams use to store what they capture, see our guide to knowledge transfer tools.
A knowledge transfer plan sample: an accounts payable handover
This sample is the filled-in example file, so you can see every section completed. An accounts payable specialist resigns with four weeks' notice. Most of the work moves to an accounts assistant, one small task goes to the office manager, and the finance manager owns the plan. The company, systems, suppliers and dates are invented. Here is section 2, the inventory.
| Task or knowledge | How often | If it stopped | Who else can do it | Priority |
|---|---|---|---|---|
| Weekly supplier payment run in the accounting system and the bank portal | Weekly, Thursday | Suppliers go unpaid; late fees and calls | Finance manager, rarely | 1 |
| Check bank details when a supplier is set up or changes them | 2 or 3 times a month | A fake bank detail change could send a payment to a fraudster | No one else does the call-back check | 1 |
| Month-end list of accruals for the close | Monthly, last working day | The close is late or the accounts are wrong | No one | 1 |
| Year-end supplier tax forms | Once a year, January | A missed filing deadline | No one; last done 10 months ago | 1 |
| Enter and match supplier invoices from the accounts payable inbox | Daily | A backlog within a week | Accounts assistant, partly | 2 |
| Answer supplier statement queries | Weekly | Suppliers chase the finance manager instead | Accounts assistant, partly | 2 |
| Monthly reminders for expense card receipts | Monthly | Expense reports come in late | Office manager | 3 |
Why the priorities fall this way: invoice entry happens every day, yet it is priority 2, because the receiver can already do part of it and a short backlog does little harm. The year-end tax forms happen once a year and are priority 1, because nobody else has done them and the last run was ten months ago. How often a task happens tells you how soon it will be missed, not how much it matters.
| Task | Receiver | How it moves | Due | Proof it moved |
|---|---|---|---|---|
| Weekly payment run | Accounts assistant | Recorded during a real run in week 1, with the leaver explaining each check. The receiver runs it in week 3 with the leaver watching, then alone in week 4. | Week 4 | The receiver ran the week 4 payment run alone; the finance manager approved it in the bank portal with no corrections. |
| Bank detail checks | Accounts assistant | Supplier setup recorded in week 1. The call-back rule written as a decision table in SOP-AP-003. | Week 2 | The receiver set up one real supplier and logged the call-back to the number already on file. |
| Month-end accruals | Accounts assistant | The leaver writes the list of recurring accruals and why each one exists, then walks the receiver through October's file. | Week 4 | The receiver prepared November's accruals list; the finance manager found nothing missing. |
| Year-end tax forms | Finance manager | The leaver records a walk-through of last year's files and report screens, without filing anything, and writes the steps and deadlines as a checklist. | Week 3 | Recording and checklist saved, and the filing date is in the finance calendar. Proven only in January: see section 8. |
| Invoice entry | Accounts assistant | Recorded once in week 1. The receiver shadows for two days, then enters invoices with the leaver checking. | Week 2 | The receiver cleared the inbox two days running with no corrections. |
| Statement queries | Accounts assistant | The receiver sits in on queries for two weeks. The leaver lists the three suppliers with special terms and why. | Week 3 | The receiver answered a week of queries; the leaver checked each reply. |
| Expense card reminders | Office manager | A short note and the reminder email template. | Week 1 | The office manager sent November's reminders. |
Look at the proof column. Every entry is something the finance manager can check without taking anyone's word for it: a payment run approved with no corrections, a call-back in the log, an accruals list with nothing missing. "Walked through the process" or "shared the documents" would not count, because neither shows that the receiver can do the work.
| Week | The leaver | The receiver | The plan owner |
|---|---|---|---|
| 1 | Records the payment run, a supplier setup and invoice entry while doing them for real. Lists the recurring accruals. | Watches the recordings. Shadows invoice entry. | Confirms the inventory and priorities. Raises the access requests. |
| 2 | Introduces the receiver to the supplier contacts. Checks the receiver's invoice entry. | Enters invoices. Sets up one supplier, with the call-back. | Checks the first supplier setup. |
| 3 | Watches the receiver do the payment run. Records the year-end walk-through. | Does the payment run with the leaver watching. Takes over statement queries. | Reviews the year-end checklist. |
| 4 | Answers questions only. Access ends on the last day. | Does the payment run alone. Prepares November's accruals list. | Approves the payment run. Signs off the plan. |
The rest of the sample fills in the other sections. Four systems move in section 5, including the bank portal, where the receiver is added through the bank's own form signed by the finance manager, and the plan says plainly that no passwords are written in it. Section 6 lists four contacts and who introduces each one. Section 7 gives a disputed invoice, a bank detail change on hold, the year-end forms and the auditor's request list each a new owner and a date. At sign-off the year-end forms are still open, so section 8 names the finance manager as their owner, with the receiver watching in January, and sets a check-in a month after the last day.
How long should knowledge transfer take?
Knowledge transfer should take long enough for the receiver to do each priority 1 task at least once while the leaver can still watch, so it should start the day notice is given. A weekly task needs at least two runs inside the plan, one watched and one alone; a monthly task needs one full month. In practice the notice period is the limit, so the priorities decide what fits.
- Daily and weekly tasks: usually move inside two weeks.
- Monthly tasks: need one real cycle. If the month-end falls after the last day, walk through the previous month's files and book a check after the first close.
- Quarterly and yearly tasks: rarely come round during a notice period. Record a walk-through of last time's files, write a dated checklist and put the date in the team calendar with a named owner.
- Judgment: takes the longest, because it needs a spread of real cases. Start the shadowing in week 1 and keep it going to the end.
When the notice is short, move only the priority 1 tasks with proof. Record or write down everything else so the plan owner holds it, and list what is left in section 8 with a check date. A plan that hands over four tasks properly does more good than one that skims twenty.
Where does a screen recording fit in a knowledge transfer plan?
A screen recording fits the tasks done on a computer: record the leaver doing the task for real, once per task, and keep the result as the receiver's reference. A recording catches every click and screen, so the receiver sees exactly what to do. It does not catch judgment, relationships or access, which the plan handles in its other sections.
This is where stepvideo.io fits, for tasks done in a browser. The leaver records each recurring task with the Chrome extension, which records a browser tab, a window or your whole screen; click-accurate editing comes from tab capture with the extension. They can talk through what they check and why as they work. stepvideo cuts the take into steps and writes a short script for each step from what happened on screen and what they said, then turns the one recording into two things: an edited how-to video with AI voiceover and captions, and a written step-by-step guide with a screenshot for each step. If you would rather keep the leaver's own explanation, the Use original voice setting keeps the narration they recorded, cut to each step, instead of the AI voice.
Here is how that maps onto the template. Each recording becomes the "How it moves" entry for its task in section 3: the receiver watches the video before their first run and keeps the guide open during it. You edit the guide in the browser and download it as a PDF for the handover folder, or send a share page that plays the video and can carry the guide under it. For internal work, set the share page to Only your organization can view, so only signed-in members of your stepvideo workspace can open it; the receiver then needs to be a member too. If the leaver fumbles a step while recording, they can do it again rather than start over: the edit is told to leave out an attempt that was redone, and any step can be trimmed or deleted afterwards. Keep each recording to one task; a single recording can run up to 5 minutes on the free trial, 12 on Creator and 15 on Studio.
Treat what comes out as a draft, checked by the leaver while they are still there. If the receiver reads another language, stepvideo transcribes 96 languages and publishes narration in 58, and a translated project gets its own written guide. Plans are on the pricing page, and how it works shows one take becoming both the video and the guide. When the receiver later trains the next person, the same recordings help there too, as our guide to employee onboarding videos explains.
How is a knowledge transfer plan different from a handover document or an offboarding checklist?
A knowledge transfer plan moves the ability to do the work, task by task, and ends on proof. A handover document is a snapshot of status and notes, usually written by the leaver. An offboarding checklist is the HR and IT list for the person leaving, and a succession plan decides in advance who could fill a role.
| Aspect | Knowledge transfer plan | Handover document | Offboarding checklist | Succession plan |
|---|---|---|---|---|
| Answers | Can the receiver now do each task? | Where does the work stand today? | Has the leaver's exit been handled? | Who could fill this role, and are they ready? |
| Written by | The manager, with the leaver and the receiver | The leaver | HR and IT | Leadership and HR |
| When | From notice to a check after the last day | In the last days | Around the last day | Long before anyone leaves |
| Covers | Tasks, methods, proof, schedule, access, contacts, open work | Status, notes, links | Equipment, accounts, pay, exit interview | Key roles, candidates, development |
| Done when | The proof for each priority 1 task is met | It is sent | Every item is ticked | It is reviewed, often yearly |
They work together. The offboarding checklist takes care of the laptop and the final paycheck; the handover document can become section 7 of the plan; and a good succession plan means the plan has a receiver ready on day one. Only the knowledge transfer plan checks that the work itself has moved.
Why do knowledge transfer plans fail?
Knowledge transfer plans tend to fail in the same few ways: they start too late, they list documents instead of tasks, they end when the files are sent rather than when the receiver can do the work, and nobody owns what is left after the last day.
- Starting in the last week. By then there is no time for the receiver to do a task while the leaver can still watch.
- Letting the leaver run it alone. They know the work but cannot judge what the receiver has understood. The plan owner has to.
- Listing documents, not tasks. A folder of files says what exists, not what has to be done every Thursday.
- Forgetting the rare tasks. Yearly and quarterly work is invisible in a four-week notice period unless someone looks back twelve months.
- Handing over passwords. Working under the leaver's login hides who did what, and it stops working the day their account closes. Every receiver needs their own access.
- No check after the last day. The first month on their own is when the receiver meets the cases nobody listed. A check-in at 30 days catches them while they are still easy to fix.
Start the plan the day notice is given
Download the template, sit down with the leaver in the first week and fill in the inventory together. Rank the tasks, give each one a receiver, a method and a proof, and record the screen work the next time it is done for real. Then let the receiver do the work while the leaver can still watch.
Frequently asked questions
What is a knowledge transfer plan?
A knowledge transfer plan is a document that lists the tasks one person does that others will need to keep doing, and for each task names the receiver, the method of handover, a deadline and the proof that the receiver can now do it. It is used when someone resigns, retires, moves role or goes on long leave.
What should be included in a knowledge transfer plan?
Include a short summary, an inventory of tasks with how often they happen and a priority, how each task moves with a due date and proof, a week-by-week schedule, access and accounts, key contacts, open work and upcoming dates, and a sign-off with a check-in date after the last day.
Is there a free knowledge transfer plan template?
Yes. This page offers a free knowledge transfer plan template as a Word .docx file and as a PDF, with no form or sign-up. It has eight sections, from the task inventory to the sign-off, and comes with a filled-in example for an accounts payable specialist leaving with four weeks' notice.
Who should write a knowledge transfer plan?
The leaver's manager should own the plan, with the leaver and the receiver filling it in together. The person leaving knows the work, but someone who stays has to decide what matters most, check the proof and own whatever is still open after the last day. HR can supply the template and the dates.
How long does knowledge transfer take?
It takes long enough for the receiver to do each important task at least once while the leaver can watch, within the notice period. Weekly tasks usually move in two weeks, with one watched run and one solo run. Monthly tasks need a full month, and yearly tasks need a recorded walk-through, a dated checklist and a check when the task next comes round.
What is the difference between knowledge transfer and knowledge transition?
Knowledge transfer usually means moving one person's know-how to another person or team, for example when someone leaves. Knowledge transition is mostly used in IT outsourcing for moving a whole service from one provider to another in planned phases. The parts are the same: an inventory, a method and proof for each part, access and contacts.
What if there is no replacement yet?
Name an interim owner, usually the manager, and run the plan anyway. Record the screen work, write down the judgment and contacts, and save everything in one handover folder. Mark each task in section 3 as waiting for a receiver, and when someone is hired, use the same plan as the backbone of their training.
Can you record knowledge transfer sessions?
Yes. For tasks done on a computer, recording the real work captures every click and screen in order. With stepvideo, one browser recording becomes a narrated how-to video and a written step-by-step guide with screenshots. Record a real run rather than a meeting, and still write down the decisions, contacts and access.

