How to write an SOP for a small hospitality business

A Standard Operating Procedure (SOP) is a written description of how a specific task should be done, by whom, and to what standard. In a small hospitality business, SOPs are one of the most effective tools you have for reducing inconsistency, shortening training time, and stopping the same problems from recurring every week.

Most independent operators know they should have them. Very few actually sit down and write them. Here's how to do it without overcomplicating it.

If you're not sure where the gaps in your operation actually are, the 2-minute Hospitality Scorecard will pinpoint which pillar — menu, operations, or growth — is leaking the most profit before you start writing anything.

Why SOPs matter more in small teams

In a large chain, SOPs are enforced through management layers, mystery shopping, and compliance checks. In a small independent, you don't have any of that — which means the only thing standing between consistent service and chaos is whether your team genuinely knows how to do things correctly.

The most common patterns in under-systemised hospitality businesses:

• The owner is the SOP. When they're there, standards hold. When they're not, things drift.
• Training is verbal. New starters learn differently depending on who shows them.
• The same mistakes repeat. Because the fix is explained but not documented, it doesn't stick.

A simple set of SOPs breaks each of these patterns. They're not a substitute for culture or management — they're the foundation that good management builds on.

What makes a good hospitality SOP

The best SOPs are short enough to actually use on shift. A two-page document that your team reads is infinitely more valuable than a 15-page manual that sits in a drawer.

Every SOP should include:

1. The task name — specific, not vague ('Opening the espresso machine' not 'Coffee setup')
2. Who does it — named role, not individual (barista, floor team, manager)
3. When it happens — start of shift, end of service, daily, weekly
4. Step-by-step instructions — numbered, one action per step, plain English
5. The standard — what does 'done correctly' look like? Include a photo where useful.
6. What to do if something goes wrong — the most common failure point and who to escalate to

The 8 SOPs every café or restaurant needs

Start here. These eight procedures cover the critical control points in most independent hospitality businesses:

1. Opening routine — full setup before first cover or order
2. Closing routine — till reconciliation, cleaning, lockdown
3. Prep SOP — daily mise en place by section, portion specs included
4. Service flow SOP — order to delivery, table turn or counter service protocol
5. Cleaning schedule — daily, weekly, deep clean tasks with owner and sign-off
6. Cash and till reconciliation — end of service process, void/refund authority
7. Stock and waste log — daily waste recording, weekly order process
8. New starter onboarding — week one tasks, what they need to know before going live

A simple SOP template

Common mistakes when writing SOPs

Too long. If it takes more than 10 minutes to read, it won't be used in the moment. Break long procedures into sub-tasks and create separate SOPs for each.

Too vague. 'Ensure cleanliness' is not an SOP. 'Wipe down the backbar surfaces with blue cloth and food-safe spray after every service' is an SOP.

Written in the office, never tested on the floor. The best SOPs are written by the person who does the job most often, then reviewed by the manager. Walk through each step in the actual space before publishing it.

Never updated. SOPs go stale when equipment changes, staff change, or processes evolve. Build a review date into every document. Quarterly is usually sufficient.

Starting without being overwhelmed

You don't need all eight SOPs written this week. Start with the two that cause the most recurring problems in your business right now. Usually this is the opening routine or the closing/till process. Write them in plain English, test them on shift, refine them once, then move to the next one. A library of eight good SOPs built over six weeks is far better than eight mediocre ones written in a single afternoon.

The businesses that run consistently aren't the ones with the best staff — they're the ones with the best systems. Good staff make good systems work. Great systems make average staff perform consistently. If you want a deeper view on the menu side of consistency, our guide on menu engineering for small restaurants pairs naturally with strong prep and service SOPs.

The Performance Builder package includes a full set of 15 role-specific SOPs built for your business.