The Expertise Exit: Auditing Know-How Before Retirement Takes It

UK organisations are usually disciplined about counting people who are due to retire. They track headcount, notice periods, pension enrolment and succession boxes. Far less disciplined is the count of what those people know. The result is a familiar operational risk: a process continues on paper after a retirement, but the judgement that made it work has already left the building.

Why retirement risk hides in plain sight

Retirement planning often sits with HR, while operational risk sits with service or production leaders. Between those two conversations, critical knowledge can fall through the gap. A long-serving manager may be the only person who knows why a supplier is handled in a particular way, which customer complaint needs an early call, or where a system workaround fails at month-end.

These are not usually recorded as risks because they do not look like failures yet. They look like competence. The danger only becomes visible when the person is unavailable and routine decisions begin to stall.

A knowledge-risk audit does not attempt to document everything. It concentrates on the small number of processes and customer outcomes where experience is doing work that procedures do not capture.

Start with a knowledge map, not a staff list

Begin with the work, then attach names. Identify the processes, customer relationships and decisions that would be materially disrupted if a key individual were absent for a month. Include informal activity: approvals, escalations, supplier negotiations, quality judgements, regulatory correspondence and the quiet workarounds that keep systems usable.

For each item, record the current holder, their likely retirement or role-change date, who else can perform the work to the same standard, and where the knowledge currently resides. The last point matters. Knowledge held in a folder is different from knowledge held in someone's memory, and different again from knowledge held in a customer relationship.

A simple scoring template

Use a five-field score for each critical process or customer outcome. A simple additive model is sufficient for prioritisation:

• Impact if the knowledge is unavailable (1–5): 1 means minor inconvenience; 5 means a customer, regulatory or safety failure.
• Concentration (1–5): 1 means several people can cover; 5 means one person holds the judgement.
• Urgency (1–5): 1 means more than 18 months away; 3 means six to 18 months; 5 means under six months.
• Documentation quality (1–5): 1 means tacit and undocumented; 5 means clear, tested and accessible.
• Transfer readiness (1–5): 1 means no named successor or training plan; 5 means a competent successor is already operating independently.

Exposure score = impact + concentration + urgency + (6 − documentation) + (6 − transfer readiness).

The maximum is 25. In practice, anything scoring 18 or above should be treated as a priority transition. Scores of 13 to 17 need active monitoring and a named owner. Lower scores can be reviewed through normal management routines.

The value of the template is not precision. It is consistency. It forces managers to compare a retiring specialist in a quiet back-office role with a customer-facing team leader whose departure is more visible.

Reading the scores

High scores usually cluster around three patterns. The first is deep technical judgement that has never been written down because it is exercised rarely but matters greatly. The second is relationship knowledge, where a customer or supplier trusts an individual rather than the organisation. The third is system knowledge, where workarounds have become the real process.

Each pattern needs a different response. Technical judgement may require structured documentation and supervised practice. Relationship knowledge may require joint account visits and a deliberate transfer of contact. System knowledge may require fixing the underlying process rather than transcribing the workaround.

A 30-day plan

Days 1–5: agree scope. Select the business units, processes and customer groups to include. Ask HR for retirement and role-change data, but do not rely on notice periods alone; some knowledge loss begins during phased retirement or long-term leave.

Days 6–10: interview and observe. Speak to departing staff and their managers. Watch the work being done. Ask what takes longer when the usual person is away, and which decisions colleagues escalate rather than make.

Days 11–15: score and validate. Apply the template with two managers independently where possible. Discuss differences; they often reveal hidden dependencies.

Days 16–20: agree actions. For each priority item, choose one of four responses: retain through flexible working or phased retirement; transfer through shadowing and joint decision-making; document through a tested procedure; or redesign the process to remove the dependency.

Days 21–25: begin transfer. Set specific handover milestones rather than generic 'knowledge capture'. A successor should make decisions under observation, not simply read a document.

Days 26–30: establish governance. Add the register to operational risk reporting, assign review dates and define what evidence will show that transfer has worked. Repeat quarterly for roles with retirement or restructuring exposure.

Turning retirement into a managed transition

The aim is not to keep every retiring employee indefinitely, nor to create a bureaucratic archive of everything they know. It is to make sure the organisation knows where it is exposed before the leaving date arrives. A modest register, scored consistently and reviewed with discipline, gives UK managers a practical way to protect continuity without treating experience as a compliance exercise.