What Is an SOP? Standard Operating Procedures Explained

An SOP, short for standard operating procedure, is a written set of step-by-step instructions for a task that happens again and again, so that anyone who follows it gets the same result. In a small business that could be opening the shop, issuing a refund or onboarding a new employee; in a lab or factory it could be cleaning a machine or handling a sample. The point is consistency: the work no longer depends on who happens to be on shift.

In everyday speech "SOP" is sometimes used loosely to mean "the usual way of doing things". In a business, it refers to an actual document that someone owns, keeps current and can hand to a newcomer.

Why a small team benefits

Large organisations write procedures because regulators or auditors ask for them. Small ones gain for more practical reasons. Knowledge stops vanishing when someone leaves or takes holiday. New staff learn faster and ask fewer repeated questions. Mistakes become easier to trace, because you can compare what happened with what the procedure says. And the owner can step back from routine work without everything slowing down.

What goes into a standard operating procedure

• Title and purpose: what the procedure is for, in one or two sentences.
• Scope: when it applies and when it does not.
• Roles: who carries out each part and who signs off.
• What you need: tools, logins, forms or materials.
• The steps: numbered, each starting with a verb.
• Warnings and checks: safety notes, quality checks and what to do if something goes wrong.
• Owner, version and review date: so everyone knows the copy in front of them is current.

Common formats

The right format depends on the task. A simple step list suits short, linear jobs. A hierarchical list, with sub-steps under main steps, handles longer jobs with detail inside each stage. A flowchart works when the next step depends on a decision, such as whether a customer has a receipt. A checklist suits experienced staff who know the work but must not skip anything. Many teams mix them: a flowchart for the overview and a checklist for the day-to-day.

SOP examples from everyday work

The stock count above connects with a wider routine described in the guide to small business inventory management, and the suspicious-email procedure is one of the habits insurers ask about when quoting cyber insurance for small firms.

How to write an SOP in six steps

1. Pick one task. Start with something frequent where mistakes are costly or annoying.
2. Watch it being done. Ask the person who does it best to talk through each step while you take notes. People skip steps they consider obvious, so ask "and then?" often.
3. Draft in plain words. One action per step, starting with a verb: "Count", "Enter", "Check". Add a screenshot or photo where it saves a paragraph.
4. Test it on someone new. Hand the draft to a person who has never done the task and watch where they hesitate.
5. Fix and publish. Store it where people actually look, such as a shared folder, a wiki or a printed binder near the workstation.
6. Set a review date. Tools, suppliers and rules change, so a procedure needs a named owner who rereads it at regular intervals.

Mistakes that make procedures useless

The most common is writing for an imaginary expert: long paragraphs, missing context and unexplained abbreviations. Another is documenting how a task should ideally work rather than how it actually works, which leads staff to ignore the document. Procedures also fail when nobody knows where they live. If a team already relies on a project tool or shared workspace, browsing app directories for integrations can show whether procedures can sit right next to the tasks they describe. For physical businesses, the useful starting point is usually the list of daily jobs in a guide like brick-and-mortar businesses you can start on a limited budget, each of which deserves its own short procedure.

Frequently asked questions

What is the difference between a policy and an SOP?

A policy says what the business requires and why, for example "refunds are offered within a set period". The SOP says exactly how staff carry that out.

How long should an SOP be?

As short as the task allows. Many good procedures fit on one page; longer ones should be split into separate tasks.

How often should procedures be reviewed?

Whenever the task changes, and otherwise on a fixed cycle that suits the business. A review date printed on each document keeps that from being forgotten.