One guest's shellfish allergy, three documents: who carries it from intake to the floor?

A host takes a phone call. The guest booking a table for twelve mentions a shellfish allergy for one attendee. That sentence has to survive three separate documents and reach a server who has never spoken to the guest. Most of the time it does. The place it can fail is worth knowing in advance.

This is a plain walk through where that one allergen lives at each stage: which hop happens without anyone touching a keyboard, and which hop still needs a person to carry it forward.

Where does the allergen first get written down?

It starts wherever intake happens — a phone call, an inquiry form, a conversation during a previous visit — and that first capture is a human job, not a system one. General restaurant practice treats this as a two-step act: a person takes the information from the guest, and a designated staff member, ideally a manager, writes it down and passes it to the kitchen. Nothing about that first step is automatic. A guest's words become a written note because a person decided to write them down.

The nine most common allergens recognized under federal law — milk, eggs, fish, shellfish, tree nuts, peanuts, wheat, soybeans, and sesame — are the standard vocabulary this note gets translated into. Sesame is a recent addition to that list, which matters if an older template or habit still treats it as an afterthought.

How does the allergen get onto the BEO?

It gets added as a named entry tied to a specific guest, not inferred from the booking. On an event's guest list, a named attendee can carry a meal choice, a VIP flag, and a table assignment on the same record — the kind of row that holds a guest's details alongside where they sit. This matches common trade practice: an event BEO typically lists allergies next to the affected guest's seating, not as a loose note elsewhere on the page.

This step is still a person's job. Someone — the host taking the call, the planner updating the guest list, the manager reviewing the event before it is finalized — has to put the allergy on that specific guest's record. Nothing scans the original phone call and fills this in on its own.

Once a BEO is finalized, the engine freezes exactly what was rendered at that moment into its own record, stamped with who finalized it and when. That frozen copy is what every later document reads from, not the live, editable version, which may keep changing after the fact.

Which hop from the BEO to the pre-shift note is automatic?

This one. Once a BEO is finalized, the pre-shift note is drafted by reading that finalized document directly, without anyone re-typing the allergy. The note draws on the finalized BEO's floor-facing view, which the engine renders with cost already stripped, and folds in the allergens present on that menu from a closed vocabulary rather than free text. A service day with a finalized BEO produces a note that already carries what was locked into that document. Nobody has to remember to mention the allergy again; it carries forward because it was written into the document the note reads.

This is the one structural hop in the whole chain that does not depend on a person remembering. Everything before it — intake, BEO entry — needed a person to notice and write something down. This step needs nothing further, as long as the allergy made it onto the finalized BEO in the first place.

What happens when the allergy is reported after the BEO is already final?

It has nowhere automatic to go, because the note reads only the finalized document, and a finalized BEO does not move once it carries a signature. The system refuses to quietly re-finalize a signed document; getting new information onto the record means publishing a new version, a visible act, not a silent edit underneath a signature someone already gave. So a shellfish allergy reported the morning of the event, after the BEO went final the week before, is not sitting in that finalized document. The automatic path that carried the first allergy through does not exist for this one.

A late allergy needs a different route to the floor: a direct word at line-up, an operator adding it by hand to the day's note, a manager telling the kitchen in person. General guidance on day-of reporting makes a related point: a late update only reaches the kitchen if it lands in something shared and live, not a printed sheet already locked for the day. A detail passed verbally from person to person, several people in a row, is also where severity and specifics tend to get lost, which is one reason a short written note, even one added by hand at the last minute, is worth the extra minute over a spoken handoff alone.

The BEO itself did its job: it is simply describing a guest list that has since changed. Our related piece on what the note shows when a guest detail lands after the BEO is final covers this exact gap for named-guest details more broadly.

What should a manager actually do with this?

Treat any allergy reported after a BEO's finalize date as its own task, separate from the usual document flow. Three hops make up the whole chain, and two of them are manual:

• Intake to guest record — a person has to write it down. Nothing captures this automatically.
• Guest record to finalized BEO — a person has to enter it on the named guest's row before the document is finalized.
• Finalized BEO to pre-shift note — this one is automatic, as long as the allergy made it into the document before it went final.

A late allergy needs a direct word to whoever is plating, because the document chain was never built to catch a detail that arrived after the chain closed. You can see how that drafted floor view actually reads, allergens included, on Excellent Craft's pre-shift notes page.

In short

An allergen travels cleanly from a finalized BEO into tonight's pre-shift note without anyone re-entering it. Getting it onto that BEO in the first place is a person's job, and so is catching it when it arrives too late for the document to help.