3 ways to automate food poisoning reporting
Liam Jones
Founder of Pilla
Date Modified
22 July 2026
I'm Liam Jones, founder of Pilla and a qualified management consultant. I've helped hundreds of businesses set up workflows, and in this article I'm going to show you three real examples of how to set up your food poisoning reporting.
I'll start with the simplest version, then show you one addition at a time, so you can pick the options your business needs. You can open up each template in our workflow builder playground as a starting point and experiment for yourself.
If you're looking to automate this part of your operation, speak to an expert and we'll show you what it would take to set up.
The workflows at a glance
- #1 - Simple report. One box capturing the report: who, what they ate, symptoms, onset, action.
- #2 - With guidance. The same report with a note on recording it and when to notify your EHO.
- #3 - With photo evidence. The guided report plus a photo of any supporting evidence.
Article Content
#1 - Simple report
Who it's for: Single-site businesses where the manager takes the report themselves and wants it captured properly, not on a scrap of paper.
What it is: Food poisoning reporting is a recorded account of a suspected food-related illness. This version captures the report as one box: the date, the affected person, what they ate and when, the symptoms, when symptoms started, and the action taken. The fields sit together so each report reads as one record.
In practice: A customer phones to say they were unwell after a meal. The manager opens the report, records who they were, the dish and date, the symptoms and onset, and that the dish was withdrawn and the kitchen checked. The report is captured while it's fresh, not reconstructed if it escalates.
Why it works: The fields live in one box, so a report is never logged missing the onset or the action. Capturing it at the time, accurately, is what lets you investigate and defend it later.
Steps included:
- 1 grouped report holding: date reported, affected person, what they ate and when, symptoms, onset, action taken
When to upgrade:
- Any manager might take a report and needs to know what to record
- You want supporting evidence on the record
#2 - With guidance
Who it's for: Businesses where any duty manager might be the one to take a report.
What it is: The simple report with a guidance note: record the details factually, keep the affected person's information securely, and notify your environmental health officer if the illness may be linked to your food, since clusters can indicate an outbreak.
What it adds to the previous template:
- The manager knows what to record and to keep it secure
- The prompt to notify the EHO means a possible outbreak isn't missed
- Reports read consistently whoever takes them
Why it works: The guidance sits in the box, so whoever takes the report knows how to handle it, including the data-protection and EHO-notification points that are easy to forget under pressure.
Steps included:
- 1 guidance note (record factually, keep secure, notify EHO)
- 1 grouped report (date, person, what eaten, symptoms, onset, action)
When to upgrade: When you want supporting evidence on the report (Food Poisoning Reporting #3).
#3 - With photo evidence
Who it's for: Businesses that want any supporting evidence captured with the report, a receipt, the dish, or relevant correspondence.
What it is: The guided report plus a photo of any supporting evidence. A receipt confirming the visit, or a photo of the dish if the customer provides one, strengthens the record if the report escalates to a claim or an EHO investigation.
What it adds to the previous template:
- A photo of supporting evidence, captured with the report
- A stronger record if it becomes a claim or investigation
- Evidence kept with the account rather than in a separate file
Why it works: A report that becomes a dispute often turns on evidence. Capturing it with the report keeps everything together and dated.
Steps included:
- 1 guidance note (record factually, keep secure, notify EHO)
- 1 grouped report (date, person, what eaten, symptoms, onset, action)
- 1 photo of supporting evidence
How to pick the right version
You don't need to know our product to choose. Just answer two questions.
Is it always you taking reports, or might other managers?
If you take them yourself and know what to record, a plain report is enough. The moment any manager might take one, the guidance needs to be on the screen. If only you, #1 is fine. If others might, start at #2.
Do you need supporting evidence on the record?
A written account is often enough. If reports could become claims or an EHO investigation, #3 lets you attach a receipt or a photo alongside the account.
Related workflows
- Accident reporting - the same report shape for workplace accidents
- Cooked food temperature check - the records that help trace a cause
- Food safety audit - the review that catches the cause before it makes someone ill
Conclusion
A suspected food poisoning report is one of the most sensitive records a kitchen makes, and the account taken at the time is the one that holds up. The versions above move from a simple report to one backed by guidance and photo evidence, so whoever takes the report gets it right and the record holds up if it escalates.
→ Build your own food poisoning reporting workflow on Pilla.