Corrective Action Example: Temperature

A useful food safety corrective action example for a temperature failure records five things: the root cause, the immediate action taken, the product decision, the person responsible, and how the fix was verified. A weak entry simply says "fridge too warm, adjusted" and moves on. A strong entry tells a full story that an Environmental Health Officer (EHO) can follow without asking a single question. Writing the second kind is a habit any Australian food business can build. When cold or hot holding drifts into the temperature danger zone of 5C to 60C, the note you write afterwards is your proof that you understood the risk and handled it properly. This guide shows the difference between a note that protects you and one that raises more questions than it answers. What is a corrective action and why does it matter? A corrective action is the documented response you take when something goes wrong with a food safety control. Under Standard 3.2.2 of the Food Standards Code, food businesses must take action when they find that a critical control, such as temperature, has failed. The written record is what shows an EHO that the failure was caught, understood and closed out rather than ignored. Temperature is one of the most common places for controls to slip. A fridge door left ajar overnight, a cool room compressor that struggles in summer heat, or a bain-marie switched on late can all push food out of safe holding. According to Food Standards Australia New Zealand (FSANZ) , keeping good evidence of how you manage food safety is central to demonstrating compliance. A corrective action is that evidence in action. The five parts of a strong corrective action Every temperature corrective action worth keeping answers five questions. Miss one and the record becomes hard to defend. Root cause — why did the temperature fail? Not just what you saw, but the underlying reason. Immediate action — what did you do the moment you found the problem? Product decision — what happened to the affected food? Discarded, reheated, or judged safe and why? Owner — who made the decision and who is responsible for the follow-up? Verification — how did you confirm the fix worked and stayed fixed? Weak versus strong: a real comparison Imagine a morning check finds the cool room reading 11C when it should be at or below 5C. Here is how two businesses might record the same event. The weak version "Cool room warm this morning. Turned it down. All good." This note tells an EHO almost nothing. Was the food safe? How long was it warm? Who decided it was fine? Did anyone check the reading came back down? A note like this can actually make an inspection worse, because it shows the failure was noticed but not properly managed. The strong version "Cool room 1 read 11C at 7:15am open check (target 5C or below). Root cause: door seal found perished, door not sealing overnight. Immediate action: moved all high-risk product to spare cool room at 3C. Product decision: dairy and smallgoods received the previous afternoon assessed as being in the danger zone beyond two hours based on the overnight timeline, so discarded and logged as waste. Vacuum-sealed items within the 4-hour window moved and used first. Owner: Sam (kitchen supervisor). Verification: relief cool room confirmed at 3C; maintenance booked for seal, temporary seal fitted; cool room 1 rechecked at 11am reading 4C and again at close reading 3C. Follow-up: added a nightly close-down door check to the routine." The second version is longer, but every sentence earns its place. It applies the 2-hour and 4-hour rule to the product decision, names an owner, and closes the loop with verification. This is what a defensible food safety corrective action example for a temperature failure looks like. How do you find the real root cause? The most common mistake is stopping at the symptom. "Fridge too warm" is a symptom. The root cause is why it was warm. A simple way to get there is to ask "why" a few times in a row. The fridge was warm — why? The door was open — why? The seal was perished — why? It had not been checked in the maintenance schedule. Now you have something you can actually fix so it does not happen again. Recording the root cause matters because it turns a one-off patch into a lasting improvement. If every temperature failure just gets "adjusted", the same problem returns. A digital corrective action workflow that prompts for root cause every time makes this discipline automatic rather than optional. Common root causes for temperature failures Symptom Likely root cause Lasting fix Cool room slowly warming Perished door seal or door left ajar Seal check in maintenance schedule; close-down door check Fridge warm after delivery Overloaded with warm stock at once Stagger loading; pre-chill before packing tight Bain-marie below 60C Turned on too late before service Preheat time added to opening checklist Freezer creeping up Iced-up evaporator or failing compressor Scheduled defrost; service call logged Making the product decision defensible The hardest part of a temperature corrective action is often deciding what to do with the food. This is where the 2-hour and 4-hour rule guides you for ready-to-eat potentially hazardous food that has been in the danger zone between 5C and 60C. Under two hours total, the food can be refrigerated and used. Between two and four hours, it should be used immediately and not returned to the fridge. Beyond four hours, it must be discarded. The trap with overnight failures is that you rarely know exactly when the temperature crossed 5C. When the timeline is uncertain and the food has clearly been warm for an extended period, the safe and defensible choice is to discard and record it. Linking your temperature monitoring records to the corrective action makes the timeline much easier to reconstruct honestly. Who should own the corrective action? Every corrective action needs a named owner, usually the Food Safety Supervisor or the person on shift who found the problem. Ownership does two things: it makes sure the follow-up actually happens, and it shows an EHO that decisions are made by someone accountable, not left to chance. If the fix needs a tradesperson or a manager sign-off, note who is chasing it and by when. Spreading this responsibility across a trained team is far more reliable than leaving it to one person. Good staff training and induction means anyone who opens or closes can write a proper corrective action, not just the owner. You can find more structured guidance in the FoodSafety HQ food safety guides . Frequently asked questions What should a temperature corrective action always include? It should always include the reading and target, the root cause, the immediate action, the product decision with reasoning, the named owner, and the verification that confirmed the fix worked. Missing any of these weakens the record. Do I have to throw out food every time a fridge is too warm? Not always. Apply the 2-hour and 4-hour rule based on how long the potentially hazardous food was between 5C and 60C. If the timeline is short and clear you may be able to use it; if it is uncertain or long, discard and record the decision. How long should I keep corrective action records? Keep them for as long as your council or state authority requires, and at minimum long enough to show recent history at an inspection. Digital records make this effortless and prevent lost paper notes. Who is responsible for writing the corrective action? The person who identifies the failure or the Food Safety Supervisor usually owns it, but any trained staff member should be able to complete one. Clear ownership ensures the follow-up is actually done. FoodSafety HQ turns each temperature failure into a guided corrective-action workflow that prompts for root cause, product decision, owner and verification, so nothing is missed. Explore the corrective actions feature or start a free trial on our pricing page to build records that stand up to any inspection.