Skip to content

Daily Food Safety Log Chase

Example prompt: "Every evening around 9pm, check that today's food safety log entries — fridge temperatures, freezer temperatures, hot-hold readings, opening and closing cleaning sign-offs — have all been filled in by the kitchen team in our daily Google Form, ping the duty chef on Slack about any that are missing before they lock up, and append today's log row to our 'Food Safety Logs' tab so the inspection folder is one sheet rather than a pile of paper."

The Problem

Every restaurant in the UK has to keep a daily food safety log — fridge and freezer temperatures, hot-hold readings, opening and closing cleaning sign-offs — and the Environmental Health inspector wants to see it for the last three months at the next visit. Most independents run the log on a paper clipboard by the pass; the page gets filled in patchily through service, the closing chef writes up the last entries from memory at midnight, and the page goes into a folder under the desk that nobody opens until inspection day. The two problems are that the log is the wrong way around — you find the gap on inspection day, not on the day the readings were missed — and that the paper does not roll up: when the rating slips because three Wednesdays in a row had a missing fridge reading, nobody saw the pattern in time to fix it. Moving the log to a daily Google Form gets the entries into a sheet, but it does not chase the entries that did not happen.

How GloriaMundo Solves It

We build a workflow that fires every evening at 9pm — before the kitchen locks up — and checks the day's food safety entries. An integration step reads the day's responses to the daily Food Safety Google Form, which the duty chef fills in at the opening fridge check, the lunch hot-hold check, the afternoon fridge check, and the closing sign-off. A code step checks the four required entries against the response sheet and works out what is missing — the morning fridge reading, the lunch hot-hold, the afternoon fridge, the closing cleaning sign-off. A conditional step routes any missing entries to a Slack DM to the duty chef and a CC to the head chef so the gap is closed before the kitchen locks up rather than discovered three months later. An integration step appends today's row to the 'Food Safety Logs' tab in the kitchen Google Sheet, keyed by date, with every reading and the timestamp it was entered. A second conditional step writes a weekly compliance row on Sundays — the count of days with all four entries present and the days with gaps — so the head chef sees the pattern before it becomes a hygiene-rating problem. Glass Box preview shows the assembled chase message before it lands so the first run can be sense-checked against a real day.

Example Workflow Steps

  1. Trigger (scheduled): Every day at 9pm.
  2. Step 1 (integration): Read the day's responses to the daily Food Safety Google Form — opening fridge temperatures, opening freezer temperatures, lunch hot-hold readings, afternoon fridge check, closing cleaning sign-off — keyed by submission timestamp.
  3. Step 2 (code): Check the four required entries against the response sheet — opening fridge reading, lunch hot-hold, afternoon fridge reading, closing cleaning sign-off — and build the list of any that are missing or that came in outside the safe range.
  4. Step 3 (conditional): If any required entry is missing, DM the duty chef on Slack with the list of missing entries, CC the head chef on the same DM, and include a link to the Google Form so the chef can complete the entry before the kitchen locks up. If a reading came in outside the safe range, DM the head chef separately with the reading, the time, and the unit so the equipment can be looked at the same evening rather than the next morning.
  5. Step 4 (integration): Append today's row to the 'Food Safety Logs' tab in the kitchen Google Sheet, keyed by date, with every reading captured, the timestamp each was entered, and the duty chef who entered it — dedupe on date so a manual replay does not append a second row.
  6. Step 5 (conditional): On Sundays, write a weekly compliance summary row to the 'Compliance Summary' tab — the count of days that week with all four entries present, the count with gaps, and the count of out-of-range readings — and email the head chef the summary so the trend is visible week-on-week rather than only at the next inspection.

Integrations Used

  • Google Forms — the daily Food Safety form the duty chef fills in across the day at the opening, lunch, afternoon, and closing checks
  • Google Sheets — the 'Food Safety Logs' tab as the persisted daily record and the 'Compliance Summary' tab for the weekly roll-up
  • Slack — the DM to the duty chef for missing entries before close-down and the separate DM to the head chef for out-of-range readings
  • Gmail — the weekly compliance summary email to the head chef on Sundays

Who This Is For

Head chefs and owner-operators at independent restaurants, cafes, bistros, gastropubs, and small chains who run a paper food safety log on a clipboard by the pass, keep the clipboards in a folder under the desk, and have once or twice had the Environmental Health inspector point at a gap nobody knew about until that morning. The workflow does not replace the readings themselves — those still have to be taken by a person with a thermometer — but it moves the chase from the inspector to the evening of the day the gap happens.

Time & Cost Saved

Filling in the four daily checks already happens in a working kitchen; the workflow does not add work to the duty chef, it chases the entries that did not get entered on the day they did not get entered. The operating value is not the minutes the head chef saves walking the kitchen at 9pm to check the clipboard, it is the gap that gets closed the same evening rather than the same month, and the slow drift on the Tuesday fridge that gets caught at week three rather than at the next inspection. For a venue with a Food Hygiene Rating riding on the inspection folder being intact, the workflow pays for itself the first time it catches a missing day before the inspector does.