PhoenixDuctClean

Guide · Food safety · UK

How to handle a suspected food poisoning complaint

The first ten minutes of a food poisoning complaint decide a lot. Here is how to listen, record what matters, check your own records, avoid admitting liability, and know when the report has to reach the local authority.

SYMPTOMS LOGGEDMEAL & DATE RECORDEDREPORTED TO LA / FSA COMPLAINT / RECORD / ESCALATE
TR19 certificate Before & after photos Filters degreased Fully insured EHO accepted

A customer phones to say they were unwell after eating with you. It is one of the most stressful calls a food business takes, and how you handle the first ten minutes shapes everything that follows - whether the person feels heard, whether you learn anything useful, and whether a genuine problem gets caught before it reaches anyone else. The instinct to apologise and admit fault, or to dismiss the caller outright, are both wrong. There is a calmer middle path, and it starts with listening and writing things down.

Why a complaint is information, not just a threat

A single report of illness rarely proves your food caused it. Most foodborne illness has an incubation period of hours to several days, so the meal a person blames is often not the meal responsible - the last thing eaten is the easiest to accuse. But you cannot know that from the phone call, and treating every report as a nuisance is how a real outbreak gets missed. Handle the complaint as a piece of evidence to be gathered accurately, and you protect your customers and yourself at the same time.

The first call

What to capture, and what not to say

Your goal on the first call is to record, not to conclude. Take down the caller's name and contact details, what they ate and when, the date and time their symptoms began, what those symptoms are, and whether anyone else in their party was affected or unwell. Ask whether they have seen a doctor. If they still have any of the suspect food, ask them to keep it chilled rather than throw it away - it may matter later.

Listen
Record symptoms, the meal, dates and times - calmly and in full
Don't admit
Do not accept liability or blame a dish before anything is established
Preserve
Keep relevant batch records, and any retained food, for investigation

What you should not do is admit liability. Saying "it must have been the chicken" may feel like empathy, but it is a conclusion you are in no position to reach, and it can complicate any later investigation or insurance position. You can be genuinely sympathetic about how someone feels without accepting that your kitchen was the cause. Thank them for letting you know, tell them you take it seriously, and explain that you will look into it - because you will.

Look inward first

Check your own records before you decide anything

Once the call ends, the investigation is internal. Pull the records that cover the day in question: fridge and freezer temperatures, cooking and reheating core temperatures, hot-holding logs, cooling times, delivery checks and your cleaning sign-offs. If the food the customer described was cooked, chilled and held correctly, and your temperature control records for the day back that up, that is powerful evidence. If there is a gap - a fridge that drifted, a cooling step that ran long - that is exactly what you need to know.

Talk to the staff who were on. Was anyone unwell? Food handlers with diarrhoea or vomiting must be excluded from work until they have been symptom-free for 48 hours, and an ill member of staff is a far more common cause of contamination than most operators expect. Look at whether other customers ate the same dish that day without complaint, which points away from a batch problem, or whether several reports are clustering, which points sharply towards one.

When it goes further

When to escalate - and to whom

Most single complaints are logged, investigated and closed internally with a courteous reply to the customer. But some cross a line that means you must act beyond your own four walls. If you have reason to believe food you served or sold was unsafe, you have a legal duty to inform your local authority - and, where food may be genuinely harmful, the matter should reach the Food Standards Agency's incidents route. If two or more people from separate bookings report similar illness linked to the same food, treat it as a potential outbreak and contact your local environmental health team promptly rather than waiting.

Do not obstruct. If an EHO contacts you following a report to them, cooperate fully, share your records, and show the corrective actions you have already taken. A business that can produce clean, contemporaneous records and demonstrate a considered response looks like one in control - which feeds directly into how an inspector rates your management. When something genuine is found, carry out a root cause analysis, fix the system, and document it. That closing loop - cause found, system changed, evidence kept - is what turns a bad day into a defensible one, and it sits alongside the wider discipline of managing a food safety incident without losing customers.

Questions

Frequently asked questions

Should I offer a refund or apologise when someone complains of food poisoning?

You can be sympathetic and offer a goodwill gesture without admitting that your food caused the illness. Keep the two separate: acknowledge how the person feels and that you take it seriously, but do not accept liability or name a dish as the cause before anything has been established. Record the conversation factually.

Do I have to report a single food poisoning complaint to the council?

Not automatically. A single report is usually investigated internally first. You have a legal duty to inform your local authority if you have reason to believe food you supplied was unsafe, and you should contact environmental health promptly if two or more people report similar illness linked to the same food, as that suggests a possible outbreak.

What records will an EHO want to see if a complaint is investigated?

Typically the temperature records for the relevant day - fridge and freezer, cooking and reheating core temperatures, hot-holding and cooling logs - plus delivery checks, cleaning sign-offs, staff sickness records and your food safety management system. Contemporaneous, legible records that match what actually happened are what demonstrate control.

Can a staff member cause a food poisoning complaint?

Yes, and it is more common than many operators expect. Anyone with diarrhoea or vomiting must be kept away from food work until they have been free of symptoms for 48 hours. Checking whether any staff were unwell is a core part of investigating a complaint.

Should I keep the food the customer complained about?

If the customer still has it, ask them to keep it chilled rather than discard it. Preserve any relevant batch of the same food on your side too, along with the records for it, so that if the matter is investigated there is something to examine rather than guesswork.

20+ Years of Experience

Phoenix Duct Clean · by the numbers

Kitchen canopies
degreased
4,287
Laundry ducts
cleaned
1,877
LEV systems
tested
1,658
Hours
on site
54,754

Keep the evidence of control on your side

A dated, thorough deep clean is part of the record that protects you if a complaint is ever investigated. Tell us about your kitchen for a no-obligation quote, UK-wide.