top of page
How to write SOPs for a small business: notebook checklist with a checked box

How to Write SOPs for a Small Business (That Your Team Will Actually Use)

4 days ago
8 min read

Short answer: Here's how to write SOPs for a small business: start with the one process that causes the most repeat questions or expensive mistakes. Record someone doing it, turn the recording into a one-page checklist of 12 steps or fewer, and test it on a person who has never done the task. If they finish with no more than two questions, the SOP is ready. Then give it an owner and a review date.

Most SOP projects in small businesses end the same way. The owner spends a weekend writing a 40-page operations manual, shares it with the team, and six months later nobody remembers where it's saved. The effort was real. The approach was wrong.

I've written SOPs and sales playbooks for teams of different sizes, and I've seen what gets used and what gets ignored. One example: a seed-stage, founder-led AI startup I worked with had a product in market but less than $10K in annual recurring revenue, and couldn't keep a sales rep past six months. I created sales playbooks and SOPs, revamped their HubSpot setup and hired four sales reps. Within 12 months of working together, they passed $1M in ARR and raised over $800K. You can read the full case study here.

Here's the approach that works for a small team: pick the right process, capture it fast, write it on one page and prove it works before you call it done.

How to write SOPs for a small business: start with what an SOP is

A standard operating procedure is a short, written set of steps for doing a recurring task the same way every time. For a small business, a good SOP is closer to a checklist than a manual. It should be quicker to read than the task takes to do.

An SOP is not a job description, a policy or a training course. It answers one question: "What exactly do I do, in what order, when this happens?"

Step 1: Pick your first SOP with the 3-Strike Rule

Don't start by listing every process in the business. Start with the one that's costing you the most right now. I use a simple test I call the 3-Strike Rule. A process is a strong candidate when it hits at least two of these:

  1. Repeat questions. You or someone else has explained it three or more times in the last 90 days.

  2. Costly mistakes. When it goes wrong, it costs real money (I use $250 as a rough line for a small business) or puts a customer relationship at risk.

  3. Single point of failure. Only one person knows how to do it, and things stall when they're out.

Decision rule: if a process hits all three strikes, it's this week's SOP. If it hits two, it goes on this month's list. If it hits one or none, leave it alone for now.

Common first picks for service businesses: turning a lead into a quote, scheduling a new job, onboarding a new client, invoicing and collections, and handling a complaint.

One more rule: document a process before you automate it. If you can't write it down in 12 steps, you're not ready to hand it to software. My guide on what a small business should automate first picks up where this one ends.

