How to Write an SOP: Format, Steps and a Free Example

A standard operating procedure (SOP) is a written, step-by-step description of how a routine task is done, so that everyone does it the same, safe way. Good SOPs make training faster, cut mistakes and give auditors something concrete to check. Bad ones sit in a binder and nobody reads them.

This guide covers the SOP format, seven steps to write one, a short example, and the mistakes that make SOPs fail. If you would rather start from a draft, the free AI SOP generator writes one in this format from a single sentence.

The SOP format

Every usable SOP answers seven questions. Use them as the headings of your document.

1. Title: names the task plainly, such as "Warehouse Receiving SOP".
2. Purpose: one or two sentences on why the procedure exists.
3. Scope: who it applies to, and where.
4. Responsibilities: the roles that do the work and sign it off.
5. Equipment & PPE: tools, supplies and protective equipment.
6. Procedure: numbered steps, one action each, with a caution on risky steps.
7. Notes & records: what to record, keep and escalate.

How to write an SOP in 7 steps

1. Pick one task and one audience

Write one SOP per task. "Kitchen operations" is too broad; "closing and cleaning the line" is a task. Decide who will follow it, because a new hire needs more detail than a supervisor.

2. Watch the task being done

Do not write from memory. Watch an experienced person do the task, or do it yourself, and write down every action in the order it happens. This is where you catch the steps people do without thinking.

3. List the equipment and PPE

Write down every tool, supply and piece of protective equipment the task needs. If a step needs gloves, the gloves belong in this list.

4. Write one action per step

Start each step with a verb: "Check", "Place", "Record". Keep each step to one action someone could see you do. Number the steps in the order they are performed.

5. Add cautions where the risk is

Put each hazard or common mistake on the step where it happens. "Never open a hot fryer" belongs on the cleaning step, not in a safety section nobody reads.

6. Test it with a new person

Ask someone who has never done the task to follow the SOP while you watch. Every place they hesitate or ask a question is a step to rewrite.

7. Approve, publish and review

Have the person responsible for the task sign it off, put the SOP where the work happens, and set a date to review it. Update it whenever the equipment or the process changes.

A short example

Here are the first steps of a warehouse receiving SOP written this way:

1. Check in the carrier: match the carrier's paperwork to an open purchase order and assign a dock door.
2. Secure the trailer: chock the wheels or engage the dock lock before anyone enters. Caution: never drive a forklift into a trailer that is not secured.
3. Inspect the seal and load: check the seal number against the paperwork and look for damage before unloading.

See the full warehouse SOP and more SOP examples by industry.

Common mistakes

• Too broad. One SOP that covers a whole department is never finished and never followed.
• Written from memory. Steps that experienced people skip without noticing go missing.
• Several actions in one step. People do the first one and miss the rest.
• Safety in a separate section. Cautions are read when they sit on the step they apply to.
• Never reviewed. An SOP that no longer matches the equipment trains people to ignore SOPs.

Make it easy to follow

People on the floor rarely read a document mid-task. Keep the SOP short, put it where the work happens, and consider a short video of each step: new staff can watch the steps before their first shift. SOPMagic can turn a finished SOP into a step-by-step training video.