Corrective Actions in Food Safety: What and How

A corrective action is what you do when a food safety control fails — a fridge running warm, food cooked too low, a missed clean. It has two parts: making the affected food safe (or discarding it) and fixing the cause so it does not recur. Under the Australia New Zealand Food Standards Code, taking and recording corrective action is central to demonstrating your controls work. Requirements vary by category and jurisdiction, so confirm what applies with your state or territory food regulator and local council. Key takeaways: A corrective action is the response when a control fails — it has two jobs: deal with the affected food, and fix the underlying cause so the problem does not happen again.. Take corrective action whenever a critical limit is breached or a check falls out of range: food in the temperature danger zone (5°C to 60°C), undercooking, slow cooling, a missed sanitising step, pest sighting or equipment failure.. Recording the corrective action is as important as taking it — an out-of-range reading with no action noted looks like a failure; the same reading with a documented fix looks like a system that works.. Close the loop: an action is not complete until the immediate risk is controlled, the root cause is addressed, and someone has verified the fix held.. Under Standard 3.2.2A, higher-risk (Category One) businesses generally must record corrective action taken for prescribed activities, or otherwise demonstrate compliance to an authorised officer; confirm your category with your regulator.. 2-hour/4-hour rule for ready-to-eat potentially hazardous food: Cumulative time in the danger zone (5°C–60°C), Action. Under 2 hours — Use now or return to refrigeration. 2 to 4 hours — Use immediately; do not re-refrigerate. 4 hours or more, or time unknown/overnight — Discard. What is a corrective action? A corrective action is the planned response you take when a food safety control does not perform as intended — when a monitoring check shows something is out of range, or a step is missed. It is not the routine control itself (checking the fridge is monitoring); the corrective action is what happens when that check reveals a problem (the fridge is at 9°C, so you act). A complete corrective action always does two distinct things. First, it deals with the product at risk — quarantine, reheat, use immediately, or discard the affected food so unsafe food does not reach a customer. Second, it corrects the cause so the same failure does not recur — repair the equipment, adjust the process, or retrain the person. Dealing with only the food (throwing it out) without fixing the cause means you will be back doing the same thing tomorrow. Monitoring finds the problem; the corrective action responds to it. Part one: control the affected food (quarantine, reheat, use now, or discard). Part two: fix the root cause (repair, adjust, retrain, re-schedule). Part three: verify the fix worked and record what you did. Where corrective actions fit in your food safety system In HACCP terms, corrective actions are one of the seven principles: for every critical control point (CCP) you set a critical limit, monitor it, and define in advance what you will do if that limit is breached. Deciding the response ahead of time — before the crisis — means staff act quickly and consistently rather than improvising under pressure. Standard 3.2.2A (Food Safety Management Tools) makes this concrete for many food service and catering businesses. Its prescribed activities cover the handling of unpackaged, potentially hazardous, ready-to-eat food — receiving, storing, displaying and transporting under temperature control, adequate cooking, minimising time in the danger zone, cooling and reheating. Where a Category One business carries out a prescribed activity, it generally must make records substantiating that the activity meets the Code — and that includes recording corrective action taken when it does not. Category Two businesses (which sell ready-to-eat potentially hazardous food they did not make themselves) generally need a Food Safety Supervisor and trained handlers, but not the full records tool. Confirm your category and obligations with your regulator, because they drive what you must record. Set the critical limit (e.g. cold holding 5°C or below). Monitor it (routine temperature checks). Pre-decide the corrective action for a breach. Record both the reading and the action taken. When do you take a corrective action? Take a corrective action any time a check falls outside its safe limit, a required step is skipped, or something happens that could make food unsafe. The trigger is a breach of a control, not necessarily proof that anyone got sick — you act on the risk. The most common triggers relate to temperature, because most food-poisoning bacteria are controlled by keeping potentially hazardous food out of the danger zone of 5°C to 60°C. Do not wait for a perfect diagnosis before acting. If a coolroom is warm, secure the food first, then work out why. The order is: make it safe, then fix the cause, then record it. Cold food above 5°C or hot food below 60°C for a concerning period. Cooked food not reaching a safe core temperature (75°C is a common simple target). Food cooling too slowly through the danger zone. A fridge, coolroom, bain-marie or probe failing or reading unreliably. A missed or inadequate cleaning and sanitising step. Pest activity, a chemical spill near food, or possible allergen cross-contact. A delivery arriving at an unsafe temperature or in poor condition. Deciding what to do with the affected food The first decision is what happens to the product at risk, and it depends on how far the control failed and for how long. Time and temperature together drive the risk — food a degree or two out for a few minutes is very different from food held in the danger zone for hours or overnight. Where you cannot reliably establish the time out of control, the safest assumption is usually the conservative one. A useful reference point for ready-to-eat potentially hazardous food is the 2-hour/4-hour rule promoted by food regulators: total time between 5°C and 60°C under two hours means the food can be used or returned to refrigeration; between two and four hours it can still be used but not returned to the fridge; and four hours or more means it should be discarded. Reheating rapidly to 60°C or above can be appropriate for some hot-held food caught early, but reheating does not reset accumulated danger-zone time or destroy heat-stable toxins some bacteria produce. Food left in the danger zone for an unknown or extended period, or overnight, should generally be discarded. When in doubt, throw it out — the cost of discarded stock is far lower than the cost of making someone ill. Never taste food to decide whether it is safe; harmful bacteria and toxins are not detectable by smell or taste. Under 2 hours in the danger zone: use now or return to refrigeration. 2 to 4 hours in the danger zone: use immediately, do not re-refrigerate. 4 hours or more, or time unknown or overnight: discard. Hot food caught early: rapidly reheat to 60°C or above where appropriate. Suspected chemical, allergen or physical contamination: quarantine and discard. Label quarantined food clearly (DO NOT USE) so it cannot be served by mistake. Fixing the root cause and closing the loop Dealing with the food controls today's risk; fixing the cause prevents tomorrow's. This is the step businesses most often skip, and the one an environmental health officer (EHO) values most. Ask why the failure happened: was the coolroom overloaded, the door left open, the thermostat faulty, the probe out of calibration, or the process simply not understood by a new staff member? The answer determines the fix — a repair, a schedule change, new equipment, or retraining. Closing the loop means the corrective action is not finished until you have verified the fix actually held. After a repair, confirm the unit is holding temperature before you restock it. After retraining, check that the person now does the task correctly. This verification step turns a one-off patch into a genuine improvement and is what separates a system that works from one that lurches from failure to failure. Identify why the control failed, not just that it failed. Apply a fix matched to the cause (repair, adjust, replace, retrain). Verify the fix worked before returning to normal operation. Watch for repeat failures — a recurring issue signals a deeper problem. Escalate persistent equipment faults rather than resetting them daily. Recording corrective actions A temperature log full of readings tells only half the story; what matters is what you did when a reading was out of range. An out-of-specification entry with no action recorded reads as an unmanaged failure. The same entry with a clear corrective action recorded beside it reads as a control system doing its job. Recording is therefore not paperwork for its own sake — it is the evidence that protects your business during an audit, a customer complaint, or a foodborne-illness investigation. A good corrective-action record captures five things: what went wrong, when it was found, what you did with the affected food, how you fixed the cause, and who did it and when it was resolved. Keep it factual and specific. Records can be paper or electronic — completed checklists, data-logger notes, photos, or a digital app entry all count. Under Standard 3.2.2A, a record once made generally must be retained for a minimum of three months; confirm the exact period with your regulator, as your food safety program or jurisdiction may require longer. What the problem was and when it was found. What happened to the affected food (used, reheated, discarded). The cause and the fix applied (repair, adjustment, retraining). Who took the action and when it was resolved. How the fix was verified. Worked examples of corrective actions Concrete examples make the pattern clear. In each, notice the two parts — food, then cause — and the closing verification, all captured in a sentence or two an officer could read and understand. Coolroom warm: 'Coolroom 9°C at 8:00am. High-risk items in danger zone overnight — discarded. Other stock moved to spare fridge. Technician called; door seal replaced. Coolroom holding 3°C by 11:30am, confirmed before restocking. Action: J. Nguyen.' Undercooked chicken: 'Chicken core temp 68°C at service. Returned to oven, reached 76°C, rechecked before plating. Probe recalibrated; cook briefed on 75°C target. Action: kitchen supervisor.' Missed sanitising: 'Prep bench not sanitised between raw and ready-to-eat at 2pm. Bench re-cleaned and sanitised at correct concentration/contact time. Staff member reminded of the two-step process; schedule sign-off tightened. Action: FSS.' State the reading or event and the time. Say what happened to the affected food. Name the cause and the fix. Note the verification and who was responsible. Worked examples: A delivery arrives warm: A chilled delivery arrives with the potentially hazardous items reading well above 5°C. The receiver rejects the affected stock rather than storing it, notes the supplier and temperature on the delivery record, and raises the recurring issue with the supplier. The corrective action covers both the food (rejected) and the cause (the supplier's cold chain). Bain-marie caught below temperature: Mid-service a cook probes the bain-marie and finds a tray of curry at 54°C. Knowing it has been under two hours in total, they reheat it rapidly to above 60°C and return it to holding, then top up the water bath so it holds temperature. The reading, the action and the time are all recorded. Checklist: The immediate hazard is controlled — affected food quarantined or dealt with. The food's fate was decided on time and temperature, not smell or taste. Quarantined food is clearly labelled so it cannot be served by mistake. The root cause was identified, not just the symptom. A fix matched to the cause has been applied (repair, adjust, retrain). The fix was verified before returning to normal operation. The corrective action is recorded: problem, food, cause, fix, who, when. Recurring failures are escalated rather than reset each day. Staff know in advance what to do when a critical limit is breached. Common mistakes: Discarding the food but never fixing the cause, so the same failure happens again tomorrow.. Recording the out-of-range reading but leaving the action blank — which reads as an unmanaged failure to an auditor.. Tasting or smelling food to decide if it is safe; harmful bacteria and toxins are undetectable this way.. Waiting to diagnose the cause before securing the food, letting the risk grow while you investigate.. Assuming reheating makes danger-zone food safe — it does not reset accumulated time or destroy heat-stable toxins.. Resetting a faulty fridge or bain-marie every morning instead of repairing or replacing it.. Not verifying the fix — restocking a coolroom before confirming it is actually holding temperature..