Knowledge Transfer When an Employee Leaves: A 2-Week Plan

When an employee leaves, you often have just a few weeks, sometimes only one, to capture what took them years to learn. The fix is a short, structured plan. List what only they know, score it by risk, capture the most critical parts first, and have the successor do the work while the leaver is still there to help.

Departures are routine, not rare. In August 2026 alone, 3.1 million US workers quit their jobs, and total separations were 5.1 million, according to the US Bureau of Labor Statistics. Most companies still aren’t ready. In a 2025 APQC survey, 92% of respondents said their organization doesn’t consistently capture knowledge from employees who are about to retire.

This guide turns public-sector playbooks from NASA and the British Columbia government into a 2-week plan for 20–500 person companies. With a longer notice period, the same steps simply stretch out. It includes a template you can copy.

Key Takeaways

• The notice period is short and the learning curve is long: often as little as one to two weeks of notice (the UK legal minimum is one week; two weeks is standard in the US), against the roughly 12 months Gallup says new hires need to reach peak performance.
• Prioritize before you capture. Score each area of knowledge on importance, availability and frequency, and start with the highest scores.
• Tacit knowledge (the “know-how”) needs shadowing, recordings and decision logs. Explicit knowledge (the “know-what”) goes into your knowledge base.
• The best knowledge transfer happens before anyone resigns: find your single points of failure now.

Table of contents

Why does knowledge walk out the door?

Because most of what people know was never written down. The British Columbia Public Service Agency’s Knowledge Transfer Guide separates two kinds:

• Explicit knowledge is the “know-what”: facts, procedures and documents that can be recorded.
• Tacit knowledge is the “know-how”: experience that is hard to put into words, such as which client needs a phone call rather than an email, or why a process has that odd extra step.

The guide warns that tacit knowledge is lost when the person who holds it leaves, unless someone makes an effort to capture and transfer it.

The time pressure makes it harder. In the UK, an employee who has worked for more than a month must give at least a week’s notice. In the US, most employment is at-will, and SHRM notes that two weeks is the standard notice period. Meanwhile, Gallup estimates that new employees typically take around 12 months to reach their peak performance potential.

It’s also expensive to get wrong. Gallup estimates that replacing an individual employee can cost one-half to two times their annual salary, and calls that a conservative estimate. Lost knowledge makes the replacement slower and the cost higher.

How to prioritize what to capture

You can’t capture everything in two weeks, so score it. The BC guide uses a simple formula you can apply in a single meeting. Rate each area of knowledge from 1 to 3 on three questions, and add the scores:

A total of 7–9 is high priority, and the BC guide says action should be taken immediately. A total of 4–6 is medium priority, and 3 is low. Example: a founder-era customer contract that only the leaving account manager understands and that renews quarterly scores 3 + 3 + 2 = 8. Capture it first.

The 2-week knowledge transfer plan

NASA’s supervisor guide gives the most important rule: as soon as you know someone plans to leave, sit down with them and make a transition plan. Here’s how to use a typical two-week notice period.

Step 1: Make the plan on day one

By the end of day one, everyone knows who takes over what, and when.

Meet with the person leaving and their manager. Agree who the successor is for each responsibility. If there isn’t a replacement yet, name an interim owner. Block time in the leaver’s calendar for handover work, because handover done “in between” doesn’t happen.

Step 2: List everything they know (days 1–2)

Get the full picture before deciding what to capture.

NASA’s guide for departing employees uses an 11-item checklist. For a smaller company, it comes down to six questions, plus one we add: decisions.

1. Duties: what do you do, daily, weekly, monthly and yearly, and what are the deadlines?
2. Contacts: who inside and outside the company do you work with, and who should the successor meet?
3. Information and equipment: where is information stored, and which tools, accounts, licenses and devices do you use?
4. Recurring problems: what goes wrong regularly, and how do you fix it?
5. Decisions: which past decisions would someone be tempted to undo without knowing why they were made?
6. Open work: what’s in progress, and what’s promised to whom?
7. Lessons learned: what did you learn the hard way?

Step 3: Score and prioritize (days 2–3)

Rank the list with the importance, availability and frequency score, and focus on everything that scores 7 or higher.

Share the ranked list with the manager and successor. It becomes the agenda for the rest of the notice period.

Step 4: Capture it the right way (days 3–8)

Match the method to the kind of knowledge.

