What Is an SOP and When Do You Need One

An SOP, Standard Operating Procedure, is a written set of step-by-step instructions that explains how to carry out a routine task the same way every time. Nothing more complicated than that. If you have ever shown a new starter how to close up the office at night, lock the safe, or handle a customer refund, you already understand the idea. An SOP just captures that knowledge on paper so it does not live only in one person’s head.

This guide explains what an SOP actually is, what it is not, and how to recognise the moment your business needs one.

Why This Matters

Every business runs on repeatable work. Opening the office, processing a delivery, handling a customer complaint, filing paperwork, preparing an invoice, these jobs happen again and again. When they are done differently each time, depending on who happens to be on shift, the business pays for it: mistakes multiply, training new staff takes longer, customers get inconsistent service, and the owner becomes the only person who knows how anything works.

An SOP fixes that by turning tribal knowledge into a written standard. The benefits are practical, not theoretical:

Consistency. Customers get the same quality of service whether it is Monday morning or Friday night, whether it is a veteran or a new hire behind the counter.
Faster training. New employees learn from the document instead of shadowing someone for three weeks and hoping they absorbed everything.
Fewer mistakes. When the correct sequence is written down, people do not have to remember it from memory under pressure.
Business continuity. If your best operator leaves, the knowledge leaves with them unless it was written down first.
Accountability. When a step was skipped, the SOP makes it clear which step and who was responsible.

Small businesses often assume SOPs are a big-company thing, something for factories and hospitals. In practice, the smaller the team, the more an SOP matters, because losing one person in a team of eight is proportionally far more disruptive than losing one person in a team of eight hundred.

Key Concepts

What counts as an SOP

An SOP describes a recurring, multi-step process that matters to the business. It states the purpose, the scope (when it applies), the responsibilities (who does what), and the steps in order. A good SOP answers three questions for the person reading it:

What am I doing?
In what order do I do it?
How do I know I have done it right?

That is the whole test. If a document does not answer those three questions, it is not an SOP, it might be a policy, a guideline, or a list of tips, but it is not a procedure.

What an SOP is not

An SOP is not a policy. A policy says what the company expects (for example, “all visitors must sign in”). The SOP says how to make it happen (“the receptionist greets the visitor, checks ID, issues a badge, and logs the visit”). Policies set rules; SOPs describe actions.

An SOP is also not a training manual. A manual teaches someone about a subject; an SOP assumes the reader is already trained and just needs the agreed sequence. SOPs work best as short, on-the-job references, ideally one or two pages, not encyclopedias.

And an SOP is not frozen in stone. It is a living document. When the process changes, new equipment, new software, a better way discovered on the floor, the SOP gets updated. An out-of-date SOP is worse than no SOP at all, because people follow the wrong steps with confidence.

One-page SOPs and visual SOPs

Not every SOP needs to be a long document. A one-page SOP covers the whole procedure on a single sheet, purpose, roles, and steps, which makes it easy to post on a wall, laminate for a workstation, or hand to a trainee. Short SOPs get read; long ones get filed and forgotten.

Visual SOPs use photos or diagrams at each step instead of relying purely on text. They are particularly useful where language barriers exist, where the task is physical (cleaning equipment, setting up a room), or where a picture genuinely replaces a paragraph of explanation.

Practical Steps: Writing Your First SOP

You do not need a committee or a project plan to start. Pick one process and write it down.

1. Choose a process that causes pain. Do not start with the process that works fine. Start with the one that goes wrong when you are not there, the close-up routine, the monthly stock count, the customer refund. Pain is the best guide to where an SOP will pay off.

2. Watch someone do it, or do it yourself. The biggest mistake is writing an SOP from memory at a desk. Watch the task happen, take notes on the actual sequence, and ask “why?” at each step. You will often discover steps that nobody remembered until they did them.

3. List the steps in order. Number them. One action per step. Use plain verbs: open, check, record, sign, lock, send. If a step has a decision point (“if the payment is over $500, get manager approval”), write it as a sub-step, not as a footnote.

4. Add the context a stranger would need. State the purpose in one line, list who does what, and note any tools, equipment, passwords, or safety warnings. Define anything that a new starter would not already know.

5. Keep it to one or two pages. If it runs longer, split it or use a visual format. Brevity is a feature: it means people will actually read it at the workstation.

6. Test it with a real person. Give the draft to someone who knows the task only roughly and ask them to follow it. Where they stumble or guess, the SOP needs fixing. This single step improves an SOP more than any amount of re-reading.

7. Date it and name an owner. Put a version date and the name of the person responsible for keeping it current. Review it at least once a year, or whenever the process changes, whichever comes first.

Common Mistakes

Writing SOPs for things that happen once. An SOP is for recurring work. A one-off project needs a plan, not a procedure. If a task happens less than a few times a year, a simple checklist or note is usually enough.
Writing from the desk, not the floor. Procedures written without watching the work reflect how the job should be done in theory. They clash with reality on day one and lose the team’s trust.
Making them too long. A twelve-page SOP for opening the office will be read exactly once, by nobody. Short documents survive contact with a busy workday.
Burying them in a folder. An SOP nobody can find is decoration. Post physical SOPs where the work happens; keep digital ones one click from the team’s main workspace.
Never updating them. Processes drift. Equipment changes. The SOP that was perfect in 2022 may be wrong now. An owner, a review date, and a simple update process prevent slow rot.
Confusing policy with procedure. “Be professional on the phone” is a policy statement, not a step. The SOP version is: “Answer within three rings. Say your name and the company name. Ask how you can help.” Actionable beats aspirational.
Writing SOPs nobody asked for. If the team does not feel the pain the SOP addresses, they will treat it as paperwork. Start with their real problems and they will adopt it themselves.