What Should a Food Cooling Log Record?

A food cooling log should identify the food and batch, show the time and temperature when cooling began, record checks during cooling, confirm the final temperature and capture any corrective action. The record should make it easy to see whether cooked time/temperature control for safety food — often called TCS food — cooled quickly enough under the food code that applies to the establishment.

Where TapTick fits: TapTick can help teams schedule cooling checks, record readings and corrective actions, and keep evidence visible across sites. It does not decide whether food is safe or replace the applicable food code, an approved process or the regulatory authority's direction.

1. What a cooling log should record

There is no single federal cooling-log form that every retail food establishment must use. The legal requirement comes from the food code adopted by the relevant regulatory authority, and local requirements can differ. A practical record should nevertheless answer the same basic question: did this batch move through the temperature danger zone within the required time, and what happened if it did not?

For each cooling batch, record:

• food and batch identity — for example, chili cooked for the evening service, with a batch, pan or preparation reference;
• site and location — including the kitchen, prep area or refrigeration unit where useful;
• quantity and container — such as two shallow pans, because volume and food depth affect cooling;
• cooling start — the time and internal food temperature at the start of the controlled cooling period;
• cooling method — shallow pans, smaller portions, an ice-water bath, rapid-cooling equipment or another approved method;
• checkpoint readings — actual times and internal food temperatures, not a tick that says only “checked”;
• final result — the time the food reached the required final temperature;
• corrective action — what was done, when and by whom if cooling was slow or a limit was missed; and
• responsibility and verification — the employee taking the readings and, where the procedure requires it, the manager who reviewed the result.

Use a clean, sanitized and suitable food thermometer to measure the food itself. A walk-in or reach-in air-temperature display cannot show how quickly the center of a deep pan is cooling. Follow the establishment's thermometer accuracy, calibration, cleaning and sanitizing procedure.

2. When temperatures should be checked

The 2026 model Food Code keeps the familiar two-stage limit for cooked TCS food:

• cool from 135°F to 70°F within two hours; and
• cool from 135°F to 41°F or less within a total of six hours.

The six hours starts when the food is at 135°F; it is not six additional hours after the first stage. A useful procedure therefore includes a start reading, an early progress check, a reading by the two-hour point and a final reading by the six-hour point. The exact monitoring frequency should be set by the establishment's process and the applicable authority.

An early checkpoint is important because it leaves time to act. Waiting until two hours have passed to discover that a deep pan is still far above 70°F can remove useful corrective-action options. For a repeatable menu item, the food-safety plan can set an earlier target based on validated experience — for example, a check after one hour — so the employee knows whether to split the batch, reduce its depth or use a faster method while time remains.

Record actual observations rather than completing the log from memory at the end of the shift. A sequence such as “3:10 p.m. — 135°F; 4:05 p.m. — 92°F; 5:00 p.m. — 68°F; 8:35 p.m. — 40°F” shows the cooling path. “Pass” alone does not.

3. Cooling methods in the 2026 model Food Code

Section 3-501.15 of the 2026 model Food Code lists methods based on the type of food, including shallow pans, smaller or thinner portions, rapid-cooling equipment, stirring in an ice-water bath, containers that transfer heat effectively, adding ice as an ingredient and other effective methods.

The 2026 edition adds placing food in containers at a depth of no more than two inches to that list. It also describes a separate alternative that may be used only with regulatory-authority approval: food is filled no more than two inches deep, left uncovered in refrigeration holding at 41°F or below, and the refrigeration system electronically monitors ambient time and temperature continuously. That alternative is not blanket permission to leave every product uncovered or to stop taking food-temperature readings.

For routine cooling, arrange containers for maximum heat transfer through the walls and keep them loosely covered or uncovered when the food is protected from overhead contamination. Do not stack hot, tightly covered, deep containers in a crowded refrigerator and assume the unit's air temperature will compensate.

