Walk-In Cooler Temperature Log: What to Record and Why
Where to measure, what to write down, a copy-ready log template, and how to read the trends before a walk-in fails.
Quick answer
Read a calibrated thermometer in the warmest part of the walk-in at set times each day, and record the time, air temperature, a product temperature, the controller reading and your initials. The FDA Food Code limit for cold holding is 41°F or below. A written log turns a failure into a documented decision instead of a guess, and its trends often warn of trouble days ahead.
A temperature log is the cheapest early-warning system a walk-in has. It also decides what happens to your food after a failure: with written, timed readings you have options, and without them the safe answer is usually to throw product out.
Why the log matters more than it looks
The FDA Food Code, the model most states adopt in some edition, requires cold-held TCS (time/temperature control for safety) food to stay at 41°F or below. The current edition is Food Code 2026, released 17 September 2026. It is a model code, so your state or local health department's adopted version is what actually applies to you.
The log earns its keep in three ways:
- Food safety decisions. The Conference for Food Protection emergency plan referenced in the Food Code lets an operation with a written plan keep refrigerated TCS food for a limited time based on the highest temperature it reached. That only works if someone was measuring. If time and temperature were not monitored and food may have gone above 41°F, the guidance is to discard it. The full rules are on food safety when a walk-in fails.
- Early warning. Most walk-in failures are gradual. A dirty condenser, a failing fan motor or a slow refrigerant leak shows up as a box that drifts a degree or two warmer each day before it quits.
- Records for inspectors, insurers and technicians. A technician diagnosing a problem wants to know when the temperature started climbing. An insurer paying for lost product wants proof of what happened.
Where to measure
The Food Code says the thermometer in a refrigerated unit must measure the air (or a simulated product) in the warmest part of the unit. Cold-holding equipment for TCS food must have at least one built-in or permanently mounted thermometer whose display is easy to read.
In most walk-ins the warmest spot is near the door, high on the shelving on the door side, or wherever product sits farthest from the evaporator (the fan-coil unit on the ceiling or wall). It is not the air right in front of the evaporator, where the controller probe often lives.
Accuracy rules from the Food Code:
| Thermometer | Required accuracy (°F scale) | Use it for |
|---|---|---|
| Ambient air thermometer | ±3°F | The mounted box thermometer |
| Food (probe) thermometer | ±2°F | Product temperatures |
| Thin-probe food thermometer | ±2°F | Thin foods like patties or fillets |
Check thermometers against ice water on a regular schedule and replace any that read off. A log full of numbers from a thermometer that reads 4°F low is worse than no log, because it gives false confidence.
Tip: Record a product temperature, not only air. Air temperature jumps every time the door opens or the unit defrosts. A probe in a container of product, or a buffered "simulated product" probe, shows what the food is actually doing.
What to record
Each entry should capture enough to rebuild what happened later:
- Date and time. Actual clock time, not "AM" or "PM."
- Air temperature from the mounted thermometer in the warmest part of the box.
- Product temperature from a probe thermometer in a representative item, ideally the same item location each time.
- Controller display reading (setpoint and displayed box temperature). A widening gap between the controller and your thermometer is a clue for the technician.
- Status notes. Defrost indicator on, delivery just loaded, door propped for stocking, any alarm on the display.
- Corrective action if the reading was out of range, and the recheck time and result.
- Initials of the person who took the reading.
A log template you can copy
| Date / time | Air °F / product °F | Controller shows | Notes, action, initials |
|---|---|---|---|
| 9/24 6:00 am | 36 / 37 | Set 35, reads 35 | Normal. JR |
| 9/24 2:00 pm | 39 / 38 | Set 35, reads 37 | Delivery loaded 1:30. Recheck 3 pm: 37/38. JR |
| 9/24 10:00 pm | 36 / 37 | Set 35, reads 35 | Normal. MK |
The example numbers are illustrations, not targets. Heatcraft ships its air-defrost cooler controllers with a 35°F default setpoint and its electric-defrost freezer controllers at −10°F, but your setpoint depends on the product and the manufacturer's instructions. The number that matters for compliance is the 41°F limit for TCS food in a cooler. For freezers, the Food Code only requires that frozen food stay frozen; it does not set a specific freezer temperature.
For a freezer, keep the same columns and add a note whenever product feels soft at the surface, since that matters for refreeze decisions.
How often to log
The Food Code does not set a single logging frequency for every establishment. Your HACCP plan, your health department or your company policy does. A common minimum is a reading at opening and at closing, with more readings after deliveries or during hot weather.
Manual logs leave long overnight gaps, and overnight is exactly when an unnoticed failure costs the most. A continuous electronic logger with alerts closes that gap. The Food Code 2026 even ties one of its new cooling methods to refrigeration with "an electronic system that continuously monitors time and ambient air temperature." See walk-in temperature monitoring for how those systems work.
Reading the trends
A log is only useful if someone looks back through it. Once a week, scan the last seven days for these patterns:
| Pattern in the log | What it often points to | Where to read more |
|---|---|---|
| Box creeps up 1–2°F over several days and never recovers | Dirty condenser, failing fan, slow leak, iced coil | Not cooling |
| Warm readings only in the afternoon or on hot days | Condensing unit struggling with heat | Summer heat |
| Brief spikes at the same times each day that recover on their own | Normal defrost cycles | Temperature fluctuating |
| Spikes get longer or larger each time | Defrost or drain trouble, coil starting to ice | Frozen evaporator coil |
| Controller and thermometer disagree more each week | Probe drifting or badly placed | Thermostat and controller |
| Readings below the setpoint, product freezing | Control or solenoid problem | Too cold |
Defrost spikes are normal. Heatcraft's Beacon II controller, for example, defaults to two air defrosts a day on coolers and four electric defrosts on freezers. Air temperature rises during those cycles and product temperature should barely move. What is not normal is a spike that keeps getting bigger or a box that takes longer each time to pull back down.
When a reading is out of range
- Recheck with a second, calibrated probe thermometer in the warmest part of the box.
- Look for the easy causes: a door left ajar, a fresh delivery, the unit in defrost.
- Write down the time you found it and every recheck after that.
- If the product is above 41°F or climbing, start the steps on what to do when the walk-in stops working and call a licensed commercial refrigeration technician.
Food safety: Never back-fill or "fix" a log entry after the fact. The value of the log is that it is honest. Your local health authority, not the log, makes the final call on product that went out of range.
Keep the log with your other records
Store temperature logs alongside service invoices and alarm history. When a technician visits, show them the log; it often shortens the diagnosis. The preventive maintenance schedule lists the other records worth keeping, and the site's general walk-in cooler maintenance guide covers the daily routine around it.
Frequently asked questions
How often should we log walk-in temperatures?
Is the controller display good enough for the log?
How long should we keep temperature logs?
Does a temperature spike during defrost count as a violation?
Related guides
- Temperature monitoringHow a walk-in temperature monitoring system catches failures early: sensor placement, alarm delays, alert chains, power-loss alerts and records.RoutineStaff can check
- Temp fluctuatingHow to tell normal walk-in temperature swings (cycling, defrost, deliveries) from swings that signal a failing part, and what to check first.Fix soonStaff checks + technician
- Food safetyThe 41°F rule, the time and temperature limits for keep-or-discard decisions, and what to record when a walk-in fails.Act nowStaff can check
- Thermostat & controllerMechanical thermostats versus electronic controllers in walk-ins, how to check if the reading is right, and how control failures show up.Fix todayStaff checks + technician
- Temperature alarmA step-by-step response to a high or low temperature alarm: confirm it, rule out defrost and door openings, read the code, protect product and call.Fix todayStaff checks + technician
- PM scheduleA component-by-component maintenance schedule showing who does each task, how often, and which failure it prevents.RoutineStaff checks + technician
About this guide
Written by a walk-in design and installation company, for the people who run them
JayComp Development has designed and built walk-in coolers, beer caves and refrigerated stores since 1996. This guide explains what goes wrong with a walk-in, what staff can safely check, and what to expect from a technician.
We don't run repair service calls. If your walk-in has failed, call a licensed commercial refrigeration technician. When repairs stop making sense, we design and install replacement walk-ins, refrigeration systems, panels and glass doors.
