VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

How Educational Knowledge Survives Staff Turnover | Handover, Tacit Knowledge and Institutional Memory

Three secondary students review open books and notes together in a classroom.

eduKateSG · Teacher Workforce Renewal · Educational Knowledge Continuity · 2 October 2026

A school can replace a departing staff member and still lose the role. The new person may inherit the timetable, title and files but not the judgment that makes the work reliable: which exceptions matter, where the policy is ambiguous, when a routine fails, who must be consulted, how standards are calibrated and why a seemingly unnecessary step exists.

This guide develops SG-AUD-20260929-11 as a distinct knowledge-continuity child beneath Teacher Retirement & Workforce Renewal. It connects to Practice Sustainment, Implementation Support Systems and Teacher Inquiry. The parent owns staffing renewal; this page owns the narrower question of whether critical knowledge survives the transition.

The wider organisational evidence shows why the problem deserves its own mechanism. A 2023 two-part systematic review of knowledge loss induced by member turnover synthesised 91 empirical studies and documented both the effects of turnover-related knowledge loss and a range of coping and preventive mechanisms. A 2024 systematic review of knowledge-transfer procedures during generational change similarly highlights digitalisation, communication and collective approaches to tacit and explicit knowledge transfer.

A concrete institutional case comes from the OECD’s 2024 description of USAID’s Knowledge Retention and Transfer model. Frequent staff rotations had produced risks of lost momentum, duplicated work and frustration; the response was a standardised set of handover tools, processes and transition practices tested across missions. Schools are not aid agencies, but the mechanism is transferable: recurring turnover requires institutional handover, not heroic memory.

Staff turnover can remove knowledge before it removes headcount

Staff turnover can remove knowledge before it removes headcount is mainly about seeing departure as a capability transition rather than only a vacancy. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a department losing the person who knows how assessment moderation actually works. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is treating replacement hiring as complete continuity. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the successor can reproduce critical decisions, not merely occupy the role. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Explicit and tacit knowledge leave differently

Explicit and tacit knowledge leave differently is mainly about distinguishing what can be written from what is carried in judgment. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a policy document being preserved while exception-handling skill disappears. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is assuming a shared drive captures expertise. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that handover includes records and demonstrated practice. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

The first handover task is identifying what matters

The first handover task is identifying what matters is mainly about avoiding memory dumping. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is listing critical decisions, recurring exceptions and failure points before collecting files. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is asking the departing employee to upload everything. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the handover prioritises knowledge that affects continuity. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Knowledge risk should be mapped before departure is imminent

Knowledge risk should be mapped before departure is imminent is mainly about moving continuity work earlier. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is identifying single-person dependencies in a department annually. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is waiting for a resignation letter. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that high-risk knowledge has a continuity plan. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Role descriptions rarely capture the real job

Role descriptions rarely capture the real job is mainly about seeing difference between formal duties and operational knowledge. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a teacher’s official role saying assessment while the real expertise includes moderation, timing and escalation. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is using the job description as the entire handover checklist. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the workflow is mapped from actual practice. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Decision rules are more valuable than document lists

Decision rules are more valuable than document lists is mainly about preserving how choices are made. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is recording when a student case needs escalation rather than just where the form is stored. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is handing over folders without judgment criteria. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the successor understands why an action is chosen. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Exceptions reveal tacit knowledge

Exceptions reveal tacit knowledge is mainly about using unusual cases to expose hidden expertise. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is asking the departing teacher how they handle incomplete evidence or contradictory student data. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is documenting only the normal process. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that handover includes boundary cases. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Failure stories are valuable institutional memory

Failure stories are valuable institutional memory is mainly about preserving what went wrong and how it was repaired. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is recording why a previous timetable process failed during examination season. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is keeping only final successful procedures. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the successor inherits lessons as well as polished outputs. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Demonstration transfers practice better than prose alone

Demonstration transfers practice better than prose alone is mainly about using worked examples and live walkthroughs. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a department head showing how moderation decisions are made on real anonymised work. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is writing a manual and assuming it is enough. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the successor can perform the workflow under observation. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Teach-back checks transfer

