What should a restaurant or hotel SOP include?

One task, one page: the outcome standard (what done looks like), the steps in order, the time it should take, who owns it, and what to do when it goes wrong. If it doesn't fit on a page, it's two SOPs.

Why do most operations manuals fail?

They're written as binders instead of tools: too long, written once and never updated, stored where nobody works, and never tied to training. An SOP that isn't referenced during onboarding and pre-shift is dead within 90 days.

Field Notes · July 2026 · Operations

SOPs That Survive Turnover: Why Most Manuals Die in a Drawer

Every operation I've ever walked into had procedures. Almost none had them written down where they mattered. The best server knew the wine service sequence; the opening cook knew the line check; the sales coordinator knew how contracts got filed. Then one of them gave notice, and the operation got measurably worse for six weeks.

That's not a staffing problem. That's a documentation problem wearing a staffing costume.

Why Manuals Fail

Most operations manuals die within 90 days of being written, for predictable reasons: they're binders instead of tools — 80 pages nobody opens mid-shift. They're written once and never touched as the operation changes. They're stored where nobody works — the office shelf instead of the station. And they're never tied to training, so using them was optional from day one.

An SOP that isn't referenced during onboarding and pre-shift isn't a standard — it's a suggestion with a staple in it.

The One-Page Rule

One task, one page. Every SOP I write has five parts:

1. The standard — what "done right" looks like, in one sentence.
2. The steps — in order, numbered, no step longer than a line.
3. The clock — how long this should take.
4. The owner — which role does it, and who checks it.
5. The exception — what to do when it goes sideways.

If a task won't fit on a page, it's two tasks. The discipline of the single page is what keeps the document alive — a new hire can hold it, a manager can audit against it, and a shift lead can retrain from it in five minutes.

Rollout Is the Product

Writing the SOP is a third of the work. The rest is rollout: introduce each one in pre-shift, have the current best performer demonstrate it, and fold it into onboarding so every new hire learns the standard — not their trainer's personal version of it. Then review the library quarterly; ten minutes per document. The operations that do this stop re-teaching the same job every time someone leaves.

That's the quiet payoff: SOPs turn your best shift into every shift — and they make your business worth more, because a buyer or a bank can see an operation that runs on systems instead of memories.

Want your operation documented so it survives turnover?

SOP playbooks are a defined engagement — documented, trained, and priced up front.

Build Your Project Brief