A guest count changes twice in one night. Which channel carries each update?

A guest count moves from 40 to 45 at 4pm. Then it moves again to 42 at 6:15, ten minutes before doors. Nobody disputes that the floor needs to know. The harder question is which channel carries which kind of change — because a signed BEO, a pre-shift note, and a verbal update do different jobs, and treating them as interchangeable is how a server ends up plating for the wrong number.

This is not a single-scenario walkthrough. It is the sorting logic itself: a short list you can hold against whatever comes up on a given night, whether it is a count, a seat, an allergy, or a menu swap.

What are the three channels, and what does each one actually do?

There are three places a change can live, and each has a different job. A BEO amendment is the only way a signed document changes — it clones the signed text into a fresh draft the client re-signs, while the original stays locked on file. A pre-shift note is the nightly briefing drafted from the finalized BEO for that service day — it pulls the floor-facing view, with the event title, guest count, run of show, and menu allergens read from what was actually signed. A verbal floor update is what you say out loud during service when a note has already gone out and something shifts again before doors, or shifts too fast to route through a document.

The useful test is not urgency. It is whether the client needs to see the change, whether it needs to be readable days later, and how close to service it happened.

Does every guest-count change need a new BEO?

No — only the kind the client needs to agree to again. Once a document carries a signature that has not been withdrawn, it cannot be re-finalized quietly; getting a changed version in front of people means publishing a new one that the client can see. A bigger change — the client formally growing the party from 40 to 70, adding a course, moving the date — is a new agreed term, and it belongs in a new, version-numbered amendment the client can see, not a note only the floor reads. Industry guidance on BEO handling draws the same line: guest-count adjustments, menu changes, and time changes made after signature are meant to be documented as a revised, version-numbered BEO, agreed by both parties, rather than passed along informally.

So the first move on any guest-count change is to ask: is this something the client needs to see and agree to again, or is it operational noise the kitchen and floor need to absorb quietly? The answer decides the channel.

What happens when the count changes a second time, later that night?

A second change, especially one close to service, usually cannot wait for a new document cycle, so it moves to the fastest channel that still leaves a trace. If the pre-shift note has already gone out and the count moves again before doors, that update goes verbally to the floor lead, because there is no time to redraft and republish a note before service starts. But a verbal-only handoff is also the weakest channel: without a written record, there is nothing to show what was communicated if something is questioned afterward. That is a real cost, not a reason to avoid speaking up — it is a reason to follow the verbal update with a written line the moment there is a beat to do it, even if that is just a note added to the file after the fact.

A sensible way to think about a night like this: the BEO amendment is for changes the client owns, the pre-shift note is for changes the kitchen and floor need going into service, and the verbal update is the last resort for a change that lands after the note is already out. Each one should hand off to the next if there is time. Building in some slack on the count itself is also common practice — a small buffer above the guaranteed number, so a last-minute addition does not create a shortage on the line.

Does the room or seating plan need a new BEO too?

No — seating is assigned against the event and its floorplan, and it is not locked to a finalized BEO. Moving a table or adding one after the BEO is final does not require re-finalizing the document. That is a separate mechanism from the guest count, and it is worth knowing the difference: a seating change is closer to a pre-shift or verbal update in nature, because the document was never the place seating lived in the first place. We have walked through that mechanic on its own in what actually happens when tables move after a BEO is final.

What if the guest-count change comes with a new allergy or a VIP addition?

Treat it as two separate facts, not one bundled update. A guest count and an allergy notice route the same way in principle — through the pre-shift note if the BEO does not need to change, through an amendment if it does — but they are two distinct pieces of information the floor needs, and folding both into one verbal aside is how one gets dropped. If an allergy shows up alongside a count change, say both, and if there is a written channel available, put both in it. The pre-shift note pulls the finalized BEO's floor-facing view, which keeps allergens to a closed, named list rather than free text, so that detail belongs there whenever there is time to route it that way.

A short list that holds up on a busy night

• Client agreed to it, and it changes the signed terms (count materially higher, menu substitution, date, time) — BEO amendment, a new version, client sees it.
• Operational, same-day, does not change what the client signed (a modest count swing, a table move, an added allergy note) — pre-shift note, drafted from the finalized BEO.
• Happens after the note is already out, too close to service to redraft — verbal update to the floor lead, written down as soon as there is a moment.
• When in doubt about which bucket a change falls into, ask whether the client needs to see it again. If yes, it is an amendment. If no, it is a note or a verbal update, in that order of preference.

A pre-shift meeting is also where a lot of this gets said out loud before service starts, since it is meant to give the whole team one shared source of truth on the night's reservations and details before doors open. For fast-changing specifics like counts, VIPs, and table layouts, that meeting works best alongside a written record rather than instead of one.

Building toward a setup where the BEO and the nightly note both draw from the same finalized record is what keeps this sorting fast instead of guesswork — you can see how that flow works in private dining software for groups. For the fuller walkthrough of what changes during service and which channel each kind belongs to, see the private-event day-of playbook, and for the specific case of a VIP or allergy landing after signature, see what changes on the floor.

In short

Route by what changed, not by how urgent it feels. A term the client agreed to needs a new, visible BEO version. An operational adjustment the kitchen and floor need tonight goes on the pre-shift note, built from the document that is already final. Anything arriving after that note is already out gets said out loud, and written down as soon as there is a chance.