A suspected food-poisoning complaint: what to do in the first hour, and what the rules forbid you to do

A complaint never arrives at a convenient moment. It comes at the peak of lunch service, or in a phone call on a day off, and the wording is almost always the same: we ate at your place yesterday and the whole family has been ill since morning. What happens in the next few minutes decides the shape of everything that follows. An establishment that knows what to do comes out of the incident with a record that protects it and a process it has corrected. One that does not can lose, inside an hour, everything that might have cleared it — and then discover that what it did in good faith is itself a regulatory violation.

The first decision: clean nothing, discard nothing#

The natural instinct of any restaurant manager who hears the word poisoning is to scrub the kitchen end to end and bin what is left of the suspected dish. That instinct is wrong on two counts. The first is regulatory: the executive regulation of the Food Law issued by the Saudi Food and Drug Authority states that where a case of food poisoning exists or is suspected, the establishment is prohibited from cleaning, removing or destroying any equipment, tools, materials or products on the premises — and the authority has stressed that breaching this prohibition is a criminal offence. The second is practical: those leftovers are the only thing capable of saying that the chicken you served was sound. Throw them out and you have deprived yourself of the evidence before you deprived the inspector of it.

In the same direction, the regulation requires the establishment not to let its workers travel outside the Kingdom while a poisoning case or suspicion is live, and to report the workers' names to the competent authority so that a travel hold can be applied. The operational meaning is plain: from the moment a serious complaint reaches you, the kitchen, its contents and its staff are all part of an investigation that has not started yet, and the only correct decision is to freeze the scene, not to clean it.

Isolate, do not discard: put what remains of the suspected batch in a closed, labelled container — item, date and time of preparation, batch number — and place it in the fridge on a separate shelf marked do not use. Isolating food is not destroying it, and it is what makes later testing possible.

What you record in the first hour#

A complaint that is not written down turns, within two days, into two contradictory accounts with nothing to choose between them. The restaurant needs one fixed form, filled in by the same shift that took the call, with the same fields every time, however minor the complaint sounds:

1. The complainant's name and contact number, and how many people ate with them.
2. The exact date and time of the visit, and the invoice or order number if there is one.
3. What each person ate — not only the suspected dish.
4. The exact time symptoms began, and their nature: vomiting, diarrhoea, cramps, fever, blood.
5. Whether everyone who ate fell ill or only some, and whether they ate elsewhere the same day.
6. Whether a health facility was consulted, and whether samples were taken or a diagnosis given.
7. Who took the complaint and at what time, and what exactly was said to the customer.

The most valuable number on that list is the gap between the time of the meal and the time symptoms began. That gap alone narrows the field before any laboratory result arrives — and sometimes takes your restaurant out of the picture altogether.

The onset time points at the process that failed#

Every foodborne pathogen has a known incubation period — the time between eating the contaminated food and the appearance of symptoms. The US Centers for Disease Control and Prevention (CDC) publishes these intervals for each germ, and they are a first-pass diagnostic tool in a restaurant manager's hands before they are a medical fact:

• Staphylococcus aureus: 30 minutes to 8 hours — nausea, vomiting, stomach cramps, diarrhoea. Rapid vomiting soon after eating points to a bacterial toxin formed in a cooked food that was handled or left warm, not to undercooked chicken.
• Clostridium perfringens: 6 to 24 hours — cramps and diarrhoea that usually last less than 24 hours. This is the signature of cooking in bulk and then cooling slowly, or hot-holding below 60 °C.
• Salmonella: 6 hours to 6 days — diarrhoea that can be bloody, fever, cramps, vomiting.
• Norovirus: 12 to 48 hours — vomiting, diarrhoea, nausea. Its commonest source is an ill employee touching ready-to-eat food, not raw chicken.
• Campylobacter: 2 to 5 days — diarrhoea, often bloody, with fever and cramps.
• Listeria: around 2 weeks — fever and flu-like symptoms. A complaint pointing at a meal two weeks ago is rarely about yesterday's dinner.

