Running Mock Inspections to Test Readiness

A mock food inspection is a practice run of the visit an Environmental Health Officer (EHO) could make to your venue at any time. You use the same checklist and scoring an inspector would, but you run it internally, so findings become lessons instead of penalties. Run consistently, mock inspections keep teams sharp, expose blind spots before a real inspection does, and build a genuine culture of readiness. This guide shows you how to plan one, how to score it against the Food Standards Australia New Zealand Food Standards Code, and how to turn the results into lasting improvement. Why Do Mock Inspections Work So Well? Because they combine realism with safety . A real EHO visit is unannounced and high-stakes; a mock inspection recreates that pressure without the consequences, so your team practises performing under scrutiny. Because they are internal, you can be brutally honest about weaknesses and fix them on your own timeline. Run quarterly , they stop the slow drift, a missed clean, a fridge left off-target, an expired certificate, that accumulates between real inspections. They also give newer staff a low-risk rehearsal of what an inspection feels like. How Often Do Real Inspections Happen? Inspection frequency varies by council and state , and generally scales with risk. A higher-risk business, one handling unpackaged potentially hazardous food, can expect more frequent attention than a low-risk retailer of pre-packaged goods, and a venue with a poor compliance history may be inspected more often still. Crucially, most inspections are unannounced , which is precisely why day-to-day readiness matters more than last-minute preparation. You cannot predict the exact day an EHO will arrive, so the only reliable strategy is to run your kitchen as though an inspection could happen at any moment. Quarterly mock inspections train exactly this habit: they keep standards high continuously rather than letting them spike before a known audit and sag afterwards. Check the typical inspection approach for your area in our food safety guides and council directory , but plan your routine around being ready every day regardless. How Do You Plan a Mock Inspection? Pick an inspector. Use your Food Safety Supervisor, an area manager, or an external auditor, ideally someone slightly removed from daily operations for objectivity. Do not tell the team in advance. An unannounced mock reflects reality; a pre-warned one only tests how well the team tidies up. Use the EHO checklist , or your own audit checklist , so the mock covers the same ground a council officer would. Time-bound the visit to 60 to 90 minutes to keep it focused and realistic. Walk the flow of food : receival, storage, preparation, cooking and holding, service, and waste. Check temperature records , cleaning sign-offs , allergen controls and certifications along the way. How Should You Score the Findings? Use the same categories councils use so results are meaningful: critical , major and minor non-conformances. A critical finding is an immediate food safety risk, for example potentially hazardous food in the 5°C to 60°C danger zone beyond the 2-hour/4-hour limits. Issue a written report with each finding, its category, a corrective action , an owner and a deadline. Then re-check those specific items at the next quarter to confirm they were fixed and stayed fixed. What Does a Real EHO Look At? To make your mock realistic, focus on what a genuine Environmental Health Officer prioritises. Temperature control is almost always first: they will check fridge and freezer temperatures, hot-holding, and whether staff understand the 5°C to 60°C danger zone and the 2-hour/4-hour rule. They examine personal hygiene and handwashing , looking at facilities, soap and the actual behaviour of the team. They assess cross-contamination controls , separation of raw and ready-to-eat foods, colour-coded equipment and cleaning between tasks. They review cleaning and pest evidence , allergen management under PEAL, date marking under Standard 1.2.5, and your records , checking that logs are complete, current and signed. They will also confirm your FSS is qualified and current . Structuring your mock around these priorities means you rehearse for the questions you are most likely to be asked. Turning Mock Results Into Action A mock inspection only pays off if the findings drive change. After each one, hold a short debrief with the team while the details are fresh, walk through what went well and what did not, without singling people out. Convert every finding into a corrective action with an owner and a deadline, then track it to closure. Compare results across rounds to see whether the same issues keep recurring; a repeat finding signals a systemic gap that needs a permanent fix, not another reminder. Over several quarters, this cycle steadily raises the baseline, so that when a real inspection arrives, the team simply keeps doing what it already does every day. Building a Culture of Readiness The fastest way to ruin mock inspections is to punish people for what they surface. Reward openness instead. When staff know a mock is a learning tool, they stop hiding problems and start reporting them. Feed the results into toolbox talks , celebrate improvements between rounds, and track trends over time. For groups, compare venues in multi-venue management to see which sites need extra support, and reinforce good habits with staff training . Frequently Asked Questions How often should we run mock inspections? Quarterly is a strong benchmark for most venues, with the full annual audit sitting alongside them. High-risk operations or sites with recent findings may run them more often to embed improvement. Who should carry out a mock inspection? Someone with food safety knowledge but slightly removed from the daily routine, such as your FSS, an area manager or an external auditor. Distance improves objectivity and makes findings more credible. Should staff know a mock inspection