The Documented Fiction: A Triage for Procedures That Have Drifted

Most organisations do not set out to maintain procedures that no one follows. Drift happens by accretion: a system changes, a team absorbs a workaround, a regulator issues new guidance, a manager retires, and the document remains in place because removing it feels riskier than leaving it. Over time the procedure library becomes reassuringly complete on paper and increasingly unreliable in practice.

The problem is not that documentation exists. It is that some documents no longer describe the work, yet still shape training, audit evidence and management assumptions. For UK organisations, that gap matters most where customer outcomes, regulatory obligations or staff onboarding depend on the document being true. The practical response is not a wholesale rewrite. It is a triage: find the procedures with the widest gap between text and practice, then decide whether to retire, rewrite or automate them.

Why procedure libraries drift

Drift is rarely a single failure. It is usually the compound effect of small, sensible adjustments. A team adopts a quicker route through a CRM system. A shift manager adds a checking step after a near miss. A supplier changes its portal, so staff follow a different sequence from the one documented. None of these changes is necessarily wrong. The issue is that the formal document does not absorb them.

Three conditions accelerate drift. First, procedures are written for ideal conditions rather than normal ones, so staff learn early that the document is a guide rather than a rule. Second, ownership is unclear: everyone assumes someone else updates the document after a process change. Third, the library is measured by completeness rather than fitness, which rewards adding documents and penalises removing them.

The result is a familiar pattern in UK operations: a well-populated intranet, a training pack that references outdated screens, and experienced staff who quietly teach newcomers the real method. The organisation has two processes - the documented one and the lived one - and often pays for both.

Start with evidence, not a full rewrite

A full documentation refresh is expensive and slow, and it often reproduces the same problem because it starts from the documents rather than the work. A better starting point is a focused sample. Select procedures that meet at least one of three tests: they are used frequently, they support a regulated or high-risk activity, or they are central to onboarding.

For each selected procedure, gather three forms of evidence. First, read the document as written and note every system, role, handoff and control it assumes. Second, observe or walk through the work with someone who performs it regularly, asking them to narrate what they actually do and why. Third, inspect artefacts: checklists, screenshots, tickets, exception logs and training materials. The aim is not to catch people out. It is to establish where the document and the work have parted company.

A useful discipline is to record the gap in neutral language. Instead of writing that the team ignores step four, note that step four is performed in a different system and that the documented approval is now captured automatically. This keeps the audit factual and makes later decisions easier to defend.

A three-screen triage

Once the gaps are visible, rank them. A simple three-screen model works well for most UK organisations because it balances external risk with internal cost.

Customer impact

Ask what happens to the customer if the documented process is followed exactly as written, or if the lived process fails. Does the customer receive incorrect information, wait longer, repeat information, or lose confidence? Procedures that sit close to customer commitment, billing, safeguarding or service recovery should rank highly. A gap that adds ten minutes of internal rework is different from one that produces a misleading letter or a missed appointment.

Compliance exposure

Consider regulatory obligations, contractual commitments and internal controls. In regulated sectors, an outdated procedure can become evidence that controls are not operating effectively, even if staff achieve the right outcome another way. The question is not whether the team is acting in good faith. It is whether the organisation can demonstrate that the control described in the document is the control actually in place. Where the answer is uncertain, the procedure should be reviewed promptly.

Training cost

Estimate the effort wasted by teaching a process that is no longer true. This includes induction time, refresher training, supervisor correction and the rework caused when newcomers follow the document and experienced colleagues correct them. Training cost is often the most visible internal signal because it shows up in duplicated effort and slower time to competence.

A simple scoring scale - high, medium or low on each screen - is enough for a first pass. The purpose is to sequence attention, not to create a perfect model. Procedures that score high on customer impact and compliance exposure should move first. Those that score high mainly on training cost can be handled through scheduled updates or automation.

Decide: retire, rewrite or automate

Triage only creates value if it leads to a decision. For each high-priority procedure, choose one of three paths.

Retire the procedure when the work no longer exists, when the risk is adequately controlled elsewhere, or when the document duplicates a system control. Retirement should be explicit: remove the document from the active library, archive it with a note, and tell the people who used to rely on it. A procedure that is left in place but ignored is worse than one that is formally withdrawn.

Rewrite when the work still needs a documented standard but the current text is materially wrong. Rewriting should be narrow. Focus on the steps, roles, systems and controls that have changed, and keep the document short enough to be maintained. A procedure that runs to thirty pages is unlikely to be read during normal work; a concise standard with clear exceptions is more likely to survive.

Automate when the gap exists because the document is asking people to perform a step that a system could handle. Approval routing, data validation, reminders and evidence capture are common candidates. Automation does not remove the need for documentation, but it can reduce the number of manual steps that drift out of date.

Govern the library lightly

A triage exercise is useful once. A light governance routine keeps it from becoming necessary again. Assign each active procedure a named owner and a review trigger - not only a calendar date, but an event such as a system change, a regulatory update, a serious incident or a role redesign. Require owners to confirm annually that the procedure still matches the work, and give them permission to retire documents without a lengthy approval chain.

It also helps to separate standards from guidance. Standards should be few, clear and controlled. Guidance can be more flexible and closer to the team. Many libraries become bloated because guidance is treated with the same weight as a controlled procedure, which makes every update feel bureaucratic.

A thirty-day sequence

In the first week, select a sample of ten to fifteen procedures using the frequency, risk and onboarding tests. In the second week, gather documentary, observational and artefact evidence for each. In the third week, score the gaps and agree the retire, rewrite or automate decision with process owners. In the fourth week, action the highest-risk items, publish a short record of decisions, and set review triggers for the rest.

This is not a documentation programme in disguise. It is an operational resilience exercise. The objective is to reduce the distance between what the organisation says it does and what it can reliably do, without asking managers to rewrite everything at once. A procedure library should be a working instrument, not a museum of past intentions. The organisations that treat it that way spend less time maintaining fiction and more time improving the work itself.