.jpg)
Food Safety Monitoring Records: What a Restaurant Kitchen Must Log
The monitoring records a restaurant kitchen keeps
Food safety monitoring records are the logs a kitchen keeps to prove its safety checks actually happened. They cover temperature readings, delivery checks, cleaning, and the action taken when a check fails. An inspector does not grade how clean the kitchen looks on the day. They grade whether the records show the checks happen every day, at every site. This article shows the full set to keep, what to write when a check fails, and how long to hold each record.
- What inspectors test. Most kitchens already run these checks. An inspector tests whether you can prove the check happened and who did it.
- Due-diligence defence. A due-diligence defence rests on the same proof. A reading scribbled on a wall chart and binned at the end of the week proves nothing a month later.
| Record | What to capture | How often | Why it matters |
|---|---|---|---|
| Fridge and freezer | Unit, reading, time, who checked | Open and close | Proves cold storage held the safe range all day |
| Cooking and hot-holding | Dish, reading, time, who checked | Each batch | Shows food reached and held a safe temperature |
| Delivery | Supplier, item, condition, temperature | Every delivery | Catches a cold-chain break before stock goes in the fridge |
| Cleaning | Area or equipment, time, who signed | Per schedule | Shows the clean happened, not just that it was planned |
| Corrective action | The failure, the fix, the approver | When a check fails | The record an inspector reads first |
Keep each record type in a fixed format so every site logs the same thing. Confirm the exact temperatures and frequencies you must hit with your local food authority, because they set the limits, not this guide.
Supporting records, such as staff training and the allergen information behind each dish, sit alongside these. The kitchen that logs every type on time has the evidence; the one that skips corrective action has the gap an inspector looks for first.
What to write when a check fails
A failed reading is not the problem an inspector cares about. A failed reading with no next step is. When a check fails, the record has to show the follow-up, not just the number that was wrong.
Work the failure in order:
- Record the failure. Write the unit, the reading, the time, and who found it.
- Check the food, not just the unit. If a fridge reads too warm, check the temperature of the ingredients inside it before you decide anything, because the food may still be in range.
- Move the stock. Shift food to a working unit, or discard it if it has been out of range too long, and write down which you did.
- Raise the repair. Log the fault as a job someone owns. The broken unit then gets fixed, not noted again tomorrow.
- Get it signed. A manager confirms the action, so the record shows a decision, not a shrug.
Staff skip this step because nobody wants the blame for a failed check. The fix is a record that rewards writing the failure down, not hiding it.
A logged failure with a clear correction is what proves the kitchen is run properly. A gap where the correction should be is what costs rating points.
How long to keep monitoring records
Keep every monitoring record long enough to cover the food it relates to and the inspection cycle you sit in. A temperature log for a batch cooked today has to outlive that batch on the shelf.
Your local authority sets the minimum retention period, so confirm it with them and keep to the longer of their figure and your own group policy. Three rules keep retention simple across a group:
- Set one retention period for the whole group. One site keeping records for a month and another for a year is a gap waiting to be found.
- Keep the record findable, not just kept. A box of paper in a back office is technically retained and practically useless when an inspector asks for last Tuesday.
- Keep the corrective-action record with its check. The failed reading and what you did about it belong together, because one without the other proves nothing.
Paper makes long retention expensive and search slow. One multi-site group that ran its checks on paper expected a digital log to free at least one person per venue. Nobody wanted to spend the night walking every fridge with a clipboard.
Keeping records in one place across sites
A group is only as ready as its weakest site. One kitchen can keep a flawless log while another loses a week of readings, and the group finds out when an inspector visits the second one. Records that sit in one system, visible to an area manager, are what let you fix the weak site before an inspector does.
Supy keeps the record types that touch stock and cost in one place today.
- Recipe allergens. Allergen tags live at ingredient level and carry into every recipe across outlets.
- Allergen matrix. The allergen information behind each dish stays current when a supplier or recipe changes, and the group can export an allergen matrix.
- Audit trail. Every inventory action carries a named user, a timestamp, and a tamper-proof audit trail, so a delivery or stock record cannot be edited after the fact.
Operators can keep ingredient and allergen data current in one inventory system rather than in a binder per site.
Dedicated temperature logs and cleaning and opening checklists are coming soon, not live yet, so treat the records above as the practice to put in place now.
- Wider framework. For the wider framework these records sit inside, read what a food safety management system records daily.
- Temperature side. For the temperature side on its own, read how to keep a food temperature log.
Start with the record an inspector reads first. Check whether your corrective-action records are written the moment a check fails, or filled in later from memory.
If they are filled in later, fix that record first. It is the one record that proves the rest are real.
