Knowledge That Walks: A Practical Handover Framework for UK SMEs Facing Senior Departures

Most SMEs do not lose know-how on the day a key person leaves. They lose it years earlier, in the small decisions nobody recorded: the supplier who only responds to the second email, the customer who will accept a price rise if it is framed as a service upgrade, or the spreadsheet that quietly reconciles a payroll export against the nominal ledger.

That is the particular difficulty with handover in a business of 20 to 200 people. Contractual notice periods are designed around continuity of tasks, not continuity of judgement. Four weeks can cover a sequence of meetings; it cannot transfer the pattern recognition that makes those meetings productive in the first place.

What follows is a workable system rather than a template. It rests on three components: a one-page knowledge map, a phased 30/60/90 plan, and a small set of indicators that tell a leadership team whether a resignation would be an inconvenience or a disruption.

Where the knowledge actually sits

Before designing anything, it helps to be precise about what is being transferred. In most SMEs, critical knowledge falls into three categories.

Customer knowledge. Who actually signs off the purchase, how tolerant they are of delivery slippage, which invoice disputes recur, and the informal escalation route that bypasses the account manager.

Supplier knowledge. Realistic lead times as opposed to quoted ones, which account handler resolves problems, what credit terms have been agreed in practice, and where quality has historically slipped.

Operational shortcuts. The workarounds, macros and exception lists that keep processes running. These are the most valuable and the least documented, precisely because they exist to compensate for a weakness in a system nobody has had time to fix.

A handover that captures only the first category produces a successor who can hold a client meeting but cannot resolve an invoice query. All three matter.

Five signals that one resignation could stall the business

It is worth testing your own organisation against the following before a resignation forces the question.

• Only one person can explain how a recurring report or reconciliation is produced.
• The register of system access and credentials has not been reviewed in the past twelve months.
• Customer relationships are described in terms of an individual rather than an account.
• Onboarding a replacement takes months because there is nothing written down to learn from.
• When a single person takes annual leave, decisions stall or are subsequently redone.

Two or more of these signals in the same role indicate a single point of failure. The operational risk is not the departure itself but the absence of a second pair of eyes on the judgement calls that role makes weekly.

Start with a one-page knowledge map

A knowledge map is not a job description and not a process manual. It is an index: a single sheet per role that tells a successor where to look and who else to ask.

Four columns are sufficient: the activity, how often it happens, the systems and access it requires, and where the detail is held. Cap the sheet at fifteen to twenty rows covering the genuinely critical items. If a role needs four pages, the exercise has become documentation and will not be maintained.

Keep the map in a shared repository rather than a personal drive, assign an owner, and review it at each appraisal and each time a process changes. A map that is six months stale is still more useful than none, but only just.

A 30/60/90-day handover plan

Days 1 to 30: capture. The leaver's remaining time should not be consumed entirely by business as usual. Ring-fence a proportion of their week, and treat that cost as trivial against the expense of a stalled account or a botched month-end. Priorities are the knowledge map, a full access and credentials list, recorded walkthroughs of recurring reports, and a written inventory of workarounds with the reason each exists.

Days 31 to 60: shadow and reverse-shadow. The successor performs the work while the leaver observes and corrects. The ten most significant customer and supplier relationships should be handed over in person, by name, with an introduction rather than an email. Exceptions and awkward cases should be documented here, not during the final week.

Days 61 to 90: remove the safety net. The leaver moves to an escalation-only footing and then to nothing at all. The test is simple: can the successor complete a full monthly cycle, or a peak trading period, without asking a question that only one person could previously answer?

Where notice periods are shorter than the plan, an extension is possible through a fixed-term consultancy arrangement, subject to the terms of the existing contract and current ACAS guidance. Where the departure is immediate, through illness or redundancy, the same structure can be compressed into a two-week break-glass version led by whoever holds the closest working relationship.

Making handover a standing discipline rather than a scramble

Exit interviews are routinely wasted. Conducted as grievance sessions, they rarely surface the operational detail that matters. Two questions are worth asking in every case: what would you have done differently, and where does this process break when nobody is watching?

Beyond the exit interview, three habits embed the practice. Every critical role should have a nominated deputy, even if that deputy is a colleague in another function who understands the workflow. A retention and knowledge-risk register should be reviewed alongside financial reporting, not separately from it. And documentation should appear in objectives, because work that is never measured is never done.

A handover system is ultimately a full-circle view of the business: it assumes that the organisation, not the individual, owns the know-how. Firms that adopt that assumption before a resignation arrives tend to find that departures cost them a fortnight of friction. Those that do not tend to find out what a single resignation can cost.