Standard Operating Procedure Template
Free editable standard operating procedure with retail, factory, and customer service scenes. Each step pairs an action with owner, tool, and done-when tags.
Use this templateWhat you get
- Three scenes: retail store opening, factory machine pre-start, and customer service complaints
- Step-by-step bars with owner, tool, and done-when tags for each action
- Operational checklist only — no BPMN, ISO, or legal compliance advice
What this template is for
A standard operating procedure is what turns 'this is how we do it' into a set of steps someone can follow without asking. A standard operating procedure template gives you that structure up front: each step carries an owner, a tool, and a done-when condition, so the person doing the work knows who is responsible and when the step actually counts as finished. That is the difference between a checklist people skim and a procedure people can execute. This template gives you three scenes to adapt. The retail scene covers a store opening and shift handover, from unlocking and disarming the alarm to opening the doors on time. The factory scene covers a machine pre-start inspection — clearing the zone, checking guards and sensors, testing the emergency stop, and signing the log. The customer service scene covers complaint handling, from the first restate of the issue to a closed ticket with a follow-up scheduled. Every step is a replaceable bar with a numbered badge and three tags for owner, tool, and done-when, and each scene uses its own color so the three procedures read apart at a glance. This template structures the operational steps; it does not provide BPMN, ISO, or legal compliance conclusions. Build the procedure around your real workflow — who does each step, what tool or record they use, and what evidence proves the step is complete.
When to use this template
- Document a retail store opening and shift handover, step by step.
- Write a factory machine pre-start inspection with safety checks.
- Define a customer service complaint-handling flow from contact to closure.
- Assign an owner, tool, and done-when condition to every step.
- Replace the sample steps with your own procedure and copy rows to add steps.
- Reuse the same three-column structure for onboarding, maintenance, or shipping procedures.
How to use it
- 1Pick a procedure that people repeat — opening a store, starting a machine, or handling a complaint.
- 2List the steps in the order they happen, one action per step.
- 3Assign an owner to each step so there is never a 'someone should' step.
- 4Name the tool or record each step uses — a register, a checklist, or a ticket system.
- 5Write a done-when condition so every step has a clear completion signal.
- 6Review the procedure with the people who do it and trim steps that do not add a check.
Quick example
Retail store opening procedure
Related resources
How it compares to similar tools
SOP vs. checklist
A checklist only asks whether a step happened; an SOP also names who does it and what 'done' looks like. The template keeps the three tags so a checklist grows into a procedure without losing speed.
Step-by-step SOP vs. flowchart
A flowchart shows branches and decisions; an SOP is a linear, repeatable sequence. Use the step list when the order is fixed, and switch to a flowchart when the procedure forks on conditions.
Simple SOP vs. Word document
A Word document is fine for distribution but hard to edit as a team and even harder to scan at a glance. A canvas SOP keeps each step as a movable bar so you can reorder, reassign owners, and copy rows without reformatting.
Common mistakes to avoid
Steps with no owner
A step that says 'someone should check the till' never gets done. Give every step a named owner or role.
No done-when condition
'Check the machine' is too vague. Write a completion signal like 'levels within spec' so the step is verifiable.
Mixing branches into one linear list
When a procedure forks on a decision, a single list gets confusing. Keep the linear SOP for fixed sequences and use a flowchart for branches.
Writing the procedure without the people who do it
An SOP written from memory misses the exceptions the operator handles daily. Review it with the person doing the work.
Too many steps with no purpose
Every step should add a check, a handoff, or a record. Cut steps that exist only out of habit.
Frequently asked questions
What is a standard operating procedure template?+
A standard operating procedure template is a step-by-step structure for a repeatable task, where each step names an owner, a tool or record, and a done-when condition. This template covers retail, factory, and customer service procedures you can edit in the browser.
What should an SOP include?+
A base SOP includes the steps in order, an owner for each step, the tool or record used, and a done-when condition. Add a header for the procedure name and a note for how to update it.
What is the difference between an SOP and a checklist?+
A checklist records whether a step happened; an SOP adds responsibility and completion criteria. The template uses owner, tool, and done-when tags to keep both.
How do I write an SOP step by step?+
List the steps in order, assign an owner to each, name the tool or record, and write a done-when condition. Then review it with the people who perform the work.
What makes a good done-when condition?+
A done-when condition is a verifiable signal, not a feeling — 'float matches the log' or 'log signed and filed'. It tells the next person the step is actually complete.
Does this template cover BPMN or ISO compliance?+
No. This template structures an operational procedure; it does not provide BPMN, ISO, or legal compliance conclusions. Use a compliance professional for those.
Start editing online
Open the template in CodePic, replace the sample content, and make it your own in a few minutes.
See examples: /templates/standard-operating-procedure/examples
