Knowledge transfer before someone leaves: a practical handover plan

When someone leaves, a folder of instructions is useful. It is not proof that their colleagues can carry on without them.

An effective handover transfers the ability to do the work: recognising what matters, making sound decisions, finding the right people and handling exceptions. The most useful test is not “Have they written it down?” but “Can someone else now do this safely and reliably?”

What is knowledge transfer?

Knowledge transfer is the process of helping another person acquire and use the knowledge needed to carry out work. Before someone leaves, this means combining accessible records with explanation, practice and checks of independent performance.

A task handover tells a colleague what needs doing. Knowledge transfer also explains:

• Why the work is done that way.
• How to recognise problems and exceptions.
• Which relationships make the process work.
• Where decisions and authoritative information are recorded.
• When to act independently and when to seek help.

The practical answer is to prioritise critical work, capture its context, practise it together and verify that the receiving colleague can perform it without prompting.

The staged plan below is a practical management approach, not a validated or proprietary model.

Why it matters

Departure exposes dependencies that can remain invisible during normal working life. One person may know which employer needs an early reminder, why a timetable contains an unusual restriction or how to resolve a recurring data error.

In FE and Skills settings, losing that knowledge can interrupt learner support, employer communication, assessment administration and funding-related processes. Elsewhere, it can affect customer service, payroll, operational continuity and supplier relationships.

Documentation alone cannot resolve all these risks. A technically accurate procedure may still leave its reader unable to distinguish a routine exception from a serious problem.

Research by Linda Argote and Paul Ingram describes organisational knowledge as embedded in people, tools and tasks, including the relationships between them. This helps explain why transferring files does not necessarily transfer capability. It does not establish that one particular handover template will work everywhere.

There is also a workload issue. If nobody receives sufficient time, access or authority to take over, the organisation has reassigned responsibility without transferring the means to fulfil it.

Understand the knowledge a task list misses

Knowledge transfer has no single inventor. An influential foundation is the distinction between explicit and tacit knowledge, associated with Michael Polanyi, notably in The tacit dimension (1966). Ikujiro Nonaka later developed an organisational knowledge-creation theory exploring interactions between tacit and explicit knowledge.

In plain English:

• Explicit knowledge can be articulated and recorded, such as a deadline, checklist or system instruction.
• Tacit knowledge includes judgement and know-how that can be difficult to put fully into words, such as noticing that an employer’s apparently routine query signals a wider concern.

This distinction is useful, but it is not a promise that every aspect of expertise can be converted into a document.

For a practical handover, examine four layers.

Layer	What to capture	Useful prompt
Tasks and information	Outputs, deadlines, systems and authoritative records	“What must happen, and where is the current information?”
Decisions	Criteria, trade-offs, limits of authority and escalation routes	“What makes you choose one response rather than another?”
Relationships	Roles, agreed commitments and communication routes	“Who needs to be involved, and at what point?”
Exceptions and warning signs	Unusual cases, recurring failures and recovery steps	“What looks normal at first but needs closer attention?”

Record reasons, not just preferences. “Contact finance before confirming this arrangement because they must approve the cost” is transferable knowledge. “I always email Sam” leaves colleagues dependent on another individual.

Build a handover plan around risk

1. Agree scope, ownership and protected time

Start as soon as the departure is confirmed. The manager, departing colleague and receiving colleague should agree:

• What must continue without interruption.
• Who will own each responsibility.
• How much working time is available for transfer and practice.
• What can be paused, simplified or stopped.
• Who will accept any unresolved risk.

Do not assume one person will inherit the whole role. Split responsibilities explicitly where necessary, and check that each recipient has capacity.

Keep the conversation respectful. Ask what the organisation needs to learn, rather than implying that the departing person has deliberately withheld knowledge.

2. Prioritise by consequence and dependency

List the main responsibilities, then consider:

• Consequence: What happens if this is missed or done incorrectly?
• Urgency: When will somebody next need to do it?
• Dependency: How many people can already perform it reliably?

A monthly process with serious consequences may deserve attention before a daily task that several colleagues understand. An annual process may also be critical if nobody else knows how to start it.

Use a simple working register:

Responsibility	Next deadline	New owner	Transfer method	Evidence of readiness
Employer review scheduling	Next fortnight	Employer engagement officer	Shared planning session and practice	Schedules reviews and explains escalation
Monthly data reconciliation	Month end	Data officer	Demonstration and supervised run	Reconciles a sample and investigates discrepancies
Annual supplier renewal	Next term	Operations manager	Decision brief and introduction	Explains approval route and locates contract

Store it in an approved shared location, not solely in the departing person’s account.

3. Capture the minimum useful operating knowledge

For each critical responsibility, create a short operating note containing:

• Purpose, trigger and expected output.
• Essential steps and checks.
• Links to current source records.
• Access requirements and approval limits.
• Common exceptions and escalation routes.
• Outstanding decisions or commitments.
• Named owner and review date.

Avoid copying policy text into several documents. Link to the authoritative version so the handover does not create competing instructions.

To uncover unwritten knowledge, ask for specific incidents:

• “Talk me through the last time this went wrong.”
• “What did you notice first?”
• “What would a new colleague be likely to miss?”
• “Which workaround should we replace rather than pass on?”
• “What are we still uncertain about?”

Capture unresolved issues honestly. An undocumented assumption should not become an apparent organisational rule simply because it appears in a handover note.

Use paired working to transfer judgement

Paired working should progress from observation to independent action.

First, demonstrate and explain

The departing colleague performs a real or representative task and narrates their thinking: what they check, why they pause, what alternatives they reject and when they would escalate.

