Joda Training All articles
Workplace Learning

The Handover Gap: A Practical Knowledge-Transfer Plan for UK Employers

Joda Training
The Handover Gap: A Practical Knowledge-Transfer Plan for UK Employers

An employee resigns. Within an hour, someone has suspended their email account, booked the return of equipment and added a leaver’s checklist to the HR folder. These are necessary steps, but they address the organisation’s administrative risk, not its capability risk. The greater exposure emerges weeks later, when a customer asks why a monthly report has changed, or a supplier chases an approval that used to arrive automatically. The notice period is the last scheduled opportunity to transfer what the departing employee knows. Treating it as a curriculum rather than a countdown makes the difference.

Begin with a task map, not a job description

Job descriptions list responsibilities; they rarely capture the work that keeps a team stable. Before the leaver’s calendar fills with farewell meetings, ask them to list the tasks they perform, including the informal ones that never appear in a formal document. For each task, record how often it happens, what occurs if it is missed, who depends on it, where the information lives and which exceptions regularly arise.

Use a simple red, amber and green priority. Red tasks are those only the leaver can currently perform, carry high operational impact and are deadline-driven. These get first call on notice time. Amber tasks are shared but incompletely understood. Green tasks are documented or easily learned. The map should be reviewed by the line manager and the successor, not left to the leaver alone. A task map produced in isolation tends to reflect what the leaver remembers rather than what the organisation needs.

Name the successor and give them authority

A common failure is to assume that everyone will shadow. In practice, everyone is busy and no one owns the transfer. Identify a named successor or a small group with clear roles. If no internal successor exists, assign a knowledge owner who will maintain notes and coordinate cover. The leaver teaches; the successor records and asks questions; the manager protects time and resolves clashes. Set two or three short checkpoints each week and put them in diaries as appointments, not aspirations.

It also helps to state what the successor is authorised to do. If they can approve a routine request, amend a schedule or contact a supplier without seeking permission from the leaver, they will learn faster and the leaver will be freed to explain judgement rather than administer routine transactions.

Use reverse shadowing to expose assumptions

Traditional shadowing places the successor behind the leaver. Reverse shadowing flips the arrangement: the successor performs the task while the leaver observes. This is more revealing because it surfaces gaps in the successor’s understanding and assumptions the leaver has stopped noticing. Start with lower-risk tasks and move towards higher-consequence work. Use real work rather than slide decks. After each session, the successor writes a short note covering what they did, what surprised them and what they would need to decide alone. The leaver corrects the note. This turns tacit knowledge into a shared record while there is still time to test it.

Reverse shadowing should begin early in the notice period. If it starts in the final week, there is no room to correct misunderstandings or repeat a task. It also gives the leaver a more useful role than simply answering questions as they arise.

Record decisions and contacts, not only steps

Process steps describe sequence; decisions explain judgement. A successor who knows the steps but not the reasoning will either follow them rigidly or abandon them at the first exception. Create a decision log with four columns: situation, options considered, action taken and warning signs. Ask the leaver to populate it for the red tasks. Include the unwritten rules: who needs a phone call rather than an email, which approval can be verbal, and what to do when a deadline collides with a system outage.

Alongside the decision log, build a contact map. List internal colleagues, external suppliers, regulators and customers, with the purpose of each relationship, preferred channel and escalation route. Store both records in a shared location, not in a personal notebook or private inbox. The test is simple: can someone else find and use the record without the leaver’s help?

A four-week skeleton

Week one: complete the task map, agree priorities and name the successor. Week two: the leaver demonstrates red tasks while the successor observes and drafts notes. Week three: reverse shadowing for red and amber tasks, with the decision log and contact map populated. Week four: the successor runs tasks independently while the leaver reviews notes and signs off. The final days should be reserved for validation, not new material. Test access to systems, confirm file locations and check that the successor can answer ordinary questions without asking the leaver. If notice is shorter, compress the schedule but keep the validation step. A handover that has never been tested is only a hope.

Make the line manager accountable

Knowledge transfer fails when it is treated as a personal favour from the leaver. The line manager should own the plan, protect the time and sign off the record. A short checklist helps: task map complete, successor named, red tasks demonstrated, reverse shadowing done, decision log stored, contacts mapped and access confirmed. The leaver should not be asked to write everything from scratch; templates and prompts reduce the burden and improve consistency. Nor should the successor be expected to absorb everything in addition to a full workload. Cover arrangements are part of the plan, not an afterthought.

Test the gap after the door closes

The real evaluation begins after departure. In the first month, track questions that would previously have gone to the leaver, missed deadlines and workarounds invented by the successor. These are not failures; they are evidence of where the handover record needs updating. Hold a short review with the successor and manager, amend the notes and add the lessons to the next handover. Over time, this creates a practical knowledge-transfer routine that reduces reliance on any single person. People leave, and that is normal. The aim is to ensure the organisation learns from the transition rather than discovering it by accident.

All Articles

Related Articles

The Early Warning Habit: Training UK Teams to Surface Concerns Before They Become Crises

The Early Warning Habit: Training UK Teams to Surface Concerns Before They Become Crises

The Relay Baton: Designing Training That Survives a Shift Change

Beyond the Indispensable Employee: Making Skills Cover Ordinary in UK SMEs

Beyond the Indispensable Employee: Making Skills Cover Ordinary in UK SMEs