# Hot-holding records: connect each check to the food and service period

A hot-holding record is useful when it identifies the food, holding equipment, service period, approved limit and actual check. Recording only an equipment name can make it difficult to understand which food was present when an exception occurred.

> A hot-holding record is useful when it identifies the food, holding equipment, service period, approved limit and actual check. Recording only an equipment name can make it difficult to understand which food was present when an exception occurred.

Kivloo editorial team · 2026-10-25

## Define the decision behind the record

A service counter can change products during a shift. Design the form so operators can associate checks with the relevant food and period without creating a separate, disconnected spreadsheet. Show the local procedure rather than a universal threshold copied from another business.

## Separate food identity, holding location and service changes

Before service, define the food or batch identifier, holding equipment, approved check method and responsible role. Establish how the record handles a tray replacement or refill. The equipment position is not the food identity: the same position may contain several batches during one service period.

Record the actual food present at each checkpoint, its relevant time and measurement context. When a tray is changed, close or reference its history and identify the replacement. If staff combine or top up products under an approved process, retain the relevant batch relationships instead of continuing the previous row as though nothing changed.

During review, compare service events with the observation sequence and any deviation response. Ask whether a reader can determine which food the result covered at that moment. An acceptance test should include one unchanged tray, one replacement and one unresolved deviation. The register should preserve those differences without assuming that a previous acceptable reading applies to the next batch.

## Worked example

A counter changes from one prepared dish to another. The team records the change and associates subsequent checks with the new food. If an exception appears, the reviewer can identify which product and service period need assessment.

## Build a usable record

Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.

- Food or batch reference

- Holding equipment and location

- Service period and product change

- Actual observation and approved limit

- Action and supervisory review

## Example record and review decision

Fictional record example: SERVICE-01 / TRAY-03: food identity, batch, holding equipment and actual check; REFILL-02: replacement batch and time.

Establish which food was present at the time of each check. A replacement tray needs its own identity and applicable checks.

Do not carry a previous tray’s acceptable reading forward when the container is refilled with a different batch.

## Test the review, not just the form

Ask a colleague to retrieve the history of one dish after service. They should not need to infer product identity from memory. Test whether the form makes an unrecorded check distinguishable from a result within the approved range.

## Can the equipment display replace every food check?

Use the measurement method required by your procedure. Do not treat different measurement sources as interchangeable without an approved basis.

## Can one reading be reused after a tray is replaced?

A reading belongs to the food and event actually checked. A replacement batch needs its own identification and the checks required by the approved procedure. Linking records is useful; carrying forward an earlier result as a new observation is not.

## Continue reading

- [HACCP guide: seven principles, food safety routines and practical records](https://kivloo.com/en/guides/haccp-guide-principles-records)

- [Fridge temperature exceptions: record the response as well as the reading](https://kivloo.com/en/guides/fridge-temperature-exception-record)

- [Food freezer temperature logs: distinguish defrost events from unexplained gaps](https://kivloo.com/en/guides/freezer-defrost-temperature-log)

- [Cooling logs: keep the batch history intact across a shift change](https://kivloo.com/en/guides/cooling-log-batch-handover)

- [Digital HACCP records: build a temperature log your team can actually use](https://kivloo.com/en/guides/digital-haccp-temperature-records)

- [Food batch traceability: connect deliveries, ingredients and finished products](https://kivloo.com/en/guides/food-batch-traceability-records)

## Sources and further reading

- [Codex Alimentarius · CXC 1-1969 / General Principles of Food Hygiene](https://openknowledge.fao.org/3/cc6125en/cc6125en.pdf)

Operational guidance, not a certification or a legal assessment. Adapt examples to your site, approved procedures and local requirements. Product links lead to the English website; this guide does not imply a fully translated application or verified hardware compatibility.

Canonical: https://kivloo.com/en/guides/hot-holding-check-record