A food safety SOP guide. What keeps a kitchen compliant, not just clean.

The short answer. What a food safety SOP actually has to prove.

A food safety SOP is a written procedure for one task in a commercial kitchen, built against a HACCP framework rather than general good practice. It covers things a generic SOP template was never designed for: the temperature range a chilled delivery has to arrive within, the corrective action when a probe reads 9°C instead of 5°C, who signs off that an allergen matrix is still accurate after a menu change. If you want the general method for writing any SOP so it actually gets followed, our guide to how to create an SOP covers that in full, and why SOPs matter sets out the cost of skipping documentation altogether. This guide assumes you already accept that case and want the food-specific version: the procedures that keep a kitchen compliant, not just clean on the day someone happens to look.

"Clean" is not the test an inspector or an auditor actually applies. The real test is whether the business can produce a defensible paper trail going back weeks, not a tidy kitchen on the one morning it mattered. The UK Food Standards Agency's Our Food 2022 report found that, as of 31 December 2022, just over nine in ten UK food businesses were rated three, "generally satisfactory", or better under the Food Hygiene Rating Scheme, with 75.7 percent reaching the top rating of five. The businesses that reliably hit five are rarely the ones that scrubbed hardest the night before. They are the ones that can show a working system: logged temperatures, a current allergen matrix, dated cleaning records, all consistent over time rather than assembled for the visit.

How it works in practice. The six procedures a kitchen actually needs.

A food safety management system built from SOPs needs six procedures working together, not one master document trying to cover everything at once. Each does a specific job, and each needs its own owner, because the person checking deliveries at 7am is rarely the person running the closing cleaning schedule at 11pm.

None of these six needs to be complicated to be effective, and none of them is exotic. The CDC's March 2025 analysis of outbreak data reported to the National Outbreak Reporting System between 2014 and 2022 found restaurants were the single most common setting for foodborne illness outbreaks in the United States, and that food left out of temperature control for too long, alongside food cooked or held at the wrong temperature, sat among the leading contributing factors identified. That is the ordinary daily discipline a temperature log is built to catch, which is why it is usually the first procedure worth getting genuinely right, before allergen control or a cleaning schedule.

Where a kitchen's workflow is complicated, several sections or a multi-site central production unit, the six procedures are easier to get right once the actual flow of food through the building is mapped, which is the same discipline behind our process mapping work: who touches the product, where, and in what order, before deciding where each check needs to sit. A food safety SOP written without that picture tends to put the check in the place that is easiest to document, not the place where the hazard actually sits.

The sequence matters as much as the six headings themselves. Goods-in has to be checked and signed off before anything from that delivery reaches a chiller, because a rejected delivery is far easier to send back at the door than to trace through a menu once it has been portioned and used across three dishes. Cleaning schedules work best mapped against the kitchen's actual service pattern rather than a generic opening-and-closing split, a wash-down after the lunch service on a site that runs a heavy lunch trade catches build-up a single evening deep clean never will. And training sign-off should sit closest to the procedure it covers, next to the temperature log a new commis chef is learning to complete, not filed separately in an HR folder nobody in the kitchen ever opens.

What good looks like. A worked example from a hospitality client.

I worked with a boutique hotel group in the Gulf on exactly this, as part of a wider piece of process documentation across their food and beverage operation rather than a stand-alone compliance project. Each outlet kept temperature records differently: two kitchens used paper clipboards with their own layout, one used a spreadsheet the other outlets couldn't see, and nobody above outlet level could say, on any given day, whether every fridge across the group had actually been checked that morning.

The judgement call worth naming is what we did not do first. The obvious fix looks like moving everyone onto one piece of digital logging software immediately. We chose not to, with an internal audit six weeks out and a team that had never used any food safety software before. Rolling out new technology and retraining staff on it in that window risked a worse audit than the inconsistent paper system already in place. Instead, we unified the paper template across every outlet first, same six fields, same layout, same corrective-action line, and only moved to a digital system once that format had run cleanly for a full quarter. It cost us real-time dashboarding for a few months. It bought a format every outlet manager could actually run under pressure, which mattered more going into the audit than the reporting layer on top of it.

The second judgement call was on the allergen matrix. The group's existing review cadence was quarterly, set by the calendar rather than by anything happening in the kitchen. We moved the trigger to every menu or supplier change instead, with the quarterly check kept as a backstop rather than the main mechanism. Within two months, a chef changing a dressing supplier mid-quarter would have slipped straight through a calendar-only review; the change-triggered sign-off caught it before the dish went anywhere near a guest. Neither fix was sophisticated. Both came from accepting that the system had to match how the kitchens actually worked, not how a template assumed they would.

The wider lesson from that engagement is the one I give most hospitality clients starting from a patchwork of habits rather than a blank page: fix the format before you fix the tool. A kitchen team that trusts a paper log because it fits the way they actually move through a shift will keep it accurate. The same team handed a dashboard they didn't ask for, built around a format that doesn't match their service pattern, will fill it in to get it out of the way rather than to record the truth, and a food safety system built on records nobody trusts is worse than one that is visibly incomplete, because it hides the gap instead of showing it.

Pitfalls to avoid. Where food safety SOPs fail in practice.

Most food safety SOPs don't fail because the procedure was wrong on the day it was written. They fail quietly, months later, once the kitchen has moved on and the document hasn't. The five patterns below cover almost every failure I've seen in practice, and all five are cheaper to fix before an inspection than during one.

• Logging without reviewing. A fridge temperature log that someone fills in every morning and nobody reads until an inspector asks for it is not a control, it is a record of a control that may or may not have happened. Build in a weekly glance by a named owner, not just a daily entry by whoever is on shift.
• No written corrective action. A log that shows a reading outside range but has no field for what was done about it proves a problem existed without proving anyone dealt with it. That gap is often what turns a minor inspection note into a formal non-compliance.
• An allergen matrix that goes stale. The matrix is only as current as the last menu or supplier change, and a calendar-only review misses exactly the changes that happen between reviews, which is where most real allergen incidents come from.
• Training sign-off treated as a one-off. A signature at induction proves someone was told once, not that they are still following the procedure six months and one menu change later. Refresh it on a cadence tied to menu or process change, the same logic as the allergen matrix.
• A generic template bolted onto a real kitchen. A downloaded HACCP template that was never adjusted for the actual layout, equipment and menu of a specific site tends to ask for checks that don't map to anything real, and skip the one that does.

Once the six procedures are genuinely working, the next step is usually pulling them into one structure a new hire or a relief manager can actually find their way around, the same job our SOP manual template covers for any growing team. And if these procedures are being built as part of opening a new site rather than fixing an existing one, our restaurant opening checklist sets out where food safety sign-off sits in the wider 90-day run-up, so it isn't left as a task for the final week.