Corrective Action Templates for Food Safety

Corrective action templates give your team a proven structure for responding to food safety incidents in a way that satisfies an Environmental Health Officer (EHO). A strong corrective action records four things: what happened , the root cause , the immediate action taken to make the situation safe, and the preventive action that stops it happening again. This guide gives you ready-to-adapt examples for the most common incidents Australian food businesses face, all aligned with the Food Standards Australia New Zealand Food Standards Code. What Makes a Corrective Action Acceptable to an EHO? An acceptable corrective action demonstrates that you found the real cause and closed the gap, not just cleaned up the symptom. EHOs routinely reject single-line responses such as "fixed" or "spoke to staff" because they show no evidence of systemic improvement. Under Standard 3.2.2 of the Food Standards Code, food businesses must take action when a food safety control fails, and they must be able to show what that action was. Every corrective action you write should answer four questions in order: What happened? Describe the non-conformance factually, with the date, time, location and who identified it. What was the root cause? Ask "why" until you reach a systemic answer, not a person to blame. What immediate action did you take? The steps that made food and the environment safe again. What prevents recurrence? The permanent change to your food safety program, schedule or training. Recording photo evidence and a sign-off from your Food Safety Supervisor (FSS) turns a note into defensible documentation. Our corrective actions feature captures all four fields plus evidence in one workflow. How Do You Find the Real Root Cause? The most common corrective action mistake is stopping at the symptom. A fridge running warm is not a root cause, it is a consequence. Use the 5 Whys technique: ask "why" repeatedly until you reach a systemic answer you can permanently fix. For example: the food was too warm (why?) because the fridge was above 5°C (why?) because the door was not sealing (why?) because the gasket had perished (why?) because there was no inspection schedule for gaskets (why?) because the cleaning schedule never included it. The genuine fix is adding gasket checks to the schedule, not just replacing one seal. Documenting this chain shows an EHO that you understand your own system. Repeat non-conformances are a red flag to inspectors, so a corrective action that only treats the symptom almost guarantees the issue returns. Template 1 — Temperature Breach Incident: Cold food held at 8°C for 3 hours in the display fridge (recorded at 2:15pm). Root cause: door gasket seal had perished, allowing warm air ingress. Immediate action: discarded all affected high-risk stock, moved remaining product to the walk-in, logged temperatures hourly until stable. Prevention: added a weekly gasket inspection to the cleaning schedule and enabled digital temperature monitoring with out-of-range alerts. The Food Standards Code sets the danger zone at 5°C to 60°C . Cold potentially hazardous food should be kept at 5°C or below and hot food at 60°C or above . Use the 2-hour/4-hour rule to decide whether affected food can be used, refrigerated or must be discarded. See our temperature monitoring tools for automated logging. Template 2 — Pest Sighting Incident: A live cockroach observed in the dry store during opening checks. Root cause: a gap in the skirting behind shelving created a harbourage point. Immediate action: deep cleaned the area, disposed of exposed dry goods, placed monitored bait stations, and had the gap sealed by a licensed contractor. Prevention: introduced a monthly pest inspection schedule and a supplier review for incoming cartons, a common way pests enter premises. Template 3 — Allergen Incident Incident: A customer reported a reaction to undeclared sesame in a salad. Root cause: a new dressing supplier changed the recipe and the menu allergen matrix was not updated. Immediate action: removed the dish from sale, offered the customer medical assistance, quarantined the affected batch, and documented the event. Prevention: introduced a supplier change checklist and a mandatory allergen review for every recipe or ingredient change, in line with the Plain English Allergen Labelling (PEAL) requirements under Standard 1.2.3. Allergen mislabelling is one of the most common causes of food recalls in Australia. Our PEAL compliance tools keep your declarations current whenever a recipe changes. Template 4 — Cleaning Failure Incident: An EHO observed grease build-up on the range hood during an inspection. Root cause: the scheduled weekly clean was missed during a period of staff shortage and no one was accountable for the task. Immediate action: completed a deep clean and replaced the baffle filters. Prevention: digitised the cleaning schedule with named responsibilities and required FSS sign-off on completion. Explore our cleaning schedule tools . Template 5 — Food Safety Supervisor Lapse Incident: The venue's FSS certificate expired without a replacement in place. Root cause: no system tracked certificate expiry dates. Immediate action: booked a refresher course and appointed an interim qualified FSS. Prevention: built a compliance calendar with automatic reminders 60 days before any certificate expires. Our team certifications tracker automates this. Responding to an EHO Improvement Notice When an Environmental Health Officer issues an improvement notice , your written response is effectively a formal corrective action with a legal deadline. Treat it seriously: acknowledge the notice, address each item using the four-part structure above, attach photo evidence of the completed work, and respond in writing before the deadline stated on the notice. A vague reply invites a follow-up visit and, potentially, escalation to a prohibition order or penalty. A clear, evidenced response, showing the immediate fix and the syst