Checklist
Five Questions to Answer Before You Publish a New SOP
If you cannot answer all five cleanly, the rollout will fail or the audit will catch it.
By Charley Bixby · 5 min read
Five questions I ask before I let a client publish a new or rewritten SOP.
Most teams answer two or three cleanly. The other two are the rollout that drifts and the audit that scrambles.
Five questions. Ten minutes. Before you ship.
Who is the one named owner of this SOP and the next review cycle?
Not a team. Not a queue. A person.
The owner is the named individual on the hook for the next review when the calendar trigger fires. The owner is the person an auditor will be referred to if there is a question about the document. The owner is the name on the version history when the next update goes out.
"QA owns this" is not an answer. "Compliance leads on this one" is not an answer. "Operations and HR co-own it" is not an answer. A single human name is the only answer.
How will the people affected know the document changed?
And what will they do differently because of it?
This is two questions packaged into one because they are inseparable. Notification without context is noise. Context without notification is a secret.
The good answer is concrete: "I am sending a 4-paragraph message to the operations team from the SOP owner, with the why up front, the specific behavior changes in the middle, and a link to the new document at the bottom. I am sending it through the channel the team actually reads, which is Slack, not email. The owner is also bringing it up in the team huddle on Monday."
The bad answer is "the document system will auto-notify everyone in the access group." That is publication, not communication. The team will not register it.
Where is the current approved version, and how would a new hire know that is the current version?
The first part is about canonical storage. There is one place — and only one place — that is the authoritative "this is current" copy.
The second part is the test. Imagine a new hire on day three. They have a question that the SOP answers. They search. What do they find? If the answer is "the right document, with no other competing versions visible, marked as current with a clear effective date," you are in good shape.
If the answer is "they would find three documents, two of which look authoritative, and have to ask their manager which one is real" — your SOP library is not findable, and the new SOPs will get lost in it.
If acknowledgment is required, how will it be captured at effective date?
Not backfilled at audit.
Acknowledgment captured at effective date is a behavior signal. Acknowledgment collected in audit-prep mode is paperwork. The two have different value and auditors are getting better at telling them apart.
The mechanism does not need to be elaborate. It needs to be triggered at the right moment. The new SOP becomes effective on March 1. On March 1 (or the next time the affected staff log into a relevant system), they get an acknowledgment prompt tied to the specific version.
If a new version publishes in May, prior acknowledgments invalidate and re-collection triggers automatically. Whatever system you are using needs to do that, or the audit story for adoption is fragile.
If an auditor asked tomorrow for proof of approval and acknowledgment, how long would it take to pull?
The audit-readiness test, compressed to a single question.
The good answer is "I can pull it in under five minutes." That means: current version visible with effective date, approval record with names and timestamps, acknowledgment list filterable by version and role, point-in-time export available.
The bad answer is some version of "well, I would need to check three systems and one spreadsheet and probably ask the SOP owner." That answer means the audit response will take days, will produce inconsistencies, and will create findings.
The five together
Each question alone is small. The five together cover most of the gap between “SOP exists” and “SOP works in production and survives audit.”
If you can answer all five cleanly, the rollout will be tight and the audit will be a non-event.
If you can answer three, you have a 50/50 rollout and an audit that will produce findings.
If you can answer one or two, do not publish yet. The work to fix the answers before publication is significantly cheaper than the work to fix them in retrospect.
Charley Bixby is co-founder and VP of Operations at SOP Studio.