Searching for an SOP template usually returns a Word document with a logo box, a revision table and twelve headings nobody fills in. This one is different in two ways: it is built around the eight elements that make a procedure followable on the floor, and it comes with a complete worked example so you can see what “good” looks like before you write your own.
Copy the blank template into your operations library, or paste it into Opscale’s AI checklist creator with your own details and let it draft the structured version. For the thinking behind each section, see the guide to standard operating procedures and how to write an SOP in 7 steps.
The blank SOP template
SOP TITLE: [Task name, as staff call it]
SOP ID / VERSION: [e.g. REC-01 v3] EFFECTIVE DATE: [date]
OWNER: [Role responsible for keeping this SOP current]
1. PURPOSE
Why this procedure exists, in one or two sentences.
2. SCOPE
Sites: [all branches / specific sites]
Departments: [kitchen / front of house / store]
Roles: [who performs it]
Applies when: [situations covered; situations excluded]
3. ROLES AND RESPONSIBILITIES
Performs: [role]
Verifies: [role]
Notified on exception: [role]
4. TRIGGER AND FREQUENCY
Starts when: [time / event / condition]
Frequency: [per shift / daily / weekly / per occurrence]
Time limit: [must be completed within ...]
5. EQUIPMENT AND MATERIALS
[thermometer, sanitizer, labels, keys, forms, app ...]
6. STEPS
1. [Imperative verb + object. One action.] Standard: [measurable] Proof: [reading / photo / signature / none]
2. ...
3. ...
7. STANDARDS AND LIMITS
[Acceptable ranges, timings, counts, appearance. The definition of done.]
8. PROOF AND RECORDS
What is captured: [readings, photos, signatures, timestamps]
Where it is kept: [system / folder] Retained for: [period]
9. EXCEPTIONS AND ESCALATION
If [condition] then [corrective action]; log [what]; notify [role] within [time].
10. RELATED DOCUMENTS
[Policy, work instructions, training video, previous version]
11. REVISION HISTORY
[version / date / change / approved by]
Eleven headings looks like a lot. In practice, sections 1 to 5 and 7 to 11 are a few lines each; the SOP is section 6. Keep it that way.
The worked example: receiving chilled and frozen deliveries
This is the SOP we recommend most operators write first. Receiving is where food safety, cost control and supplier management meet, and it is the record inspectors in Saudi Arabia and the UAE most often ask to see.
SOP TITLE: Receiving chilled and frozen deliveries
SOP ID / VERSION: REC-01 v3 EFFECTIVE DATE: 1 May 2026
OWNER: Head of Operations
1. PURPOSE
Make sure every chilled and frozen delivery is safe, matches the order and is
recorded, before it enters storage.
2. SCOPE
Sites: All branches and the central kitchen
Departments: Kitchen
Roles: Receiving team member on shift; shift manager
Applies when: Any delivery containing chilled or frozen food.
Dry goods follow REC-02.
3. ROLES AND RESPONSIBILITIES
Performs: Receiving team member
Verifies: Shift manager (reviews the completed task daily)
Notified on exception: Shift manager immediately; Head of Operations if a
delivery is rejected
4. TRIGGER AND FREQUENCY
Starts when: A delivery vehicle arrives
Frequency: Per delivery
Time limit: Chilled and frozen items into storage within 15 minutes of arrival
5. EQUIPMENT AND MATERIALS
Calibrated probe thermometer, sanitizing wipes, delivery note, Opscale
receiving task on phone
6. STEPS
1. Open the "Receiving" task and select the supplier.
Proof: automatic timestamp
2. Check the vehicle: chilled compartment running, no pests, no strong odours.
Standard: compartment on and clean. Proof: tick; photo if not compliant
3. Match delivered items and quantities against the delivery note.
Standard: quantities equal to the note. Proof: tick per line; note variances
4. Probe one chilled item per category between packs (do not pierce packaging).
Standard: 0–5°C. Proof: reading per item
5. Check frozen items for solid state and ice crystals indicating thaw/refreeze.
Standard: frozen solid, no large crystals. Proof: tick; photo if rejected
6. Check dates and labels on every item.
Standard: use-by date at least 3 days away unless agreed otherwise.
Proof: photo of label on any short-dated item
7. Accept or reject each line. For rejected lines, go to section 9.
8. Move chilled items to the walk-in and frozen items to the freezer.
Standard: within 15 minutes of arrival. Proof: completion timestamp
9. Sign the delivery note; keep the branch copy; photograph the signed note.
Proof: photo
10. Submit the task.
7. STANDARDS AND LIMITS
Chilled 0–5°C. Frozen at or below -18°C (frozen solid). Use-by at least 3 days.
Storage within 15 minutes.
8. PROOF AND RECORDS
Readings per item category, photos of labels and rejections, signed delivery
note photo, user and timestamp. Stored in Opscale; retained 24 months.
9. EXCEPTIONS AND ESCALATION
Chilled above 5°C or frozen showing thaw: reject the line, photograph it, note
the reading, inform the driver, log the rejection in the task. The shift manager
is notified automatically. Head of Operations contacts the supplier the same day.
Quantity variance: accept delivered quantity, note variance, flag for purchasing.
Thermometer missing or uncalibrated: do not accept chilled items; escalate to
shift manager.
10. RELATED DOCUMENTS
Food-safety policy FS-01; work instruction WI-04 "Calibrating the probe
thermometer"; training video "Receiving in 3 minutes"; REC-01 v2 (retired).
11. REVISION HISTORY
v3 1 May 2026 Added photo of signed delivery note; use-by minimum 3 days.
v2 10 Jan 2026 Added 15-minute storage limit.
v1 2 Sep 2025 First issue.
What to notice in the example
The steps carry the standards and the proof. A reader does not have to flip to section 7 to know what “acceptable” means at step 4; it is right there. Sections 7 and 8 just summarize.
Proof is targeted. Ten steps, but only the ones that matter produce a reading or a photo. Asking for a photo of everything trains people to photograph nothing properly.
The exception path is specific. It says what to do, what to log, who hears about it and when. “Inform manager” on its own is where most SOPs fail. See our note on this in the restaurant SOPs every branch needs.
Roles, not names. The SOP survives the receiving team member leaving next month.
Version history is short and dated. When an inspector or auditor asks “when did you add the 15-minute limit?”, the answer is on the document.
Turning the template into a live task
A template on paper is still a document. The point of the structure above is that it maps directly onto a digital task:
| Template section | In a digital task |
|---|---|
| Trigger and frequency | Schedule: per delivery, or 07:00 daily, assigned to a role |
| Steps | Checklist items in order |
| Standards | Validation rules on each field (0–5°C), automatic flag when breached |
| Proof | Field types: number, photo, signature, auto timestamp |
| Exceptions | Corrective-action sub-task triggered by the breach; notification to the manager role |
| Records | Searchable history by branch, date and item |
In Opscale, the SOP document sits in the operations library with its training video; the task version runs through tasks and checklists; rejections and corrective actions are recorded in the logbook; and the AI checklist creator can produce the whole task from this template, or from a photo of your existing paper form, in a minute.
Next SOPs to write with this template
Once receiving is live, the same template handles the rest. The usual order for a restaurant group:
- Opening and closing (template here)
- Cold-holding and temperature logs
- Cleaning and sanitation schedule
- Cash handling and end-of-day
- Guest complaint handling
- Incident reporting
For a café chain, start with the espresso machine cleaning SOP in coffee shop SOPs; for a delivery kitchen, with packaging and handover in cloud kitchen SOPs.
Write one. Test it on a new hire. Assign it to a role. Then write the next one.