Step 2: Capture the process in 30 minutes (record, don't write)

Owners stall on SOPs because they try to write from memory, and memory skips steps. It's faster and more accurate to capture the work while it happens.

  1. Record it. Have the person who does the task best walk through it once while recording their screen or filming on a phone. Ask them to talk out loud about what they're doing and why.

  2. Ask about exceptions. At the end, ask: "What usually goes wrong? What do you do when a customer is missing information? When do you come and ask me?" Those answers become your decision points.

  3. Grab the artifacts. Save copies of any forms, templates, email wording or screenshots they used.

Thirty minutes of recording usually beats three hours of writing from scratch.

Step 3: Write it on one page with the 7-part SOP format

Every SOP I write follows the same seven parts. One format makes them faster to write and easier for your team to scan.

  1. Name, owner and version. For example, "New Job Scheduling, owned by Dana, v1.0."

  2. Trigger. What starts the process. "A customer accepts a quote."

  3. Done looks like. What's true when it's finished. "Job is on the calendar, deposit is paid, customer has a confirmation."

  4. Steps. No more than 12, each starting with a verb. "Open the accepted quote in the CRM."

  5. Decision points. If-then rules for the common exceptions. "If the deposit isn't paid in 48 hours, call the customer."

  6. Common mistakes. The two or three errors people actually make.

  7. Last tested. The date someone new last followed it successfully.

Decision rule: if the steps run past 12, split it into two SOPs. A long SOP is usually two processes pretending to be one.

How to write steps people can follow

  • Start every step with a verb: open, check, send, call, enter.

  • Put one action in each step. "Check the address and send the confirmation" is two steps.

  • Name the exact tool, button or template. "Use the 'New Job' email template," not "send an email."

  • Add a screenshot only where people get stuck, not on every step.

Step 4: Use AI to turn your recording into a draft

AI is very good at this part. Transcribe your recording (many video and meeting tools do this automatically), then use a prompt like the one below in ChatGPT, Claude or Gemini. Remove customer names, addresses and any payment details before you paste anything in.

You are helping a small business write a standard operating procedure. Below is a transcript of [role] doing [process]. Turn it into a one-page SOP with these sections: Name/owner/version, Trigger, Done looks like, Steps, Decision points, Common mistakes, Last tested. Rules: Use no more than 12 steps. Start every step with a verb. Put one action in each step. Name the exact tool or template used. Write decision points as "If [situation], then [action]." Use plain language a new employee in their first week could follow. After the SOP, list any steps that seem missing or unclear in the transcript, as questions I should ask [person]. Transcript: [paste transcript]

Read the draft line by line with the person who does the work. AI will smooth over gaps, so the "missing steps" questions at the end are often the most useful part.

Step 5: Run the New-Person Test

An SOP isn't finished when it's written. It's finished when someone who has never done the task can follow it.

Hand the SOP to a new hire, someone from another role or even a family member, and watch them do the task (or a safe practice version of it). Don't help. Just take notes.

Decision rule: if they finish with two questions or fewer, the SOP is ready. If they ask more than two, or hesitate at the same step twice, rewrite those parts and test again.

This is the step most businesses skip, and it's the main reason SOPs go unused. A document that only makes sense to the person who wrote it isn't an SOP. It's a reminder.

Step 6: Give every SOP an owner and a review date

Processes change. Software updates, prices move and someone finds a better way. An SOP that's wrong is worse than none, because people stop trusting all the others.

  • Assign one owner to each SOP, usually the person who does the work most often.

  • Review every six months, or right away when a tool or policy changes.

  • Keep them in one place. A single shared folder organized by area (sales, operations, billing) works fine for most small teams. Link to it from wherever your team already works.

  • Update the "Last tested" date every time someone new follows it successfully.

Worked example: Harbor Lane Plumbing documents quote-to-schedule

Here's how this plays out at a fictional company. Harbor Lane Plumbing has six people: the owner, an office manager, three plumbers and an apprentice. The owner estimates he answers about 25 "how do I" questions a week from the office and crew, at roughly 4 minutes each. That's 100 minutes a week, or about 87 hours a year spent re-explaining things.

He runs his processes through the 3-Strike Rule:

  • Quote to scheduled job: explained constantly, a missed deposit or wrong address costs a wasted trip, and only the office manager really knows it. Three strikes.

  • End-of-day job notes: explained often, and missing notes cause billing errors. Two strikes.

  • Ordering parts: usually handled by the owner, with few mistakes. One strike, so it waits.

Quote-to-schedule goes first. The office manager records herself handling two accepted quotes. The AI draft comes back with 15 steps, so the owner splits it into two SOPs: "Accepted Quote to Deposit" (8 steps) and "Deposit to Scheduled Job" (7 steps).

The apprentice runs the New-Person Test and asks four questions, all about what to do when a customer wants a different day than the ones offered. The owner adds a decision point: "If the customer can't take any of the next three openings, offer the waitlist and note it in the job record." On the second test, the apprentice asks one question. Done.

The business case is simple. If the two SOPs cut the owner's repeat questions in half, he gets back about 43 hours a year. If they prevent just two wasted trips a month at around $300 each, that's another $7,200 a year. And the office manager can finally take a week off.

Copy this: a one-page SOP template

SOP name: [Process name] | Owner: [Name] | Version: [1.0] | Last tested: [Date] Trigger: [What starts this process] Done looks like: [What's true when it's finished] Steps: 1. [Verb + one action + tool or template] 2. [Next step] (12 steps maximum) Decision points: If [situation], then [action]. If [situation], then [action]. Common mistakes: [Mistake 1] | [Mistake 2] Related SOPs: [Links]

The mistake to avoid

The biggest mistake is documenting the ideal process instead of the real one. Owners often write how they wish the work happened, skipping the workarounds the team actually uses. The team reads it, sees it doesn't match reality and goes back to doing it their way.

Write down what really happens first, warts and all. Improve the process in version 1.1, after the team trusts the document. The second mistake is trying to document everything at once. Three SOPs that pass the New-Person Test are worth more than thirty that nobody opens.

When to get help with your SOPs and processes

If your business runs on what's in people's heads and you can't decide where to start, or every attempt to document things has stalled, an outside view helps.

In a Process Consulting Session, we spend 90 minutes on it together. We'll run your processes through the 3-Strike Rule, map the top one step by step on screen, find where it breaks or depends on one person and outline the SOP using the 7-part format. You'll leave with a draft SOP and a short, prioritized list of what to document or fix next.

If you'd rather have the documentation and automations built for you, take a look at my done-for-you services.

Frequently asked questions

What is an SOP in a small business?

An SOP, or standard operating procedure, is a short written set of steps for doing a recurring task the same way every time. In a small business it's usually a one-page checklist, not a manual. Its job is to let someone other than the owner do the task correctly.

How long should an SOP be?

One page, with no more than 12 steps, is a good target. The SOP should take less time to read than the task takes to do. If it runs longer, split it into two separate processes.

What processes should a small business document first?

Start with the process that creates the most repeat questions, the most expensive mistakes or depends on just one person. For many service businesses, that's lead-to-quote, scheduling, client onboarding or invoicing. Use the 3-Strike Rule to choose.

Can I use ChatGPT to write SOPs?

Yes, and it saves a lot of time. Record or transcribe someone doing the task, then ask ChatGPT to turn it into a structured checklist. Always review the draft with the person who does the work, remove private customer information first, and test it on someone new before you rely on it.

Book a Process Consulting Session

Ready to get your processes out of people's heads and onto the page? Book a Process Consulting Session: 90 minutes, $495. We'll pick your highest-impact process and you'll leave with a draft SOP your team can use. Book your Process Consulting Session here.

bottom of page