Writing Kitchen SOPs Your Team Will Actually Follow
Every kitchen has procedures; few have them written down in a way people use. A good SOP is short, visual and placed exactly where the work happens. Here's the approach I've used from Marriott in Dubai to independent kitchens in Ontario.
Start with what goes wrong
Ask your team where mistakes happen: late openings, missed temperature checks, inconsistent plates. Write SOPs for those first. Ten useful SOPs beat a hundred-page binder nobody opens.
One task, one page
Each SOP should fit on one page and cover one task: opening the line, receiving deliveries, cooling sauces, closing the tandoor. Use numbered steps, start each with a verb and keep sentences short.
Make it visual
Add photos of the correct result — a properly labelled container, a plated dish, a clean station. Pictures cross language barriers in diverse kitchen teams.
Include the essentials
- Who is responsible
- When it happens (time or trigger)
- Tools and ingredients needed
- Food safety points such as temperatures and holding times
- What “done” looks like
Train, then check
Walk each cook through the SOP once, watch them do it, then sign it off. Managers should spot-check with short daily checklists rather than long audits.
Review them regularly
Update SOPs when the menu, equipment or team changes. An out-of-date SOP teaches people to ignore all of them.
Clear SOPs make a kitchen calmer, safer and easier to scale. If you're opening a new site or fixing a busy one, this is where I usually begin.
