SOP audit checklist

Twelve checks that decide whether an SOP survives real use.

Q: What should an SOP audit checklist include?

Two layers. Per-document checks: named owner, review date, current contacts with working numbers, correct emergency numbers for the property's country, specific actionable steps, defined roles, referenced forms that exist, and staffing assumptions that match today's roster. Cross-document checks: no two SOPs give different deadlines or instructions for the same situation, and no SOP relies on a step or contact another SOP omits.

Q: How often should SOPs be audited?

Quarterly for high-risk procedures (emergency response, evacuation, medical, death in property) and at every operational change — new staff, new phone system, renovation, new local regulation. Most libraries are audited far less often; that gap is where findings accumulate.

Q: Can an SOP audit be automated?

The per-document and cross-document checks in this checklist can be run by AI across an entire library in minutes — which makes quarterly re-audits practical. You can run one SOP through a free automated check to compare it with your manual pass.

Most procedures read fine at a desk and fail at 3am. This checklist is the difference: eight checks inside each document, four between documents. Work through it manually — or run the same checks automatically on one of your SOPs, free, in minutes.

See the checklist Run the checks automatically

Part 1 · Inside each SOP

The per-document checks.

01 · Owner

A named person owns it

"The security team" is not an owner. If no individual is accountable for the next review, the SOP is already aging.

02 · Review date

It says when it was last verified

No review date and no change log means no way to know whether it still matches the site.

03 · Contacts

Every name still works here

Check each named person against the current roster. Departures are the single most common audit finding.

04 · Numbers

Every phone number connects

Dial them. Numbers last verified over a year ago fail surprisingly often.

05 · Jurisdiction

Emergency numbers match the country

"Dial 911" at a property in Spain (112) is a real, recurring finding — especially in libraries copied across a portfolio.

06 · Specificity

Every step is executable

"Complete the appropriate report" fails the test. Which report, which fields, filed where, by when?

07 · Roles

Every role is defined

"Notify all key personnel" — if "key personnel" isn't defined in the document, nobody is notified.

08 · Reality

Staffing assumptions match today

"The third officer secures the rear exit" fails if the night shift was cut to two officers last year.

Part 2 · Between SOPs — the checks most audits skip

The cross-document checks.

09 · Deadlines

No two SOPs disagree on timing

Theft SOP: "report within 24 hours." Incident SOP: "notify within 48." Staff follow whichever they opened.

10 · Instructions

Same situation, same answer

If the bomb-threat SOP says evacuate and the fire SOP says shelter in place, the overlap scenario has no answer.

11 · Dependencies

No SOP relies on a step another omits

A medical SOP that lists an on-site nurse the emergency SOP never mentions is a gap between documents, invisible inside either.

12 · Coverage

Nothing falls between procedures

List your top 20 scenarios and trace each through the library. The ones with no clear owning SOP are the audit's biggest finds.

The honest caveat

Checks 9–12 don't scale manually.

The per-document checks take about 20 minutes per SOP. The cross-document checks require holding the entire library in mind at once — which is why they're skipped, and why the most dangerous findings live there. This is the part AI is genuinely good at: reading every procedure against every other one, in minutes, every quarter. Run one SOP through the free check to see the difference, or have the whole library audited — severity-ranked findings with fixes, report in 24 hours.

Cross-SOP check · full libraryfindings

Conflicting deadlines across 2 procedures

CONFLICT

Escalation contact missing from 3 SOPs that need it

GAP

Scenario with no owning procedure

COVERAGE

Common questions

Frequently asked questions.

What should an SOP audit checklist include?

Two layers. Per-document: named owner, review date, current contacts with working numbers, correct emergency numbers for the property's country, specific actionable steps, defined roles, referenced forms that exist, and staffing assumptions that match today's roster. Cross-document: no two SOPs give different deadlines or instructions for the same situation, and no SOP relies on a step or contact another omits.

How often should SOPs be audited?

Quarterly for high-risk procedures, and at every operational change — new staff, new phone system, renovation, new local regulation. Most libraries are audited far less often; that gap is where findings accumulate.

Can this be automated?

Yes — all twelve checks can be run by AI across an entire library in minutes, which makes quarterly re-audits practical. Try it on one SOP free.