• Explicit knowledge → write it down. Turn procedures and answers into short pages in your internal knowledge base, one question per page, and keep policies in your employee handbook. Our guide to creating an internal knowledge base includes a page template.
• Tacit knowledge → show it. NASA’s supervisor guide says that if time allows, shadowing is the best method for transferring knowledge. Where shadowing isn’t possible, record short videos. NASA suggests clips of three to five minutes.
• Decisions → log them. Software architect Michael Nygard wrote that one of the hardest things to track is the motivation behind decisions. His decision record format works for any team: title, context, decision, status and consequences.

Step 5: Let the successor do the work (days 8–10)

Swap roles: the successor does the tasks while the leaver watches and corrects.

The BC guide calls this overlap “double banking”, and it’s where gaps show up. Every question the successor asks is a sign that a page is missing or unclear, so fix the page right away rather than just answering out loud.

Step 6: Hand over access and say goodbye properly (last days)

Make sure nothing is locked in a personal account, and keep the door open.

Transfer ownership of files, shared drives, recurring meetings and external accounts, and introduce the successor to key contacts. Check for accounts tied to the leaver personally: two-factor authentication or recovery set to their own phone or email, domains and vendor accounts registered to their address, and shared passwords they know. Move or rotate those, then revoke their access on the last day. NASA also recommends planning for post-departure communication. If the person leaves on good terms, ask whether you may contact them with a question or two in the first weeks.

What if there’s no overlap?

Sometimes someone leaves suddenly, or the successor hasn’t been hired yet. NASA’s guides distinguish three scenarios:

For the no-overlap case, your best defense is whatever was written down before. That’s why the most important step happens before anyone resigns.

Make knowledge transfer continuous

The best time to capture knowledge is before anyone hands in their notice. NASA’s supervisor guide asks a question every team should ask now: “Is anyone the sole owner of critical knowledge?”

Software teams call this the “truck factor”: the minimum number of people who would have to leave before a project stalls. In a study of 133 popular GitHub projects, 65% had a truck factor of two or less. Many small companies have the same risk in finance, sales or operations.

Three habits keep that risk low:

1. Capture in the workflow. When a question has no written answer, write it down then and there. Our guide on why employees keep asking the same questions shows how.
2. Cross-train on every critical process, so each one has at least two people who can run it.
3. Hold stay interviews. SHRM describes these as structured conversations to learn what would keep an employee engaged. They aim to reduce departures in the first place, and they’re a natural moment to ask what only that person knows.

Knowledge transfer plan template

Copy this into a document or your knowledge base at the start of every notice period:

KNOWLEDGE TRANSFER PLAN
Leaving: [name, role]        Last day: [date]
Manager: [name]              Successor(s): [name per area]

1. KNOWLEDGE INVENTORY  (score 1–3 each; total 7–9 = capture first)
   Area / task          | Importance | Availability | Frequency | Total | Successor
   [e.g. Client X renewal] |     3      |      3       |     2     |   8   | [name]

2. CAPTURE PLAN
   Area              | Method (page / video / shadowing / decision log) | Due
   [area]            | [method]                                          | [date]

3. ACCESS AND OWNERSHIP
   [ ] Files and shared drives transferred
   [ ] Recurring meetings and calendars reassigned
   [ ] External accounts and vendor contacts handed over
   [ ] Key contacts introduced to successor

4. CHECK
   [ ] Successor completed top tasks with leaver present
   [ ] Every question from the successor turned into a page
   [ ] Post-departure contact agreed (if appropriate)

Frequently asked questions

How long should knowledge transfer take?

Use the whole notice period, and for a key role aim for at least two weeks of overlap. With one week or less, capture only the items that score 7 or higher. And don’t wait for a resignation: continuous capture means most knowledge is already written down.

What should a knowledge transfer document include?

At a minimum: duties with their deadlines, key contacts, where information and tools live, recurring problems and fixes, open work, and the reasons behind important decisions. NASA’s checklist for departing employees is a good starting point.

What if the employee is leaving on bad terms?

Keep the process short, professional and focused on the work. Prioritize what only they know, and handle access to systems and data according to your security policy. If the departure could become a dispute, talk to HR or an employment lawyer about how to manage it.

Who should own the knowledge transfer process?

The departing employee’s manager owns the plan, with support from HR or operations. The successor owns the result: they’re the one who needs to be able to do the job.

Plan now, not at the exit interview

• Expect departures: they happen every month, and notice periods are short.
• Prioritize with importance, availability and frequency, and capture 7–9 scores first.
• Match the method: write down explicit knowledge, show tacit knowledge, and log decisions.
• Swap roles before the last day, so the successor practices with help.
• Capture continuously, so no single person is the only one who knows how something works.