How Do I Write Standard Operating Procedures for My Small Business?
By Bill Stilwell · Last reviewed October 18, 2026
The short answer
Section titled “The short answer”A standard operating procedure (SOP) is a short written recipe for a task you do again and again. Each one should say why it exists, where it applies, who owns it, what you need before starting, the steps in order, what “done” looks like, how to check it, what to do when things go wrong, what records to keep, and when to review it. Start with the tasks that touch customers or money.
Why it matters
Section titled “Why it matters”Without written steps, the business lives in the owner’s head. A cleaning company owner gets sick for a week and nobody knows how to reschedule clients or answer the Google messages. Quality drifts, customers notice, and reviews follow. Written procedures also make training faster and selling the business easier later.
22.1.1 Purpose
Section titled “22.1.1 Purpose”What it means: one or two sentences on what the procedure gets done.
How to do it: start with “This procedure makes sure that…” For example: “This procedure makes sure every new lead gets a reply within one business hour.”
Common mistake: skipping the purpose, so people follow steps without knowing what matters most.
22.1.2 Scope
Section titled “22.1.2 Scope”What it means: where the procedure applies and where it doesn’t.
How to do it: name the situations it covers and the ones it doesn’t. “Covers residential estimates. Does not cover commercial bids, which follow 22.4 Sales and Estimate Procedure.”
Common mistake: a procedure that tries to cover everything and ends up covering nothing clearly.
22.1.3 Owner
Section titled “22.1.3 Owner”What it means: the one person responsible for the procedure working and staying current.
How to do it: name a role and a person, such as “Office manager, currently Dana.” In a one-person business, that’s you, and it’s still worth writing down for the day you hire.
Common mistake: “everyone” owns it, so no one updates it.
22.1.4 Inputs
Section titled “22.1.4 Inputs”What it means: what’s needed before starting: information, tools, materials, logins, or approvals.
How to do it: list them. For a roof inspection: ladder, harness, inspection form, customer address, and signed permission.
Common mistake: leaving out access needs, so a new person gets stuck at step 2 without a login.
22.1.5 Steps
Section titled “22.1.5 Steps”What it means: the actions in order.
How to do it: use numbered steps, each starting with a verb. Keep each step to one action. Add a short reason when a step isn’t obvious. Add screenshots for software steps.
Common mistake: writing a paragraph instead of steps, or skipping the steps you do without thinking.
22.1.6 Outputs
Section titled “22.1.6 Outputs”What it means: what exists when the procedure is done.
How to do it: describe the result, such as “estimate sent and logged in the customer relationship management (CRM) system with a follow-up date.”
Common mistake: no clear end point, so people aren’t sure when they’re finished.
22.1.7 Quality check
Section titled “22.1.7 Quality check”What it means: how you confirm it was done right.
How to do it: add a short check at the end: a second person reviews, a checklist is signed, or a photo is uploaded.
Common mistake: trusting that it was done because the steps were written.
22.1.8 Exceptions
Section titled “22.1.8 Exceptions”What it means: what to do when things don’t go as planned.
How to do it: list the common problems and the response for each, and who to call when something isn’t on the list.
Common mistake: no exception plan, so staff make it up or freeze.
22.1.9 Records
Section titled “22.1.9 Records”What it means: what must be kept as proof the work was done.
How to do it: name the record, where it’s stored, and how long to keep it (see 9.8.1 Required Records and 9.8.2 Record Retention Periods).
Common mistake: records saved on someone’s personal phone or email.
22.1.10 Review date
Section titled “22.1.10 Review date”What it means: when the procedure gets checked and updated.
How to do it: put a review date at the top, usually every 6 or 12 months, and add it to your calendar (see 22.11 Updating Procedures).
Common mistake: procedures written once and never touched, so they describe software screens that no longer exist.
A simple SOP layout
Section titled “A simple SOP layout”Use the same layout every time so people know where to look:
- Title, version, owner, and review date
- Purpose and scope
- Inputs
- Steps
- Output and quality check
- Exceptions
- Records
Keep it to a page or two. If it’s longer, split it into two procedures.
When to get help from a pro
Section titled “When to get help from a pro”An operations consultant can help if you’re building many procedures at once or preparing to sell. Your attorney or insurance professional should review any procedure that deals with safety, privacy, or legal requirements. Questions to ask:
- Which of my procedures carry legal or insurance risk if they’re wrong?
- Are the records I’m keeping enough to prove the work was done?
- Is anything in this procedure promising more than we can deliver?
Bill’s note
Section titled “Bill’s note”[Bill: add a short note. For example, the first procedure you wrote for SiteSmarty and why, or a business that struggled when the owner was away because nothing was written down.]
How I did this for SiteSmarty
Section titled “How I did this for SiteSmarty”- [Date I did this:]
- [What I actually did, step by step: which SiteSmarty tasks I wrote procedures for first and where they live]
- [What it cost and how long it took:]
- [What surprised me or what I’d do differently:]
- [Screenshot or photo to add, with private info blurred: one finished procedure doc]
- [Result so far:]
Questions people ask
Section titled “Questions people ask”What should an SOP include? Purpose, scope, owner, inputs, steps, outputs, quality check, exceptions, records, and a review date.
How long should an SOP be? Usually one or two pages. If it’s longer, split it.
Which procedures should I write first? The ones that touch customers or money: lead handling, estimates, scheduling, payments, and review requests.
How often should I update procedures? Review each one every 6 to 12 months, and right away after a mistake or a tool change.
Audit check
Section titled “Audit check”| Outline line | Question | Pass looks like | Fail looks like | Evidence to collect |
|---|---|---|---|---|
| 22.1.1 Purpose | Does each SOP state its purpose? | One clear sentence | No purpose | SOP doc |
| 22.1.2 Scope | Does it say where it applies and doesn’t? | Clear in and out | Unclear limits | SOP doc |
| 22.1.3 Owner | Is a named owner listed? | Role and person | “Everyone” | SOP doc |
| 22.1.4 Inputs | Are tools, info, and access listed? | Complete list | Missing logins or materials | SOP doc |
| 22.1.5 Steps | Are steps numbered and in order? | Numbered, one action each | Paragraphs | SOP doc |
| 22.1.6 Outputs | Is the finished result defined? | Clear end point | No end point | SOP doc |
| 22.1.7 Quality check | Is there a way to confirm completion? | Check or sign-off | None | Checklist or log |
| 22.1.8 Exceptions | Are common problems covered? | Problems and responses | None | SOP doc |
| 22.1.9 Records | Are records and storage named? | Record, place, retention | Personal devices | Records folder |
| 22.1.10 Review date | Is there a review date that is current? | Date within the last year | No date or long overdue | SOP header and calendar |
Where this fits
Do this first: 15.6 Customer Lifecycle Stages, 21.10 Conversion Rate Testing
Do this next: 22.2 Opening and Closing Checklist
Related pages: 22.3 Lead Handling Procedure, 22.10 Training Materials, 22.11 Updating Procedures, 12.2 Shared Files, 9.8.1 Required Records
Sources
- Google Business Profile Help, "Tips to improve your local ranking on Google" (checked October 18, 2026)
This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.