Skip to main content

Logging temperatures

This is the daily-record half of temperature monitoring - the part that used to live on a clipboard. Most readings go on the reading board, the Readings tab of Temperature checks (/safety/temperature-checks), which opens first. The Equipment tab is the equipment register.

Readings can also come from a checklist, from the equipment's history sheet or from a SwitchBot sensor. They all land in the same history for each piece of equipment.

The reading board​

The board shows one site. With several sites, pick the site in the tabs at the top: there is no All sites board. A business with no sites has one board of its own. If every site has been switched off, the tab says No open sites.

Each unit is a row (a card on a phone) showing:

  • The unit - its name, type and safe range, or No safe range in amber when it needs one
  • Its last reading in the last 7 days - the temperature, the time on the site's clock ("07:58" today, "Sun 8 Nov, 17:02" for an earlier day) and an icon for where it came from (a checklist, the SwitchBot sensor or logged by hand). An out-of-range reading shows Out of range, and one taken with no safe range Not judged. With none, it reads "No reading in the last 7 days"
  • Today's checks - one chip for each reading due today (see below)
  • Its status - for example Done, Due by 12:00, Overdue, Needs an action or Later today. A unit set to Not checked daily reads Not checked daily
  • The reading box - for anyone who can log readings

Tap a unit's name, or anywhere on its row outside the reading box, to open its temperature history. The board refreshes every five minutes while it is open, so readings taken on the kiosk or the Team App show up without reloading.

Today's checks​

A unit's Readings a day (set on the equipment) splits the site's day into that many checks:

  • 1 a day is Daily
  • 2 a day are Opening and Closing
  • 3 or more are Opening, Check 2, Check 3 and so on, ending with Closing

The checks are spread evenly over the site's opening times for the day, from Settings > Locations. Each is due by the time the next one starts, and the last by closing time. With no opening times set, they are spread over the whole day. For example, with 2 a day:

  • Open 07:00 to 17:00: Opening is due by 12:00 and Closing by 17:00
  • No opening times: Opening is due by 12:00 and Closing by the end of the day

Any reading taken during a check's time counts for it, early or late in the day included: one recorded on the board, a SwitchBot pull, or an answer on a checklist item linked to the unit at that site. A reading taken on the kiosk or the Team App counts at the time it was taken, even if the device was offline. A unit added during the day is never overdue for a check that was due before it was added.

Each chip reads, for example, "Opening: Done", "Closing: Due by 17:00" (Due by end of day with no closing time), "Overdue since 12:00" or "Needs an action" (an out-of-range reading with no corrective action). A check still to come reads "From 12:00", and an earlier check whose time ended with no reading reads Not checked.

On a day the site is closed, no readings are due: "Closed today, so no readings are due. You can still log one." See Closed days.

Recording a reading on the board​

  1. Type the temperature into the unit's box. A minus sign and a decimal point both work, so -18 and 3.5 are recorded as typed
  2. Press Enter, or click Record reading
  3. "Reading recorded" confirms it, and the cursor moves to the next unit's box

So a sweep of the kitchen is a number and Enter for each unit. The cursor only moves on once the reading is saved: if it can't be saved, the box keeps the number and says why, for example "We couldn't record the reading. Check it and try again."

A reading taken earlier​

The reading is timed when it is saved. For one taken earlier, click Earlier time and set When. It is always on the site's clock, whatever the device's time zone, and can go back up to 7 days ("Up to 7 days ago."). On a clock-change day, a time the clocks skip says "That time doesn't exist on the clock-change day". A time in the hour the clocks go back asks which one you mean ("The clocks go back that night, so 01:30 happens twice. Which one?"), for example 01:30 BST or 01:30 GMT.

An out-of-range reading​

An out-of-range number opens a red box straight away: "This reading is out of range (acceptable: 0°C to 5°C). Add what you did about it before you save." Enter takes you to What did you do about it?, and Record reading waits until it is filled in. The reading and its corrective action are saved together: "Reading and corrective action recorded".

If the unit's range was changed since the page loaded and the reading is in range now, nothing is saved: the page says the reading doesn't need a corrective action, and the box goes. Click Record reading again to save the reading on its own. What you typed is kept, and comes back if you change the number to one that is out of range.

Quick choices and Check again​

Under What did you do about it? sit quick choices for the most common answers, such as "Moved the food to another fridge", "Adjusted the setting" and "Called an engineer". Tap one to fill the box. If the box already has text, the choice is added after it as its own sentence, never replacing what you typed. The text stays editable, so add the detail ("Moved the milk to the walk-in").

