How Do I Create SOPs My Team Will Actually Use?
Create SOPs your team actually uses: one page, numbered steps, stored where the work happens. Use your AI to write first drafts in minutes.
How Do I Create SOPs My Team Will Actually Use?
Standard Operating Procedures. Every business needs them. Almost no small business has ones that people actually use. The SOPs that get ignored are long, overly formal documents written in a style that nobody reads, stored somewhere nobody checks. The SOPs that get used are short, specific, and available exactly when the person needs them. Here is how to write SOPs that your team will actually follow, and how to build the system that keeps them current.
Why Most SOPs Fail
The most common SOP failure is format. A ten-page Word document describing a process end-to-end is rarely consulted. It gets written once, filed somewhere, and forgotten. When someone needs to do the process, they ask a colleague rather than finding the document.
Effective SOPs are short enough to be read in under two minutes, specific enough that a new person could follow them without asking questions, and stored where the person will be when they need them, not buried in a shared drive.
The Right Format for Small Business SOPs
The format that gets used:
Title: the task name as a verb phrase. “How to onboard a new client” not “Client Onboarding Process.”
Purpose: one sentence explaining when to use this SOP.
Who does this: the role responsible.
Steps: numbered, short, actionable. Each step is one action. Not “set up the client” but “create a new row in the Client Tracker with the client’s name, email, and start date.”
What to do if something goes wrong: the two most common problems and their fixes.
Links: to any tools, templates, or resources referenced.
That is the entire template. Nothing else. One page maximum.
Using AI to Write Your SOPs
The fastest path to a complete SOP library is to describe a process to your AI and let it write the first draft.
Ask your AI: “Can you write a standard operating procedure for [describe the process] at my [type of business]? Use this format: title, purpose (one sentence), who does this (role), numbered steps (each step is one specific action), two common problems and their fixes, and links to relevant resources. Keep the whole document to one page maximum.”
Review the output for accuracy. Add any steps the AI missed. Correct anything that does not match your actual process. A ten-minute review beats writing from scratch.
For your most critical processes, have the team member who actually does the task review and edit the draft. They will catch the nuances that are not obvious from outside.
Where to Store SOPs So People Use Them
The storage location determines whether SOPs get consulted. The right location is wherever your team already goes when they need information.
| Storage Location | Best For | Search Capability | Access |
|---|---|---|---|
| Notion workspace | Teams using Notion already | Excellent full-text search | Desktop and mobile |
| Google Drive (Docs) | Google Workspace teams | Basic search | Desktop and mobile |
| Pinned in Slack channels | Real-time process reference | None (pinned only) | Wherever Slack is open |
Notion is the most practical SOP storage for most small businesses. Create a “How We Work” section in your team Notion workspace. Organise SOPs by department or process type. The search function in Notion means people can find what they need without knowing exactly where it is filed.
In the tool where the process happens: if you have an SOP for processing refunds in Shopify, pin a link to it in your Shopify notes or in the Slack channel where refund requests come in. The SOP is available exactly when needed.
Linked from Slack channels: pin relevant SOPs to the appropriate Slack channel. The team member in #client-success sees the client management SOPs without searching.
Keeping SOPs Current
An outdated SOP is worse than no SOP because it causes confident wrong action.
Two practices keep SOPs current:
Review trigger: every time a process changes, the relevant SOP is updated the same day. Make this a rule.
Quarterly audit: once per quarter, someone (rotate the responsibility) reviews all SOPs and marks each one as reviewed. Add a “Last reviewed” date to each document.
Ask your AI: “Can you create a quarterly SOP review checklist for my business? It should help whoever is doing the review check that each SOP is still accurate, identify any processes that now need an SOP but do not have one, and flag any SOPs that describe processes we no longer use.”
Frequently Asked Questions
How many SOPs does a small business need?
Start with the ten processes that cause the most questions or errors when not followed consistently. Add more as the need arises. A library of twenty focused, accurate SOPs is more valuable than a library of two hundred that nobody reads.
Should SOPs be written by managers or by the people doing the tasks?
By the people doing the tasks, reviewed by managers. The person closest to the work knows the nuances. Managers write SOPs from theory; task-doers write them from practice.
How do I get my team to actually read SOPs?
Reference them explicitly. When someone asks how to do something covered by an SOP, send them the link rather than explaining it verbally. Do this consistently and the team learns to check the SOPs before asking.
What is the difference between an SOP and a checklist?
An SOP explains how to do a process including the decisions and judgements involved. A checklist is the quick-reference version: the steps without the explanation. Most processes benefit from both. Write the SOP first, then extract a checklist for daily use.
The One Thing to Remember
SOPs fail because of format and storage, not because the information is wrong. Keep them to one page, in verb-phrase title format, with numbered steps that are each one specific action. Store them where the work happens. Use your AI to write first drafts in minutes. Review quarterly. Reference them when team members ask questions instead of explaining verbally.
Want your business running reliably on documented processes? → Snapdock
New here? These might help: How do I build a knowledge base for my business? → How do I build a simple project management system for my team? →