SOP Builder (Standard Operating Procedure)

A standard operating procedure, or SOP, writes down how a recurring task is done so that anyone trained can do it the same way. Cafés use them to open the shop safely, clinics to clean equipment, offices to onboard a supplier. This page builds a procedure document. It is not the “statement of purpose” essay that university applicants write, which has its own planner on this site.

The header

The title, an optional document number and the department identify the procedure. A version number, an effective date and a review interval in months control its life. The tool adds the interval to the effective date to print a next review date: effective 10 November 2026 with a 12-month interval gives 10 November 2027. The owner, who maintains the SOP, and the approver, who authorises it, are listed too.

The body

Section 1 is the purpose, a sentence on why the procedure exists. Section 2 is the scope, saying who and what it applies to. If you list roles, a table of role and responsibility follows. Tools and materials is a bulleted list. The procedure is a table: each line you type as step | who | time becomes a numbered row with the action, the person responsible and how long it takes. Safety, quality and compliance notes, the records to keep, and a table of terms and meanings close the body. Any section you leave empty is dropped, and the sections that remain are numbered in order. Signature lines for the owner and the approver end the page.

A worked example

The sample is “Opening the café each morning” for Kettle & Co, document OPS-014 in Store operations, version 1.2, effective 10 November 2026 with a next review on 10 November 2027. The purpose is to make sure every café opens on time, safe and ready to serve, and the scope is all opening staff at every Kettle & Co café. Two roles are listed, the opening lead who runs the checklist and signs it off, and the barista who prepares the machines and the bar. The tools are a checklist, sanitiser and cloths, a thermometer and a cash float bag. The six steps are disarm the alarm and turn on the lights (2 min), check and record fridge and freezer temperatures (5 min), switch on and flush the espresso machines (10 min), sanitise counters and tables (10 min), count and record the till float (5 min) and unlock the front door at opening time (1 min). Safety notes say fridge temperature must be 5 °C or below and to wear non-slip shoes, and records are the signed checklist, kept for 12 months, and the temperature log.

Writing steps that work

Start each step with a verb and give one action. Put them in the order people do them, and name one owner per step. State limits as numbers, such as a temperature or a time, not as “adequate”. Use the same words for the same things throughout. Test the draft by asking someone who has not done the task to follow it and note where they hesitate.

Keeping it alive

An SOP that is not reviewed becomes wrong. Set a review interval that fits how often the process changes, update the version when the steps change, and keep the old version for the record. Make sure the current one is where people work, on a wall or a shared drive, and remove old copies.

Limits

The tool gives a clear structure and works out the review date. It does not check that steps are safe or complete, and it does not make a procedure compliant with a quality or safety standard. Regulated settings, such as food, health or manufacturing, have their own requirements. Nothing you type is uploaded or saved.

Related tools

• RACI Matrix Builder settles who is responsible for each part of a larger process.
• Incident Postmortem Builder turns failures into improvements to a procedure.
• PRD Template Builder documents a product, a different thing from a repeatable task.
• Bug Report Builder records problems found when a procedure is followed on software.