Pillar guide
The 90-Day SOP Freshness Audit: How to Keep Procedures Accurate
Outdated SOPs are worse than none. Here's a review schedule by risk level, a 30-minute audit routine, and how freshness checks keep your library trustworthy.
The fastest way to kill an SOP library is to let it go stale. One person follows an outdated step, a client gets hurt, and from then on everyone 'just checks with Sam'. Tools change, pricing changes, clients change, and procedures quietly drift away from reality. A freshness audit is a small, scheduled habit that keeps your documentation trustworthy. This guide covers how often to review, how to run a review in 30 minutes, and how Cloopp's freshness checks make the schedule automatic.
01
Why stale SOPs are dangerous
A missing SOP makes people ask. A wrong SOP makes people confidently do the wrong thing. That is why accuracy matters more than coverage.
Typical drift: a tool's interface changed, a step was moved to another team, a client-specific exception became the norm, or the person who owned it left.
02
Set review cadence by risk
Not every SOP needs the same attention. A good rule of thumb is to review by risk: the more money, security or client trust a process touches, the more often it gets checked. These are general guidelines — adjust them to your agency.
- High risk (billing, access, launches, anything client-facing): every 30–60 days.
- Standard delivery procedures: every 90 days.
- Low risk (internal admin, reference pages): every 6 months.
- Any SOP: immediately after a mistake, a tool change or an owner leaving.
03
The 30-minute review routine
Reviews fail when they feel like rewriting. Keep them short: the owner walks through the steps against how the work was actually done last time.
- 1Open the SOP next to the most recent real example of the work.
- 2Read each step: is it still done, in this order, in this tool?
- 3Check prerequisites and links still work.
- 4Add any fix from a recent mistake as a step or troubleshooting item.
- 5Mark it verified so the date updates for everyone.
Review notes template
SOP: Reviewed by / date: Still accurate? Yes / Partly / No Changes made: Linked mistake or ticket (if any): Next review due:
04
How freshness checks work in Cloopp
Every SOP in Cloopp carries a last-verified date. After 90 days without verification it's flagged as due for review, so owners and admins see what needs attention instead of relying on calendar reminders.
From the flag, the owner either marks it still accurate or opens it to edit. Either action resets the clock. Readers can see when a procedure was last verified, which builds trust in the library.
05
Turning mistakes into better procedures
Every client-facing mistake should end with one question: which step would have prevented this? Add that step to the SOP the same day, while the context is fresh.
Over a year, this habit turns your library into a record of everything the agency has learned the hard way — which is exactly what new hires need.
Before
- • Mistake fixed for this client only
- • Lesson stays with one person
- • Same mistake repeats next quarter
After
- • Prevention step added to the SOP
- • Everyone gets the update immediately
- • Verified date shows it was just reviewed
Frequently asked questions
- How often should SOPs be reviewed?
- A 90-day default works for most delivery procedures, with high-risk processes more often and low-risk reference pages less often. Always review after a mistake or tool change.
- Who should review an SOP?
- Its owner — the person who does the work most. A lead approves bigger changes.
Put it into practice
Keep every procedure trustworthy
Cloopp flags SOPs that haven't been verified in 90 days, so reviews happen without anyone tracking dates.
Explore free templates
