Writing an SOP people will actually follow
What separates an SOP that gets used from one that sits in a folder, and how procedures become the checks staff perform on shift.
A standard operating procedure documents how a task should be performed so that it's done the same way regardless of who is doing it. In frontline operations most SOPs fail the same way: they're written once, filed, and never consulted again by anyone actually doing the work.
Why most SOPs go unread
- They are written for an auditor, in the register of a policy document
- They cover the whole process when the reader needs one step
- They live somewhere separate from where the work happens
- They describe the ideal rather than what the shift can actually do
A procedure nobody reads isn't a control. It is a document asserting a control exists.
The useful test
Could someone on their second shift follow this and get the same result as someone with two years of experience? If not, the procedure is a memory aid for people who already know, which is the group that needs it least. That means naming things the way staff name them, in the order the work happens, with the specific numbers included rather than "at the appropriate temperature".
Turning a procedure into a routine
The most reliable way to make an SOP get used is to stop presenting it as a document. Broken into ordered steps, attached to the shift where it applies, and answered as it is performed, the procedure and the record become the same object.
That has a consequence worth accepting deliberately: the checklist becomes the real definition of how the site runs, and the document becomes a description of it. Where they diverge, staff will follow the checklist. Write it accordingly — see checklists.
Keeping them current
Procedures rot quietly. Equipment changes, suppliers change, a step turns out to be impossible at 6am and everyone works around it without telling anyone.
Two signals are worth watching. An item failing everywhere usually means the procedure is wrong rather than the staff. An item that's never once recorded as failed across months either does not matter or is not being genuinely checked. Both are prompts to revisit the procedure instead of the people.
Common questions
- What should a standard operating procedure include?
- The purpose, who performs it, the specific ordered steps with real numbers rather than vague qualifiers, what to do when something is out of range, and who to inform. The test is whether someone on their second shift could follow it and reach the same result as an experienced colleague.
- Why do SOPs get ignored?
- Usually because they are written for an auditor rather than an operator, cover an entire process when the reader needs one step, live somewhere separate from the work, and describe an ideal the shift cannot actually achieve. A procedure nobody reads asserts that a control exists rather than providing one.
- How do you keep SOPs up to date?
- Watch the completion data. An item failing at every site usually means the procedure is wrong rather than the staff, and an item never once recorded as failed across months either does not matter or is not genuinely being checked. Both indicate the procedure needs revisiting.
More on operations
Run these checks on a schedule
EasyBee turns recurring obligations into dated, attributable records.