What Is a Standard Operating Procedure?

The plain-English definition

A Standard Operating Procedure — SOP — is a written document that describes how a specific task should be performed, step by step, to a defined standard. It answers three questions: what needs to be done, how it should be done, and to what standard the result will be judged.

SOPs are used across every industry that cares about consistency: healthcare, food service, manufacturing, property management, cleaning, aviation, pharmaceuticals, and beyond. The name changes — sometimes they are called "work instructions," "procedures," "runbooks," or "playbooks" — but the purpose is the same.

What an SOP is not

• It is not a policy. A policy says what a company requires ("all food must be stored at safe temperatures"). An SOP says how to meet that requirement ("check walk-in cooler temperature at opening, log the reading, escalate if above 4 °C").
• It is not a job description. A job description defines a role. An SOP defines a task.
• It is not a manual. A manual is a reference document covering a broad topic. An SOP covers one specific process in enough detail to act on it.

Why SOPs matter

Consistency

The most valuable thing an SOP delivers is a consistent output regardless of who does the work. A cleaning company whose best cleaner is on holiday should produce results indistinguishable from the days she is in. A restaurant kitchen that runs perfectly on a Tuesday should run the same way on a Friday with a different team. SOPs make that possible by encoding the knowledge of your best performers into a document anyone can follow.

Training

Onboarding a new employee without written procedures means training through shadowing, verbal instruction, and hope. With SOPs, a new hire has a document to reference independently — reducing the time a senior team member spends supervising, and reducing the gap between what a new hire is told and what they actually do.

Compliance and audit readiness

In regulated industries — food safety, healthcare, property management, childcare — an inspector will ask to see your procedures. A written SOP with a version history, an issue date, and a named author demonstrates that your process is deliberate and controlled. "We train our staff verbally" is not an acceptable answer during a compliance audit.

Scalability

You cannot scale a business that runs on tribal knowledge. If the process lives in someone's head, it leaves when they do. SOPs are what allow a business to grow — to open a second location, to bring on a second team, to hand off a process to a contractor — without quality degrading.

The anatomy of a well-written SOP

A complete SOP has these seven components:

1. Document control block — title, SOP number, version, date issued, author, approver.
2. Purpose — one or two sentences explaining why this SOP exists and what outcome it is designed to produce.
3. Scope — where and to whom this procedure applies. Be specific: "This SOP applies to residential deep cleans only — not commercial sites."
4. Definitions — any technical terms, abbreviations, or product names that need clarifying.
5. Responsibilities — who does each part of the procedure. Name roles, not individuals.
6. Procedure — the numbered, step-by-step instructions. Each step should contain one action and be specific enough to follow without asking questions.
7. Revision history — a table showing every version, what changed, and who approved it.

What makes a procedure section good

The procedure section is the heart of an SOP and the section most often written poorly. Three rules:

Use numbered steps, not paragraphs. People follow procedures under pressure, often on a phone or clipboard. A paragraph requires reading comprehension. A numbered list requires only execution.

One action per step. "Spray the surface, wait 60 seconds, and wipe" is three steps. Combining them means a reader can complete two and think they have finished. Separate them.

Be specific about products, quantities, and standards. "Clean the fryer" is a task. "Drain fryer oil into heat-proof container, wipe interior with approved degreaser on a lint-free cloth, allow to dry fully before refilling with fresh oil to the MAX line" is a procedure.

How to write your first SOP

1. Pick one process. Start with your most common, most important, or most error-prone task.
2. Shadow the person who does it best. Watch them do it. Take notes on what they actually do, not what they are supposed to do.
3. Draft the steps. Write them in sequence. Use action verbs: spray, wipe, check, log, discard.
4. Add inspection criteria. Define what "done correctly" looks like in measurable terms.
5. Test it with someone new. Ask a team member who wasn't involved in writing it to follow the SOP literally. Every question they ask is a gap to fix.
6. Version it and share it. Save it with a version number, add it to wherever your team accesses reference materials, and set a date to review it.

The goal of a first draft is not perfection. It is capturing the knowledge that currently lives only in someone's head and putting it somewhere the whole team can use it.