---
title: "Allergen Error: How to Document It"
description: "What to record after an allergen error: the ticket and modifier trail, the plate's path through the kitchen, the guest's own words, and the product to keep."
url: https://www.docu-coach.com/restaurant-allergen-incident-report
markdown: https://www.docu-coach.com/restaurant-allergen-incident-report.md
datePublished: 2026-09-12
dateModified: 2026-09-12
pageType: guide
---

# Allergen Error: How to Document It

> What to record after an allergen error: the ticket and modifier trail, the plate's path through the kitchen, the guest's own words, and the product to keep.

## Key takeaways

- Document the exact modifier as it appeared on the ticket and on the kitchen display, the time it fired, every station the plate passed through, what the guest reported, the care offered, and the product you retained — the same night, before the line resets.
- Allergen errors are the fastest-decaying incident in a restaurant, and the reconstruction two days later always turns into a disagreement between the server and the kitchen that nobody can settle.
- A ticket that never carried the modifier is a front-of-house failure; a ticket that carried it clearly and the plate went out anyway is a kitchen failure; a modifier entered as a free-text note that the display truncated is a systems failure that nobody has noticed until tonight.
- You cannot tell which without the artifacts.
- Photographing the kitchen display sounds excessive until the first time it shows a modifier that was truncated to something unreadable.
- Table 14 got a shellfish allergy and the kitchen sent it out with the sauce anyway.

The ticket, the modifier, the hands the plate passed through — captured before the POS rolls and the line resets.

## An allergen incident report follows the ticket, not the argument

**Document the exact modifier as it appeared on the ticket and on the kitchen display, the time it fired, every station the plate passed through, what the guest reported, the care offered, and the product you retained — the same night, before the line resets.** Allergen errors are the fastest-decaying incident in a restaurant, and the reconstruction two days later always turns into a disagreement between the server and the kitchen that nobody can settle.

The chain is the point. A ticket that never carried the modifier is a front-of-house failure; a ticket that carried it clearly and the plate went out anyway is a kitchen failure; a modifier entered as a free-text note that the display truncated is a systems failure that nobody has noticed until tonight. You cannot tell which without the artifacts.

## What to capture before the line resets

| Capture | Where it comes from |
|---------|--------------------|
| Ticket number, time fired, time expedited | POS and kitchen display export |
| Modifier as entered | The POS record, verbatim, including whether it was a coded allergen modifier or free text |
| Modifier as displayed | Photograph the kitchen display or the printed ticket. They are not always the same |
| Physical ticket | Retrieve it from the spike and keep it with the report |
| What the guest told the server | The server's account, in the server's words, taken the same night |
| Server, expo, and cook on the plate | Names, roles, and which station handled each component |
| The dish as fired vs as plated | Components, garnish, sauce, fry oil, shared surfaces |
| Product retained | Remaining portion, packaging, and the same product from the line — bagged, labeled, dated, refrigerated |
| Guest's reported reaction | Their words. Symptoms as reported, not as diagnosed |
| Care offered | First aid, EMS called by whom and at what time, whether the guest used their own medication |
| Guest details | Name and contact, party size, table |
| Immediate action | Line stopped, product pulled, station broken down, boards changed |
| Notifications | GM, above-store, insurer or broker, and any regulatory report, each with a time |
| Training records | Whether the staff involved have documented allergen training, and the dates |

Photographing the kitchen display sounds excessive until the first time it shows a modifier that was truncated to something unreadable. That photograph has ended more front-of-house-versus-kitchen arguments than any conversation.

## What the record should say

**Not usable:**

> Table 14 got a shellfish allergy and the kitchen sent it out with the sauce anyway. Guest had a reaction. Kitchen swears they never saw it. Comped the table.

**Usable:**

> Saturday 3/8. Ticket #2214, fired 7:31 p.m., expedited 7:44 p.m., table 14, server Dana R., expo Luis M., sauté Diego M. Guest: Ms. A. Patel, party of two, contact provided. Server states the guest told her at 7:26 p.m. "I have a shellfish allergy, it's serious." POS record shows the item entered with the coded modifier ALLERGY-SHELLFISH plus free text "NO FISH SAUCE." Photograph of the kitchen display taken at 8:05 p.m. shows the coded modifier present on line 2 and the free-text note truncated after "NO FISH." Dish as plated included the house nam prik, which contains fish sauce per the recipe card. At approximately 7:52 p.m. the guest reported tingling in her mouth and asked for the manager. I arrived at 7:53 p.m. She stated: "I can feel it, I need my EpiPen from the car." Her companion retrieved it at 7:56 p.m.; the guest self-administered at 7:58 p.m. I called EMS at 7:57 p.m.; EMS arrived 8:06 p.m. and transported at 8:19 p.m. Remaining portion, the nam prik container from the line, and the fish sauce bottle bagged, labeled, dated, initialed and refrigerated at 8:25 p.m. Physical ticket retrieved from the spike and attached. Line stopped on that dish at 7:55 p.m.; remaining nam prik pulled. Witnesses: Dana R., Luis M., Diego M., and Mr. R. Patel (guest). Notified GM at 8:00 p.m., above-store at 8:35 p.m., broker after-hours line at 9:10 p.m. Allergen training on file: Dana R. 11/4, Luis M. 11/4, Diego M. none on record. POS ticket detail exported 11:15 p.m.

