6 ways to automate dishwasher temperature checks
I'm Liam Jones, founder of Pilla and a qualified management consultant. I've helped hundreds of businesses set up workflows, and in this article I'm going to show you six real examples of how to set up your dishwasher temperature checks.
I'll start with the simplest version, then show you one addition at a time, so you can pick the options your kitchen needs. You can open up each template in our workflow builder playground as a starting point and experiment for yourself.
If you're looking to automate this part of your operation, speak to an expert and we'll show you what it would take to set up.
The workflows at a glance
- #1 - Simple log. One box holding the dishwasher's temperature reading. The leanest version, on a phone.
- #2 - With guidance. The basic check plus a note on the target wash and rinse temperatures.
- #3 - With a signature. The basic check plus a sign-off signature naming who checked the temperature.
- #4 - With photo evidence. The basic check plus a photo of the gauge, captured at the time.
- #5 - With Poppi checking the photo. The basic check plus a photo that Poppi reviews the moment it's saved, telling the team chat if it spots problems.
- #6 - With a team alert if the check is overdue. The basic check plus a Poppi message to the team chat if the reading isn't finished by deadline.
Article Content
#1 - Simple log
Who it's for: Single-site kitchens where the chef or duty manager reads the dishwasher gauge themselves. No second checker, just a need to record that the machine is sanitising.
What it is: A dishwasher temperature check is a recorded reading of a commercial dishwasher's temperature. This version keeps it to the one thing that matters: the gauge reading, logged in one box. A commercial machine should rinse at 82°C or above, which is what actually sanitises crockery and glassware. A machine that washes and rinses too cool leaves plates that look clean but still carry bacteria.
In practice: A single-site bistro logs the dishwasher gauge once service starts: 84°C. Under a minute, and a dated record that the machine was sanitising that day. If the gauge reads 70°C, the log turns a "the glasses smell odd" hunch into a documented fault to chase with the engineer.
Why it works: The reading lives in its own box, tied to the machine, so a number is never logged adrift from what it measures. The record stays readable months later, which is what an inspector wants.
Steps included:
- 1 grouped check (one box) holding: dishwasher temperature (number)
#2 - With guidance
Who it's for: Kitchens with new starters or a rota of staff who don't all know the target wash and rinse temperatures.
What it is: The basic check with a guidance note added to the box. The note explains that a commercial dishwasher should wash at around 55 to 60°C and rinse at 82°C or above to sanitise, and that a low rinse temperature means crockery is being cleaned but not disinfected.
In practice: A high-turnover pub kitchen runs this. A new kitchen porter reads the gauge, sees the note explaining the rinse should hit 82°C, logs 78°C, and flags it rather than carrying on. The machine gets serviced before a week of under-sanitised glassware goes out.
What it adds to the basic check:
- The target temperatures are on screen at the moment of the reading
- New staff know what counts as a fail without asking
- The difference between "clean" and "sanitised" is spelled out
Why it works: The guidance sits in the same box as the reading, so staff see it as they check. It turns the head chef's standard into a prompt that is always on screen.
Steps included:
- 1 guidance note (target wash and rinse temperatures)
- 1 grouped check (one box) holding: dishwasher temperature (number)
#3 - With a signature
Who it's for: Kitchens where the temperature reading needs a name against it. Single-site operations with rotating duty managers, and groups where someone signs off the day's reading.
What it is: A signed temperature check is the basic check plus a signature captured at sign-off. The temperature reading stays the same; the signature confirms who did the check and when they signed it.
In practice: A bistro with rotating closes logs the dishwasher temperature and signs. The next morning the manager knows exactly who to ask if there's a question about the reading, not just that someone left a number.
What it adds to the basic check:
- A signature naming who did the check, captured at sign-off
- A record of when the check was signed, next to the reading
- Accountability without asking anyone to take a photo
Why it works: The name goes on the record at the moment the reading finishes, not from memory later. When a machine is found not to reach temperature, you know exactly who to ask about it.
Steps included:
- 1 grouped check (one box) holding: dishwasher temperature (number)
- 1 signature (sign-off)
#4 - With photo evidence
Who it's for: Kitchens under scrutiny that want to show proof the machine sanitises, rather than ask an inspector to trust a number.
What it is: The basic check plus a photo of the gauge next to the reading. A photo of 83°C on the gauge is proof the rinse was reaching temperature, which matters because a machine's sanitising step is invisible: the plates look the same whether it hit 82°C or 70°C.
In practice: A care-home kitchen photographs the dishwasher gauge each service. When an inspector asked how they knew crockery for vulnerable residents was sanitised, the run of gauge photos answered it on the spot.
What it adds to the basic check:
- A photo of the gauge, captured at the time
- Proof that the rinse reached sanitising temperature
- A visual record an inspector can trust without taking your word
Why it works: Evidence taken in the moment is far stronger than a number recalled later. The photo ties the reading to the machine and the time.
Steps included:
- 1 grouped check (one box) holding: dishwasher temperature (number)
- 1 photo of the dishwasher gauge or display showing the wash or rinse temperature
#5 - With Poppi checking the photo
Who it's for: Kitchens where the temperature photo gets taken but nobody looks at it. Multi-site groups where head office can't review every site's photos.
What it is: A photo-checked reading is the basic check plus a photo of the dishwasher gauge or display that Poppi (AI) reviews the moment it's saved. Poppi answers one question about that photo, set by you: does the gauge show the rinse temperature reached at least 82°C? A single named spot is something an AI can actually judge, where a wide shot or a vague reading is not. If the answer is no, Poppi posts what it spotted to the team chat, so the problem gets fixed before everyone leaves.
In practice: A three-site restaurant group closes at 6pm. The closing manager photographs the gauge as always. Poppi reads the photo: clear, 84°C on the display, rinse reached temperature. Verdict yes, and nothing changes. On a rushed Friday the photo shows the gauge stuck at 68°C. Poppi answers no and posts the reason to the team chat ("The gauge shows the rinse temperature did not reach 82°C"). The manager alerts the engineer and holds service until it's fixed.
What it adds to the basic check:
- A photo of the gauge that gets checked the moment it's saved, not just stored
- A team chat message with Poppi's reason the moment a photo fails the check
- The manager stops being the only person who ever looks at temperature photos
Why it works: The check happens in the seconds between the photo being taken and the staff leaving. That's the only moment the problem is still cheap to fix. A manager reviewing photos the next morning can only record that the rinse was too cool; Poppi catching it at 6pm gets the machine serviced while the shift is still on.
Steps included:
- 1 grouped check (one box) holding: dishwasher temperature (number)
- 1 photo of the dishwasher gauge or display showing the wash or rinse temperature
- 1 Poppi decision (judges the photo against your question)
- 1 Poppi action (posts to the team chat if the photo fails the check)
#6 - With a team alert if the check is overdue
Who it's for: Kitchens with a set reading deadline. Busy operations where the check sometimes gets forgotten, and food safety teams where a missed reading is a gap in the daily record.
What it is: An overdue-reading alert is the basic check plus a Poppi (AI) action set to the workflow's scheduled time. If the temperature reading isn't completed by the time it's meant to be logged, Poppi posts a message in the Pilla team chat so the outstanding reading gets done before service ends. It watches the scheduled time, so it catches the reading that got quietly abandoned, not just the one that never started.
In practice: A 6-site restaurant group logs their dishwasher readings at 10am each day before service. On a busy Friday the team skips it, and by lunch nobody remembers. With this version, if the reading isn't logged by 10am, the team chat gets a message, so the shift lead catches the missed reading that morning rather than the food safety manager finding out a week later during the audit.
What it adds to the basic check:
- A message in the team chat if the reading isn't completed on time
- A catch for the reading that got skipped or abandoned
- A record of when the reading should have been done, next to when it was
- The food safety lead finds out that day, not from the weekly audit
Why it works: The alert is tied to the scheduled check time, so an unfinished reading raises its own hand. Nobody has to notice it's missing; the deadline does.
Steps included:
- 1 grouped check (one box) holding: dishwasher temperature (number)
- 1 Poppi action (posts to the team chat if the reading isn't completed by the scheduled time)
How to pick the right version
You don't need to know our product to choose. Every version here is the basic check plus one addition, so pick the additions your kitchen actually needs.
Do other people read the gauge, or just you?
If you read it yourself and know the target, the plain log is enough: #1. The moment rota staff read it, the target needs to be on the screen: #2.
Does the reading need a name against it?
If knowing the reading was done is enough, skip this one. If you want who signed it off on the record, #3 adds a signature.
Do you need photo proof?
A logged number says the reading was done; a photo shows it. If you want visual proof, #4 adds a photo of the gauge.
Does anyone actually look at the photos?
If a manager genuinely reviews every photo, #4's record is enough. If photos get taken and filed unseen, #5 has Poppi (AI) check each one as it's saved, and tell the team chat when something's wrong.
Does the reading have to be finished by a set time?
If a busy team sometimes skips the step, #6 posts a message to the team chat when the deadline passes with the reading unfinished.
Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps. That's how the product works anyway: every option here is one step added to the same basic check.
Related workflows
- Cooked food temperature check - proving food reached a safe temperature when cooked
- Fridge temperature check - the storage check that keeps cold food safe
- Food probe accuracy test - making sure the probe you check with reads true
Conclusion
A dishwasher's sanitising step is invisible. You can't see if the rinse hit 82°C or only reached 70°C. A logged reading is the only way to prove it. Every version above is the same basic check plus one addition: guidance, a signature, a photo, an AI check on the photo, or a deadline alert. Pick the ones your kitchen needs and combine them in the playground.
More additions are coming in future refreshes, like flagging an overdue reading to the manager by name and pulling every site's readings into one dashboard. Those need more review time and will land separately.