Write the SOP for the person doing the task, not for an auditor. One page. Eight fields: task name, owner, trigger, inputs, numbered steps, quality check, failure path, handoff. One action per step, every step starts with a verb, and the person doing the task keeps it updated.
Ask a small business owner if they have procedures and many will point to a folder. Ask the person doing the work if they use those documents and the honest answer is usually no. The document exists. The process in people's heads is different.
Why most SOPs fail
They fail because they are written for the wrong reader. An SOP written to satisfy an auditor, a franchise manual or a manager's sense of completeness optimizes for coverage: every policy, every disclaimer, every edge case, in paragraph form, across six pages. The operator, the person standing at the counter or answering the email, needs something else entirely: what do I do right now, in what order, and how do I know it worked?
Three symptoms tell you an SOP was written for auditors, not operators:
- It explains policy background before giving the first action.
- Steps bundle several actions into one sentence, so nobody can tell where they are in the process.
- It says nothing about what to do when the process fails, which is exactly when people reach for a document.
The fix is not better writing. It is a smaller, stricter structure.
The one-page SOP structure
Every SOP gets one page and the same eight fields. Copy this table and fill in the right column for each task in your business.
| Field | What to write |
|---|---|
| Task name | A short verb phrase. "Process a refund request," not "Refund policy overview." |
| Owner | One name or one role. If two people own it, nobody does. |
| Trigger | The event that starts this task. An email arrives, a shipment lands, a date hits. If you cannot name the trigger, the task will not happen on time. |
| Inputs needed | Everything the operator must have before step 1: logins, tools, information, approvals. Missing inputs are the top reason steps get skipped. |
| Numbered steps | The actions, in order. Rule: one action per step, and every step starts with a verb. "Open the orders dashboard." "Copy the order number." Never "Handle the order details." |
| Quality check | How the operator knows it worked, stated as something observable. A confirmation email received, a status changed to closed, a number that matches. |
| When it fails | The two or three most likely failure points and the exact action for each, including who to contact and what to say to the customer in the meantime. |
| Handoff | What happens next and who needs to know. Even "no handoff, task complete" is worth stating. |
The one-action-per-verb rule is the heart of it. When each line holds exactly one action, an interrupted operator can find their place again, a new hire can be trained against the list, and a failed run can be traced to a specific step.
A worked example: answering a customer refund request email
Here is the template filled in for a real task most small businesses handle weekly. Adjust the tools and limits to your own setup.
| Field | Entry |
|---|---|
| Task name | Answer a customer refund request email |
| Owner | Whoever runs the support inbox that day (one person per day, named on the schedule) |
| Trigger | An email arrives asking for a refund, or containing the words "refund," "money back" or "cancel my order" |
| Inputs needed | Support inbox login, orders dashboard login, refund policy page, the reply templates folder |
| Numbered steps | 1. Open the customer's email and copy the order number. 2. Find the order in the dashboard and confirm the purchase date. 3. Check the purchase date against the 30-day refund window. 4. Choose the matching reply template: inside window, outside window, or order not found. 5. Personalize the template with the customer's first name and order number. 6. Send the reply. 7. If the refund is approved, issue it in the payment dashboard on the original payment method. 8. Log the request in the refunds sheet: date, order number, amount, reason. |
| Quality check | The customer has a reply within one business day, the refunds sheet has a new row, and for approved refunds the payment dashboard shows the refund as issued |
| When it fails | Order number not found: reply with the order-not-found template asking for the receipt. Refund over $200: do not issue, forward to the owner with a one-line summary. Payment dashboard errors: retry once, then email the owner and tell the customer the refund is being processed and will take 3 to 5 business days. |
| Handoff | Approved refunds over $200 go to the owner. Everything else: no handoff, task complete once logged. |
Notice what the example does not contain: no policy history, no mission statement, no paragraph about why customer service matters. An operator who has never done this task could complete it from this page alone. That is the test.
Maintenance rules: keep it alive
An SOP that no longer matches reality is worse than no SOP, because people learn to ignore documents. Three rules keep the page trustworthy:
- Date every SOP. Put a "last updated" date at the top. An undated procedure cannot be trusted or audited.
- Review quarterly. Fifteen minutes per SOP, four times a year. Read it against how the task is actually done today and fix the gaps.
- The person doing the task edits it, not the manager. The operator sees the drift first: the new login screen, the changed shipping form, the step everyone quietly skips. Give them edit rights and make updating the page part of the job.
Start with one SOP this week, ideally the task you most dread handing to someone else. If you are still working toward your first sale, write the SOP for the exact steps that produced it, as described in our business launch checklist. Then protect a recurring time slot to write the next one using the 5-hour week business planner.
Related guides
- The small business launch checklist: from idea to first sale
- The 5-hour week business planner for side business owners
- Deciding whether a tool should replace a manual process? See the AI Assessment Mastery course
- Browse all guides or see our services
Turn working processes into a working business
TheMagne builds practical guides and apps for owners who run lean: clear procedures, clean books and honest numbers.
Read more guides