Knowledge handover works when it is scheduled as its own block of the notice period, addressed to a named person, and recorded where the next holder of the role will look. It fails when it is a document the leaver writes in their last two days and emails to their manager.
The notice period is the only fixed resource here. Its length comes from the contract or from the statutory minimum, as Acas sets out for people resigning during probation, and the same principle holds for everyone else. So you know how many working days you have. Book the handover sessions into them on day one of the notice, because every other demand on those days will otherwise take the slot.
What actually needs handing over
Five categories cover almost every role. Anything outside them is usually already documented, in which case the handover should link to it rather than restate it.
The recurring calendar comes first: the weekly close, the monthly report, the quarterly filing, the annual renewal nobody else knows about, each with its trigger date and what it produces. This is the category that causes the most visible failure after a departure, because a missed recurring task surfaces as a surprise rather than as a gap.
Then live work with its current state, which is different from a project list. Each item needs what has happened, what is waiting, and who is waiting for it. "Contract with the Leeds supplier: redlines sent 3 September, waiting on their legal, chase after the 20th."
Then named contacts, internal and external, with what each one is for. A role that works across teams carries a relationship map nobody else has, and it is the first thing to evaporate.
Then access and accounts: which systems the role needs, which of them the leaver holds as an individual rather than through a group, and anything where they are the sole administrator. The NCSC's joiners, movers and leavers framing is useful here, because the point of the list is that access can be revoked when it is no longer needed and changed for movers, and you cannot do either without knowing what is held.
Last, pending decisions. Things the leaver was going to decide and now will not. These get handed to a person with authority rather than written into a document.
Address it to a person
A handover written to "my successor" is a document with no reader. Send it to the manager and, when one exists, the named successor, and put both names at the top.
Where a successor has been planned in advance, the handover can be pointed directly at them. Unframed HR lets a departing person's replacement be planned ahead of the day and applied automatically when the effective date arrives, which means the successor is identified before the leaver has gone rather than after. The plan snapshots the role as it was when the plan was made, so it does not drift as the leaver's record is edited during the notice period.
Where nobody has been named, hand over to the manager plus whoever is actually covering. Record that cover explicitly with a start date and an end date, so the org chart shows who is holding the work rather than showing an empty chair. A cover recorded this way changes nothing about the covering person's own job, which is what makes it easy to end cleanly when the seat is filled.
Write it where the next person will look
The ICO makes a practical point about employment records that applies directly to handover material: organisations should consider central storage rather than arrangements that leave them dependent on individual employees. A handover stored in the leaver's own drive is the same failure mode as the knowledge it was meant to replace.
The test is simple. Six months after the departure, when the successor hits something unfamiliar, can they find the handover without asking HR where it went? If the answer depends on somebody remembering an email thread, put it somewhere else.
Attaching handover material to the role rather than to the person is what makes it survive the second departure as well as the first. The successor inherits the notes with the seat, adds to them, and the next holder gets both.
Three days of sessions beats thirty pages
Written handovers are necessary and insufficient. The parts of a job that are hardest to write down are exactly the parts a successor most needs: why the process has the odd extra step, which supplier answers the phone, what happened the last time somebody tried the obvious thing.
So schedule sessions rather than only requesting a document. A working pattern that fits a four-week notice looks like this: week one, the leaver drafts the recurring calendar and the live-work list. Week two, two sessions with the successor or manager walking through both. Week three, the successor runs the recurring work with the leaver watching. Week four, the leaver is available for questions and does not own anything.
Week four is always the one that gets cut, and it is the only week that tests whether any of the previous three worked.
What HR owns here
HR does not write the handover. HR makes sure it happened, which is a different job.
Put it on the offboarding checklist as the first step, owned by the manager, ahead of anything that logs the leaver out. An offboarding checklist that closes access, devices and paperwork explains why that ordering is load-bearing. Then check it at clearance: the manager cannot sign off until the handover step is closed, which puts a real gate in front of a step that is otherwise easy to leave amber.
When a departure is known well in advance, the same material feeds the replacement decision. The employee lifecycle from signed offer to final day shows where handover sits between notice and the final day, and managed HR services covers running the process with a named partner when the team is stretched.
Answered here.
- What should a handover document contain?
- The recurring work with its dates, the live work with its current state, the named contacts inside and outside the company, the access and accounts that have to move, and the decisions that are pending. Skip anything already written down elsewhere and link to it instead.
- When should knowledge handover start?
- On the day the departure is confirmed, not in the final week. Notice length is set by the contract or by statute, so you usually know exactly how many working days you have. Handover competes with every other demand on those days and loses unless it is scheduled first.
- What if there is no successor yet?
- Hand over to the manager and to a named interim rather than to a role that does not exist. A handover addressed to nobody is filed and never read. If somebody is covering the work in the meantime, record that cover with a start and an end date so it is visible on the org chart.
- How do you capture knowledge from someone who is leaving on bad terms?
- Lower the ambition and raise the specificity. Ask for the recurring calendar, the list of live items with their current state, and the contacts, all of which are factual and verifiable. Judgement and context are given voluntarily and cannot be extracted by a template.