Records and alerts
Logged readings are only useful if you can find them again. SafetyBrik keeps a full history per piece of equipment and surfaces problems on Today and the Overview the moment they happen.
Where temperature records live
There are three views of the same data, each suited to a different question.
1. Per-equipment history (the daily view)
The Temperature history side sheet answers "what has this fridge been doing?". Open it by tapping a unit on the Readings tab of /safety/temperature-checks, or clicking its row on the Equipment tab (archived equipment is under Show archived there). On a phone, each reading is a card.
For each reading you see:
- When - when the reading was taken, on the site's clock (with its zone, for example "01:30 GMT", in the repeated hour on the day the clocks go back, or when your device's clock differs). A reading typed in by hand more than an hour after it was taken also shows when it was entered, for example "Entered 7 Oct 10:15" (with the year when it differs, "Entered 2 Jan 2027 09:00")
- Temp - the value in °C
- Limits - the limits the reading was judged against, kept with it, for example "1°C to 5°C" or "Max -18°C" ("-" for a reading that wasn't judged). Changing the range later doesn't change them
- Status - In range, Out of range, or Not judged when the equipment had no safe range at the time (hover for "No safe range was set when this was taken"). See Equipment with no safe range
- Source - the name of the checklist it came from, Manual if logged directly, or SwitchBot for a sensor reading (a sensor reading used on a checklist shows once, as "SwitchBot · checklist")
- By - who logged it
- Notes - any free-text added at the time
Under any reading with a corrective action, the history shows "Corrective action: ..." with what was done. An out-of-range manual or SwitchBot reading without one shows an Add corrective action link to anyone who can log readings, which opens a box to add it there and then: click Record corrective action to save it. Otherwise it reads "No corrective action recorded".
A fridge's history only includes readings taken at its own site. If the history can't be loaded, the sheet says "We couldn't load the readings." with Try again, rather than "No temperature readings yet".
The newest 200 readings load first. While older readings could still fall inside the range shown, the count reads "Latest 200 readings" and Load older readings shows the next 200. If that fails, the sheet says "We couldn't load older readings. Try again." and keeps the readings it has. If a refresh fails, the readings stay on screen with "We couldn't refresh the list. Reload the page to see the latest."
This is the view to use during the day, on the floor, with a manager.
2. Records (the reference view)
The Records page (/safety/records) is where your reference records live: Risk assessments, the COSHH register, Cleaning sign-offs, Suppliers, Emergency contacts, Customer complaints, Pest control events and Corrective actions. It is not where you read individual temperature logs; for that, use the equipment history above or the EHO Report Pack below.
What was done about each out-of-range reading, with any follow-up checks, is listed under Records > Corrective actions (/safety/records?tab=corrective-actions). See Corrective actions.
3. Reports (the audit view)
To see every reading across your equipment for a run of dates - "every out-of-range reading in March" - download the EHO Report Pack from Reports for those dates and the site. Its Temperature Log groups the readings by equipment and shades out-of-range rows red. Reports has no other filters or exports; for one piece of equipment, open its temperature history.
How readings are stored
Each reading is one row, with:
- The equipment it belongs to
- The time it was taken at and, for a reading typed in later, when it was entered
- The value in °C
- The limits it was judged against: the minimum and maximum of the equipment (or the checklist item) at the moment the reading is saved. Every reading keeps them, whether it was logged by hand, pulled from a SwitchBot sensor or answered on a checklist
- Whether it was in range, judged against those limits. A range with one side only (a freezer at -18°C or colder) is judged on that side
- Where it came from - logged by hand, a SwitchBot sensor, or the checklist that produced it
- The user who logged it
Editing the equipment's acceptable range later does not rewrite history. Each reading keeps the limits and the judgement that applied when it was captured.
Out-of-range alerts
Out-of-range readings show on Today and the Overview. Readings logged on a checklist, logged by hand on a piece of equipment and pulled from a SwitchBot sensor all count, and each reading is counted once. The all-sites views count open sites only, so readings at a site that has been switched off or removed are left out:
- Today lists them under Needs an action, and one taken today makes the day Behind until it has its corrective action
- The Overview's alert counts out-of-range readings that have no corrective action yet, however old they are, for example "2 out-of-range readings need an action". It opens that site's Needs an action list on Temperature checks (see Readings that need an action). Once each has its corrective action, the alert goes. In the all-sites view of a business with several sites, there is one alert for each site with readings to deal with, for example "1 out-of-range reading at Witney needs an action". A unit shared by all sites counts at every site
- The safety score's temperature part counts them
- The diary lists them in that day's Activity summary
- The EHO Report Pack counts them in its summary, lists them in its Temperature Log, and lists their corrective actions
An out-of-range reading also sends one shared Temperature alert notification. Everyone who signs in to Brikly sees it in their notifications (it isn't sent to the Team App), and once someone reads it, it is read for everyone:
- On a checklist (typed or from SwitchBot), it opens the checklist itself.
- Logged by hand on a piece of equipment, it reads "Temperature alert: (equipment)", for example "Walk-in Fridge logged at 9°C by Sam Taylor at Station Road (acceptable: 1°C to 5°C)." View Reading opens that equipment's temperature history.
- A SwitchBot reading pulled from the history sheet sends no notification. Realtime alerts from sensors come from the SwitchBot app (see SwitchBot temperature sensors).
There's no separate "alert centre" to babysit - out-of-range readings live with the records they came from, so a reviewer always sees the reading and its corrective action in the same place.
A single out-of-range reading is usually a stock door left open. Several over a week is a different conversation - probably the equipment. Download last month's EHO Report Pack and this month's from Reports and compare their Temperature Logs before calling an engineer.
Exporting records
For an EHO visit, an insurer query, or a brand audit, go to Reports and download the EHO Report Pack for the dates and site you choose. Its Temperature Log lists every checklist and manual reading in the period, grouped by equipment, with the limits, whether it was in range, where it came from, who logged it and the corrective action. Each SwitchBot sensor gets one row per day with its lowest and highest reading, and every out-of-range sensor reading is listed on its own. The limits shown are the ones in force when each reading was taken, and a reading typed in more than an hour later also says when it was entered. The pack's summary counts every out-of-range reading, its Corrective Actions section shows what was done about them, and its Checklist Completion Log shows which checklists were completed, late, missed or closed.
Prove It is different: it is the live log of your proving checks (cooking, chilling, calibration), not an export.
Cross-references
- Build the checklists that capture readings: Building templates
- The day-to-day flow: Logging temperatures
- The audit-ready PDF: Reports
- Proving checks and calibration: Prove It