Why most SOP templates fail at the second location
Most freely available SOP templates are structured around the procedure itself: purpose, scope, steps, done. That is adequate for a single restaurant where one person holds the standard and can correct anything that drifts.
It falls apart across locations, because it answers what to do and not the three questions that actually determine whether anyone trusts the document:
- Is this the current version?
- Does it apply to me, in my role, at my restaurant?
- Who do I go to when it does not match reality?
A template that omits those produces documents that are technically correct and practically ignored. The header is not bureaucratic overhead — it is the part that makes the procedure authoritative.
The template
1 · Control block
Procedure title
Plain language, matching what staff call it. “Opening the Patio Bar,” not “FOH-BAR-001.”
Version and date
A visible version number and the date it was approved. If someone has to open file properties to work out which is newest, the document has already failed.
Status
Draft, In review, or Approved. Anything not Approved should be visibly not-yet-authoritative.
Applies to — roles
The specific roles this governs. A procedure that implicitly claims to apply to everyone gets discounted by everyone.
Applies to — locations
All locations, or named restaurants. This is the field that lets approved local variation exist without becoming tribal knowledge.
Owner
The named person who can approve a change. Not a department — a person. Ambiguity here is a common reason changes stall.
Review trigger
What forces a review: a menu change, equipment change, vendor change, regulatory change, or a date. Event triggers catch more than calendars do.
2 · Procedure
Why this matters
One or two sentences on what goes wrong if this is done incorrectly — guest impact, safety, cost. Staff follow procedures they understand the reason for and shortcut ones they do not.
Before you start
Equipment, ingredients, access, or prior steps required. Most procedure failures happen because a prerequisite was missing, not because a step was performed wrong.
Steps
Numbered, one action per step, written in the order performed. Include quantities, times, and temperatures as specific values — never “until done” where a number exists.
Standards and tolerances
What correct looks like, and what range is acceptable. “4.5 oz portion” is a standard; “appropriate portion” is not.
Common mistakes
The two or three things that actually go wrong. Usually the most-read section of any SOP, and the one most templates omit entirely.
When something is wrong
What to do if the procedure cannot be followed as written — who to tell, and whether to proceed. Without this, staff improvise silently.
3 · Connected information
Related material
Other procedures, recipes, or references this depends on or affects. This is what makes change manageable: when this procedure changes, this list is where the change has to travel.
Training reference
Where this appears in onboarding or role training, so a change here can be traced into what new hires are taught.
Change log
What changed, when, and who approved it. Three lines is enough. It is how you answer “when did we start doing it this way” a year later.
A worked example
Here is the template filled in for one recipe standard.
Grilled Chicken Bowl
Version 4 · Approved March 12
Applies to
Kitchen and Expo
Review trigger
Menu or vendor change
Standard
Chicken portion4.5 oz
Rice6 oz
Sauce1.5 oz
Common mistake
The portion was 5 oz until March. Older printed line references may still show it.
If this changes, update
Prep guide→Line reference→Role training
That related-material list is the reason a change to this procedure doesn’t quietly leave three other documents wrong.
Rules for writing the steps
01One action per step
If a step contains “and,” it is probably two steps, and the second one gets skipped.
02Numbers, not adjectives
Times, temperatures, quantities and counts. “Chill thoroughly” means something different to every person who reads it.
03Write it in the order it’s done
Not the order that’s easiest to explain.
04Name the tool or station as staff name it
Including local naming where it differs.
05Keep it to one screen where possible
A procedure someone has to scroll through during service is a procedure they will do from memory.
Where to store it, and the honest limitation
A template solves the format problem. It doesn’t solve the management problem.
A folder of well-structured SOPs still can’t tell you which restaurant is running an older version. The harder problem is keeping each SOP current across:
ProceduresTrainingLocationsRolesRelated answersFuture changes
If you’re adopting this template, decide at the same time who owns review, where unresolved issues get raised, and what happens to training when a procedure changes. More on SOP management across locations, or how to keep procedures current once they exist.