Teach-back checks transfer is mainly about requiring the successor to explain or perform the process. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is the incoming coordinator running the next moderation meeting with the predecessor observing. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is ending handover after one explanation. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the successor demonstrates usable understanding. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Shadowing works when attention is guided

Shadowing works when attention is guided is mainly about turning observation into structured learning. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is the successor watching a complex parent meeting with a checklist of decision points. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is sitting beside the predecessor without knowing what to notice. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that observation focuses on invisible judgment. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Reverse shadowing reveals gaps

Reverse shadowing reveals gaps is mainly about letting the successor work while the expert watches. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is the new staff member running a process and receiving correction. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is assuming attendance equals transfer. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that performance exposes what was not understood. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Overlap time is a high-value resource

Overlap time is a high-value resource is mainly about creating a period where both people can act on the same work. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is scheduling two weeks of shared responsibility for a critical role. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is planning the successor to start after the predecessor leaves. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that handover includes real joint work. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Not every role gets overlap

Not every role gets overlap is mainly about designing alternatives when departure is abrupt. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is using recorded walkthroughs, peer interviews and archived cases. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is giving up because direct overlap is impossible. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that continuity has fallback methods. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Teams preserve more knowledge than individuals

Teams preserve more knowledge than individuals is mainly about distributing understanding across several people. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is cross-training two teachers on a specialised assessment process. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is allowing one expert to remain the only person who knows the workflow. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that critical capability has more than one holder. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Communities of practice carry living knowledge

Communities of practice carry living knowledge is mainly about using peer interaction to keep methods current. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a subject team discussing difficult cases regularly. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is treating knowledge management as a document repository only. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that practice is rehearsed socially. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Structures can buffer turnover

Structures can buffer turnover is mainly about embedding knowledge in routines, roles and systems. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a standard moderation cycle surviving staff changes. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is depending on one person’s memory to trigger every step. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the organisation carries part of the knowledge. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Too much structure can freeze outdated practice

Too much structure can freeze outdated practice is mainly about keeping institutional memory revisable. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is reviewing the moderation protocol after curriculum changes. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is treating old procedures as sacred because they survived. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that continuity includes correction. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Version control matters

Version control matters is mainly about knowing which procedure is current. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is dating and owning assessment guides. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is keeping multiple conflicting documents in shared folders. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that staff can identify the authoritative version. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Ownership matters after handover

Ownership matters after handover is mainly about assigning responsibility for maintaining the knowledge. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is naming a current process owner for each critical guide. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is assuming documentation maintains itself. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that someone is accountable for updates. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Source provenance matters

Source provenance matters is mainly about preserving where a rule came from. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is linking a school process to the current policy or assessment source. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is copying inherited rules without origin. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that successors can verify and refresh the basis. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Handover should distinguish policy from local habit

Handover should distinguish policy from local habit is mainly about preventing accidental institutionalisation of preference. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is marking which steps are required and which are team conventions. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is describing one predecessor’s style as mandatory. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the successor knows what can be changed. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Handover should distinguish current state from history

Handover should distinguish current state from history is mainly about reducing noise. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is keeping active procedures separate from archived past versions. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is mixing every historical note into the live manual. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that current action is easy to identify. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Meeting calendars are part of knowledge

Meeting calendars are part of knowledge is mainly about preserving timing dependencies. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is recording when moderation, reporting and parent communication must happen relative to terms. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is documenting tasks without when they occur. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the successor can reconstruct the annual rhythm. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Relationships are knowledge channels

Relationships are knowledge channels is mainly about recognising who must be consulted. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is mapping internal and external contacts for recurring decisions. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is preserving only procedures and losing stakeholder routes. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the successor knows who holds complementary knowledge. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Boundary roles are especially vulnerable

Boundary roles are especially vulnerable is mainly about protecting people who connect departments. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a coordinator who translates between curriculum, IT and operations. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is replacing only their formal tasks while losing the network. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that cross-boundary knowledge is captured. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Leadership turnover carries cultural knowledge

