📚 Part of the Operations That Actually Work series
Also in this series:
• Stop Building SOPs Nobody Reads
• I Automated My SOP Writing With AI — Here's What I Learned
• The Weekly Review Template That Caught Problems
The first SOP I ever wrote was beautiful. Clear steps. Proper formatting. Color-coded sections. I put it in the shared folder and waited for the team to thank me. Three weeks later someone asked if we had documentation for the new hire. They never found my SOP. They asked the person next to them instead. That is when I realized the problem was not my SOP. The problem was that nobody reads SOPs.
Here are the four rules I learned since then.
Rule 1: Write It for the Person Who Is in a Hurry
Nobody has ever woken up excited to read a process document. They are reading because something broke or they are onboarding a new hire or they are covering for someone who is out. They want the answer now. They do not want background. They do not want context. They want the step.
Write your SOPs like a recipe. Ingredients first. Steps numbered. Time estimates per step. Who to call if it breaks. Anything that is not a step goes in a notes section at the bottom. The person in a hurry reads the steps and is done in three minutes. The person who wants context stays for the notes.
Rule 2: Every SOP Needs an Owner
If nobody owns it nobody maintains it. Within six months it is fiction. Every SOP should have a named owner and a review date. The owner is responsible for keeping it true. The review date ensures it gets checked even if nothing breaks.
I worked with a team that had fifty SOPs on a shared drive. Fifty. The newest one was fourteen months old. Most described tools and processes the team had stopped using. Nobody knew who wrote them. Nobody was responsible for updating them. They were not documentation. They were digital landfill.
Rule 3: Include the Exception Path
The best SOPs are not the ones that cover every possible scenario. They are the ones that tell you what to do when the standard process does not work. What if the primary approver is out? What if the vendor does not answer? What if the urgency bypasses normal procedure?
Include a single line after each critical step: If X happens, do Y instead. This is the difference between an SOP that helps and an SOP that becomes a wall you have to climb over to get work done.
Try it now. Take your most-used process and write down what happens when something goes wrong. If you can't write the exception path in one sentence, you don't understand your own process well enough to document it.
If you want a fillable template with exception paths built in: grab the free Daily Operations Checklist →
Rule 4: Test It on Someone Who Has Never Done the Job
Write the SOP. Then hand it to someone who has never done this task and watch them try to follow it. Do not help. Do not explain. Just watch. Where they hesitate your SOP needs work. Where they make a wrong turn your steps are not clear enough. Where they give up and ask you something your SOP is missing information.
I tested a vendor management SOP this way once. The person following it made a wrong turn at step three. Then again at step five. By step eight they had given up and were asking people for help. The problem was not their reading comprehension. The problem was my SOP assumed knowledge they did not have. I rewrote it assuming nothing. It worked the second time.
Try it yourself: The free Daily Operations Checklist has all four rules built in. Fill it for one process this week. See where your SOPs actually break.
What This Looks Like in Practice
The SOPs that actually get used in my team look nothing like the beautiful documents I used to write. They are short. They have owners and review dates. They include exception paths. They are tested on real people who have never done the job before.
The format is flexible enough for a one-page checklist or a multi-step workflow. The structure is what matters.
We built fillable templates with all four rules built in. Ownership fields are required. Review dates are scheduled at creation. Exception paths are prompted for every step. The templates work in Google Docs, Notion, or as standalone PDFs.
Why templates and not AI? I wrote about my failed attempt to automate SOP writing with AI — the 7 lesson in why human-tested docs still win. The short version: AI writes great skeletons, terrible organs. Templates with real human judgment beat AI-generated docs every time.
Start here: Download the free Daily Operations Checklist — it's the exact template we use. Five minutes to fill. Morning open, evening close. If it works for your team, the full SOP Template Pack adds onboarding, vendor management, issue resolution, and weekly reviews. But the free one first. Always.
Browse all templates at fieldwork-sops.surge.sh — including free checklists, process improvement tools, and full SOP packs.
What is the worst SOP you have ever inherited? The one that was wrong, outdated, or just plain impossible to follow? Drop it in the comments — I guarantee someone else has the same problem.
Top comments (0)