How I Set Up the Dishwasher Temperature Check Template with Customers in Pilla
Dishwashers are one of the most trusted pieces of kit in a commercial kitchen, and that trust is the problem. I've walked into kitchens where nobody has checked the rinse temperature in months because the machine "seems fine." Items come out hot, they look clean, so the assumption is that sanitisation is happening. Then an EHO puts a thermometer on the final rinse and it's reading 68°C. The dishes looked spotless. They were covered in bacteria.
The gap between "looks clean" and "is sanitised" is invisible, which is why you need a recorded check. This article covers what your dishwasher actually needs to achieve, the template I use with customers to set it up as a daily check in Pilla, and how Poppi can chase the follow-up so the check doesn't quietly stop getting done.
Key Takeaways
- What is a dishwasher temperature check? A daily verification that your commercial dishwasher's final rinse reaches 82°C or above for thermal disinfection. It confirms that items coming out of the machine are sanitised, not just visually clean
- Why do you need a dishwasher temperature check? Regulation (EC) 852/2004 requires food contact surfaces to be effectively cleaned and disinfected. Your EHO will check that you can prove your dishwasher reaches sanitising temperatures, and a failure here can drop your food hygiene rating
- How do you set it up in Pilla? Use the work template below, set it to run twice daily for each dishwasher unit. Check once at the start of service and once later in the day. Each machine needs its own reading
- How do you automate the follow-up? Set up Poppi to chase anyone who misses a scheduled check, notify managers when a temperature reading fails, and flag when maintenance is coming due
Article Content
Understanding What's Required of You
Commercial dishwashers sanitise in two stages. The wash cycle runs at 55 to 65°C with detergent to remove visible food debris. The final rinse runs at 82°C or above to kill bacteria through thermal disinfection. Both stages matter, but the rinse is the one that makes items safe. A plate can come out of the wash looking perfect and still be carrying enough bacteria to cause food poisoning if the rinse didn't reach temperature.
At 82°C, most harmful bacteria are destroyed within seconds of contact. Below that threshold, survival rates climb sharply. At 70°C some pathogens can survive long enough to transfer to the next item loaded onto the rack. This is why the check targets the final rinse specifically, not the wash.
The legal basis sits in Regulation (EC) 852/2004, which requires food business operators to keep food contact surfaces clean and, where necessary, disinfected. The regulation doesn't prescribe exactly how you do it, but failing to reach effective sanitising temperatures on your dishwasher would not meet the requirement. In practice, 82°C on the final rinse is the benchmark your EHO expects to see.
EHOs check dishwasher temperatures during inspections. I've been present for dozens of these. They'll usually ask to see the machine's display during a cycle, then ask for your records. If you can't show that you're monitoring rinse temperatures regularly, you're looking at lost marks on your food hygiene rating. In more serious cases, where the machine is clearly failing and there's no monitoring in place, I've seen prohibition notices served on the spot.
Your machine type affects how the check works. Pass-through hood dishwashers are the most common in commercial kitchens and usually display the rinse temperature clearly. Conveyor machines in high-volume operations run items through temperature zones. Undercounter units and glasswashers follow the same 82°C target. If you have a glasswasher running at a lower temperature, check the manufacturer's specifications, but most commercial units should still hit 82°C.
Setting It Up as a Work Activity
I've built a dishwasher temperature check template in Pilla covering machine identification, final rinse temperature recording, pass/fail assessment, and notes for follow-up. It's designed as a recurring daily check assigned to whoever opens the kitchen.
Create a new work activity that runs twice daily for each dishwasher unit and tag it with "Food Safety Checks". Check once at the start of service and once later in the day. Each machine needs its own reading. Use the same tag across all of your food safety checks so they're grouped together and Poppi can track them as a set.
The template is designed to be edited, not just filed. If you have more than one dishwasher, you can duplicate the activity for each unit or add fields for each machine. If you also have glasswashers, either create a separate check or extend this one to cover them. Label each machine clearly: "Kitchen Dishwasher", "Bar Glasswasher", "Prep Area Dishwasher". Your staff shouldn't have to guess which machine they're recording against.
One thing I tell every customer: make sure whoever does the check understands the difference between the wash temperature and the rinse temperature. The wash display will show 55 to 65°C and that's normal. It's the final rinse reading that matters. If your machine shows both, note in the template instructions which display to read.
What I'd want to see when reviewing this:
The temperature reading is the heart of the check. I want to see 82°C or above recorded after the machine has fully warmed up, not from the first cycle of the day when the boiler is still getting to temperature. Most commercial dishwashers need 10 to 15 minutes to heat their internal tanks. Running the check on a cold machine gives a falsely low reading and creates unnecessary corrective actions.
I'd also want to see that the check is being done consistently at a similar time each day. If I'm reviewing records and the check happens at 7am one day and 2pm the next, that tells me there's no routine behind it. The best time is after the machine has warmed up but before the first service, so you know you're sanitising from the very first rack.
Common mistakes I see:
The most frequent problem is checking the wash temperature instead of the rinse temperature. Machines display both, and the wash reading (55 to 65°C) is the one that shows first. Staff record it, see it's within a "normal" range, and move on. They've logged a number, but it's the wrong number. Your template instructions should make this explicit.
The second mistake is running the check on a cold machine. Someone turns on the dishwasher at 6am, immediately runs a cycle, gets a reading of 72°C, and logs it as a fail. The machine wasn't broken. It just hadn't warmed up. I tell customers to build "allow warm-up time" into the template guidance so the person doing the check knows to wait.
I also see kitchens where the machine reads 82°C on the display but items are coming out lukewarm. The display can drift over time. Periodic verification with thermal indicator strips, the kind you place on a plate before running a cycle, confirms that the display is accurate. If there's a gap between the display and the strip, get the machine serviced.
Automate the Follow-Up with Poppi
Setting up the check is one thing. Making sure it actually gets done every day is another. Poppi can handle the chasing so you don't have to.
If you set the work activity to recur daily, Poppi will track whether it's been completed on time. You can set up automations to chase the person responsible when a check is overdue, notify managers when a temperature reading fails, and get a regular report showing completion rates across all your food safety checks.
We're still finalising the best automation setup for food safety checks. Once that's ready, this section will show you how to use Poppi to chase overdue checks, alert managers to failed readings, and flag when equipment maintenance is coming due.