What is a food cooling log?

A food cooling log is a record that documents the temperature of cooked food at set time intervals as it cools, proving the food moved through the bacterial danger zone (135 F to 41 F) within the time limits set by the FDA Food Code. The cooling log is the proof that a hot batch got cold fast enough, checked at the right moments, with a timestamp attached to every reading.

A cooling log is not a hot-hold log and it is not a walk-in log. Those records capture a steady-state condition. A hot-hold log asks "is this food holding at or above 135 F right now." A walk-in log asks "is the cooler holding at or below 41 F right now." A cooling temperature log is different. It captures a transition over time. A single value tells you nothing on its own. You need the start time, the start temp, the 2-hour checkpoint, and the completion time and temp.

The danger zone is the temperature band where bacteria multiply fastest, roughly 70 F to 125 F. The whole point of cooling fast is to cut the time food spends there. These are TCS foods, time and temperature control for safety foods. Cooked rice, beans, soups, sauces, stocks, chili, gravy, large protein roasts, and cooked pasta all need a cooling log.

A complete cooling log captures four data points:

• The food item name
• The time cooling began
• The temperature at the 2-hour mark
• The time and temperature when cooling was complete

It also records the corrective action and time if a stage failed. Here is why a single reading fails an inspection. An inspector who reads "soup, 68 F" with no timestamp cannot tell whether that soup is safely chilling at hour 5 or dangerously stalled at hour 3. The clock is the evidence. For the steady-state contrast, see the walk-in cooler temperature log and the food holding temperature records, which track an ongoing hold rather than a countdown.

Regulatory framework

Two-stage cooling is required under FDA Food Code 3-501.14. Cooked TCS food must cool from 135 F to 70 F within 2 hours, then from 70 F to 41 F or below within 4 additional hours, for a maximum total cooling time of 6 hours. The current baseline is the 2022 FDA Food Code, section 3-501.14(A).

The clock-start rule trips up a lot of operators. The 6-hour window starts the moment the food drops below 135 F at the cooking or holding stage. It does not start when the pot goes into the cooler or the ice bath. By the time a line cook decides to chill a stockpot, part of the clock may already be gone. The two-stage cooling analysis from LegalClarity spells out the rule the same way.

There is an alternate provision, 3-501.14(B). Food prepared from ingredients already at room temperature, like a cold deli salad or a reconstituted product that never reached 135 F, gets a single 4-hour window to reach 41 F or below from the time of preparation. This food never hit 135 F, so the two-stage process does not apply. Do not mis-apply the two-stage rule to cold-prep items.

For record retention, templates and many local codes ask operators to keep cooling records for at least 90 days. Local health-department requirements can run longer, so check your jurisdiction. State agencies often restate the federal rule for their inspectors. The Georgia Department of Agriculture cooling-food guidance is one example of a state-level articulation.

| Stage | Temperature range | Time limit | Why it matters |
|---|---|---|---|
| Stage 1 | 135 F to 70 F | Within 2 hours | This is the fastest-bacteria-growth band. The 2-hour cap is the strictest part of the clock. |
| Stage 2 | 70 F to 41 F or below | Within 4 more hours | Slower growth band, but the food still has to land at 41 F by the 6-hour total mark. |
| Total | 135 F to 41 F | 6 hours maximum | Clock starts when food drops below 135 F at cooking or holding, not when it enters the cooler. |

The rule is widely misunderstood at the store level. A manager survey reported in the NIH study on restaurant food cooling practices found that 36.2% of restaurant managers did not know their jurisdiction's cooling regulation. Only 20.2% correctly matched the FDA two-stage rule. The same body of research found 79% of full-service restaurants failed to cool fast enough in a prior FDA study, and 86% of managers ran a cooling process that lacked all the FDA-recommended components. That gap is the reason a documented, scheduled cooling log matters. For the broader picture, see the food safety regulatory frameworks overview covering FDA Food Code, FSMA, and HACCP.

The two-stage cooling clock: 135 F to 70 F to 41 F

The two-stage cooling clock runs in two legs. Stage 1 takes food from 135 F to 70 F in no more than 2 hours. Stage 2 takes it from 70 F to 41 F or below in no more than 4 hours. Because Stage 1 can use up to 2 hours, the total window can never exceed 6 hours.

The 2-hour mark is the make-or-break checkpoint. StateFoodSafety guidance is explicit on this point. Check at the 2-hour mark so you have time to take corrective action before the food has been in the danger zone too long. This is why interval logging matters. A cooling log is the one record where checking every hour, or every 30 minutes, during the cool-down genuinely changes the safety outcome. It tells you at hour 1 whether you are on pace to make the 2-hour gate.

Cooling is a textbook critical control point. HACCP stands for Hazard Analysis and Critical Control Points. The FDA HACCP principles and application guidelines map cleanly onto cooling. Principle 3 sets the critical limits, the 135, 70, and 41 marks and the 2-hour, 4-hour, and 6-hour windows. Principle 4 establishes the monitoring procedure, the interval checks. Principle 5 establishes the corrective action when a stage fails. A cooling log is HACCP Principle 4 monitoring written down. For the format and frequency of the wider record set, see the HACCP temperature logs guide.

How does Xenia handle food cooling logs?

Xenia turns the cooling clock into a scheduled task. Picture the line cook who is supposed to walk back to the stockpot at the 2-hour mark during a Friday dinner rush. On paper, that check depends on memory, and memory loses to a full rail of tickets. Timed prompts fire the 2-hour and 6-hour checks on the shift clock instead. Bluetooth thermometers log the interval temps. An out-of-range reading triggers a follow-up question, a required photo, and a corrective task, before the inspector ever arrives.

Here is how the pieces fit together:

