Governance
The Quarterly SOP Review: A 30-Minute Ritual That Saves Hours
Most SOPs go stale in weeks, not years. A procedure written in January is quietly wrong by April — a field renamed in the CRM, a button moved in an app, a new approval step added after a near-miss. Nobody notices because nobody re-reads the document. Then, the week a regulator asks or a trainee follows the old steps, you find out the hard way.
The fix isn't a one-time cleanup. It's a rhythm: a quarterly SOP review that takes about 30 minutes keeps every living procedure accurate enough to trust. This guide gives you the exact ritual — which documents to pull, what to check in each one, and how to turn a review into edits your team will actually apply.
Key takeaways
- Quarterly beats annual because the gap between reality and documentation stays short enough to remember.
- The 30-minute ritual: pull the active list, triage to the top 10, walk procedures against reality, assign edits.
- Give each fix to the person who runs the process, and update the change log visibly so the review closes the loop.
Why Quarterly, Not Annual
An annual review is the minimum anyone sets, and it's the minimum that fails. Twelve months is longer than most tools and roles stay stable, so a yearly pass mostly catches a year's worth of drift you then have to reconstruct from memory. A quarterly cadence keeps the gap between reality and documentation short enough that you can still remember what changed when you look.
Quarterly also matches how teams actually change. Most of us re-plan budgets, retool, and rotate roles on a quarterly calendar, so the review lines up with the moments processes genuinely shift. It is a small, recurring timebox rather than a dreaded backlog-clearing project, which is exactly why teams actually keep doing it.
If you are new to the governance side of this, our SOP version control guide explains the review-cycle controls you should build on top of — change logs, effective dates, owners, and archives. The quarterly review is where those controls get exercised.
The 30-Minute Ritual, Step by Step
Set a repeating calendar block each quarter. Invite the owners of your higher-risk procedures. Then run this sequence:
- Pull the active list (3 minutes). Open the one source of truth — not the emailed copies, the controlled library — and list every procedure with a review date that has passed or is due. If you don't have a central list, that's the first thing to fix, because a quarterly review without a single registry just re-checks whatever you happen to remember.
- Triage to the top 10 (5 minutes). You'll rarely have time to review every SOP in one sitting. Sort by risk and change rate instead: customer-critical flows, anything touched by a recent incident, and procedures tied to regulated work go to the top. The rest roll to next quarter. Our guide on why SOPs go stale explains which procedures are most prone to drift, so you can predict what belongs on the list.
- Walk one procedure against reality (15 minutes). For each top item, the owner walks the actual process once — ideally by doing it in the live tool — and ticks every step in the SOP. Mark anything that doesn't match: renamed fields, removed steps, added approvals, or background knowledge that isn't written down. Discrepancies are the entire point of the meeting; finding them is success.
- Assign edits (5 minutes). Every discrepancy gets a named owner and a "fix now" or "fix next week" label. Update the review date, note the change in the log, and set the next review. Two minutes of cleanup at the end is what turns a good meeting into a durable system.
The whole thing fits in a half hour because you're not rewriting documentation in the meeting — you're identifying what's wrong and assigning the fixes. Rewriting happens after, by the person who actually knows the workflow.
The Discrepancy Checklist
To keep reviews fast, use a fixed checklist instead of trying to "feel out" what changed. For every procedure on the table, ask:
- Does each step match what actually happens in the tool today?
- Are named tools, menus, and button labels still accurate?
- Are the named owner and reviewer still the right people?
- Are there unwritten decisions — the "ask Dave" parts — that need to be made explicit?
- Did any incident or near-miss since last review imply a step is missing?
- Is the linked file, template, or sub-procedure still reachable?
That last point matters more than it looks. A huge amount of SOP staleness is broken links — the procedure is fine, but the Google Doc it opens was moved and now 404s. If you're capturing steps as visual recordings rather than prose, the same rule applies to the assets: a screenshot or video that still matches the current UI carries far more weight than prose that doesn't align with it. Our write-up on visual SOP documentation gets into why current-on-screen evidence is easier to trust and verify than a rewritten paragraph.
Turning Findings Into Edits People Apply
A review only pays off if the edits land, and that depends on who makes them. The single best rule: the person who runs the process edits the SOP. If reviews always dump work on a documentation owner who never touches the tool, edits lag and the review loses credibility. Give each fix to the person who saw the discrepancy, and keep the change small enough to do in one sitting.
Then close the loop visibly. Update the revision number, note what changed and why in the change log, and have the reviewer acknowledge the new version. Teams that already run adoption practices will recognize this as the same "don't grade yourself on writing, grade yourself on usage" principle covered in our piece on getting teams to actually use their SOPs — a procedure nobody reads is exactly what a review cycle is meant to fix.
Recording the workflow as it actually runs — rather than reconstructing it from memory during the review — collapses most of this loop. When your documentation is captured from a real run of the process, the quarterly walk is just "did anything change since the last capture", and edits become re-captures instead of archaeology. It is the difference between maintaining prose and maintaining reality.
Capture the process as it actually runs
Claudia records browser workflows click-by-click and exports structured documentation you can review next quarter — so the review is a change check, not a reconstruction project.
Add to ChromeFAQ: Quarterly SOP Review
How long should a quarterly SOP review take?
Roughly 30 minutes if you triage to your highest-risk procedures and assign edits rather than rewriting in the meeting. Budget an extra hour or two afterward for the small edits across your top few documents.
Do all SOPs need a quarterly review?
No. Quarterly is for high-change, customer-critical, or regulated procedures. Stable, low-risk work can go annual or on-trigger (after incidents, audits, or system changes). The point is to match review cadence to change rate, not to review everything equally.
What if we never wrote review dates into our SOPs?
Start with a single pass to add an owner and a next-review date to each living procedure, then begin quarterly reviews. The first review is also the moment you date honestly — give everything a review date within the next two quarters so the backlog clears itself.
Who should attend the quarterly review?
The owners of the procedures being reviewed, plus whoever holds the documentation registry. Keep it small. A reviewer who can acknowledge changes is useful for regulated work, but don't inflate the room — the people who run the process are the ones who know what's wrong.
A quarterly review turns "did our documentation survive?" into "is our documentation true?" It's 30 minutes a quarter against the cost of a stale procedure failing at the worst possible moment — an audit finding, a trainee error, a regulator question. Pick your top five procedures, walk them against reality, assign the edits, and let the rhythm do the rest. The full controls for review cycles, change logs, and archives are covered in our SOP Guide 2026 if you want the complete framework.