Skip to main content

Logging temperatures

This is the daily-record half of temperature monitoring - the part that used to live on a clipboard. SafetyBrik captures readings two ways, both feeding the same history per piece of equipment.

The day-to-day flow​

A typical day looks like this:

  • Opening checks - first person in records every fridge, freezer and hot hold as part of the opening checklist
  • Mid-shift readings - any spot checks during service, often on hot holds, go straight onto the equipment via the side sheet
  • Closing checks - the closing checklist captures the final readings of the day

Most readings come through checklists. Some are logged directly. Both end up in the same place.

Logging a reading via a checklist​

The recommended flow. Build an opening or closing checklist (see Building templates) with one Temperature item per piece of equipment. When a team member completes the checklist:

  1. They open the checklist on web or in the Team App
  2. For each temperature item, they enter the reading in °C
  3. The acceptable range from the linked equipment is shown beside the input
  4. If the reading is outside the range, the input turns red and a Corrective Action Required box appears
  5. They describe what they did about it (moved stock, reset the thermostat, called the engineer)
  6. Submitting the checklist saves every reading and creates corrective-action records for any that were flagged

Because the temperature item is linked to the equipment, the reading flows straight into that equipment's history with the source marked as the checklist it came from.

Link items to equipment

When you add a temperature item to a checklist, link it to a registered piece of equipment. The acceptable range is then pulled from the equipment automatically, so updating the fridge's target range updates every checklist that uses it.

Logging a reading directly​

For ad-hoc readings - a probe check during service, a delivery temperature, a reading taken outside of any scheduled checklist - use the equipment side sheet:

  1. Go to Temperature checks (/safety/temperature-checks)
  2. Click the graph icon on the row for the piece of equipment
  3. The history sheet opens; click Log reading
  4. Enter the temperature, when it was taken, and an optional note
  5. Click Save reading

The reading is added to the history with the source badge Manual, so anyone reviewing the records can see whether it came from a structured checklist or was logged directly.

Out-of-range readings​

When a reading falls outside the acceptable range on a checklist, three things happen:

  • The reading is stored with is_in_range = false
  • The item is flagged on the response, which surfaces it on the dashboard and in Prove It
  • A Corrective action box appears, requiring the person completing the checklist to record what they did

This is the digital equivalent of the SFBB "What went wrong / what did I do about it" column. The corrective action is stored against the response and is visible whenever that record is reviewed.

Don't ignore an out-of-range reading

Submitting a checklist with a flagged reading and no corrective action is allowed by the system, but it leaves a hole in your records. Train your team to fill it in at the time, while the cause is fresh.

Probe calibration entries​

A probe thermometer is a piece of equipment in its own right. The recommended pattern:

  • Add the probe to the register with type Other (no temperature range)
  • Build a weekly Probe calibration checklist with a Text or Number item per probe
  • Capture the calibration result (ice point, boiling point) in the response
  • Photograph the probe display if you want visual evidence

The probe's calibration history then sits alongside all your other records and is included in your Prove It bundle.

Where readings end up​

Every reading - manual or from a checklist - is stored against the equipment and surfaces in three places:

  • The equipment history sheet - chronological list, with in-range / out-of-range and source badges
  • Records and reports - filterable, exportable views (see Records and alerts)
  • Prove It - the export bundle you hand to an EHO

You don't need to do anything to make this happen - logging once writes everywhere it needs to be.