When the unit needs looking at again, turn on Check again under the box. It adds a follow-up to the corrective action:

  • By when - on the site's clock, two hours on from when you turned the switch on. Change it to any time still to come
  • Who (optional) - leave it blank and the follow-up stays with you, the person recording it, or choose someone else

The re-check goes in with the reading and its action: all three are saved together, or none of them is. A time that has already gone is refused, and then nothing is saved, not even the reading, so fix the time and record it again. The confirmation says a follow-up was added to check again. Check again needs a connection: it is sent straight away, never kept to send later.

The quick choices and Check again are in every box on the web that asks what you did about an out-of-range reading: the board, Needs an action (here and on Today), Check sensor and the history sheet. The box on a checklist itself doesn't have them: once the checklist's corrective action is saved, add the check-again time from its row (see Out-of-range responses). The kiosk and the Team App don't have them yet.

Check sensor​

A unit with a bound SwitchBot sensor also has Check sensor. It reads the sensor there and then and records the reading: "Reading captured from SwitchBot at 09:12". If the sensor reads out of range, the reading is recorded and the box asks what you did about it, for example "SwitchBot read 9°C at 09:12, which is out of range (acceptable: 0°C to 5°C). The reading is recorded." Fill it in and click Record corrective action, or click Add it later: the reading then waits under Needs an action.

Viewers see the board without the reading boxes or Add action. A site that has been switched off or removed has a read-only board.

Readings that need an action​

Above the units, Needs an action (2) lists every out-of-range reading at the site that has no corrective action yet, however old it is. It covers every source: readings logged by hand, SwitchBot readings and checklist answers, linked to a unit or not, on any unit, including those not checked daily. A unit shared by all your sites lists its readings at every site.

Readings taken today come first. Older ones follow under From before today (3), with "They don't count against today. Each stays here until someone records what was done." Only a reading taken today makes Today Behind. Past the first five, the older ones fold behind Show 2 more, and Show fewer folds them again. The list shows the newest 200 from before today. With more than that, the headings still count every one, the list ends with, for example, "3 more from before today show once these have their actions.", and each one you deal with brings the next one in.

Each one shows the unit (or, for an unlinked checklist item, the item), the checklist for a checklist answer, the temperature, when it was taken ("Today, 07:58", or "Sun 8 Nov, 17:02" for an earlier day, with the year from another year), where it came from, who took it and the acceptable range. To deal with one:

  1. Click Add action
  2. Write what you did about it under What did you do about it?
  3. Optionally, tap a quick choice, or turn on Check again to add a re-check (see Quick choices and Check again)
  4. Click Record corrective action

"Corrective action recorded" confirms it, and the reading leaves the list. If someone else recorded one a moment before you, it says "Someone has already recorded an action for this reading. The list is up to date now."

Show only these shows just this list, and Show every unit goes back to the full board. Today shows the same list for its site, and the Overview's out-of-range alert opens it (see Out-of-range alerts). With nothing left, it reads "Nothing needs an action" and "Every out-of-range reading has its corrective action."

Set-up warnings​

