Two chairs get added to a table. Does the note's allergen tally still hold?

A host adds two chairs to table 14 an hour before doors. Nobody touches the BEO. Nobody reopens the proposal. The seating change happens where seating always happens — on the floorplan, against the event — and the pre-shift note that already went out this morning still says what it said at print time.

That gap is not a mistake. It is a property of how the note gets built. But a seating add is exactly the kind of change the note's allergen line can miss, and it is worth knowing precisely why, so a manager knows what to check tonight.

Does the allergen tally on the note update when a chair is added?

No. The pre-shift note is drafted from the finalized BEO for that service day, and the BEO facts it uses are read from the document's frozen snapshot rather than the live document. A chair added to a table afterward is a seating change, not an edit to that snapshot, so the note's allergen line keeps saying what it said when it was drafted. Nothing in the note rewrites itself, because nothing about the finalized BEO changed.

The tally is accurate for the guest list the BEO described. What changed sits downstream of that document, in a place the note does not watch.

Why doesn't seating live inside the same finalized document?

Because seating is assigned against the event and the elements on its floorplan, and changing the room after a BEO is final does not require re-finalizing the document. That boundary is intentional — it is why a host can adjust a room without triggering a new signature every time. The tradeoff is that anything the BEO's snapshot captured, including its allergen tags, stays frozen at the moment it was finalized, even as the floor keeps moving underneath it.

For the general version of that boundary — what a table add does and doesn't touch on the signed document — the floorplan-and-BEO post covers it directly. This one is about the allergen number specifically, because a seat count and an allergen count are easy to treat as one problem when they are two.

What actually needs to happen when the two new chairs go in?

Someone has to find out, on the spot, whether either new guest carries an allergy, and get that word to the kitchen and the section before the first course goes out. Suppose a host at the stand adds two seats to a table for a walk-in party. Nothing about that add is captured anywhere the BEO's snapshot can see, and the note printed that morning has no way to reflect it either. The detail either travels by a direct, fast channel tonight, or it does not travel at all.

This is the same sorting problem worked through in choosing the right channel for a day-of change: a seating add with an allergy attached is not big enough to justify a new document, and the note itself was already drafted before the chairs existed, so it needs a channel that reaches the floor faster than the next scheduled briefing would.

Is telling someone about the allergy enough on its own?

Not by itself. Research on restaurant allergy incidents found that more than half of documented reactions happened even after staff had already been told about the allergy. A related look at those same incidents points to communication breakdowns between the person who heard the allergy and the person plating the dish — often in a loud or distracting room — as a common reason the message did not get through. That finding does not specify a fix, but it does say plainly that notifying someone is not the same as the detail landing where it needs to land.

A calmer version of this same problem — a named guest's allergy arriving days out instead of an hour out — is worked through in the shellfish-allergy post. The mechanics are close; the time pressure here is what's different.

What if the two new guests don't have any allergy at all?

Then nothing on the note needs to change. The recheck is not there because every seating add introduces a new allergen. It is there because the note has no way of knowing either way — it was drafted before those two chairs existed — so someone has to check the one table on purpose.

Organizing allergy information by table or seat, rather than as one long paragraph, is one way event-staffing guidance suggests making this kind of detail usable mid-shift: a table-level view is faster to check against a last-minute add than a narrative summary is. Where a floor plan and guest list already carry that structure, checking two added chairs is a look at one table, not a reread of the whole note.

The short version

The pre-shift note's allergen tally is accurate for the BEO it was drafted from, and it stays exactly that accurate after a seating change, because seating lives outside the finalized snapshot by design. A table that grows by two chairs needs a fast, direct way for the allergy detail to reach the kitchen and the section — not a new document and not an assumption that the printed note already covers it. For the training side of building that habit on the floor, Excellent Craft is built around exactly this kind of day-of briefing.