Job handover: the complete method (and a checklist so nothing gets lost)

An employee announces they're leaving. Resignation, retirement, an internal move, parental leave: whatever the reason, the same question follows right away. How do we make sure everything they know doesn't leave with them?

The usual answer fits in one word: handover. A few meetings with the successor, a Word document filled in during the last week, and a "you can always call me." Three months later, the successor discovers the gaps one by one.

This guide lays out a handover method that works, even when the notice period is short and the successor hasn't been hired yet. There's a checklist to copy at the end.

Why most handovers fail

They start too late

The handover usually begins once the departure is official, which is the worst possible moment. The person leaving is already halfway out the door, has to wrap up ongoing work, and rarely has the headspace to document anything. The last two weeks turn into a race against the clock.

They rely on live conversations

The classic format is a series of face-to-face handover sessions. The problem is twofold:

1. The person leaving forgets what they do on autopilot. The better you know a job, the less you see its steps. What seems obvious to them will never get said.
2. The person arriving can't retain it all. Three days of intensive handover is an avalanche of information with no context. The successor will need those explanations six weeks later, when they hit the actual case. By then, the person is gone.

They depend on the successor being there

In many small and mid-sized companies, the replacement arrives after the departure. There's nobody to hand over to in person, so the handover boils down to a document nobody will read.

The 3 kinds of knowledge to hand over

Before getting into method, you need to know what to hand over. Every role has three layers of knowledge, and they don't transfer the same way.

The information layer is the easiest, and it's often the only one that really gets handed over. Yet the other two are what separate a successor who copes from one who struggles for six months.

The method in 5 steps

Step 1: map the role (days 1 to 3)

Ask the person leaving to list everything they do, without trying to be exhaustive:

• Day to day: recurring tasks, even the most mundane
• Every month, quarter, year: cyclical tasks, which get forgotten precisely because they're rare (year-end close, a contract renewal, inventory…)
• When something goes wrong: what they do when things break
• People: who they call, what for, and who calls them

An hour is enough for a first version. The manager adds what they see from the outside.

Step 2: prioritize by risk (day 3)

For each item on the list, ask one question: if the successor can't do this, what happens?

• Critical: financial, legal, customer or safety risk. Hand it over first.
• Important: slows the team down or causes mistakes.
• Secondary: the successor will figure it out on their own.

You'll often end up with about ten critical items. That's where the remaining time should go.

Step 3: record the procedures (first half of the notice period)

This is the step that changes everything. Instead of explaining each procedure in a meeting, the person leaving records it on video while actually doing it: they share their screen, talk, and show.

Why it works:

• It's fast: a 6-minute procedure takes 6 minutes to record. Writing it up would take an hour.
• It captures the motions: where to click, in what order, which field not to touch.
• It captures the reflexes: when you do the task for real, you remember to say "careful, here I always check X." That kind of detail disappears in a document.
• It doesn't depend on the successor: they may not be there yet. The videos will wait for them.

A good rule: one video per procedure, between 3 and 10 minutes. Fifteen short, well-titled videos beat one two-hour recording nobody will watch to the end.

With a video knowledge base tool like KnowVault, recording happens straight from the browser, the video is transcribed automatically, and the text becomes searchable. A successor who types "supplier credit note" lands on the exact moment the procedure is explained.

Step 4: hand over judgment (second half of the notice period)

Judgment is the most valuable and the most fragile layer. It doesn't get recorded while doing a task. You have to draw it out with questions:

• "Which three customers need extra care, and why?"
• "What mistake did you make early on that you'd never make again?"
• "When do you step outside the official procedure?"
• "What do you wish you'd known when you started this job?"

The manager asks, the person leaving answers on camera or while narrating their screen. Ten minutes per topic is enough. These are often the videos the successor will watch the most.

Step 5: organize and validate (last week)

The content exists. Now it needs to be usable:

1. Organize the videos and documents in a space dedicated to the role, sorted by theme (daily, monthly, incidents…).
2. Attach the relevant documents to each video: the file template, the contract, the supplier's instructions.
3. Have someone else test one or two procedures. If they get stuck, the video needs to be redone.
4. Plan the successor's viewing: which videos to watch the first week, which to keep for later.

When the successor arrives after the departure

It's the most dreaded case, and yet the method above handles it easily: everything is recorded and organized before the departure. On day one, the successor finds a space that explains their role, procedure by procedure.

Two extra precautions:

• Name a temporary point of contact on the team, who knows the handover space and can answer questions about context.
• Schedule a 30-day check-in to spot what's missing. The point of contact or a team expert can fill the gaps with new videos.

The job handover checklist

Copy it into your task management tool.

Information

• List of access and tools (no passwords: transfer those through the company password manager)
• Key internal and external contacts, with each person's role
• Ongoing files, with their status and next action
• Deadlines for the next three months (renewals, filings, deliveries)
• Where reference files and documents live

Procedures

• List of daily, monthly and yearly tasks
• One video per critical procedure (3 to 10 minutes)
• Documents attached to the videos (templates, contracts, instructions)
• Incident procedures: what to do when things break

Judgment

• Sensitive customers, suppliers or files, and why
• The usual exceptions to the official procedure
• The history of important decisions
• Mistakes to avoid

Validation

• One procedure tested by a colleague
• A viewing path defined for the successor
• A temporary point of contact named
• A 30-day check-in scheduled

Next: never depend on a handover again

The best handover is the one you never have to organize in a rush. Teams that document their procedures as they go, with a few-minute video each time a process changes, have almost nothing to do the day someone leaves. The knowledge is already there.

That's exactly what KnowVault was built for: your experts record what they know how to do in a few minutes, the team finds it in an instant, and the know-how stays in the company when people move on. To see what it looks like, the public demo is open, no sign-up required.

Further reading

• How to onboard a new employee successfully: the complete guide
• How to document a process with video: a 6-step method
• 5 signs your team needs a video knowledge base