An SOP nobody reads is just a long email.

Most small businesses that try to document their processes end up with a shared folder of beautiful documents that nobody opens. The problem isn't the template. It's that the document was written to exist, not to be used.

I've written procedures for my own businesses and for handing work off to someone else. Here's how I write them now, where AI earns its place, and the mistakes that make them useless. For the bigger picture of making a business less dependent on one person, start with how to systemize a small business.

What an SOP is for

A standard operating procedure answers one question: how do we do this, every time, so the result doesn't depend on who is doing it?

That's it. It has three jobs:

  1. Let a new person do the task correctly without asking the owner.
  2. Make the standard visible, so you can tell when work falls short of it.
  3. Get the process out of someone's head so the business survives their absence.

If a document doesn't do those, it isn't an SOP. It's background reading.

Step 1: Choose the right process to write first

Don't document everything. Pick the process where one of these is true:

  • It happens often and is done differently by different people.
  • It breaks when a particular person is out.
  • A mistake costs real money or a customer.
  • You're about to hire for it.

For a service business that usually means lead response, quoting, scheduling, job handoff and invoicing. If you're deciding where to start with automation too, the same list applies. I cover that logic in my rule for what to automate first.

Step 2: Capture how it's really done, not how it's supposed to be done

This is where most SOPs go wrong. They describe the official process, and the real work happens somewhere else.

The most reliable way to capture the real thing is to watch or listen to someone do it. Two methods work:

  • Narrated walkthrough. Have the person who does the task talk through it out loud, recording the screen or a voice memo. "Now I open the quote, check the address, then I look at the last job we did there."
  • Shadowing. Sit next to them and write down every step, including the ones they skip mentioning because they've done them for ten years.

People leave out the judgment calls. Ask directly: "What do you do when it isn't straightforward? What do you check that you've never written down?" Those answers are the valuable part.

Step 3: Use AI to turn the raw capture into a draft

This is where AI saves real time.

  1. Transcribe the recording. Most meeting and voice tools do this.
  2. Ask an AI assistant to turn the transcript into a numbered procedure, with a purpose line, who does it, when, the steps in order, and a short "what to check" list.
  3. Tell it to mark anything unclear instead of guessing. This one matters. AI will happily fill a gap with something plausible, and a plausible wrong step in an SOP is worse than a blank.

The shape I ask for:

Purpose: one sentence. Owner: a role, not a name. Trigger: what starts it. Steps: numbered, one action each, starting with a verb. Done means: how you know it's finished. Check: the two or three mistakes that actually happen.

I haven't timed this and won't pretend I have a stopwatch result. What I can say is that the draft stops being a blank-page problem. The editing is the work that remains, and it's the work only someone who knows the process can do.

Step 4: Edit it down

Cut it ruthlessly.

  • One page if you can manage it. Long SOPs don't get read.
  • One action per step. "Check the address and confirm the schedule" is two steps.
  • Plain words. Write for a smart person on their first day.
  • Name the owner as a role, like "office manager," so the document survives staffing changes.
  • Say what "done" looks like. Otherwise people decide for themselves.

Add a screenshot or link where a step is easy to get wrong. Skip decoration.

Step 5: Test it on someone who doesn't know the work

This step is what separates a real SOP from a decorative one.

Hand it to a person who hasn't done the task and watch them try, without helping. Where they hesitate, the document is unclear. Where they ask a question, an answer is missing. Fix those spots and test again.

If you can't find a new person, use someone from a different department. If the owner is the only person who can follow it, it fails.

I'd also run the draft past one person who actually does the job. They'll find the step you got wrong in about thirty seconds.

Step 6: Put it where the work happens

A document in a folder nobody opens doesn't exist. Make it findable at the moment of use. Link it from the task, the board card, the CRM stage or the checklist. One place, one current version.

Each item should have one view, and that view should tell whoever opens it everything they need, without digging through folders.

Step 7: Keep it alive

SOPs rot. A tool changes, a customer type shows up, someone finds a faster way, and the document goes stale. A stale SOP is worse than none because people trust it.

Three small rules:

  • Every SOP has a named owner responsible for keeping it current.
  • Anyone can flag a wrong step, and the owner fixes it within the week.
  • Review on a schedule. Quarterly is fine for the ones that matter.

Strike out superseded versions and say what replaced them, instead of quietly deleting. People cite old documents when they find them.

Mistakes I'd avoid

  • Writing the SOP for the boss and not the doer.
  • Documenting a broken process. Fix it first. If the team can't explain it manually, writing it down just records the confusion.
  • Making it too long to use.
  • Skipping the test.
  • Letting AI invent steps nobody confirmed.

Where SOPs fit in a bigger plan

If you're building a business that has to run without you, whether to scale it, hire a manager or eventually sell it, SOPs are the base layer. A buyer looking at a company reads documented procedures as evidence the business isn't just the owner. The flip side is in owner-dependent business.

If you want help turning how your company really works into procedures people use, start with Di-Hy's free audit.

FAQ

What should an SOP include?

A purpose, an owner, the trigger, numbered steps with one action each, what "done" means and the common mistakes to check. Keep it to a page where possible.

Can AI write SOPs?

AI can draft one quickly from a transcript or notes, and that's where it helps most. A person who does the work has to edit and test it, because AI can invent plausible steps that aren't real.

How many SOPs does a small business need?

Start with the three to five processes that are frequent, error-prone or person-dependent, such as lead response, quoting and invoicing. Add more as you hire or find new failure points.