Skip to main content

Temperature Question type

Record temperatures by typing or with a Bluetooth thermometer, score them with intervals, and raise follow-up when a reading is out of range.

Written by Logan Bowlby

Overview

A Temperature Question records a temperature reading in a Checklist. Users type the reading in °C or °F, or take it with a Bluetooth thermometer. You can score readings with Score Intervals and use them in logic and triggers, which makes it the right type for food safety, cold-chain and equipment-temperature checks.

For other measurements, such as pressure or fluid level, use a Number Question with a unit.

At a glance

Who can do this

Super Users, a Role with Checklists › Modify (or Create, for Checklists you created), or an Administrator or Editor of the Checklist's permission folder

Where

Checklists › open a Checklist › Add an element › Temperature Question

Works on

Backend (web) to set up. Answered in the Mobile app; not supported in RideOps.

Availability

All organizations

💡 Why this matters: Temperature is the reading inspectors ask about most: cold holding, hot holding, freezers, bearings. Recording it as a Temperature Question keeps it structured and scoreable, so an out-of-range reading is flagged at once and the history is there when an auditor asks for it.


Add a Temperature Question

1. Open the Checklist editor

In the Backend, go to Checklists and open or create a Checklist.

Checklist editor in the Mobaro Backend

2. Add the question

Click Add an element and choose Temperature Question. Enter a Title and, optionally, Explanatory Text, for example where to take the reading.

3. Set the score intervals

In Score Intervals, click Add Interval and enter From, To and Points for each temperature band. Both ends are included, and the answer scores the first interval that matches. You enter the values in the temperature format set in your own user settings; Mobaro converts them, so they apply whichever unit the User answers in.

4. Save

Save the Checklist.


How Users record a temperature

In the Mobaro mobile app, the question has two buttons:

  • Input Temperature — the User types the reading and chooses °Celsius or °Fahrenheit. The unit starts on the one set in their profile.

  • Use Device — the User takes the reading with a Bluetooth thermometer paired with the device. See How to Pair a Bluetooth Device with Mobaro.

The app shows the reading with one decimal. It's saved in both °C and °F, and PDF reports show it in the reader's own temperature format. To correct a reading on a completed Result, see Modify Checklist Results.

⚠️ Heads-up: RideOps doesn't support Temperature Questions: operators get a warning when they open the Checklist and can only leave the question unanswered. If a RideOps Checklist contains one, the Backend also warns that the Checklist has content not yet supported by the RideOps app. For a reading in RideOps, use a Number Question with Unit category Temperature instead. See Configuring Checklists for RideOps.


Scoring, logic and triggers

Scoring. A reading that matches no interval gets no points and is left out of the Checklist's score rather than counted as zero. See Understanding Checklist scoring.

Logic and triggers. Conditions use Colder than, Colder than or equals, Warmer than and Warmer than or equals. You can enter the limit in Celsius or Fahrenheit; readings in either unit are compared correctly. Temperature Questions support Assignment, Ad Hoc Slot and Requirement triggers, so a reading above your limit can raise an Assignment or require a photo. See Assignment triggers in Checklists.


Settings compatibility

Setting

Available?

Notes

Score Intervals

Yes

Bands in °C or °F; first match scores.

Unit, minimum, maximum, decimals

No

Readings are always °C or °F.

Reference Images, Manuals, Videos, Links

Yes

Show where and how to take the reading.

Question Categories

Yes

Group temperature checks for reporting.

Logic

Yes

Colder than / Warmer than conditions.

Triggers

Yes

Assignment, Ad Hoc Slot and Requirement triggers.


Best practices

  • Set score intervals to your compliance limits, for example full points at or below your cold-holding limit and 0 above it, so a failed reading lowers the score without anyone interpreting the number.

  • Add an Assignment Trigger with Warmer than (or Colder than) your limit, so an out-of-range reading becomes a tracked task.

  • Name the unit and location of the reading in the title, for example Walk-in chiller 1 core temperature.

  • Use one Temperature Question per appliance, so dashboards can chart each one separately.


Frequently asked questions

Can I do an hourly temperature check in RideOps?

Not with a Temperature Question: RideOps doesn't support it. Record the reading in the Mobaro app with a Checklist on a Schedule instead; see How to schedule a Checklist. In a RideOps Checklist, use a Number Question with Unit category Temperature.

Can I show temperature readings as a graph on a dashboard?

Yes. The Value Development By Question and Value Development By Location widgets accept Temperature Questions and chart the readings over time. See Value Development by Question Widget.

How do I get notified when a fridge temperature is wrong?

Add an Assignment Trigger to the question with Warmer than your limit. When a reading is above it, an Assignment is raised for the people you choose, who are notified according to their notification settings. See Assignment triggers in Checklists.

What are the points on a temperature question for?

They score the reading. Each score interval gives points to a temperature band, so readings in range raise the Checklist's score and readings out of range lower it. Scores feed reports and dashboards.

Did this answer your question?