How to Write an SOP That People Actually Follow

Most SOPs fail the same way: they are written like essays. Long paragraphs, background nobody needs, and the actual steps buried somewhere in the middle. The person reading it gives up and asks you instead, which is the exact thing the SOP was supposed to prevent.

A good standard operating procedure is closer to a recipe than a report. Do this, then this, then check this. Here is how to write one that survives contact with a real workday.

Step 1: Pick one process, and only one

An SOP covers a single repeatable job: onboarding a client, sending an invoice, closing the books each month. If the document tries to cover three jobs, it will be vague about all of them. Write down the job in one sentence at the top, along with the result that tells you it was done right.

Step 2: List the steps in the order they happen

Walk the process yourself, slowly, and write each action as you take it. Use verbs: open, send, check, save. Number the steps. If a step has a decision in it (if the client has not replied, do X), write the branch down instead of leaving it to judgment.

Step 3: Add the details that trip people up

• Where things live: file names, folders, links, logins
• The exact template, script, or example to copy
• Timings: when it starts, how long it should take, what is time-sensitive
• The two or three mistakes everyone makes the first time

These details are the difference between a document and a procedure. They are also the parts that live only in your head right now, which is why writing them down feels slow. It is still faster than explaining them twelve times.

Step 4: Cut everything that is not a step

History, strategy, and motivation belong in a different document. Every sentence in an SOP should either be an action, a decision rule, or a warning. If a paragraph does none of those, delete it. Short SOPs get followed; long ones get skimmed.

Step 5: Draft it fast, then fix it in real use

Staring at a blank page is the slow way to start. The SOP Generator from Leave It to Bum Bum turns a rough description of the job into a structured first draft you can edit, which gets you to the useful part sooner: handing it to someone and watching where they get stuck. Every stuck point is an edit. Two or three rounds of that and the document is genuinely yours.

Step 6: Store it where the work happens

An SOP nobody can find is a diary entry. Keep procedures with the tools and files they reference, name them by the job (not by date or author), and update the same document instead of saving copies. When the process changes, change the SOP the same day, or it quietly becomes fiction.

Frequently asked questions

What is an SOP in a small business?

A standard operating procedure is a short, step-by-step document for one repeatable job, written so someone else can do the job the same way without asking questions. In a small business it is how the owner stops being the only person who knows how things work.

How long should an SOP be?

As short as the job allows. Most small-business procedures fit on one or two pages: a one-sentence purpose, numbered steps, and the details that trip people up. If it runs much longer, it is probably covering more than one job and should be split.

What is the difference between an SOP and a checklist?

A checklist is the short list you tick off while doing the work. An SOP explains how and why each step is done, including decision rules and warnings. Many teams keep both: the SOP for learning and reference, the checklist for the daily run.

How often should SOPs be updated?

Whenever the process changes, and reviewed at least once or twice a year. The fastest way to keep them honest is to fix them during real use: any time someone gets stuck or improvises, that moment is an edit waiting to happen.

Can AI write an SOP for me?

It can draft one. Tools like the SOP Generator turn your description of a job into a structured draft, which saves the blank-page hour. The draft still needs your judgment: the decision rules, timings, and common mistakes are the parts only you know.