The method field on the log makes the record more useful. If several batches cooled slowly, the operator can compare food depth, batch size, equipment and container arrangement instead of treating each failure as an isolated temperature problem.

4. What to do when cooling is off track

The procedure should state what employees may do at an early checkpoint and what requires manager or regulatory guidance. Possible early actions include dividing the food into smaller portions, transferring it to shallower pans, using an ice-water bath with stirring, adding ice where the recipe permits or moving the batch to suitable rapid-cooling equipment.

If the food has not reached 70°F within two hours, or has not reached 41°F or less within the total six-hour period, do not invent a new deadline. Follow the establishment's written corrective-action procedure and the code that applies to the site. That may require discarding the food. Reheating and restarting cooling should be done only where the applicable code and an approved procedure allow it; it should never be used to disguise an unknown or missed cooling history.

A complete corrective-action entry should include:

• the time and temperature that triggered the action;
• what happened to the food;
• the immediate step taken to regain control or dispose of the batch;
• who made the decision;
• any manager or regulatory-authority escalation; and
• the preventive follow-up, such as changing pan depth, batch size, staffing or equipment.

Never backfill a missing reading with an estimate. If the time or temperature history is unknown, record the gap and apply the site's procedure for food with an unverified cooling history.

5. How multi-site operators should manage cooling records

Convenience stores, travel centers, quick-service restaurants and food-to-go operators often prepare the same item in different jurisdictions and with different equipment. Use a core cooling procedure, but maintain a site profile that identifies the adopted food code, local amendments, regulatory authority and effective date.

Standardize the fields and escalation route across the estate where possible. Then adapt product instructions to the actual batch size, containers and equipment at each location. A cooling schedule that works with a blast chiller at one site may fail in a crowded reach-in refrigerator elsewhere.

Review the records across sites for patterns:

• foods repeatedly close to the two-hour or six-hour limit;
• missing start readings or late first checks;
• one unit, shift or container type associated with slow cooling;
• the same corrective action being repeated without a permanent fix; and
• changes in local rules that have not reached the site procedure.

This turns a cooling log from a filing exercise into an early-warning control. Repeated exceptions may point to capacity, process design, training or equipment problems that a single batch record cannot resolve.

6. Common cooling-log mistakes

Logging refrigerator air instead of food temperature

The refrigeration unit may be at 38°F while the center of a deep container remains warm. Measure the internal food temperature at a representative location using the establishment's procedure.

Starting the clock at the wrong point

For the model two-stage process, the total time runs from 135°F. Do not start a new six-hour window at 70°F or when the pan is placed in the refrigerator.

Checking only at the deadline

A deadline check can confirm failure but may come too late to correct the process. Use at least one earlier progress check suited to the product and method.

Recording a number without the method

Two identical temperature paths may have different causes. Recording batch size, food depth, container and method helps the operator find the real constraint.

Assuming the newest FDA model is already the local rule

Jurisdictions may adopt a different edition, amend the model or set their own requirements. FDA's state directory is a useful starting point, but the establishment should confirm current requirements with its state or local regulatory authority.

Confusing retail controls with FSMA rules

The FDA Food Code addresses retail food and foodservice establishments. FSMA requirements for covered manufacturing, processing, packing or holding operations are a separate legal framework. A business with both types of operation should determine which rule applies to each activity.

A practical final check

Before using a cooling log across the business, ask:

• Does it capture an identifiable food and batch?
• Does it show the actual start time and food temperature?
• Is there an early checkpoint that leaves time for corrective action?
• Can the record prove the two-hour and total six-hour model limits, where adopted?
• Does it record the cooling method, food depth or container where relevant?
• Are missed or unknown readings treated as exceptions rather than guessed?
• Does every site know which jurisdiction's rule applies?

If the record cannot answer those questions, improve the workflow before adding more signatures. The purpose of a cooling log is to support a safe decision while there is still time to make one.