• Timed-prompt task scheduling. The cooling log is a timed sequence, not a once-a-shift checklist item. Xenia schedules the start-of-cool entry, the 2-hour gate check, and the completion check on the shift clock. The line does not have to remember mid-rush.
• Bluetooth thermometer integration. Paired probes log the cooling temps at logged intervals, every 15 minutes in the Dave's Hot Chicken setup. The reading drops into the cooling record automatically. No clipboard transcription, which also removes the "copy yesterday's numbers" temptation. Pair Bluetooth thermometers with Xenia to auto-log temps and auto-alert when a reading is out of range, the top driver in Dave's 321-location rollout. See the full Bluetooth thermometer setup walkthrough for pairing and audit-ready trails.
• Follow-up questions with required photo capture. If the 2-hour check reads above 70 F, the form auto-presents the prompt: "Stage 1 missed. What did you find and what corrective action did you take? Photo required." Temperature out of range automatically asks what corrective action the cook took and requires a photo. Evidence is captured at the moment of failure, not reconstructed from memory later.
• End-to-end corrective action workflow. A failed stage auto-creates a corrective task, the reheat-and-recool or discard decision, assigns it, sets a deadline, and escalates to the DM if it is not resolved. Audit failure leads to an automatic corrective task tracked to closure. Most platforms collect audit data. Few drive it to closure. The audit trail and the closure trail are the same record. For the full reheat-or-discard logic, see food safety corrective action.
• Dashboards on issues. The ops director sees which locations are missing the 2-hour cooling check, not just a completion percentage. The view shows where the next failure is forming, not just whether yesterday's tasks got done.

| Approach | Paper clipboard log | Xenia with Bluetooth and timed prompts |
|---|---|---|
| Interval reading | Cook walks back manually, often skipped during a rush | Probe logs temps automatically at logged intervals |
| 2-hour gate check | Relies on memory mid-shift | Timed prompt fires on the shift clock |
| Failed-stage evidence | Reconstructed later, if at all | Follow-up question plus required photo at the moment of failure |
| Corrective action | Handwritten note, easily lost | Auto-created task with assignee, deadline, and DM escalation |
| Inspector readiness | Timestamps the cook wrote from memory | Time-stamped trail tied to probe readings |

Two honest limits. The probe logs at intervals, not as a continuous real-time stream. And Xenia supports HACCP-aligned cooling monitoring, it is not a HACCP certification. The audit trail is ready for the inspector, but submission stays operator-driven. For the cross-cluster view of how critical-item thresholds drive these scores, see weighted audit scoring with critical-item thresholds.

Where do operators see results?

The cooling log stops being a clipboard nobody verifies and becomes a process the DM can see across every location. Dave's Hot Chicken runs Bluetooth thermometers across 321 locations, so cooling and line-check temps log automatically and the audit trail is ready before the health inspector arrives. Dave's migrated from RizePoint, and the drivers were weighted scoring, Bluetooth integration, and corrective action workflows.

The same temperature-capture pattern shows up at QSR scale and in the c-store world:

• Cook Out runs the process across 335 locations, pairing a weekly price-change rollout with line-check temperature capture.
• H&S Energy runs continuous Bluetooth and LoRaWAN sensors across 360-plus stores for cooler and hot-hold temperature monitoring, the c-store secondary vertical. For the broader c-store picture, see the convenience store operations software hub.

The problem digital logging solves is pencil-whipping. Paper cooling logs get falsified because the cook is supposed to walk back to the soup at the 2-hour mark during a dinner rush and rarely does. The pencil-whipping problem is well documented, and automatic probe capture removes the transcription step and the temptation to copy yesterday's numbers. It also closes the time-temperature abuse gap that improper cooling creates.

The inspection-day payoff is documentation. Improperly cooled food gets flagged for immediate corrective action and recorded on the inspection report. A complete, time-stamped cooling log with corrective-action entries is the operator's defense. That is the gap a scheduled, probe-fed log fills, the same gap the NIH research on restaurant cooling practices traced back to 504 outbreaks tied to improper cooling between 1998 and 2008. For the wider food-safety program, start at the food safety operations hub or the restaurant operations platform.

How to set up a food cooling log in Xenia

Setting up a cooling log in Xenia takes three building blocks: a cooling template with the two-stage fields, timed prompts that fire the 2-hour and completion checks, and a corrective-action rule that triggers when a stage runs out of range. Here are the steps:

1. Build the cooling template. Add the four required fields: food item, time cooling began, temperature at the 2-hour mark, and completion time and temperature. Or upload your existing paper cooling log to the AI Template Agent, which converts a SOP PDF into a digital form in minutes.
2. Set the timed prompts. Schedule the 2-hour gate check and the 6-hour completion check to fire on the shift clock from the moment the cool-down starts. The line does not have to remember mid-rush.
3. Pair the Bluetooth thermometer. Connect the probe so interval temps log automatically into the cooling record, every 15 minutes in the Dave's Hot Chicken setup. The Bluetooth thermometer setup guide walks through pairing.
4. Add the corrective-action trigger. Configure the follow-up. If the 2-hour reading is above 70 F, require a description plus a photo and auto-create a corrective task, reheat-to-165-F-and-recool or discard, with an assignee and a deadline.
5. Set escalation. Route an unresolved corrective task to the DM at the deadline so a stalled batch never sits silent.
6. Review on the dashboard. Watch the issues view: which locations are missing the 2-hour check, which cooling tasks are open, across all units.

The AI Template Agent converts an existing SOP or PDF into a digital form. It does not generate an audit from a vague brief, so keep your source document handy. Once the template is live, the same temperature-monitoring backbone covers your other records. See the temperature monitoring software overview for the wider picture.