What Should a Cooking Temperature Log Record?

A cooking temperature log should identify the food and batch, show when and where it was cooked, record the actual core temperature and any required holding time, and explain every corrective action. It should prove that the site's approved cooking method was followed — not simply show a tick beside “cooked”.

TapTick can help teams schedule cooking checks, capture actual readings and corrective actions, and make missed or failed checks visible to managers. See the TapTick features.

What the cooking log should record

A useful entry lets another person reconstruct the check without asking the cook what happened. Include:

• date and site — plus the kitchen, counter or production area where useful;
• food and batch — for example, “chicken curry, batch 2”, not simply “hot food”;
• cooking equipment — oven, grill, fryer, combi or other unit, especially where several units are used;
• check time — and start or finish time where the process depends on it;
• approved target — the time-and-temperature combination or other validated safe method in the food safety procedure;
• actual core temperature — the number displayed by the probe, not “OK” or a pre-filled target;
• holding time — when the critical limit requires the food to remain at or above a temperature for a stated period;
• check location or sample — where this is needed to show that the coldest or thickest part was tested;
• person responsible — initials, name or authenticated user; and
• corrective action and final result — whenever the first check does not meet the approved limit.

A probe identifier can also be useful where a site uses several thermometers. It links the result to calibration or accuracy-check records and makes a doubtful reading easier to investigate.

Do not pre-populate the result with the target temperature. The target tells staff what must be achieved; the result records what actually happened. Keeping those fields separate makes failed and marginal readings visible.

How to record time and temperature correctly

Cooking safety depends on a combination of temperature and time. FSA guidance for businesses gives 70°C for two minutes as standard advice and lists equivalent combinations including 75°C for 30 seconds and 80°C for six seconds. FSAI guidance gives 75°C instantaneously or an equivalent such as 70°C for two minutes.

The log must match the combination the business has approved. A single reading of 70°C does not, by itself, show that the food stayed at or above 70°C for two minutes. If the procedure uses a timed combination, record when the required temperature was reached and when the holding period finished, or use a validated monitoring method that provides equivalent evidence.

Equally, do not assume that every food has the same cooking instruction. Follow manufacturer instructions for supplied products, and use the validated recipe or process for food prepared by the business. Sous-vide, cook-chill and other specialist processes need controls designed for those processes rather than a generic kitchen log.

Where and how to take the reading

Check the centre or thickest part because that is normally the slowest part to heat. For a large batch, tray or liquid dish, stir where the process allows and check more than one place. For several pieces, select samples that represent the largest, thickest or most slowly heated items.

The probe should be suitable for the food, accurate and cleaned and disinfected before and after use. Avoid touching a bone, tray or hot surface with the sensing area, because that can produce a reading that does not represent the food's core.

Record the stable reading at the point of the check. If the reading looks implausible, repeat it correctly and investigate the probe rather than choosing the more convenient number. Keep probe accuracy checks as a separate linked record; a cooking log is not a substitute for verifying the thermometer itself.

How often cooking checks should be recorded

There is no honest universal answer such as “once per day” for every food business. The monitoring frequency should come from the HACCP-based procedure and reflect the food, batch size, cooking method, equipment, variability and consequences of failure.

For some processes, checking every batch is the appropriate control. For a stable, validated method, the business may use a defined verification frequency alongside consistent recipes, load sizes, equipment settings and visual checks. The food safety system should state which approach applies, who performs it and what triggers more frequent checks.

Increase monitoring when something changes or confidence is lower, for example:

• a new recipe, product, supplier or pack size;
• a different oven, programme, load pattern or batch size;
• food starts from frozen or from an unexpected temperature;
• equipment has been repaired, moved or is heating unevenly;
• a previous check failed or produced an unusual result; or
• staff are learning or have not demonstrated the method reliably.

What to record when a check fails

Do not erase the first result or change it to the temperature reached later. The failed reading is useful evidence. Keep it, then record the immediate action and the final disposition of the food.

Depending on the approved procedure, the immediate action may be to continue cooking, adjust the equipment or divide the batch so it heats evenly. Recheck the core and record the new temperature and any required holding time before the food is released.

If the food cannot be made safe under the procedure, isolate it from service and dispose of it or escalate it for an authorised decision. Do not serve first and complete the log later. If potentially unsafe food has already been served or sold, follow the incident procedure and consider whether the environmental health authority or another regulator must be contacted.

The corrective-action entry should answer four questions:

1. What failed? Record the actual reading, food, batch and time.
2. What happened to the food? Continued cooking, isolated, discarded or another authorised action.
3. How was safety confirmed? Record the repeat result or final disposal decision.
4. What prevents a repeat? Review loading, cooking time, equipment, recipe, probe, training or supervision.

Example cooking record

Suppose a site cooks a tray of chicken portions using an approved limit of 75°C for 30 seconds. A useful record might show:

• Food: chicken portions, batch 2;
• Unit: combi oven 1, programme CH-04;
• Check: 12:18, thickest portion, 71.6°C;
• Action: returned the full tray to the oven for five minutes;
• Recheck: 12:24, two thick portions checked, 77.4°C and 78.1°C; required hold completed;
• Release: batch moved to service at 12:26; and
• Follow-up: supervisor reviewed tray loading before the next batch.

“Chicken — 75°C — tick” would hide the failed first check, the actual results and the action. The fuller record shows that the food stayed under control and gives the manager something useful to review.

How multi-site operators should review cooking records

Standardise the fields and escalation rules, but do not force every product into one critical limit. Each site should use the approved method for the product and jurisdiction while reporting results in a format that head office can compare.

Useful review questions include:

• Which products, batches or equipment produce the most failed first checks?
• Are staff recording actual values or repeating the target number?
• When a timed combination is used, is the holding time evidenced?
• Are repeat readings linked to the original failure?
• Do failures cluster around particular load sizes, shifts or sites?
• Are probe accuracy checks current for the devices used?
• Are corrective actions closed, or does the same failure recur?

A perfect row of identical readings is not automatically reassuring. It may indicate a very stable process, but it can also point to copied targets or retrospective completion. Review patterns alongside recipes, equipment settings, probe records and observed practice.

Ireland and UK: law, guidance and site limits

Food businesses must operate food safety procedures based on HACCP principles, proportionate to the nature and size of the operation. That includes setting critical limits where appropriate, monitoring the controls, taking corrective action and keeping suitable evidence.

The commonly quoted cooking temperatures in official guidance are practical safe time-and-temperature combinations. They should be built into the site's food safety system where appropriate. They are not permission to ignore a manufacturer's instruction, a validated process or a stricter limit adopted by the business.

FSA guidance for England, Wales and Northern Ireland gives 70°C for two minutes and equivalent combinations. The FSA's Safer Food, Better Business material tells businesses to write down what went wrong and what they did about it. Its Safe Catering material for Northern Ireland includes a cooking, cooling and reheating record with food, times, core temperature, initials and comments or actions.

FSAI guidance for Ireland says the core should reach 75°C instantaneously or an equivalent such as 70°C for two minutes, and that measured temperatures should be recorded as part of the HACCP plan. Food Standards Scotland's CookSafe system likewise provides a Hot Temperature Record and tells businesses to set monitoring frequency in their Temperature Control House Rules.