Restaurant Temperature Log Guide: What to Record, How Often, and What Inspectors Expect

A restaurant temperature log is the written proof that time/temperature control for safety (TCS) food stayed out of the danger zone — in the walk-in overnight, on the line during the rush, through cooking, cooling, and reheating. Health inspectors ask for it because temperature abuse is among the leading contributors to foodborne illness in food service, and because a log that shows a failed reading and what was done about it is the clearest evidence of active managerial control. This guide covers the temperatures the FDA Food Code sets, what to record and how often, sample entries, and how to handle an out-of-range reading.

The temperatures that matter (FDA Food Code)

Every entry in a temperature log is compared to a limit. These are the model limits from the 2022 FDA Food Code (opens in a new tab); your adopted edition may differ slightly (for example, some jurisdictions still enforce the older 15-second hold at 165°F for poultry).

What to log, and how often

The Food Code requires that cold-holding equipment have a thermometer (§4-204.112) and that TCS food be held at the required temperatures, but it does not prescribe a universal logging schedule for routine operations. Frequency is set by your health department’s expectations, your franchisor, your HACCP plan if you have one, and common sense. The table below reflects widespread practice.

Air temperature is not product temperature

The Food Code regulates the temperature of the food. An air thermometer at the door of a walk-in tells you the unit is running; it does not tell you the internal temperature of the tuna salad on the top shelf near the fan. A good refrigeration log pairs the unit reading with a product probe, and a good manager knows the warm spots in each unit.

How to structure the log

A temperature log that will hold up in an inspection or a franchise audit answers five questions for every entry: what was measured, when, what it read, who took it, and — if it failed — what was done. A blank “corrective action” column that is never used is a red flag; a log with occasional failures and documented fixes is what active managerial control actually looks like.

UNIT: Walk-in cooler #1     SET POINT: 36°F     DATE: 09/07
TIME    AIR   PRODUCT (item)         INIT  ACTION
06:05   37°F  38°F  (sliced turkey)   JM    —
10:30   38°F  39°F  (cooked rice)     AR    —
14:15   43°F  42°F  (tuna salad)      AR    FAIL — door found ajar (delivery).
                                            Closed door, rechecked 14:45 = 39°F air /
                                            40°F product. Product held <45 min out of
                                            range; retained. Reported to mgr.  AR/JM
18:00   37°F  38°F  (tuna salad)      TB    —
23:10   36°F  37°F  (marinara)        RC    —

DATE: 09/07     STATION: Grill
TIME   ITEM                 TEMP    STD     INIT  NOTES
11:52  Grilled chicken br.  171°F   165°F   KP    ✓
12:40  Burger patties (6)   157°F   155°F   KP    ✓ 17 s hold
13:05  Burger patties (6)   149°F   155°F   KP    FAIL — returned to grill,
                                                  re-probed 154→158°F at 13:08 ✓

What to do when a reading is out of range

The reading is the easy part; the decision is what inspectors and auditors read most carefully. A written corrective-action procedure removes the guesswork for a line cook at 2 PM or a closing manager at midnight.

Cold-holding failure

1. Confirm with a second, calibrated thermometer; probe the product, not the air.
2. Find the cause: door ajar, overloaded unit, defrost cycle, blocked airflow, compressor failure.
3. Determine how long the product has been above 41°F. If you cannot determine it, treat it as unknown.
4. Product above 41°F for a short, known period can often be rapidly re-chilled and retained; product above 41°F for more than 4 hours, or for an unknown time, should be discarded. Your health department or HACCP plan may set the exact decision points — write them into your procedure.
5. Move product to a working unit, call for service, and recheck on a schedule.
6. Record everything: times, temperatures, disposition, who was notified.

Hot-holding failure

Product below 135°F for less than 4 hours can typically be reheated to 165°F and returned to hot holding once; product below 135°F for more than 4 hours, or for an unknown time, is discarded. Fix the unit (empty wells, low water, thermostat) before reloading.

Cooking failure

Continue cooking and re-probe. Never serve a product that did not reach its required temperature. If undercooked product left the line, treat it as a food-safety incident and follow your recall/notification procedure.

Cooling failure

If product has not reached 70°F at the 2-hour mark, it may be reheated to 165°F and the cooling process restarted once, with a better method (shallower pans, ice paddle, blast chiller). If it fails again, or was not checked and its history is unknown, discard it.

Thermometers and calibration

A log is only as good as the instrument. The Food Code requires food thermometers to be accurate to ±2°F (§4-502.11) and requires that they be provided and readily accessible (§4-302.12). In practice:

• Use thin-tip digital thermocouple or thermistor probes for thin items (patties, chicken breast); dial bimetallic stems need about 2 inches of immersion and are slow.
• Calibrate weekly using the ice-point method (32°F / 0°C in a slurry of crushed ice and water), after any drop, and whenever two thermometers disagree. Our step-by-step calibration guide covers both ice-point and boiling-point methods.
• Clean and sanitize the probe between products to prevent cross-contamination.
• Keep a calibration log: date, thermometer ID, reading, adjustment, initials.

Continuous monitoring vs. manual logs

Manual logs capture a snapshot a few times a day. They cannot see a compressor that failed at 1 AM and recovered at 5 AM, and they depend on the person holding the clipboard. Wireless temperature sensors record every few minutes, alert someone when a unit drifts, and produce a continuous record that is timestamped by the system rather than by memory.

Continuous monitoring does not replace every manual check. Product probes on the line, cooking temperatures, and cooling logs are still hands-on measurements. A sensible program uses sensors for refrigeration and hot-holding equipment and a digital or paper line-check form for the rest. Our restaurant temperature monitoring system page describes the equipment side; our blog post on temperature data logging covers why the continuous record matters.

Record retention and inspections

The FDA Food Code requires records for specific situations — HACCP plans under a variance (§8-201.14), time-as-a-public-health-control procedures, certain specialized processes — but does not set a single retention period for routine temperature logs. Many health departments expect to see at least the last 30 to 90 days on site, and many franchisors and insurers ask for a year. Keep logs at least as long as the strictest party that can ask for them, and make them retrievable by unit and date. If you use a HACCP-based food safety plan, the plan itself should state the retention period.

What an inspector typically does with your temperature log:

• Takes their own readings and compares them with your most recent entries.
• Looks for gaps — days or shifts with no entries.
• Looks for suspiciously uniform numbers (every unit at 38°F every time, for weeks).
• Reads the corrective-action column and asks what happened.
• Checks that thermometers are present, clean, and calibrated.

Build the log into your daily routine rather than treating it as a separate chore: the opening checklist and closing checklist both include temperature entries, and labeled product (see the food labeling guide) makes the “how long has this been here” question answerable when a unit fails.