Offboarding knowledge transfer is the work of capturing what a departing employee knows, and getting it to the people who will carry the work on, before their last day. Do it well and the team keeps moving. Skip it and someone spends months rediscovering what the leaver could have explained in an afternoon.
This guide covers what to capture, when to start, how to draw out knowledge people can't easily write down, and how to confirm the handover worked. It is written for HR professionals, team leaders and project managers who have a resignation on their desk today.
TL;DR
- Start the day the resignation lands. Don't wait for a successor to be hired.
- Capture more than tasks: decisions, exceptions, relationships and the reasons behind "how we really do it."
- Documents alone rarely carry judgment. Pair them with interviews, shadowing or recorded walkthroughs.
- Name one owner for the handover, and treat it as done only when the recipient can apply what they received.
- If no single successor exists, split the role by area and map who covers what.
Table of Contents
- What offboarding knowledge transfer actually is
- What to capture before someone leaves
- When to start, and who owns it
- Getting tacit knowledge out of someone's head
- When there is no single successor
- Confirming the transfer worked
- Where offboarding knowledge transfer goes wrong
- Our perspective
- Capture the reasoning with Kept
- FAQ
- Sources
What offboarding knowledge transfer actually is
A structured handover reduces the risk of lost knowledge, gives everyone clarity about responsibilities and keeps the transition orderly, as Karolinska Institutet's offboarding guidance for managers puts it. That is the minimum. The harder part is the knowledge nobody has written down.
The research literature draws a useful line. A 2024 systematic review in PMC separates tacit knowledge (ideas, mental models, know-how and intuition built up through practice) from explicit knowledge, which belongs to the organization and can be codified in documents, procedures and manuals. Most offboarding checklists cover the second kind well. The first kind walks out the door.
APQC's guidance says offboarding should include a deliberate process for identifying, capturing and transferring the knowledge an organization cannot afford to lose, with particular attention to tacit knowledge gained through hands-on experience.
Why does it matter so much? SHRM quotes HR consultant Shawn Stout-Jough describing what happens otherwise: colleagues try to piece together projects, systems, vendor agreements and staff management, which can mean chaos and lost productivity. And most organizations don't have a reliable approach. In a Training Industry and Raytheon survey, only 39% of learning leaders rated their organizations as very or somewhat effective at transferring knowledge from transitioning employees to replacements. The biggest challenge they named was the lack of a formalized approach. That survey dates from 2012, but the gap it describes is familiar to anyone who has inherited a role with no notes.
What to capture before someone leaves
The most common mistake is capturing the job description. You already have that. You need the real version of the job.
Cornell's knowledge transfer checklist is a good model of the ground to cover: core responsibilities, recurring tasks and timelines, active projects, upcoming milestones, key workflows (SOPs), systems and tools, shared materials and file naming conventions, internal partners and external contacts, standing meetings, known risks and ideas for improving processes. Carleton University's capture and transfer template adds a monthly calendar of events, reports and activities, which catches the quarterly and annual duties that nobody remembers until they're missed.
Here is how we group it in practice, contrasting what a document can hold with what only the person holds:
| Area | What the document holds | What the person holds |
|---|---|---|
| Tasks | The steps of the procedure | Which steps are load-bearing and which are ceremony |
| Decisions | The rule or threshold | When they break it, and why |
| Relationships | Names and email addresses | Who answers quickly, who needs a call, who is sensitive about what |
| Systems | Logins, locations, naming rules | Workarounds, known quirks, what failed last time |
| Projects | Status and next milestones | The history behind them and the risks not yet written down |
The right-hand column is where handovers fail. Coassemble's checklist advice says the same thing in different words: record the lessons learned, the context behind key decisions, what was tried and didn't work, and the unwritten rules.
Not everything deserves equal effort. The UK government's guidance note says a transfer plan should be proportionate, shaped by how quickly the knowledge goes out of date, how easily it can be written down and who it is for. Spend your hours on the high-risk expertise first: the things only this person can do, or the things that would hurt most if done wrong. The same logic applies to talent retention best practices, where identifying high-risk expertise early is what gives you time to act.
When to start, and who owns it
Start immediately. Cal Poly's plan tells departments to begin collecting documentation as soon as they learn of an employee's intent to leave, with the plan's timeline beginning right after a knowledge transfer interview. The same plan covers identifying key tasks and projects, naming who takes them over, transferring responsibilities with a RACI framework and listing skill gaps with action plans.
Karoliska's process places the work inside the notice period: the manager plans and documents the handover, saves files to a shared drive and books the exit interview, according to its offboarding page.
One person should own it. NASA's transitions guide says each step should be led by a leader or someone the leader designates, while every team member can contribute to the shared knowledge. In a small company that owner is usually the departing person's manager. HR supplies the template and the calendar. The leaver supplies the substance. When all three assume someone else is driving, nothing happens until the final week.
A realistic notice-period rhythm looks like this:
- Day one: the manager and leaver agree what is high-risk and rank it.
- Week one: run the first interview, assign owners for each area, and create the shared home for everything captured.
- Middle weeks: shadowing, recorded walkthroughs and live handoffs with the people taking over.
- Final week: recipients run the work with the leaver watching, then gaps are logged and assigned.
If your notice period is short, compress the order but keep it. The ranking comes first, because it decides where the scarce hours go. Better still, don't treat it as a one-time event. SHRM notes that knowledge capture works best as a year-round process, so that a resignation finds you already half prepared.
Getting tacit knowledge out of someone's head
Asking a departing colleague to "write up everything you do" produces a thin document and a resentful colleague. People are often poor at describing their own expertise in writing, because the expertise has become automatic.
APQC notes that tacit knowledge often needs mentoring, peer conversations, storytelling, observation and one-on-one instruction, and that documentation alone may not convey judgment built over years. It groups transfer methods into four families: elicitation (structured interviews, after-action reviews), peer-based transfer, learning (training, job shadowing) and documentation (knowledge bases, desk guides, playbooks, process maps).
SHRM's source makes a practical suggestion: if someone struggles to put their work into words, have a manager or colleague shadow them for a day or two, or have them record their day-to-day duties.
Our own approach borrows from oral history and investigative interviewing. A good interviewer doesn't ask "what's the procedure?" They ask for the last time it went wrong. These questions tend to work:
- "Walk me through the last time you handled this. What did you do first?"
- "When do you skip a step in the SOP, and what tells you it's safe to?"
- "What would a new person get wrong in their first month?"
- "Who do you call when this breaks, and what do you say?"
- "What did we try before that didn't work?"
The answers expose exceptions and reasoning, which is exactly what a written procedure leaves out. Record the conversation (with consent), then turn it into a structured process document that the successor can search. The turning-into-a-document step is where most teams stall, since transcripts nobody reads are just a different kind of lost knowledge. For templates that people actually reuse after the handover, see our guide to project handover documentation, and for the wider picture, how to preserve organizational memory before people leave.
When there is no single successor
Often nobody can simply step into the role. The work gets split, or the replacement arrives months later. NASA's guide covers this case: review the departing member's activities, identify what others can cover, and where a one-to-one transfer is impossible, make sure the people taking on related parts of the role know each other's responsibilities and potential overlaps. A knowledge map showing who is involved in each process helps.
In practice:
- List every recurring duty and active project on one page.
- Assign each a primary and a backup owner, even if the backup is only "knows where to look."
- Mark the duties nobody wants. Those are the ones that quietly lapse.
- Keep the captured knowledge in a searchable shared place, so a future hire can use it without asking the leaver, who will be unreachable.
This is also where the work overlaps with onboarding. Whatever you capture in offboarding is the raw material for whoever comes next, which is why we treat the two as one loop. Our onboarding use case and our piece on piloting onboarding documentation in four to eight weeks show how.
Confirming the transfer worked
A stored document is not a completed transfer. APQC is direct on this point: knowledge has not been transferred just because an expert shared it or a file was saved. The recipient must understand, apply and internalize it.
Its onboarding and offboarding guidance recommends giving recipients chances to ask questions, practice the work, get feedback and demonstrate competency while the departing employee is still available. That suggests a simple test for the last week:
- Pick three real scenarios from the leaver's work, including one exception.
- Have the recipient handle each using only the captured material, with the leaver observing.
- Log every question the recipient had to ask. Each one is a gap in the documentation.
- Fix the gaps while the leaver is still there, then close the handover.
Two further checks catch most failures. Can someone who was never in the room find the material in under a minute? And does it explain why, not just what? A procedure without its reasoning gets followed until the first exception, then abandoned.
Where offboarding knowledge transfer goes wrong
No formal approach. The Training Industry survey cited above named this as the greatest challenge. A template and a named owner fix most of it.
Waiting for the successor. The knowledge is freshest and the leaver most willing during the notice period. A successor arriving in month three finds a thin trail.
Writing it all at the end. Handover crammed into the last two days captures tasks and misses judgment.
Capturing only the leaver's view. Interview the people who depend on their work. They know which parts of the role actually matter.
Treating it as an HR form. The checklist belongs to HR, but the substance belongs to the manager and the team. The same survey found that the most-cited improvement was peer-to-peer and team training, including coaching, shadowing and paired work, named by 23% of respondents. Building a formal process came next at 16%.
For a longer-term view, our guides on building a knowledge retention plan and engineering onboarding documentation show how to make capture routine, so that a resignation is no longer an emergency. Teams that bring in contractors can apply the same thinking, as in our contractor onboarding checks.
Our perspective
We have watched the same pattern many times. A valued person gives notice, someone sends them a template, and two weeks later there is a folder of documents that describes the job as it appears on paper. The person who actually knew when to override the threshold, which customer needs a phone call, and which step in the SOP is pure ceremony, leaves with all of it.
That is the reason Kept exists. Documents hold rules. People hold exceptions and reasoning. So we built a conversational platform where people describe their work in their own words, and guided interviews ask the follow-up questions a good investigator would: what happened last time, why that choice, what would you warn a newcomer about. The result is structured, searchable process knowledge that keeps the context and judgment, not just the steps.
We also think capture should be respectful. Our workspaces are designed to be opt-in, with review and deletion controls, so people stay in charge of what they share. That matters because the best knowledge transfer is given willingly, not extracted on the way out.
If you take one idea from this article, take this: begin before the last week, and ask for the reasoning, not only the steps.
Anthony
Capture the reasoning with Kept
If you want the interview, structuring and search steps handled in one place, Kept for Business gives teams a shared workspace where departing experts document their processes by talking them through, with workspace-level access controls and citation-backed answers for whoever inherits the work. Individuals can use kept for you for their own personal workspace.
Both plans, and how onboarding works, are on the pricing page. If your immediate need is a single departure, our expert handoffs use case is the place to start.
FAQ
How long before an employee leaves should knowledge transfer start?
As soon as the resignation is confirmed. Cal Poly's plan says to begin collecting documentation immediately after learning of the intent to leave. Better still, keep capture running all year, so a departure only needs a top-up.
Who is responsible for offboarding knowledge transfer?
One named person, usually the departing employee's manager, or someone the manager designates. NASA's guide recommends a leader or designee lead each step. HR provides the template and timeline, and the leaver and teammates contribute the substance.
What should a knowledge transfer checklist include?
Core responsibilities, recurring tasks and calendar, active projects, systems and tools, internal and external contacts, standing meetings, known risks and the reasoning behind key decisions. Cornell's checklist and Carleton's template are good starting points. Add exceptions and lessons learned, which standard forms often omit.
How do you capture knowledge that is hard to write down?
Use conversation instead of a blank page: structured interviews, shadowing for a day or two, or recorded walkthroughs of real work. APQC lists these among the main methods for tacit knowledge. Then turn the recording into a structured, searchable document.
How do you know the handover is complete?
When the recipient can apply the knowledge, not when the files are stored. Have them handle real scenarios, including an exception, while the leaver is still around, and fix every gap that surfaces.
Sources
- Offboarding at KI, Staff Portal
- APQC: How Can Knowledge Practices Improve Onboarding and Offboarding
- APQC: How Can Critical Knowledge Be Transferred and Retained When Experts Leave
- SHRM: Capture What Employees Know Before They Leave the Company
- Training Industry and Raytheon: Onboarding and Knowledge Transfer
- Cornell: Knowledge Transfer
- Coassemble: How to build a knowledge transfer checklist
- UK Government: Knowledge and Skills Guidance Note
- Cal Poly: Offboarding Knowledge Transfer Plan
- NASA: Sustaining Knowledge Through Transitions
- Igoa-Iraola and Díez: Procedures for transferring organizational knowledge (PMC)
- Talent Retention Best Practices for HR Leaders in 2026