A useful small-business SOP explains when a process starts, who owns each step, what to do, and how to confirm the work is complete. Start with one recurring task that causes confusion, document the real workflow, and test the instructions with someone who did not write them.
What an SOP should include
A standard operating procedure is a repeatable set of instructions for work that needs to happen consistently. Identify its purpose, scope, owner, trigger, tools, steps, decision points, quality check, and escalation path. A five-step checklist may be enough for a routine task; a high-risk process may need screenshots, approvals, or troubleshooting guidance.
How to write a small-business SOP
- Choose a recurring process with a real pain point.
- Ask the person doing it to explain the current steps and exceptions.
- Define what “done” looks like and who checks it.
- Write one clear action per step and name the tool or record to update.
- Test the instructions with a new user and revise where they hesitate.
Keep procedures current
Assign an owner and review date. Update the SOP when a tool, policy, or handoff changes, and link it from the place where the work is managed. A document nobody can find will not create consistency. For a structured documentation system, see SOP and process documentation support.
How long should an SOP be? Only as long as needed to complete the process correctly. Should every task have one? No. Start with recurring, high-impact, risky, or difficult-to-delegate work.
What a useful SOP should contain
A standard operating procedure explains how a repeatable task is completed to an agreed standard. It should tell the reader when to use it, who owns the work, what access or materials are needed, the steps to follow, the quality checks to perform, and what to do when something goes wrong. A short checklist may be enough for a simple recurring task. A process with several decision points may need screenshots, examples, or a flowchart.
Write for the person who will perform the task, not for the person who already knows it. Use familiar language, name the system or folder precisely, and show what “done” looks like. Test the draft with someone who did not create it. Their questions reveal missing context far faster than proofreading it alone.
Build and maintain the procedure
- Pick a frequent task where inconsistency creates rework or risk.
- Observe the current process and confirm the actual steps with the owner.
- Draft the simplest format that supports accurate completion.
- Test it on a real task and revise unclear steps.
- Add an owner, version date, and review trigger.
Keep procedures close to the work and searchable by the words the team uses. Review them when a tool, policy, or customer requirement changes, and invite the people doing the work to suggest improvements. An SOP is a living reference, not a document created once and forgotten.
Frequently asked: How long should an SOP be?
Only as long as needed to help a trained team member complete the task safely and consistently. Remove background information that does not help them act or make a decision.
A worked example: the client invoice SOP
Take a task most small businesses repeat every month: sending client invoices. Written as an SOP, it might look like this. Purpose: every active client is invoiced correctly by the third working day of the month. Owner: the operations assistant. Trigger: the first working day of the month. Tools: the time tracker, the accounting software and the client list.
- Export last month's tracked hours for each active client.
- Check the hours against the agreed retainer or project scope and flag anything over the limit to the account lead before invoicing.
- Create the invoice from the saved template and attach the hours report.
- Send it from the accounts inbox and record the date in the client list.
- Set a reminder for the payment due date.
Done means: every active client has an invoice dated this month and the client list shows the sent date. If something is wrong: a disputed amount goes to the account lead, never back to the client directly. That is the whole document. It fits on one page, and a new team member could follow it on their first day.
Mistakes that make SOPs fail
- Writing from memory. The person who does the task skips steps without noticing. Watch the task being done, or record it, then write.
- Documenting the ideal process. If the SOP describes how the work should happen and not how it happens, people stop trusting it after the first exception.
- Leaving out the decision points. Steps are easy. What to do when the client has not replied, the file is missing or the amount is wrong is what people really need.
- No owner. An SOP without a named owner is out of date within a few months and nobody knows it.
Where to start this week
Pick the one task you are asked about most often. Record yourself doing it once, write the steps from the recording, and hand it to someone who has never done it. Every place they hesitate is a gap in the document, not a gap in the person. Once the document exists, the harder part is getting it used, which I cover in how to get employees to use SOPs.
Want a second opinion on your operations?
Take the free Business Scale Readiness Assessment, or book a strategy call and I will tell you what I would fix first.