How Often Should a Small Business Update Its Procedures?
By Bill Stilwell · Last reviewed October 18, 2026
The short answer
Section titled “The short answer”Procedures go stale. Have each procedure’s owner review it on a schedule, ask the people who do the work what’s wrong with it, update it after a mistake or a change in law, tax, insurance, technology, or customer needs, give each update a new version number, record who approved it, and remove old copies so only the current version is in use.
Why it matters
Section titled “Why it matters”An outdated procedure is worse than none, because people trust it. A cleaning company switches scheduling software, but the procedure still shows the old screens, so new hires book jobs wrong. A contractor’s state changes a license rule, and the estimate procedure doesn’t mention it. A simple update routine prevents both.
22.11.1 Owner review
Section titled “22.11.1 Owner review”What it means: the procedure’s owner reviews it.
How to do it: on the review date at the top of each procedure, the owner reads it, walks through it, and fixes anything outdated. Most procedures need a review every 6 or 12 months. Put the dates on a calendar (see 28.4 Annual Review Checklist).
Common mistake: review dates written down but never put on anyone’s calendar.
22.11.2 User feedback
Section titled “22.11.2 User feedback”What it means: feedback from the people doing the work.
How to do it: ask staff what steps they skip, where they get stuck, and what’s missing. Give them an easy way to suggest changes, such as a comment in the shared doc or a note in a weekly meeting.
Common mistake: the owner rewriting procedures alone, missing what really happens on the job.
22.11.3 Incident review
Section titled “22.11.3 Incident review”What it means: update procedures after errors or incidents.
How to do it: after a mistake, complaint, injury, or security problem, ask whether the procedure was followed. If it was and the problem still happened, fix the procedure. If it wasn’t, ask why and fix the training or the procedure (see 11.4.5 Incident Reports and 17.8 Complaint Handling).
Common mistake: blaming the person and never asking whether the procedure made the mistake easy.
22.11.4 Requirement change
Section titled “22.11.4 Requirement change”What it means: update after legal, tax, insurance, technology, or customer changes.
How to do it: when a law, tax rule, insurance policy, software tool, platform rule, or customer expectation changes, list which procedures it affects and update them. Platform rules change often. Google, Bing, and Apple update their listing features and policies, so check the procedures that touch your listings at least a few times a year.
Common mistake: updating the tool but not the procedure that explains how to use it.
22.11.5 Version
Section titled “22.11.5 Version”What it means: assign a new version number.
How to do it: use a simple pattern, like 1.0, 1.1, 2.0. Small fixes get a small bump. Big changes get a new whole number. Keep a short change log at the bottom: date, version, and what changed.
Common mistake: no version numbers, so two people work from different copies and both think theirs is current.
22.11.6 Approval
Section titled “22.11.6 Approval”What it means: record who approved the change.
How to do it: add the approver’s name and date to the procedure header. In a one-person business, that’s you, and the date still matters.
Common mistake: changes made by anyone at any time with no record of who signed off.
22.11.7 Distribution
Section titled “22.11.7 Distribution”What it means: retire old versions and publish the current one.
How to do it: keep one live copy in your shared files (see 12.2 Shared Files). Move old versions to an archive folder marked “retired.” Tell everyone affected what changed, and update training if needed (see 22.10 Training Materials).
Common mistake: printed copies of old procedures still taped to the wall or sitting in the truck.
When to get help from a pro
Section titled “When to get help from a pro”Your attorney, certified public accountant (CPA), or insurance professional can tell you when a rule change affects your procedures. Questions to ask:
- Which rule changes this year affect how we work?
- Which of our procedures should you review before we update them?
- How should we keep old versions in case we need them later?
Bill’s note
Section titled “Bill’s note”[Bill: add a short note. For example, a Google Business Profile change that forced you to update how SiteSmarty manages client profiles, or a procedure that kept causing problems until staff feedback fixed it.]
How I did this for SiteSmarty
Section titled “How I did this for SiteSmarty”- [Date I did this:]
- [What I actually did, step by step: my review schedule, version pattern, and where old versions go]
- [What it cost and how long it took:]
- [What surprised me or what I’d do differently:]
- [Screenshot or photo to add, with private info blurred: a procedure header and change log]
- [Result so far:]
Questions people ask
Section titled “Questions people ask”How often should procedures be reviewed? Every 6 to 12 months, and right away after a mistake or a rule or tool change.
Who should review a procedure? Its named owner, with feedback from the people who do the work.
How do I track versions? Use a version number, an approval date, and a short change log on each procedure.
How do I make sure staff use the latest version? Keep one live copy, archive old ones, and tell people what changed.
Audit check
Section titled “Audit check”| Outline line | Question | Pass looks like | Fail looks like | Evidence to collect |
|---|---|---|---|---|
| 22.11.1 Owner review | Are procedures reviewed by their owner on schedule? | Reviews on time | Overdue reviews | Review dates and calendar |
| 22.11.2 User feedback | Is staff feedback collected? | Feedback channel used | None | Comments or meeting notes |
| 22.11.3 Incident review | Are procedures updated after incidents? | Updates tied to incidents | No changes after problems | Incident log and change log |
| 22.11.4 Requirement change | Are procedures updated after rule or tool changes? | Updates within weeks | Old rules still listed | Change log |
| 22.11.5 Version | Does each procedure have a version and change log? | Version and log | No versions | Procedure doc |
| 22.11.6 Approval | Is approval recorded? | Name and date | No approval | Procedure header |
| 22.11.7 Distribution | Are old versions retired and staff told? | One live copy, archive | Old copies in use | Shared folder and archive |
Where this fits
Do this first: 22.1 Writing Standard Operating Procedures, 22.10 Training Materials
Do this next: 23.1 Deciding Whether to Hire
Related pages: 12.2 Shared Files, 11.4.5 Incident Reports, 17.8 Complaint Handling
Sources
- Google Business Profile Help, "Tips to improve your local ranking on Google" (checked October 18, 2026)
This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.