How Often Should SOPs Be Reviewed? A Review Schedule That Sticks

The short answer

Review most SOPs every 6 to 12 months, and review an SOP right away whenever the tool, price, rule, role or customer promise behind it changes. Procedures that walk through software deserve a look every quarter; stable routines can wait a year. Every SOP needs a named owner and a next review date written on it.

That lines up with long-standing quality guidance. The U.S. EPA’s guidance on preparing SOPs says SOPs should be updated whenever procedures change and also reviewed on a periodic basis, giving every one to two years as an example, with the review date added to each SOP (EPA QA/G-6, Guidance for Preparing Standard Operating Procedures). A lab with a quality department can work on that cycle. A 12-person team whose tools and prices change every few months usually needs a shorter one.

Why SOPs go stale faster than you expect

Nobody decides to let an SOP rot. It happens quietly, one small change at a time:

• Software moves the buttons. A menu gets renamed, a setting moves, and step 4 no longer matches the screen.
• Prices and packages change. The SOP still quotes last year’s plan or last year’s discount rule.
• People change. The person named in step 6 left, or the role was split in two.
• Workarounds become the real process. The team found a faster way and never wrote it down.
• Promises to customers change. Turnaround times, refund terms or onboarding steps get updated in sales but not in the SOP.

An out-of-date SOP does more damage than a missing one, because people trust it. That is why the review schedule matters as much as the first draft.

How often to review each type of SOP

One interval for everything is easy to set and easy to ignore. Match the interval to how fast the work behind the SOP changes. These are starting points for a small business, not rules; if a regulator, insurer or contract sets a schedule for you, that schedule wins.

If you are starting from zero, do not try to schedule everything at once. Give the ten SOPs people use most a 6 month interval and adjust after the first round, once you see which ones actually changed.

What should trigger a review before the due date?

The calendar catches slow drift. Events catch everything else, and they matter more. Review the SOP that week when:

1. A tool it uses is replaced or gets a major update.
2. A price, package, discount or payment term changes.
3. The owner or a person named in it leaves or changes role.
4. Someone makes a mistake while following it, or a customer complains about the result.
5. Someone asks a question the SOP should have answered.
6. A team member flags a step as wrong or unclear.
7. A new legal, insurance or client requirement applies to the work.
8. The team quietly started doing it a different, better way.

A good rule: if a change would make someone doing the task for the first time do it wrong, update the SOP before the next person does that task.

Who should review an SOP?

The owner reviews it. The owner is the person who leads that work, not whoever happened to type the document. Their job is to keep it true and to decide what changes.

The owner should not review alone. Pair them with one person who does the task regularly, because the people doing the work notice drift first. The EPA guidance makes a similar point about drafts: it is especially helpful when an SOP is tested by someone other than the person who wrote it.

Small teams rarely have a quality department, and they do not need one for this. Owner plus doer is enough for most SOPs. Add a manager’s sign-off only for SOPs that involve money, safety or legal risk.

One more rule that saves a lot of pain: when someone leaves or changes role, move ownership of their SOPs as part of the handover. An SOP whose owner has left is an SOP nobody will review.

How to run an SOP review in 7 steps

A review is not a rewrite. Most of the time you are confirming that the SOP is still right and setting the next date.

1. Put the SOP next to the real work. Watch someone do the task, or do it yourself with the SOP open. Reading it at your desk misses what has changed.
2. Check every step against reality. Mark steps that are missing, no longer needed or in the wrong order.
3. Check the details that rot first. Links, screenshots, menu names, prices, amounts, deadlines and people’s names.
4. Read the feedback since the last review. Comments on steps, questions people asked and mistakes that were made.
5. Decide what to do with it. Keep it, update it, split a long one into two, merge it with a near-duplicate or retire it.
6. Make the change and record it. Keep the earlier version so you can see what changed and roll back if needed.
7. Set the next review date and tell people. If a change affects how someone works, send it to them rather than hoping they notice. For a signed policy, ask people to sign the new version.

When nothing has changed, the review is short: confirm, set the next date, move on.

SOP review checklist

Copy this into your review routine or the review section of your SOP template:

• The owner is still the right person and still works here.
• The steps match how the work is actually done today.
• Every link opens and every screenshot matches the current screen.
• Names, roles, prices, amounts and deadlines are current.
• Questions and comments since the last review are answered in the SOP.
• The SOP is still needed (if not, archive it).
• What changed, and why, is recorded.
• The next review date is set.
• Everyone affected by a change has been told or reassigned the SOP.

How to keep SOP reviews from slipping

Most review schedules fail for the same few reasons. These habits fix them:

• Put the date on the SOP itself, not only in someone’s calendar. Anyone reading it should be able to see when it was last checked and when it is due.
• Stagger the dates. If every SOP is due in January, none of them get reviewed. Spread them across the year.
• Review a few each week. Fifteen minutes on Friday beats a dreaded annual review day.
• Make overdue reviews visible by owner, so each person sees their own list instead of a giant shared backlog.
• Keep every version. People edit more willingly when they know a mistake can be undone.
• Keep SOPs short. A one-page SOP gets reviewed. A 20-page one gets postponed. Split long procedures so each part has its own owner and date.

How SOPCompass handles SOP reviews

In SOPCompass, each SOP has an Owner and a Review every (days) setting that fills in the Next review date. When that date passes, the SOP shows Review overdue under its title for everyone who opens it. On the Business plan, Insights shows each owner how many of their SOPs are overdue, how many have no review set and how many are current.

Feedback arrives on the exact step that needs it, because anyone, viewers included, can comment on a step. When it is time to update, Build with AI can propose targeted changes in improve mode for you to approve, and version history keeps the last 50 versions of each SOP with a one-click restore. SOPs nobody needs anymore can be archived, which takes them out of boards and search without losing them. The keep SOPs current page shows how these pieces fit together.

If a review turns up a process that was never written down at all, the free AI SOP generator will draft one, and our SOP template already includes an owner, a last reviewed date and a review section, so the next review is planned from day one.