Reading Your Food Inspection Report

Reading and acting on your food inspection report is where compliance is won or lost. Passing the moment of inspection is only half the job — what you do with the report afterwards determines whether the same issues reappear at the next visit and whether you meet the legal deadlines attached to any notice. A council report from an Environmental Health Officer (EHO) is not just a scorecard; it is a prioritised action list referenced to specific clauses of Standard 3.2.2 and state regulations. This guide explains how to decode the report, prioritise by risk, write corrective actions that stick, and respond to improvement notices correctly. What Does an Inspection Report Contain? Formats vary by council, but most reports share a common anatomy. Findings are usually categorised by severity — often critical, major and minor — and each is cross-referenced to the clause of the Food Standards Code or state regulation it relates to. The report typically records the date, the inspecting officer, the areas assessed, and a deadline for corrective actions . In more serious cases it may attach a formal improvement notice or, rarely, a prohibition order. Read the whole document carefully and make sure you understand the clause reference behind every finding before you act. How Should You Prioritise the Findings? Work in order of risk, not the order the findings appear on the page: Critical findings — issues posing an immediate risk to health, such as a major temperature failure or pest infestation. Fix these immediately, sometimes before resuming trade. Major findings — significant issues that must be corrected within days, with documented evidence. Minor findings — lower-risk issues to correct within a scheduled, reasonable timeframe. Assign an owner and a due date to every finding, and track them to completion. A simple corrective actions log turns a static report into a managed list where nothing slips. How Do You Write an Effective Corrective Action? A weak corrective action just says "cleaned the fridge." A strong one prevents the problem returning. Structure each corrective action around four elements: What happened — the finding, in plain terms, with the clause reference. Root cause — why it happened (for example, no scheduled check, unclear responsibility, faulty equipment). Immediate action — what you did to fix it now, with evidence such as a photo or a temperature reading. Preventive action — what changes so it does not recur, such as a new scheduled check, retraining or a repair. Our library of corrective action templates and examples shows this structure applied to common findings. How Do You Respond to an Improvement Notice? An improvement notice is a formal legal instrument with a fixed deadline and specified requirements. Treat it as a priority: Read the notice and the deadline carefully and diarise it. Engage your Food Safety Supervisor to lead the response. Gather evidence of compliance — photos, corrected records, receipts for repairs, and retraining records. Contact the EHO if any requirement is unclear; it is far better to ask than to guess and miss the mark. Respond by the deadline with your evidence, and keep a copy of everything you submit. Recorded staff training is often part of the evidence an EHO expects when a finding relates to handler practice. Turn Findings Into Prevention Every finding is a free lesson. Add each one to your internal audit checklist so your next self-audit specifically checks for recurrence. Over time this builds a food safety program that gets stronger with each inspection rather than repeating the same mistakes. If you were caught out because you were not ready, our guide to preparing for a council health inspection helps you get ahead. A Worked Example: From Finding to Fix Suppose the report reads: "Cool room recorded at 8°C — potentially hazardous food not stored at 5°C or below (Standard 3.2.2)." A strong response looks like this: Immediate action: move affected food to a working fridge, probe and record temperatures, and discard any product that had been above 5°C beyond the 2-hour/4-hour limit. Root cause: the cool room's door seal had perished, so it could not hold temperature. Preventive action: replace the seal, add the cool room to a twice-daily temperature check, and set an alert so any future drift is caught early. Evidence: photos of the repair, the new temperature log, and the invoice for the seal replacement. That response fixes the symptom, removes the cause, and proves it — exactly what an inspector wants to see. Logging it through corrective actions keeps the trail together. Communicating With Your Team A report is a chance to improve the whole team, not to single someone out. Share relevant findings in a toolbox talk, explain why each one matters, and update procedures so the corrected practice becomes routine. Where a finding relates to handler behaviour, refresh the relevant staff training and record it. A blame-free, learning-focused response is far more likely to prevent recurrence than a reprimand. When You Disagree With a Finding If you believe a finding is factually wrong, you can raise it respectfully with the officer or council rather than simply ignoring it. Provide evidence — records, photos or supplier documentation — that supports your position, and keep the tone constructive. Most councils have a review or appeal process for formal notices. Even while a query is being resolved, keep working on the underlying issue so you are not exposed if the finding stands. Frequently Asked Questions What do the severity ratings on a food inspection report mean? Most councils rate findings as critical, major or minor. Critical findings pose an immediate health risk and must be fixed at once; major findings are significant and fixed within days; minor findings are lower-risk and fixed within a scheduled timeframe. Each is usually tied to a specific clause of the Food Standards Code. How long do you have to fix inspection findings? The r