What Is an SOP? Standard Operating Procedure Meaning, With Examples

What does SOP stand for?

SOP stands for standard operating procedure. Each word does some work.

In business, "SOP" almost always means standard operating procedure. People also say "standard operating practice", and they usually mean the same thing. If you're searching for "SOP meaning" because of a university application, that's a statement of purpose, which is something else entirely.

The plural is SOPs. A collection of them, kept together, is often called an SOP library or, with the wider rules of how the business runs, an operations manual.

What goes in an SOP?

The headings vary, but a working SOP answers the same questions. These are the parts we'd expect to find.

A short SOP for one person's job can drop some of these. Our one-page SOP template keeps just the task, owner, trigger, steps, mistakes to avoid and a check date. For a job that touches money or clients, or that several people share, use the fuller SOP template, which adds who does each step and how to check it.

An SOP example

This is a typical example for a small service business. It's short on purpose, so you can see the shape.

If something goes wrong: if a project is running late, the project lead calls the client before the update goes out, so the email isn't the first they hear of it.

That's an SOP. It isn't long, and it doesn't need special SOP software. What makes it work is the trigger, the named people and the check on each step. For seven more written out in full, see SOP examples for small business.

SOP vs process vs policy vs work instruction

These four words get used as if they mean the same thing. They don't, and the difference tells you which document to write.

One way to remember it: the policy is the rule, the process is the route, the SOP is the written directions and a work instruction is a close-up of one turning. Quality management systems often show this as a pyramid, with policies at the top, then procedures, then work instructions, then the records that prove the work was done.

A small business rarely needs all four layers written down. Most of the value is in the SOP. Write a work instruction only for a fiddly step that trips people up, and keep policies short and separate so the SOP can point to them. For more on how a process differs from a procedure, and where policies fit, see process vs procedure. The line between a process and a system is a separate question, covered in process vs system.

Try sorting a few. Each line below is a typical example.

Why do businesses write SOPs?

An SOP earns its keep in a few specific moments.

• When someone new does the job. They can follow the page instead of interrupting whoever did it last.
• When the usual person is away. The work carries on, because how it's done isn't stored in one head.
• When something goes wrong. You can see which step failed and fix that step, instead of arguing about what was meant to happen.
• When a job is handed over. The handover follows the page, so less gets lost.
• When a client or buyer asks. Some contracts and supplier checks ask for documented procedures. A small business with a few clear SOPs can answer honestly.

An SOP is still only a document. It can sit in a folder with nobody using it. What makes it stick is an owner, a trigger, a place in the team's routine and a review date, and that's the subject of why SOPs alone don't work.

When do you need an SOP?

Not every job needs one. Write an SOP when a job passes at least two of these three tests:

1. It happens often. Weekly or monthly jobs pay back the writing time quickly.
2. It causes real trouble when it goes wrong. Money, clients, deadlines or data.
3. It depends on one person. If they're off, the job stops.

A good moment to write one is the second time a job causes a mistake or a question. The first time could be bad luck. The second time, it's a gap.

You can usually skip an SOP for one-off projects, for work that's mostly judgement (such as approving a final design), and for software tasks the vendor already documents well. Link to the vendor's help page instead of copying it. And if a regulator, insurer or major client sets the format, use theirs.

What makes a good SOP?

A good SOP is short enough to read mid-task, specific enough that two people would do the job the same way, and owned by one named person who keeps it up to date. It's been tested by someone who didn't write it.

For the seven traits in detail, read what makes a good SOP. To write your first one, how to write an SOP that actually gets used takes you through it step by step, and the free SOP generator lets you draft one on screen. The free Task Card in The Business Operating Manual, the free pack from SystemaFlow™, is a one-page SOP template in Word and PDF you can start with today. Like all our systems, it's a done-for-you template, not software.