Make it last: reviewing your procedures on a schedule
You are at a good point: procedures documented, every step owned, approvals on a clear path, work visible and measured, the first bottleneck treated. One question decides whether that effort lasts: who keeps the written procedure matching reality?
A procedure does not break suddenly, it erodes. A new tool arrives, an employee leaves, a regulatory update is issued, an exception repeats until it becomes the rule. Six months later the file describes an organization that no longer exists, so the team stops opening it. This lesson is about the loop that prevents that: the regular review.
Why procedures go stale
Four causes repeat in almost every organization:
- Tools change: you took requests by phone only, then opened a WhatsApp channel the procedure never mentions.
- People change: a step still carries the name of someone who left, so nobody knows who owns it.
- Regulations change: the competent authority issues a new requirement, so the invoicing or retention step changes while the file does not.
- The exception becomes the rule: you skipped approval for urgent cases, then most cases became urgent.
Signs your procedure has gone stale
You do not need a formal audit. These show up in an ordinary day:
- An experienced employee asks a colleague how to do something already written down.
- A form field nobody has filled in for months.
- A step everyone skips, and nobody complains.
- New hires learn by watching, not from the file.
- A recurring customer question the procedure has no answer for.
None of these is a behaviour problem. Each is a gap between the written and the real. Fix the writing or fix the reality — do not ignore both.
A concrete example: a maintenance workshop
A workshop wrote its intake procedure at the start of the year: the customer calls, reception logs the request, assigns a technician, and confirms the appointment. Three months later the workshop opened a WhatsApp number because customers asked for it.
The procedure did not change. Phone requests are all logged; WhatsApp requests are logged when someone remembers. The owner sees fewer requests in the sheet and hears customers saying we messaged you and nobody replied. The problem is neither the employee nor the new channel — nobody reopened the file.
A review would have caught this within a month with one question: has the way requests reach us changed?
The review loop
You need no complicated system — a fixed date, a clear owner, a written output. This table works for a small or mid-sized organization:
| What is reviewed | How often | Who reviews | Output |
|---|---|---|---|
| Procedure steps against reality | Every 3 months | Procedure owner | Updated version, or confirmation of no change |
| Owner names and permissions | On any team change | Line manager | Updated responsibility table |
| Unused form fields | Every 6 months | Procedure owner | Remove the field or put it back to use |
| Repeated exceptions | Every 3 months | Procedure owner | Change the rule, or stop the exception |
| Regulatory requirements | When an official update is issued | Finance or admin lead | Amend the affected step |
A review ending with no change is not wasted time. Recording reviewed, no change with its date tells you the file is still alive and someone actually looked at it.
Manage change on the procedure itself
Treat an amendment as you would any decision: document it and announce it.
- Version number and date: at the top of the file, so any reader knows whether it is current.
- One change line: what changed and why — WhatsApp added as a request source because most customers now message us.
- Tell the people affected: an amendment that never reaches the person doing the work did not happen.
- An effective date: we work by the new version from this date, not from the moment it was saved.
- Keep the previous version: so you can later see why work ran differently months ago.
A quarterly review checklist
- Has the channel or source of incoming requests changed?
- Is every name mentioned in the procedure still in that role?
- Is there a step that has not been performed once since the last review?
- Has any exception repeated more than a handful of times?
- Has a regulatory requirement touching one of our steps changed?
- Could a new hire carry out the procedure from the file alone?
The last question is the strongest practical test. If a new employee needs a verbal explanation to complete a step, the file is incomplete at exactly that point — and that is where the edit begins.
In short: procedures go stale as tools, people and regulations change and exceptions pile up; the sign is that the team stopped opening the file. Give it a fixed review date and a clear owner: every 3 months for the steps, on every team change for responsibilities, on every official update for regulatory requirements. Document each amendment with a version, a date and a reason, and tell whoever performs it.