Temperature Monitoring: Manual Checks vs Data Loggers

Temperature monitoring means routinely checking that cold food stays at or below 5C, hot food stays at or above 60C, and cooking hits a safe core temperature. You can do this with manual probe checks recorded on a log, or with digital data loggers that measure continuously and alarm on breaches. Both are acceptable under the Food Standards Code. The right choice depends on your risk, staff time, and how you keep records. Key takeaways: Cold food should be kept at or below 5C and hot food at or above 60C; cooking generally targets a core of 75C.. Manual probe checks and continuous data loggers are both acceptable ways to monitor and evidence temperature control.. A calibrated probe accurate to about plus or minus 1C is essential for verifying any storage or cooking temperature.. Records must be legible, dated, and kept long enough to satisfy your auditor, EHO, or customer specification.. Data loggers cut manual workload and catch overnight breaches, but you still need probes for spot checks and cooking.. Manual checks vs data loggers at a glance: Factor, Manual probe checks, Digital data loggers. Coverage — Only at the moment of the check — Continuous, including overnight and weekends. Upfront cost — Low — Higher (devices plus any subscription). Labour — Ongoing staff time each check — Minimal once installed. Breach detection — Relies on staff being present — Automatic alarms enable early action. Best for — Cooking, cooling, reheating, deliveries — Fridges, freezers, coolrooms, hot-holding. Records — Handwritten log, prone to gaps — Exportable digital reports. What temperature monitoring actually requires Under the Australia New Zealand Food Standards Code, food businesses handling potentially hazardous food must keep it under temperature control and be able to demonstrate that they are doing so. The Code sets the outcome (safe temperatures) rather than dictating one method. In practice that means keeping cold potentially hazardous food at or below 5C, keeping hot food at or above 60C, and cooking to a safe core temperature (commonly 75C for many foods). Monitoring is how you prove the outcome is being met, and record-keeping is how you evidence it after the fact. Cold storage and display: 5C or below. Hot holding and display: 60C or above. Cooking core target: commonly 75C (confirm for specific foods and methods). The Code requires the safe outcome; you choose a monitoring method that reliably achieves it. Manual checks: probes and written logs Manual monitoring means a staff member physically measures temperatures with a probe thermometer or reads a fridge/freezer display, then records the result on a log. It is low-cost, flexible, and easy to train. A probe thermometer accurate to about plus or minus 1C is the backbone of manual monitoring: it verifies deliveries, checks the core of cooked and reheated food, and confirms that fridge air-temperature displays reflect reality. Manual checks work well for smaller operations, but they only capture the moment of the check and depend entirely on staff remembering to do them. Use a clean, sanitised probe and insert into the thickest part or core. Allow the reading to stabilise before recording. Record the actual number, not just a tick, plus time, date, and initials. Do not rely on fridge dial settings alone; verify with a probe or an internal thermometer. Digital data loggers: continuous, automatic monitoring A data logger is an electronic device that records temperature automatically at set intervals, storing readings and often transmitting them to an app or cloud dashboard. Fixed loggers sit in fridges, freezers, coolrooms, and hot-holding units and run 24/7, so they capture breaches that happen overnight, on weekends, or during a power outage when nobody is present. Many support configurable alarms that notify staff by light, sound, SMS, email, or push notification when a temperature drifts out of range, allowing action before food is lost. Records continuously, including outside trading hours. Reduces manual logging workload and human error. Alarms enable early intervention before stock is compromised. Produces a tamper-resistant digital record that is easy to export for audits. How often should you check? There is no single legally mandated frequency in the Code; frequency should match your risk and be documented in your food safety program or procedures. A common, defensible practice is to check refrigeration and hot-holding at least at the start and end of each trading day, plus at key control points such as deliveries, cooking, cooling, and reheating. Higher-risk or high-volume sites often check more frequently. Data loggers effectively make storage monitoring continuous, but manual verification of cooking, cooling, reheating, and deliveries is still needed because those happen to the food itself, not the appliance. Deliveries: check cold and frozen goods on arrival. Cold and hot storage/display: at least start and end of day (more if higher risk). Cooking and reheating: probe the core each time. Cooling: verify the food moves through the danger zone quickly enough. Alarms and acting on a breach An alarm is only useful if someone responds to it. Set alarm thresholds sensibly (for example, an alert as a fridge approaches 5C rather than only after it fails), decide who is responsible for responding, and document the corrective actions. Not every excursion means food must be discarded; short, minor fluctuations during restocking or defrost cycles can be acceptable if the food's own temperature stays safe. The 2-hour/4-hour rule is a useful tool for deciding whether cold food that has been in the 5C to 60C danger zone can be used, refrigerated, or must be thrown out. Set thresholds with a safety margin, not right at the limit. Name who responds to alarms and how they escalate. Verify the food's temperature, not just the appliance reading, before deciding. Record what happened and the corrective action taken. Calibration keeps every method honest Whether you use probes, loggers, or both, the readings are only trustworthy if the equipment is accurate. Probe thermometers should be checked regularly, typically against an ice slurry (around 0C) and boiling water (around 100C at sea level, lower at altitude), and adjusted or replaced if they drift beyond about plus or minus 1C. Fixed data loggers should be verified or professionally recalibrated on a schedule recommended by the manufacturer. Keep a calibration log; auditors frequently ask to see it, because an uncalibrated device makes every recorded temperature meaningless. Ice slurry check should read close to 0C. Boiling water check should read close to 100C at sea level. Acceptable accuracy is about plus or minus 1C. Log calibration checks and keep manufacturer verification records for loggers. Record-keeping that satisfies an auditor Records are your proof of a working system. Good temperature records are legible, show the actual reading, and include the date, time, unit or food checked, and who recorded it. They should also capture out-of-range readings and the corrective action taken; a log with no breaches ever recorded can look less credible than one showing occasional issues that were fixed. Data loggers make this easier by generating exportable reports automatically. How long you must retain records varies, so confirm the required retention period with your state or territory regulator, local council, or customer specification. Include reading, date, time, unit/food, and initials. Record breaches and the corrective action, not just passes. Keep records readily retrievable for audits and EHO visits. Confirm retention periods with your regulator, council, or customer. Checklist: Probe thermometer available, clean, and calibrated to about plus or minus 1C. Every fridge, freezer, and hot-holding unit is monitored. Check frequencies documented and matched to risk. Logger alarms set with a safety margin and an assigned responder. Deliveries, cooking, cooling, and reheating probed and recorded. Calibration log maintained. Temperature records legible, dated, initialled, and retained. Corrective actions recorded for any out-of-range reading. Common mistakes: Trusting the fridge dial or display instead of verifying with a calibrated probe. Ticking a box instead of recording the actual temperature reading. Never calibrating probes or loggers, making every reading unreliable. Setting alarm thresholds right at the limit, leaving no time to react. Only monitoring appliances and forgetting cooking, cooling, and reheating of the food itself. Logging only passes and never recording breaches or corrective actions.