# Handling an Out-of-Range Temperature

A temperature log is only worth keeping if somebody acts when a number is wrong. Boost puts the safe range and the instruction in the same place as the reading, so the person holding the probe does not have to go and ask.

## The log knows the safe range

![The temperature log on the tablet](https://ikhejtbmenrxkoctpysb.supabase.co/storage/v1/object/public/kb-screenshots/kb/handling-an-out-of-range-temperature/2/431f2965/1-handling-an-out-of-range-temperature-templog.png)

Each piece of equipment carries a target range set in the back office under **Checklists > Equipment > Equipment**, along with the corrective action your manager wrote for it.

## When a reading is out

1. **Record the real number.** Do not round it into range. The reading is the evidence.
2. **Follow the corrective action** on screen. That is the instruction your shop agreed in advance, usually something like moving product to another unit and calling maintenance.
3. **Report an issue** against that equipment so the repair gets chased rather than remembered.
4. **Check it again** rather than waiting for the next scheduled round.

> \[!CAUTION]
> Product safety is the point of the log, not the paperwork. If a unit is out of range, deal with what is in it before you deal with the app.

## What happens next

An out-of-range reading counts toward **Out of Range (7d)** on the Equipment Health card and shows on the Equipment Dashboard in the back office, so a pattern becomes visible even when each individual reading was dealt with at the time.

> \[!NOTE]
> One out-of-range reading is often a door left open during a delivery. Several in a week is a failing unit, and that is exactly the difference the seven-day count is there to show you.

## What you should see

An honest log, a corrective action carried out at the time, and an issue raised for anything that needs a repair.

***Account Level:** Pro*