4 ways to automate food poisoning reporting

#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.

Available on: Basic.

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:

1. Any manager might take a report and needs to know what to record
2. You want supporting evidence on the record
3. You run more than one site and need signed, comparable reports

#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.

Available on: Standard.

What it adds to the previous template:

1. The manager knows what to record and to keep it secure
2. The prompt to notify the EHO means a possible outbreak isn't missed
3. 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) or signatures for a defensible record (Food Poisoning Reporting #4).

#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.

Available on: Standard.

What it adds to the previous template:

1. A photo of supporting evidence, captured with the report
2. A stronger record if it becomes a claim or investigation
3. 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

When to upgrade: When the report needs naming and signing for a defensible, multi-site standard (Food Poisoning Reporting #4).

#4 - With signatures

Who it's for: Multi-site groups that need every report recorded to one signed standard head office can review.

What it is: The photo report plus two signatures: the person recording it, and the manager. The signatures turn the report into a named, dated record that shows a manager saw it and acted.

Available on: Standard.

What it adds to the previous template:

1. A recorder signature confirming the account
2. A manager signature confirming it was seen and actioned
3. A complete record (account, photo, signatures) head office can review across sites

Why it works: A signed report shows the report was taken seriously and seen by a manager, not left unread. With the account and evidence, it's the full record an EHO or an insurer expects.

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
• 1 recorder signature
• 1 manager signature

When to upgrade: When you want Poppi to flag a possible cluster across sites or notify the EHO contact, or roll reports into one report. Those versions are coming in the next post update.

How to pick the right version

You don't need to know our product to choose. Just answer three 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 investigations, #3 lets you attach a receipt or photo.

Does it need signing off?

In one site, the report speaks for itself. Across sites, head office wants each report seen and signed by a manager. If no sign-off is needed, #3 is enough. If you run more than one site, #4 adds recorder and manager signatures.

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 a signed, evidenced record an EHO or insurer will accept.

Five more versions are coming in the next refresh that bring AI into reporting. Poppi can flag a possible cluster across sites and roll reports into one view. Those need more review time and will land separately.

→ Build your own food poisoning reporting workflow on Pilla. The Basic plan unlocks the simple report today.