I’ve seen businesses with hundreds of SOPs that nobody follows, and businesses with a dozen one-page checklists that run like clockwork. Volume isn’t the point. Use is.
Here’s how to write standard operating procedures your team will actually use.
The anatomy of a good SOP
Every SOP I write has the same short structure:
- Title — the task, in plain words. “Schedule a new install,” not “Installation Scheduling Protocol v3.”
- Purpose — one sentence on why it matters.
- Owner — the seat responsible for the SOP being right and followed.
- Trigger — what starts it.
- Steps — numbered, each starting with a verb.
- Standard — what done right looks like.
- Tools and links — where to click, what to use.
- Watch out for — the two or three most common mistakes.
- Last reviewed — date and initials.
That’s a template you can copy today.
The record-it-once method
The hardest part of writing SOPs is finding time. So don’t write them — record them.
- Do the task as normal and record it. Screen recording for computer work, a phone video for hands-on work.
- Narrate your decisions. “I check this first because…” is where the real knowledge is.
- Get a transcript and turn it into a draft checklist. AI tools are good at this first draft; you still check it. See SOPs for AI for that workflow.
- Test it. Someone else follows it while you watch silently.
- Fix the gaps and publish it where the work happens.
Twenty minutes of recording beats three hours of writing, and it captures the judgment calls a written-from-memory SOP misses.
Checklist or procedure?
Not every task needs the same format.
| Format | Best for | Example |
|---|---|---|
| Checklist | Routine tasks where order and completeness matter | Opening the shop, closing a job, onboarding a customer |
| Step-by-step procedure | Tasks with decisions or technical detail | Pricing a custom job, running payroll |
| Decision rules | Recurring judgment calls | Which discounts reps can approve |
| Short video | Physical or visual tasks | Installing a part, navigating software |
Most small businesses should be mostly checklists, with procedures for the complex work and decision rules wherever the owner is currently the bottleneck.
SOP examples for small business
A few examples, written in the short format:
New lead follow-up. Trigger: new inquiry. Steps: call within the agreed response window; if no answer, text and email using the template; log the attempt; schedule the next touch per the follow-up cadence. Standard: every lead has a next action and a date. See sales follow up system.
Customer onboarding. Trigger: signed agreement. Steps: send the welcome message, confirm the schedule, collect the intake form, introduce the delivery lead, set expectations for updates. Standard: the customer knows what happens next and who to contact.
Weekly scoreboard update. Trigger: every Friday by noon. Steps: each number owner enters their number; the integrator flags anything off track; issues go on the meeting list. Standard: complete before the weekly meeting. See business scorecard.
Where SOPs should live
Put them where the work happens. If your team lives in a project board, link SOPs from the cards. If they live in a CRM, link them from the stages. Keep one master library organized by department — marketing, sales, operations, finance, people — so you can find everything. See process documentation.
Keeping SOPs alive
SOPs decay. The fix is a habit, not a project:
- Every SOP has an owner on the Ownership Chart.
- When the process changes, the SOP changes that week.
- Review core SOPs quarterly. Put it on the quarterly planning agenda.
- Train from the SOP. If trainers teach from memory, the SOP drifts out of date.
- Reward improvements. When someone finds a better way, update the SOP and thank them publicly.
Which SOPs to write first
Start with the ones that hurt most:
- Tasks only you know how to do.
- Tasks where mistakes cost money or customers.
- Tasks you train new hires on most often.
- Tasks that happen daily.
Write one a week. In a quarter you’ll have the backbone of a business that doesn’t depend on any single person’s memory.
SOPs and accountability
An SOP gives you something fair to hold people to. Without one, a mistake becomes an argument about how it “should” have been done. With one, the conversation is simple: was the SOP followed? If yes, the SOP needs fixing. If no, why not? That clarity makes coaching easier and lowers the temperature of hard conversations. It also protects good employees from being blamed for a broken process. See accountability in the workplace.
Next steps
Pick one task from the list above and record it this week. For the bigger picture, read business systems. If your business has dozens of processes trapped in a few people’s heads and you need help prioritizing, request a strategy call.
Questions people ask
What is a standard operating procedure?
A standard operating procedure (SOP) is a written description of the agreed best way to do a recurring task — the steps, the standard, the owner and the tools — so anyone trained can do it consistently.
What should an SOP include?
A clear title, purpose, owner, trigger, the steps in order, the standard for done, tools or links needed, common mistakes, and a last-reviewed date. Keep it as short as the task allows.
How long should an SOP be?
As short as possible. Most SOPs should fit on one screen as a checklist, with a short video for tricky steps. Long, essay-style SOPs rarely get read.