The board flags what stops it working properly, each with the way to fix it (Set range and Choose its site need edit permission):

  • Units with no safe range - "1 unit has no safe range, so its readings aren't judged." Set range opens the unit's form, where Use the SFBB range fills in its type's default (an Other unit's range is typed in). See Equipment with no safe range
  • Units that need a site - in a business with several sites, a fridge, freezer, display or hot hold set to All sites isn't checked at any site. Choose its site opens its form
  • Checklist temperature items not linked to a unit - "2 temperature items on your checklists are not linked to a unit, so they count for no unit here." Each checklist is listed, and opens in the checklist builder to link them

Logging a reading via a checklist​

A checklist can still take readings. Add a Temperature item for each piece of equipment (see Building templates) and link it to the equipment. When a team member completes the checklist:

  1. They open the checklist on the web, in the Team App or on the site's kiosk
  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 box asks what they did about it (moved stock, reset the thermostat, called the engineer)
  5. On the web, each reading saves as it is entered, and an out-of-range one saves together with what they did (see Out-of-range responses). The checklist can't be signed off on the web or the Team App, or submitted on the kiosk, until every out-of-range reading has a corrective action

A linked item's reading goes into that equipment's history, with the checklist as its source, and counts for the unit's check on the board. An unlinked item's reading counts for no unit, which is why the board flags it.

New businesses record fridges on the board

A new business's default Opening Routine has no fridge or freezer items: the board takes those readings. Its Closing Routine keeps the Fridge/freezer temps logged tick, which asks you to check every fridge and freezer has its closing reading on Temperature checks. Businesses set up earlier keep their checklist items. Link them to your equipment so they count on the board, or remove them and use the board.

Logging a reading from the history sheet​

You can also log a reading from a unit's temperature history, for example a delivery temperature with a note:

  1. Open the unit's history: tap it on the board, or click its row on the Equipment tab
  2. Click Log reading (viewers don't see it)
  3. Enter the temperature and an optional note. When is the time you save, on the site's clock, unless you change it
  4. Click Record reading

A reading can be logged up to 7 days after it was taken ("Up to 7 days ago." under the picker). An older time is refused with "A reading can be logged up to 7 days after it was taken. Check the date and time.", and a time later than now with "That time is in the future. Check the date and time." A reading entered more than an hour after its time keeps both: its history and the EHO Report Pack show when it was taken, with "Entered 7 Oct 10:15" underneath. SwitchBot readings never carry the mark.

Archived equipment, and equipment at a site that has been switched off or removed, has no Log reading: its history opens read only. The sheet says "Archived. Its readings are kept for your records." or "Station Road is closed. Its records can be read and printed but not changed." See Editing, archiving and restoring equipment.

A reading over 999.99°C either way (a typing slip such as 12345 for 12.3) is refused with "That number is too large to record. Check the reading and enter it again." and nothing is saved, on the board and in the sheet.

Readings recorded on the board or the sheet are added to the history with the source Manual, so anyone reviewing the records can see whether a reading came from a checklist or was logged directly.

An out-of-range reading in the sheet asks for its corrective action as the board does, and Record reading waits until What did you do about it? is filled in. A note in Notes isn't taken as the corrective action.

The corrective action is recorded as done, with the reading's time (for a reading typed in later, the time it was taken). If the equipment needs checking again later, turn on Check again before you record it (see Quick choices and Check again), or add a follow-up afterwards in Records > Corrective actions (see Corrective actions). A reading has one corrective action: a second is refused with "This reading already has a corrective action. To check it again, add a follow-up to it in Records."

Out-of-range readings​

When a reading falls outside the acceptable range, wherever it was taken:

  • The reading is stored as out of range, with the limits it was judged against, and keeps both even if the range changes later
  • It needs a corrective action: what was done about it, recorded at the time. Until it has one, it is listed under Needs an action on the board
  • Everyone who signs in to Brikly sees one shared Temperature alert in their notifications (it isn't sent to the Team App; see Records and alerts)
  • While it has no corrective action, it counts in the Overview's out-of-range alert. It always counts in the diary, the safety score and the EHO Report Pack

This is the digital equivalent of the SFBB "What went wrong / what did I do about it" column. The corrective action is stored with the reading, recorded as done, and shows wherever that reading is reviewed: the equipment history ("Corrective action: ..."), the checklist, the diary, Records > Corrective actions and the EHO pack. When something needs checking again, add a follow-up with Check again as you record the action, or later from Records > Corrective actions.

Fill it in at the time

A reading typed in out of range, on the board, a checklist or the history sheet, can't be saved without a corrective action. Train your team to write what they actually did, while the cause is fresh.

Probe calibrations​

Record probe calibrations in Prove It as a Probe calibration check, with the iced-water and boiling-water readings (a pass is iced water -1°C to 1°C and boiling water 99°C to 101°C). You can add a photo of the probe display as evidence. The probe doesn't need to be on the equipment register.

Only a passed Prove It calibration counts. A calibration written on a checklist is kept with that checklist, but it doesn't count anywhere: not on the Last passed calibration card, the Overview's alert, the safety score, the weekly reminder, the 4-weekly review or the EHO Report Pack.

Where readings end up​

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

  • The reading board - the unit's last reading and today's checks, and Needs an action while an out-of-range reading has no corrective action
  • The equipment history sheet - chronological list, with the limits each reading was judged against, in-range / out-of-range and source badges, and the corrective action under any reading that has one
  • The diary - out-of-range readings appear in that day's Activity summary
  • Records > Corrective actions - what was done about each out-of-range reading, with any follow-up (see Corrective actions)
  • The EHO Report Pack - the PDF you hand to an EHO. Its Temperature Log lists every checklist and manual reading in the period, and each SwitchBot sensor's lowest and highest reading for each day, plus every out-of-range sensor reading. Its corrective-actions section says what each one was for

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