How it works
Nobody sits down at the end of service to fill in paperwork. The person doing the job records it where they are standing, and everything downstream follows from that one entry.
Areas, equipment, ranges, service intervals, schedules, roles and who is trained for what. This is the foundation the engine reasons about.
Set up with you during onboarding. Corporate templates can be published to every site with controlled local variation.
Each morning the system works out what that specific site owes today, from its own equipment and schedule. Add a fridge and its checks appear. Take one out of service and they stop.
No master checklist to maintain by hand, and no site quietly running last year’s version.
PIN sign-in on a wall-mounted tablet. One question per screen, a number keypad, a camera when evidence is needed. Big targets, because it is used with wet hands in a hurry.
No shift, no check. A record cannot be written without an open attendance, which is what makes it accountable to a named person.
A reading outside its range cannot be submitted on its own. The tablet will not save it until the person records what they did about it, while they are still standing in front of the fridge.
The range is read from the asset, never typed into the question, so it cannot be quietly widened to make a problem disappear.
The manager platform opens on what needs attention, ranked. Nobody scrolls a hundred and twenty eight completed forms looking for the one that failed.
Across one site or every site in the group, depending on who is looking.
When someone asks what happened, the history is already there: who did what, where, when and on which device. Export any date range and send it. The work of producing evidence was done by doing the work.
Records that count as evidence can never be edited or deleted, only superseded, and every change leaves a trail.
Two interfaces, one system
So they get different interfaces sharing one data layer, never one screen squeezed into two shapes.
Web, on a laptop or an office tablet. Dense, white and exception-driven. It opens on Needs Attention, not a dashboard, because the first question a manager has is never "show me everything".
Navy, large-target, wall-mounted and shared by the whole brigade. PIN sign-in, one question at a time, a number keypad and a camera. Every action is confirmed with a personal 6-digit PIN, so each record carries a name.
The rules underneath
These are enforced by the server, not by a warning message someone can click past. They are what makes the record worth having.
A record cannot exist without an open attendance for the person making it. This is what separates a real record from a box someone ticked.
An out-of-range reading blocks its own submission until a corrective action is recorded against it.
Closure conditions are data, evaluated by the server. The close button stays disabled, with the unmet reason shown, until they are genuinely met.
Completed checks, readings, corrective actions and incidents can never be removed. Mistakes are superseded and the trail is kept.
Whether you are running one kitchen or managing several locations, we would be happy to show you how it works and talk through what you actually need.