Two findings fall out of that record without anyone asserting them: the display truncated the free-text note, and one cook has no allergen training on file. Both are fixable. Neither would have been visible from a comp and an argument.

## What not to write down

- **A cause.** "The kitchen ignored the modifier" is a conclusion. The modifier was present on line 2 and the free text was truncated — write that and let the review decide.
- **A medical characterization.** "Anaphylaxis," "allergic reaction," "she overreacted." Record reported symptoms in the guest's words and the care that was provided.
- **Blame in front of the guest, or in the report.** Naming a cook as the cause in a document a third party will read is both premature and damaging.
- **Liability or payment statements.** No offers, no admissions. Route to your insurer and your own counsel.
- **Discipline, in this document.** If a standard was missed, the employee record is separate. See [food safety write-up](/restaurant-food-safety-write-up) for that document and its boundary against this one.
- **A regulatory conclusion.** Whether anything is reportable is a question for your compliance advisor, not a line in a manager's report.

## Which document this becomes

The primary artifact is an **allergen incident report** — build it with the [incident report generator](/tools/restaurant-incident-report-generator), which captures people, sequence, notifications, and evidence in the order above. The general form is on [restaurant incident report](/restaurant-incident-report).

Alongside it: individual accounts from the server, expo, and cook, taken separately on the [witness statement form](/restaurant-witness-statement-form) before they compare notes, because this is exactly the incident type where accounts converge into a story overnight. And if the review shows an acknowledged standard was missed, the employee record is a [food safety write-up](/restaurant-food-safety-write-up) written from the same facts.

## Follow-up

**Same night:** stop the dish, retain product, save the ticket, photograph the display, export the POS record, take statements, make the notifications, write the report.

**Next day:** follow up with the guest through whoever your process designates. Record the contact and what was said; do not negotiate anything.

**Within the week:** fix the chain where it broke. If free text truncates on the display, stop using free text for allergens and configure coded modifiers. If a cook has no training record, deliver and document it. If the allergen slip is not physically attached to the ticket, change the procedure and say so at pre-shift.

**Ongoing:** review allergen tickets as a category, not one at a time. Near misses — the plate caught at the pass — are worth the same five-line record as an incident that reached a table, and they are what tell you the system is drifting. The kitchen-side standards and evidence are in [documenting line cooks](/restaurant-line-cook-documentation); the full record set is on the [pillar guide](/restaurant-employee-documentation).

## Conclusion

**Follow the ticket end to end and retain the physical evidence.** Modifier as entered, modifier as displayed, the plate's path, the guest's own words, the care given, and the product in a labeled bag in the walk-in.

Build the report with the [incident report generator](/tools/restaurant-incident-report-generator) and take accounts on the [witness statement form](/restaurant-witness-statement-form). Docu-Coach™ keeps the report, the statements, and the training records in one place so the review has everything in front of it — better documentation and organized records, not legal, medical, or compliance advice. Reporting and liability questions belong with your own advisors.

See it against a real service at [/demo](/demo#trial).
## FAQ

### What should an allergen incident report include?

The ticket number and time, the exact modifier as it appeared on the ticket and on the kitchen display, what the guest told the server and when, the dish as fired and as plated, every station the plate passed through, what the guest reported experiencing, what care was offered, whether EMS was called, the product and its packaging, and every notification with a time. Save the physical ticket and export the POS record the same night.

### Should I keep the food after an allergen incident?

Bag and label the remaining portion, the packaging of any component involved, and the same product from the line, and refrigerate them with the date, time, and your initials. Note in the report exactly what you retained and where. It costs nothing, and it is the only physical evidence of what was actually served.

### Do I have to report an allergen incident to the health department?

Reporting obligations depend on your state and local jurisdiction, what happened, and whether a reportable condition is involved. Do not guess. Confirm the trigger with your own compliance advisor or counsel before the situation arises, and log any report you do make — who, when, and the reference number — in the incident record.

### Is an allergen error a food safety write-up or an incident report?

Often both, and they are different documents. The incident report records the event: the ticket, the plate, the guest, the response. A food safety write-up is the employee record when someone missed an acknowledged standard — an unread modifier, a skipped allergen slip, a shared board. Write the incident report first, from facts, and decide about discipline after you know where the chain broke.

### What do I tell the guest?

Focus on their wellbeing and offer to call for medical help. Do not speculate aloud about what was in the dish, do not assign blame to a staff member in front of them, and do not make statements about liability or costs. Record what they told you in their words and what you offered, with times, and route anything beyond that to your insurer and your own counsel.

### How fast does the evidence disappear?

Faster than any other incident type in a restaurant. The plate goes in the dish pit within minutes, the line resets between turns, the physical ticket gets spiked and thrown out at close, and many POS systems roll detailed ticket-level modifier data before the summary reports. Retain the product, save the ticket, and export the POS record before you leave.

---
Start a 30-day free trial: https://www.docu-coach.com/demo.md
More pages for AI agents: https://www.docu-coach.com/llms.txt