Knowledge Transfer for Departing Employees: A 3-Step Plan

To transfer knowledge from a departing employee, decide what to ask them about, record the answers in their own words, and test the handover with the successor before their last day. The notice period is the only window you get, so start in the first week.

Key takeaways

• Start in the first week of the notice period, not the last.
• Focus on the work only this person does, not their whole job description.
• Record the reasoning and exceptions in their own words, not just the steps.
• Test the handover with the successor while the leaver can still fill the gaps.

Someone hands in notice. And somewhere in the back of your mind a quiet alarm starts: everything that person holds in their head is about to walk out the door.

Most managers treat the notice period as a countdown. It should be a knowledge transfer window. This guide is for the HR or operations lead who has to make it one, plainly, without a project plan nobody will follow.

In short: knowledge transfer for departing employees means getting the know-how that lives in one person's head into a form their successor can use, before the last day. It takes three steps: ask the right people, record the specifics, and test the result with the successor while there is still time to fix it.

Why the notice period decides whether the know-how survives

Think about the last time a tenured person left. What actually broke?

Rarely the job description. It was the production day that got scrapped because one operator knew the machine runs hot after a cold start. The client who nearly walked because nobody remembered why their orders arrive in a strange split. The monthly report no one could reproduce because the steps lived in one person's fingers.

None of that was written down. All of it was real. And the longer the person had been there, the more of it there was. To put a number on it for your own team, work out what a departure costs.

The window is short, whether it is 20 calendar days (the default when an employee resigns in Lithuania) or a month. The person is often still willing to help, but they are already half out, and their attention is finite. Ask them to "write documentation" and you will get a wiki page that says nothing. Sit down with them and ask the right questions while you still can, and you get the thing that actually matters.

A 3-step knowledge transfer plan: who to ask, what to record, when to test it

You do not need a platform to start. You need a sequence.

Step 1: Who to ask

Start with the departing employee, but do not stop there.

• The person leaving knows the decisions and the unwritten rules. They are the primary source.
• Their closest working partners know what they quietly absorbed, the things that never made it onto a ticket.
• The successor knows what they are most worried about getting wrong. Ask them before the interviews, not after.

The worried new owner of the work usually has a sharper list of questions than anyone on the org chart.

Step 2: What to record

Skip the general questions. Ask for the specifics that carry know-how:

• The routines that only make sense in context, like why the Tuesday check happens at all.
• The exceptions and workarounds, the "we always do it this way because once it went wrong" stories.
• The relationships. Who to call, for what, and what they expect from you.
• The judgment calls. When to escalate, when to let it slide, when to take it seriously.

One good prompt beats a form: "Walk me through a day when this went wrong." People remember the failures and the recoveries. That is where the undocumented knowledge hides.

Step 3: When to test it

Do not wait until the last day to test what you recorded.

Play it back to the successor midway through the notice period. Ask them one question: can you do the work from this? Where they stumble is where the handover is thin, and you still have time to go back and fill the gap. A handover that is never tested is just optimism.

A knowledge transfer timeline for any notice period

Plan backwards from the last day. The split works whether the notice is three weeks or three months.

Turning the interviews into a handover the successor can use

The trap is collecting a pile of notes and calling it done. Notes decay. Nobody reads a folder of transcripts on a Friday afternoon.

Turn what you recorded into something someone can pick up on a bad day:

• Structure it around the work, not the person's whole career: the daily things, the monthly things, the rare emergencies.
• Write it in plain sentences, in the second person, the way you would brief a colleague standing next to you.
• Name the moments that need judgment, so the successor knows where the safe path ends.
• Keep a short "who to ask" list. Some knowledge will always live in people, and the successor needs to know which ones.

Then check it once more, with the person still there. The point is not a perfect document. It is a successor who can do the work without calling the person who left.

Common knowledge transfer mistakes

• Waiting until the last week. Leavers are busiest at the end. Start while there is still time for a second conversation.
• Asking for a document instead of a conversation. Few people will write a manual in their final weeks. Most will happily talk through how they work.
• Covering the routine, not the exceptions. The routine is often written down somewhere. The workarounds and judgment calls are not.
• Skipping the test. A handover nobody has tried to use has gaps you only find after the last day.
• Leaving it in one inbox. Put the handover where the successor and the team already look.

Knowledge transfer FAQ

How long does knowledge transfer take for a departing employee?

As long as the notice period allows, so plan backwards from the last day. Book the interviews in the first few days, finish them by the midpoint, and use the rest to test the handover with the successor and fill the gaps.

What should a handover document include?

The recurring work (daily, monthly and the rare emergencies), the exceptions and workarounds, the judgment calls, the reasoning behind past decisions, and a short list of who to ask for what. Organise it around the work, not around the person's career.

What questions should you ask a departing employee?

Questions that pull out specifics, not summaries. "Walk me through a day when this went wrong." "What do you check that nobody asked you to?" "Who do you call when this breaks, and why them?" "What would you warn your successor about in week one?"

Is an exit interview the same as knowledge transfer?

No. A standard exit interview asks why the person is leaving and what the company could do better. Knowledge transfer asks how the work gets done, so the next person can do it. Run both, but keep the questions separate.

Questions about OakHive itself are answered in the OakHive FAQ.

Make the notice period count

You cannot stop a resignation. You can decide what it takes with it.

Run the three steps: ask the right people, record the things that live between the lines, and test the handover while there is still time to fix it. Do that, and the day after their last day feels less like a cliff and more like a handover.

If you want the lightest way to run the interviews, that is what OakHive is for: one guided interview with the person leaving, turned into a searchable handover for the manager, the successor and the team. No script, no form to fill in. See how it works.