Leadership turnover carries cultural knowledge is mainly about seeing norms and decision history beyond formal strategy. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is recording why certain routines exist and what values they protect. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is copying goals without institutional history. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that successors can adapt without accidentally removing safeguards. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Teacher turnover can affect curricular memory

Teacher turnover can affect curricular memory is mainly about preserving sequencing and misconception knowledge. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a subject team retaining notes on where students typically struggle in a unit. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is starting each year as if prior teaching evidence never existed. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that curriculum improves cumulatively. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Assessment knowledge is especially consequential

Assessment knowledge is especially consequential is mainly about protecting standards and moderation judgment. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is keeping exemplars and annotated borderline cases. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is preserving only mark schemes. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that new staff can calibrate decisions. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Student-support knowledge requires privacy boundaries

Student-support knowledge requires privacy boundaries is mainly about preserving continuity without oversharing sensitive information. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is passing only necessary current support information through authorised channels. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is copying personal detail into general handover notes. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that continuity respects data governance. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Technology can support but not replace handover

Technology can support but not replace handover is mainly about using searchable repositories and recordings intelligently. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a tagged knowledge base with current owners and examples. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is assuming an AI search layer fixes poor source quality. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the system points to reliable underlying material. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

AI summaries need source traceability

AI summaries need source traceability is mainly about keeping generated handover concise without losing evidence. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is a draft summary linked to original procedures and cases. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is accepting a fluent synthesis with no provenance. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that every consequential claim can be checked. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Searchability is part of continuity

Searchability is part of continuity is mainly about making knowledge findable by future staff. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is consistent naming and metadata for policies and exemplars. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is storing files under personal filenames. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that a newcomer can retrieve information without knowing the predecessor. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Access rights should survive role change correctly

Access rights should survive role change correctly is mainly about closing personal access while preserving institutional assets. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is moving owned documents to shared repositories before departure. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is leaving critical files in a departing account. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that knowledge survives identity changes. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Exit interviews should target knowledge, not only HR sentiment

Exit interviews should target knowledge, not only HR sentiment is mainly about using departure conversations to identify risks and lessons. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is asking what work depends uniquely on the person and what the successor will likely misunderstand. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is focusing only on reasons for leaving. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that the organisation learns from the transition. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Retirement is predictable enough for deeper transfer

Retirement is predictable enough for deeper transfer is mainly about using longer lead time where possible. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is phased handover of specialised teaching or leadership expertise. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is waiting until the final month despite years of visibility. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that predictable exits support planned continuity. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Unexpected turnover requires resilience, not perfect prediction

Unexpected turnover requires resilience, not perfect prediction is mainly about designing systems that tolerate sudden loss. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is keeping current procedures and shared ownership even when nobody plans to leave. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is assuming every departure will offer handover time. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that critical work can continue after abrupt exits. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Knowledge retention should not become knowledge hoarding

Knowledge retention should not become knowledge hoarding is mainly about avoiding incentives for people to protect status through exclusivity. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is recognising and rewarding documentation, mentoring and cross-training. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is making expertise valuable only when nobody else has it. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that sharing increases rather than reduces professional value. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

Successors should be allowed to improve the system

Successors should be allowed to improve the system is mainly about preserving capability without cloning the predecessor. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is using inherited knowledge as a baseline and reviewing it after real use. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is requiring exact imitation of the departing expert. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that continuity and adaptation coexist. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

The return test is operational continuity

The return test is operational continuity is mainly about checking whether the organisation still performs after the transition. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is the new team completing the first reporting cycle accurately without emergency rescue. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is declaring handover complete when files are transferred. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that real work verifies that knowledge survived. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

A later review closes the handover loop

A later review closes the handover loop is mainly about examining what was missed once the successor has experience. Educational organisations carry knowledge in people, documents, routines, relationships, examples and shared standards. A continuity plan should therefore ask not merely what files leave with a person, but what decisions would become slower, riskier or inconsistent if that person disappeared tomorrow.

