If it's longer than a page, nobody's reading it

The procedure your team actually follows is probably the one somebody wrote on the whiteboard. That tells you everything about how to write the rest.

It's short. It's where the job happens. It says exactly what to do next. And someone who does the job wrote it.

Does this ring a bell? You spent a weekend writing a proper procedure, and the team still does it the way it's scribbled on the whiteboard. The whiteboard won because it was useful.

That's the template. Here's how to turn it into procedures for the rest of your business.

What should a standard operating procedure include?

On one page, six things.

PartWhat goes in it
NameWhat the job is, in the words your team uses for it. "Weekly stock count", not "Inventory reconciliation process".
WhyOne line on why it matters. What goes wrong if it's skipped.
Before you startWhat they need: tools, logins, materials, information.
StepsNumbered, one action per step, starting with a verb.
Done looks likeHow anyone can tell it's finished properly. A photo, a reading, a ticked box.
Owner and review dateWho keeps this page right, and when it next gets checked.

That's the whole thing. If it won't fit on one page, it's two jobs. Split it.

How do you write a standard operating procedure?

1. Pick the job

Start with the job you get asked about most, even if it isn't the most important one. That's the one that'll give you time back first.

2. Get it out of the head of whoever does it

Sit with the person who does the job well. Ask them to talk you through it, or record them doing it on their phone. Don't write it yourself from memory. You'll skip the steps you do without thinking, and those are the ones a new person gets wrong.

If the job only lives in your head, record yourself explaining it. Then get AI to turn the recording into steps. I explain how to set that up in Write the job down before you open the AI.

3. Cut it down

Your first draft will be too long. Go through it and:

  • cut anything that's background, not action
  • cut anything a reasonable person would do anyway
  • turn paragraphs into numbered steps
  • start every step with a verb: check, ring, photograph, enter, send

4. Add the why and the done

This is what makes people follow it. "Photograph the meter before you leave" gets skipped. "Photograph the meter before you leave, so we can prove the reading if the customer queries the bill" gets done.

5. Test it on someone who doesn't know the job

Give it to the newest person in the business, or someone from a different part of it. Watch them use it. Every time they stop and ask a question, the answer goes on the page.

6. Put it where the job happens

On the wall, on their phone, inside the job in your software. A procedure in a folder nobody opens is no use to anyone. Where does your business actually live? covers how to file them so they're easy to find.

Still answering the same questions every day? Missing procedures might only be part of it. My free quiz, Why does everything still come back to you?, shows you what else might be going on.

Should you use a template?

Yes. One template, the same for every procedure. When every page looks the same, people know where to look for the steps, and you know straight away when something's missing.

The table above is a good start. Make it a Google Doc or Word template, give it your logo, and use it for everything.

What are the most common mistakes?

Writing the perfect version. Write the version that's good enough to use today. Fix it when your team tells you what's wrong with it.

Writing it alone. The owner's version always misses steps.

Using policy language. "Employees shall ensure" turns people off. Write how you'd say it out loud.

Never reviewing it. A procedure that's wrong is worse than none, because people stop trusting all of them.

Writing 40 in a month. You'll burn out at 12, and the rest will never happen. One a week is plenty.

How do procedures stop the questions?

They stop the questions when you use them. When someone asks how to do the job, send them the page. Every time. It feels slower for a fortnight. Then they go to the page first.

That's when the business starts living somewhere other than your head. If you want the bigger picture on why procedures fail and how to get your team using them, read Unpopular opinion: your procedures manual is the reason nobody follows your procedures.

And once a job's written down, you can hand it over properly. That's in You delegated it. So why are you still doing it?

What to do next

Find out what's sending everything back to you. Take my free quiz, Why does everything still come back to you?. You'll get a quick fix you can use this week.

Want help getting it done? In the BAR, owners with staff decide what to fix first, find the time, and get held to it. It opens in February 2027. Join the waitlist.

HI, I'M SAM

I've co-run a field service business for 22 years and served 12 years in the Navy. Now I help solopreneurs get the back-end stuff done, the money, systems, marketing and AI, so they get their weekend back.

NOT SURE WHAT'S SLIPPING?

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore.

+123-456-7890000

Newsletter

Subscribe now to get daily updates.

Created with © systeme.io