Five topics of doing it right. This one is about the day it does not work, which happens to careful restaurants too — and about the difference between a place that can find out what went wrong and a place that can only apologise. That difference is made entirely of things written down before anybody knew they would be needed.
🚨 The call you were not expecting
Somebody rings to say they were ill after eating with you. It is Tuesday, it was Saturday, and they are upset.
What you do in the first ten minutes matters more than anything else in this topic:
- Take it seriously and write it down. Who, when they ate, what they ate, when the symptoms started, what the symptoms were, whether anyone else in the party was affected, whether they have seen a doctor. Time-stamped, in the same place every time.
- Do not argue and do not admit. Neither "that is impossible" nor "we are so sorry, it must have been us" is a thing you know yet, and both close doors.
- Do not throw anything away. The instinct to clear out the suspect product is exactly wrong: if there is any of it left, it is the only physical evidence that exists, and it can equally well clear you.
- Look at your own records for that day before you form an opinion. This is the moment the temperature log stops being paperwork.
- Find out who you are required to notify and when, because in most places a suspected foodborne illness is reportable, and the threshold is lower than people assume.
One report is a report. A second one naming the same dish is a pattern, and patterns are only visible if the first one was written down properly rather than remembered vaguely.
🦠 The symptoms that force a decision
Most of this course is about food. This part is about people, and it is the shortest and least negotiable section in it: vomiting, diarrhoea, jaundice, sore throat with fever, and infected wounds on the hands are the symptoms that take somebody off food handling, and the reason they are listed everywhere is that they are the ones that transmit.
The previous topic on hygiene covered why this rule fails in practice — because staying home costs money — and what to do about it. What belongs here is the other half: somebody who has had vomiting or diarrhoea does not come straight back the moment they feel better. There is an interval, your food code sets it, and it exists because people are still shedding after they feel fine. Find out what yours is and write it down before you need it, because the day you need it is the day it is most tempting to shorten.
The same applies to a guest being ill in the dining room, which is an ordinary occurrence and a genuine hazard: it is a cleaning job with a specific procedure, not a mop and a bucket, and the difference is worth knowing in advance.
🐜 Pests, and the record that shows you were trying
A pest problem is a food safety problem, a reputational problem and, if it gets far enough, a closure. It is also the one hazard in this course that mostly gets solved by boring building maintenance rather than by procedure: gaps sealed, doors closing properly, bins away from the door and with lids on, nothing stored on the floor, and no standing water.
What matters as much as the treatment is the record of it. A restaurant with no pest log looks like a restaurant with no pest activity right up until the moment it obviously has some, and then it looks like a restaurant that was not paying attention. One with a log showing sightings, actions and a service history looks like what it is: a building being managed.
| Date | Service provider | Action taken | Initials |
Log the sightings, not just the visits. A single fly is not an incident; three entries in the same corner in a fortnight is a gap in the wall somebody needs to find.
☎️ Fire, and the numbers you will not have time to look up
Fire is not strictly food safety, and it shares this section for a practical reason: it lives on the same wall, it is inspected by the same visit, and it has the same shape — equipment that is fine until the day it is not, on a maintenance interval nobody remembers.
Extraction and hood cleaning, suppression system servicing, extinguisher checks: all on a schedule, all with a record, and all of them the kind of thing that gets deferred for two years without any visible consequence at all.
| Date | Work performed | Provider / Department | Initials |
And the last one is the simplest and the one most likely to be missing when it is needed: a list of who to call. Your health department, the fire service, your pest contractor, your refrigeration engineer, your gas and electricity emergency lines, your insurer, and whoever owns the building. Written down, on the wall, not in one person's phone — because the day you need it is the day that person is not there.
| Contact | Organization | Phone number |
That closes the rules. What is left of this run is the visit: what happens when somebody arrives to check that all of the above is true, what they look at, and what to do with what they find. Everything in these six topics is what that visit is looking for, and the folder from the compliance course is how you show it.