Stop staff using an old procedure after you change it

Find where the old versions live

Before creating a new document system, list the places staff already look: a printed folder, a photo in chat, a note beside the till or a saved file on the tablet. Ask a weekend colleague which copy they use. Your assumed official location may not be their practical reference.

A restaurant manager's communication-access problem and an operator's noisy-chat account both show why publishing an update is not the same as making it usable. The current instruction needs an obvious home that every relevant shift can reach.

Put a small identity block on the procedure

Use a task name staff recognise, an owner, a revision identifier and an effective date where relevant. Explain which equipment, product or location the instruction applies to. A heading such as 'Closing process final final' cannot reliably distinguish the approved copy.

The identifier can be simple: version 3, revised 29 October 2026. Do not create a numbering system so elaborate that nobody maintains it. What matters is being able to compare two copies and know which one applies.

Where possible, keep a stable location for the current instruction instead of sending a new file link with every edit. The version changes inside the reference, while the route from a task or workstation remains predictable.

Procedure identity
Task name:
Applies to:
Owner:
Current version:
Effective from:
What changed:
Approver where required:
Next review trigger:
Location of the current copy:

Approve the method before changing the reference

For ordinary service work, a designated manager may approve the update. Technical or safety changes need the relevant competent input and your proper review process. HSE's training guidance reinforces that clear information and instruction must accompany work; a revision stamp alone does not provide that instruction.

Avoid editing a live document halfway through a shift without explaining when the change takes effect. Where immediate action is required for safety, communicate it directly and follow the relevant controls rather than waiting for a routine document update.

Further reading: HSE: information, training and supervision

Use a deliberate changeover

Original retail example: the shop changes its click-and-collect packing sequence. The manager approves version 2, replaces the counter printout, updates the shared article and briefs each affected shift. The announcement describes the changed step and points to the current copy.

Keep a record of any colleague who still needs the briefing. Remove obsolete local downloads where you control them. Where an archived version must be retained, label it clearly and keep it outside the normal working view.

Test the route a real worker will take

Ask someone who missed the original announcement to find the procedure and explain the changed step. If they retrieve the old screenshot, fix that route. If they find the new document but cannot interpret it, improve the wording or demonstration.

Review the system when equipment, suppliers, recipes or shop layouts change. A calendar reminder can help, but it will not catch every event that makes a procedure wrong. Assign responsibility for noticing those triggers as well as for editing the text.