A practical example is meeting after one term to update the handover package. The example matters because tacit knowledge often becomes visible only when a real case arrives. Someone who knows the work notices signals that a manual may not describe. Handover becomes stronger when those cues are surfaced through walkthroughs, cases, shadowing and teach-back rather than relying on prose alone.

The common failure is never revisiting the transition. This usually produces a large archive and a weak transition. The successor receives documents without knowing which are current, critical or optional. Or the departing expert transfers habits without explaining their source, causing personal style to harden into institutional rule. Good continuity needs both preservation and interpretation.

The acceptance test is that future handovers improve from evidence. The successor should be able to perform the critical work, explain the decision rules, locate authoritative sources, handle representative exceptions and update the system when conditions change. Knowledge has survived only when the organisation can still act reliably after the person has gone.

A practical school knowledge-handover sequence

  • Identify the decisions and services that would fail or slow if the person left.
  • Separate explicit records from tacit judgment, relationships and exception knowledge.
  • Choose representative cases that expose how decisions are actually made.
  • Create or update one authoritative source for each critical process.
  • Use demonstration, shadowing and teach-back where judgment matters.
  • Assign a successor or shared owner before the transition closes.
  • Move institutional assets out of personal accounts and confirm access.
  • Review the first real cycle after turnover and update the handover package from what was missed.

A worked case: the assessment coordinator leaves

The obvious handover is the assessment calendar, templates and mark schemes. The hidden knowledge is richer: which departments need reminders early, how borderline cases are moderated, what happens when evidence is incomplete, who owns appeals, how files are named, which deadlines are externally fixed and which can move, and what previous failure caused the current checking step.

A strong handover therefore includes one annotated annual calendar, authoritative policy links, two or three representative moderation cases, a live walkthrough, a reverse-shadowed cycle where the successor leads, and a review after the first assessment period. The aim is not to reproduce the predecessor’s personality. It is to preserve the capability of the system.

Frequently asked questions

Is staff handover just documentation?

No. Documentation is necessary for explicit knowledge, but tacit judgment, exception handling, relationships and practical skill often require demonstration, dialogue and supervised practice.

What knowledge is most at risk during turnover?

Knowledge held by one person, used infrequently, poorly documented, difficult to observe, highly contextual or critical to consequential decisions is especially vulnerable.

How early should handover begin?

For predictable retirement or rotation, continuity planning should begin well before the final weeks. For all critical roles, shared ownership and current documentation should exist even when no departure is planned.

What is tacit knowledge?

Knowledge expressed through judgment, pattern recognition and practice that may be difficult to write fully. It often appears in how experts handle exceptions and uncertainty.

Should every departing employee create a huge manual?

No. Prioritise critical workflows, decisions, sources and exception cases. A focused, current handover is usually more usable than a memory dump.

Can recordings replace overlap time?

They can help, especially when direct overlap is impossible, but they are weaker than live practice when the role depends on judgment, questioning and adaptation.

How should student information be handed over?

Use authorised channels, minimum necessary data and current data-governance rules. Knowledge continuity does not justify unrestricted sharing of sensitive learner information.

Can AI help with handover?

AI can help summarise, search and organise authorised material, but source quality, access controls and provenance remain necessary. A generated summary should not become the only institutional record.

How do we know a handover worked?

Observe the successor completing real critical work without emergency dependence on the predecessor, then review what information or practice was missing.

Should successors follow the old process exactly?

Not forever. They should understand the inherited rationale well enough to preserve necessary controls and improve parts that no longer earn their cost.

The quiet conclusion: institutions must remember without becoming unable to change

Educational knowledge lives in more places than a shared drive. It lives in the sequence of a curriculum, the interpretation of a standard, the memory of a failed rollout, the relationship between teams, the mentor’s eye for a recurring misconception and the quiet habit that prevents a predictable error.

Turnover becomes dangerous when those forms of knowledge are allowed to remain private until departure. The stronger institution distributes critical capability while people are still present, keeps authoritative records current, rehearses the handover through real work and reviews what survived afterwards. That is how a school can lose a person without losing what the organisation learned.