# Air temperature and food temperature: keep the measurement context

A record should state what was measured and how. An air sensor, an equipment display and a food probe can produce different observations; storing only the numeric value strips away context needed to interpret the result.

> A record should state what was measured and how. An air sensor, an equipment display and a food probe can produce different observations; storing only the numeric value strips away context needed to interpret the result.

Kivloo editorial team · 2026-10-25

## Define the decision behind the record

Name the measurement source in the form and keep units explicit. Software should not silently substitute an equipment display for an independent food measurement. The site procedure determines which observations support each check and what to do with an exception.

## Keep the measurement subject visible from entry to export

Define what each control is intended to observe before choosing the field names. Cabinet air, equipment displays and measurements of identified food are different subjects. Record the approved method, instrument, location and decision criterion for the actual control. A shared unit such as °C is not sufficient context.

When a check uses another method, identify the method and subject explicitly. Keep a cabinet observation connected to any food assessment without merging them into one undifferentiated temperature field. Retain event times because two measurements taken later cannot automatically describe the conditions at the earlier observation.

Review the export without relying on the form’s colours or screen layout. A reader should identify which values describe air, food or another defined subject and which procedure applied. Test similar values from two different methods and a missing subject identifier. The system should expose the missing context rather than interpret all readings using one default rule.

## Worked example

A receiving operator records a food measurement while a storage device reports air conditions. The reviewer sees them as two observations with different subjects and times. Linking them to the delivery can be useful, but they are not merged as equivalent results.

## 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.

- Measured subject and location

- Instrument or source identifier

- Method required by the procedure

- Actual time, result and unit

- Product or equipment reference

## Example record and review decision

Fictional record example: AIR-01: cabinet air sensor and timestamp; FOOD-01: identified food batch, probe method and timestamp; PROC-01: applicable interpretation.

Retain the measurement subject and method with the value. The same unit does not make two different measurement types interchangeable.

A food measurement cannot silently replace a required equipment observation, or the reverse, without a documented procedural basis.

## Test the review, not just the form

Inspect an exported row without looking at the app. Another person should be able to identify the subject, method and unit. If the source is ambiguous, improve the form before trying to automate decisions from it.

## Should two different methods always give the same reading?

Do not assume equivalence. Interpret results using the approved method and relevant conditions.

## Is the unit enough to identify what a reading means?

No. A temperature needs its measurement subject, method, time and applicable criterion. Equal units do not establish equivalent observations or authorise substituting one control for another.

## 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/air-versus-food-temperature-records