Creating Standard Operating Procedures (SOPs)

A standard operating procedure (SOP) is a written, step-by-step description of exactly how a task should be done every time — opening the restaurant, closing the line, prepping a station, handling a refund. SOPs are what let your restaurant run to the same standard whether you're on the floor or on vacation, because they take the "right way" out of your head and put it where every staff member can follow it. Without them, quality depends on who happened to work that shift.

Why SOPs matter more than owners think

Most restaurant problems aren't people problems — they're consistency problems. A dish comes out differently depending on the cook. Closing gets done thoroughly or sloppily depending on the closer. New hires take weeks to learn what a one-page checklist could have taught in a day. SOPs fix all of that by defining "good" once and making it repeatable. They also make you less trapped in your own business: a restaurant that only works when the owner is present can never grow or give the owner a day off.

Start with the tasks that hurt most when done wrong

Don't try to document everything at once — you'll never finish. Prioritize the procedures where inconsistency costs you the most:

Knock out the top few first. An opening and closing SOP alone eliminates a huge share of daily chaos.

Write them so people actually follow them

An SOP nobody reads is wasted effort. Keep them usable:

1. One task, one document. Don't bury closing inside a 40-page manual. A single clear checklist per task gets used.
2. Number the steps in order. Simple, literal, in the sequence they happen. "1. Turn off fryers. 2. Filter oil. 3..."
3. Write for a brand-new hire. Assume no prior knowledge. If a step needs a judgment call, say what "right" looks like.
4. Add the why for the important ones. People follow rules they understand. "Cool soup to 41°F within 2 hours — bacteria multiply fast in the danger zone."
5. Make them visible. Laminate the closing checklist and hang it where closing happens. An SOP in a binder in the office doesn't exist.

Use the worksheet below as a template to draft your first SOPs in a consistent format.

An SOP isn't written until a brand-new hire can complete the task correctly using only the document, with no one explaining it to them.

Bake procedures into your systems, not just paper

The strongest SOPs are the ones your tools enforce so they can't be skipped. When your point-of-sale requires a manager code for voids, prompts the right steps at close, and logs who did what, the procedure enforces itself. Cobblestone POS supports this with permission controls, guided closeouts, and reporting that shows what actually happened each shift — on a free, all-in-one platform with no monthly fee, where a system like Toast charges $470+/mo for comparable controls. A cash-handling or void SOP backed by system permissions beats one that relies on everyone remembering the rule.

Keep them alive

SOPs go stale the moment your menu, equipment, or team changes. Review them on a schedule — quarterly is reasonable — and update any that no longer match reality. Assign an owner to each SOP so someone is responsible for keeping it current. Fold them into onboarding so every new hire learns the documented way from day one; see Onboarding New Hires the Right Way and Creating an Employee Handbook for Your Restaurant.

Start with one this week

Don't wait for a perfect operations manual. Pick your single messiest recurring task — usually closing — and write the SOP for it this week using the template below. Test it by handing it to a new staff member and watching them follow it. Fix the gaps they hit, then move to the next procedure. A handful of clear, followed SOPs will do more for your consistency and your freedom than any amount of hovering.