These intervals indicate; they do not prove. Someone whose vomiting began half an hour after dinner cannot have been given Salmonella by your chicken in that window — but that does not clear your restaurant: it could be a staphylococcal toxin in a sauce or salad prepared in your kitchen that afternoon and left out of refrigeration. The reverse holds too: symptoms that began four days later could be Campylobacter from your meal, or from an entirely different meal the following day. The restaurant's job is not to reach a verdict, but to read the number and point its internal investigation at the right process.

The ill employee is the first thing you check#

Before you go through the delivery and the fridges, ask who was on shift and whether any of them was unwell. The FDA Food Code, in clause 2-201.11, lists symptoms a food employee must report to the person in charge as soon as they appear: vomiting, diarrhoea, jaundice, sore throat with fever, and lesions containing pus. Specific actions follow from these — from restricting what the employee may do up to excluding them from work — and management must notify the regulatory authority when an employee is jaundiced or diagnosed with one of the listed pathogens. The authority's handbook also recommends that the establishment hold a written procedure for vomiting or diarrhoeal events on the premises, and that food which may have been contaminated by such an event be discarded.

The reason this comes first is simple: norovirus, one of the commonest causes of restaurant-linked outbreaks, does not reach the food from the chicken — it reaches it from a human hand. And an employee who turns up unwell because they do not want a deduction from their pay is a genuine operational hazard, not a discipline issue. A written policy stating plainly that anyone with these symptoms does not work in preparation is what makes reporting possible in the first place.

Who you notify, and when#

In Saudi Arabia the channels are well known, and open to both sides. Reports about food establishments go through the municipalities' unified number 940 and the municipality's electronic channels, while the Saudi Food and Drug Authority receives reports and complaints through its unified centre on 19999 and the complaint form on its website. Riyadh Municipality additionally runs a dedicated e-service through which a physician at a health facility files a report of a suspected food-poisoning case. Which means the report may well start at the hospital rather than with your customer, and the regulator may reach you before the complainant's second phone call does.

The practical difference between an establishment that comes out of an incident intact and one that comes out in violation is not who called first — it is the state of the records when the inspector walks in. Those records should have been ready long before the incident.

• The receiving log and supplier invoices for the batch numbers that went into the suspected dish.
• Cooking, rapid-cooling and reheating temperature logs for the day in question.
• Fridge, freezer and hot-holding temperature records.
• The cleaning and sanitising schedule, signed and dated.
• Staff health certificates and the food-safety training record.
• The earlier customer-complaint log — including complaints that looked minor at the time.
• The retained sample, or what is left of the batch, isolated and labelled.

After the incident settles: what actually changes#

On 31 August 2025 the Ministry of Municipal and Rural Affairs and Housing and the Saudi Food and Drug Authority launched an updated table of Food Law violations built on a tiered principle: a warning with a corrective grace period for non-serious breaches, and direct penalties for serious ones that touch consumer safety. The updated table covers elements that were not previously spelled out — among them the handling of poisoning cases, food traceability, documentation, and delivery couriers. The operational reading of that is simple: documentation itself is now something you are held to account for, not an optional internal piece of paper.

Once the procedure is over, the hardest and most valuable task remains: asking what allowed this in the first place. A single complaint is not an isolated case — it is a signal about a process that served hundreds of other people the same day. If the onset time points at slow cooling, the problem is pot size and cooling method, not one particular cook. If it points at an ill employee, the problem is the sickness-reporting policy, not the person. And the only correction that counts is the one that changes a written procedure and is fixed in documented training — not the one that ends with a verbal word at the close of the shift.

Write the procedure while you are calm, not in the middle of an incident: one page on the office wall covering who takes the complaint, what gets recorded, what gets isolated, who is notified, and who calls the owner. Restaurants that have that page act within ten minutes; the ones that do not spend those ten minutes cleaning away what should have been left exactly as it was.