FoodSafety HQ logo
Home Features Free Tools Food Safety Australia Food Safety Glossary Blog Pricing About Contact

How Corrective Actions Work

How corrective actions work in FoodSafety HQ: a failed check auto-raises one, you record what made food safe and who did it, and resolving it closes the loop.

A corrective action is the record of what you did to make food safe again after something went wrong. In FoodSafety HQ a failed check automatically raises a corrective action and prompts the staff member to record the action taken — then resolving it closes the loop and gives you proof you identified and managed the issue. This matters because the FSANZ Food Standards Code, including Standard 3.2.2A, expects food businesses not just to monitor controls but to act when a control fails and keep evidence of it, and corrective actions capture exactly that. Watch the walkthrough . Watch it done: resolving a corrective action raised by a failed check. A failed check raises a corrective action that stays open until resolved. What it does Corrective actions turn a failed check into a tracked task with a clear, timestamped outcome. Whenever one of the four Daily Checks fails on the mobile app — a Temperature, Cleaning, Delivery or Allergen check — FoodSafety HQ raises a corrective action automatically and prompts the staff member to record what they did there and then. The original problem is captured straight from the failed check, so nobody has to retype it: the app already knows a fridge read 8°C against a 0–5°C target, or that a delivery arrived above the 5°C chilled limit. Each action stays open until its resolution is recorded, and the dashboard shows the open count so nothing lingers unseen. A resolved action reads as a complete story — what was wrong, the action taken to make food safe, and who resolved it and when — stored with your compliance history and exportable in council-ready PDF or CSV audit reports. Because the app is an installable PWA that works offline and syncs when back online, an action raised on the floor during a busy service is captured even without signal and uploaded once you reconnect. Step by step A staff member completes a Daily Check on the mobile app and a reading or task falls outside its rule — for example a Temperature check using Check Items → Temperature → Fridge (0–5°C) returns 8°C, which fails. FoodSafety HQ raises a corrective action automatically and captures what was wrong from the failed check. The app prompts for the action taken to make food safe again — moved stock to a working unit, discarded affected food, called for repair, re-cleaned a surface, or rejected a non-compliant delivery. Record who resolved it and when so the record names a responsible person and a time. Mark the action resolved to close the loop. It leaves the open count on the dashboard and becomes part of your permanent, audit-ready compliance record. For an issue you spot outside a scheduled check, raise a corrective action manually and record it the same way. Use cases Sydney cafe, fridge drift: a morning Temperature check on the under-counter fridge reads 8°C against the 0–5°C target and fails. The corrective action prompts the barista to move milk and prepared items to a working unit and log a repair call, all before the first orders go out. Regional pub, cleaning gap: a closing Cleaning check can’t be completed because the sanitiser has run out. The failed check raises an action, and the closer records re-cleaning the surface once fresh stock arrives the next morning, with their name and time. Caterer, rejected delivery: a Delivery check finds chilled seafood arriving above the 5°C limit. The staff member rejects the non-compliant stock, and the corrective action documents the rejection and the supplier follow-up, leaving a clean trail for traceability. What a strong corrective action records Three things make an action defensible at audit. First, what was wrong — captured automatically from the failed check, including the actual reading and the threshold it breached, so there is no ambiguity about the hazard. Second, the action taken to make food safe — a specific, concrete step such as “moved all chilled stock to the back-of-house fridge, discarded two trays of prepared sandwiches, logged a repair call” rather than a vague “fixed it”. Third, who resolved it and when , so responsibility and timing are on the record. An inspector is looking for proof you managed the risk, not merely noticed it; a resolved action that names the problem, the remedy and the person is the evidence that your monitoring actually drives action. How failed checks trigger an action Corrective actions sit downstream of your Temperature, Cleaning, Delivery and Allergen checks, so the thresholds you set on each check item decide what counts as a failure. A reading at or above a “≥” limit passes and one below it fails — so Hot holding (≥ 60°C) or Cooking / reheating (≥ 75°C) raise an action only when the reading drops under the limit. A reading at or below a “≤” limit passes — so Cold holding / display (≤ 5°C) or Freezer (≤ -18°C) raise an action when the reading climbs above it. Cooling records apply the two-stage FSANZ rule — 60°C to 21°C within two hours, then 21°C to 5°C within a further four hours — and fail automatically on the timing, raising a corrective action if either stage is missed. Getting your presets right means actions fire for genuine breaches and not for noise. Common mistakes Leaving actions open. An unresolved action sits on the dashboard count indefinitely. Clear it promptly by recording the resolution — an open action with no outcome reads, to an auditor, like a problem you never dealt with. Vague resolutions. “Sorted” or “OK now” proves nothing. Write the specific step you took to make food safe, and the fate of any affected food. Not recording who and when. An action without a named resolver and a time is weak evidence. Always capture both. Treating repair as resolution. Calling a technician is part of the action, but the food safety fix (moving or discarding stock) is what makes the food safe now — record both. Forgetting ad-hoc issues. Not every problem comes from a scheduled check. If you spot thawing stock left out or a pest sighting, raise a corrective action manually so it joins the same closed-loop record. Related guides, tools & features Guide pillar: Records & audits — how monitoring and corrective-action records fit a documented food safety system. Free tool: Corrective action form — a printable template to capture problem, action and sign-off. Feature: Corrective actions — how auto-raised actions and the open count work across your venues. Related help: Recording temperature checks — set the presets that decide when an action is raised. Frequently asked questions Do I have to create corrective actions manually? No. A failed Temperature, Cleaning, Delivery or Allergen check raises one automatically and the app prompts for the action taken. You can also add one manually for an issue you spot outside a scheduled check. What information is captured automatically? What was wrong is captured from the failed check — including the reading and the threshold it breached. You then add the action taken to make food safe and record who resolved it and when. Why does the dashboard show “open” corrective actions? An action stays open until its resolution is recorded. The dashboard count keeps unresolved issues visible so they get closed out rather than forgotten. Are corrective actions part of my audit record? Yes. They are stored with your compliance history and can be exported in council-ready PDF or CSV audit reports, demonstrating a closed-loop food safety system to councils and auditors. What counts as a check failure that raises one? Any reading or task outside its rule — a fridge above its 0–5°C range, hot holding under 60°C, a cooling stage that misses its time limit, or a delivery outside its receipt temperature. A reading at or above a ≥ limit passes; at or below a ≤ limit passes; outside fails. Does this satisfy my obligations under the Food Standards Code? Corrective actions give you the records and evidence of action that a food safety system expects under the FSANZ Code, including Standard 3.2.2A. Exactly which obligations apply depends on your business’s activities and classification — confirm with your state or territory regulator or council.

FoodSafety HQ is food safety compliance software for Australian hospitality: temperature monitoring, cleaning records, PEAL allergen management, waste and expiry, and council-ready audits, aligned with the FSANZ Food Standards Code.

About Us Contact Features Pricing Food Safety Compliance Software Food Traceability Software SQF Certification BRCGS Certification Best Food Safety Software (AU) Food Safety Software for Restaurants Food Safety Software for Cafés Food Safety Software for Multi-Site Food Safety Compliance Checklist Food Safety Questions Food Safety Guides Free Record Templates Free Tools Blog Editorial Guidelines Privacy Policy Terms of Service Security Sitemap
Sydney, NSW, Australia

© 2026 Toradigm Pty Ltd, Trading as Food Safety HQ · ABN 70 679 136 577. All rights reserved.

Back to top