Opening, closing, temperatures and the evidence
The fridge at six in the morning, with the photo attached
A tick box proves somebody tapped a tick box. A reading and a photograph, taken at the fridge, at the time, is the thing an inspector actually asks for.
What it actually does
instead of Check65A tick is not always enough
A step can demand a number, a photograph, or both, and refuse to close without them. The ones that matter are the ones that cannot be waved through.
A missed check tells the right person
Not a report at the end of the month. The manager responsible for that site hears about the close that did not happen, on the day it did not happen.
Kitchen and front of house run their own
Two sets of checks, two sets of people, one record. A chef is not scrolling past the bar opening to find the probe reading.
Your lists, not ours
Build the opening round your kitchen actually does. Nothing here assumes a burger shop, whatever the demo data looks like.
What it doesn’t do
—Readings are entered by the person doing the check. Nothing connects to a probe or a fridge sensor, so the number is as good as the person who typed it.
—It is a record, not a certificate. It does not sign anything off on your behalf or speak to your local authority.
The rest of it
This one is worth having on its own. It is worth more beside these.
Rotas and clock-in
instead of PlandayBuild the week, publish it, and let people clock in from their own phone.
Stock and ordering
instead of SupyCount as a round, see what the variance cost, and send the supplier order.
Team and training
instead of All GravyChat, announcements, handbooks and training, in the app everyone already has open.
See this part on your own setup
Pick two times and say what you run. We build the demo around that rather than showing you a restaurant that is not yours.
Request a demo