An observer should be able to interrupt with questions. Silent shadowing can show the sequence without revealing the reasoning.

Next, reverse the roles

The receiving colleague performs the task while the departing colleague observes. Encourage the learner to explain their decisions.

Ask the observer to avoid stepping in immediately unless safety, confidentiality or a significant operational risk requires it. Otherwise, frequent prompting can conceal gaps in understanding.

Finally, check independent performance

Agree what successful performance looks like before the check. Depending on the work, this might mean that the receiving colleague can:

• Complete the task accurately using approved guidance.
• Explain the important checks and decision points.
• Handle a representative exception.
• Recognise their authority limits.
• Locate help without relying on the departing colleague.

Independent working does not mean working from memory or never asking for help. It means using normal resources and escalation routes without requiring the departing person to guide every step.

For infrequent or high-consequence work, use a simulation or sandbox. One successful routine attempt does not establish competence in every possible situation.

Record demonstrations carefully

Short recordings can be useful for visual or multi-step processes. They should supplement practice, not replace it.

Before recording:

• Explain the purpose, audience, storage location and intended retention period.
• Obtain appropriate agreement to participation and follow organisational recording requirements.
• Confirm the lawful basis for processing any personal data with the relevant organisational lead.
• Use dummy or suitably anonymised information wherever possible.
• Close unrelated windows and disable notifications.
• Avoid capturing passwords, private messages or sensitive learner, employee or customer information.

Agreement to appear in a recording is not automatically the organisation’s UK GDPR lawful basis. ICO guidance explains that consent can be problematic where there is a power imbalance, including employment.

Use approved tools and restricted storage. Add a clear title, date, accessible captions or a transcript, and a brief written checklist. Set a review or deletion date: a recording of an obsolete process can mislead its next user.

Never transfer access by sharing passwords or authentication codes. Arrange authorised access through the normal process and remove the departing person’s access at the appropriate time.

Two examples in practice

The following examples are illustrative, not reports of particular providers or workplaces.

An apprenticeship coordinator leaves an FE college

The initial handover contains employer contacts and review dates. Discussion reveals something more important: changes to some employers’ shift patterns regularly disrupt appointments, and the coordinator negotiates alternatives through agreed workplace contacts.

The manager arranges joint introductions, records commitments in the approved system and asks the receiving colleague to schedule the next review cycle. They also work through a scenario involving repeated non-response.

The handover is ready when the new coordinator can organise the cycle, explain the escalation route and distinguish a scheduling issue from a concern requiring specialist support. Learner information remains in the authorised system, not a separate handover spreadsheet.

A workplace operations officer owns a monthly reconciliation

The written process says, “Check totals and resolve differences.” It does not explain how the officer distinguishes a timing difference from an incorrect entry.

The officer demonstrates the process using a sanitised sample and records a short explanation of the main decision points. The replacement then works through a different sample containing both routine and unusual discrepancies.

The manager checks the output and the reasoning. A gap emerges around approval limits, so these are clarified before ownership transfers.

The benefit comes from exposing the missing judgement, not from producing a longer recording.

Adapt the plan when time is short

With several weeks available, use an early period for mapping and capture, a middle period for paired work, and the final period for independent checks and unresolved issues.

With only a few days:

1. Protect imminent deadlines and high-consequence work.
2. Assign named owners.
3. Secure authorised access and locate source records.
4. Demonstrate the most critical processes.
5. Record gaps and agree temporary controls.

If the person has already left, reconstruct knowledge through system records, colleagues, process owners and relevant external contacts. Mark assumptions as unverified. Do not treat silence in the records as evidence that no action is needed.

Do not assume unpaid availability after departure. Any continuing support should be separately agreed, including scope, payment where applicable, confidentiality and access arrangements.

Limitations and common misunderstandings

A handover cannot instantly replace years of expertise. Complex work may require continuing coaching, formal training or supervised practice.

Nor should every existing practice be preserved. Workarounds may be unsafe, inefficient or inconsistent with policy. Retain useful insight while correcting the process.

Relationship knowledge must remain professional. Record responsibilities, preferences and commitments, not gossip or speculative judgements about individuals.

Use complementary approaches where appropriate:

• Cross-training reduces dependency before anyone leaves.
• Standard operating procedures support stable, repeatable work.
• Job rotation and communities of practice spread expertise over time.
• Business continuity planning prepares for sudden absence as well as planned departure.
• Formal competency assessment may be necessary for regulated or safety-critical activities.

The manager remains accountable for resourcing the transition and accepting residual risks. A departing employee’s completed checklist does not discharge that responsibility.

Summary and your next step

An effective handover transfers tasks, judgement, relationships and exception-handling. Documentation provides a reference; paired working builds understanding; independent practice reveals whether the transfer has worked.

Your next step: identify one responsibility that currently depends on one person. Name a backup and arrange a paired session in which the backup performs the work and explains their decisions.

Sources and further reading

• Argote and Ingram: Knowledge transfer, a basis for competitive advantage in firms. Foundational research on where organisational knowledge resides and how it transfers.
• Nonaka: A dynamic theory of organizational knowledge creation. An influential theoretical account of tacit and explicit knowledge, rather than a tested departure-handover checklist.
• ICO: A guide to lawful basis. Guidance for deciding how personal data can lawfully be processed, including the limits of consent.
• ICO: A guide to the data protection principles. Guidance relevant to minimising, securing, maintaining and retaining handover information.
• HSE: Management standards, change. Practical guidance on communication, consultation and support during organisational change.