The room changes twice after the BEO is final. What actually gets re-briefed?

Suppose a private event books two rooms for one party: a reception space and a dinner room next door. The BEO is finalized a week out. Then, two days before the event, the client asks to swap which room holds the bar. Nobody re-signs anything. Nobody re-finalizes the BEO. This is normal, and it is worth walking through exactly why.

The short version: seating lives on the event and its floorplan, not on the finalized document. The BEO freezes the plan as it stood when it was signed. The floor still needs to hear about what changed, but that happens through a different channel than the document itself.

What does finalizing a BEO actually freeze?

Finalizing writes a snapshot of the document as it stood at that moment. The document is marked final and points at that snapshot; later edits produce new versions, but they do not reach back and change what the snapshot says. That is the whole point of finalizing: it is a fixed point, not a live mirror of the room.

Does moving tables in one of the rooms touch the signed BEO?

No. Event seating is assigned against the event and the elements on its floorplan, and it is not locked to a finalized BEO — changing the room after the document is final does not require re-finalizing it. That holds whether one table shifts six inches or a whole room gets rearranged. The floorplan and the signed document are two different records tracking two different things: one is the plan the client agreed to, the other is where the furniture actually sits tonight.

This matters in a two-room event, because the two rooms can drift out of sync with the signed plan in different ways and at different times — one room settled a week out, the other settled an hour before doors. Neither drift requires touching the BEO.

So what carries the layout change to the banquet team?

The pre-shift note, built from a defined set of sources — but seating is not one of them. A pre-shift note is composed from the venue's live menu, the day's 86 list, whatever the operator adds by hand, and the finalized BEO for that service day, read from its snapshot rather than the live document. From that BEO it pulls the floor's own view: event title, guest count, run of show, and the allergens present on that menu. It does not track floorplan changes on its own.

Which means a change like the bar moving to the other room, decided two days out, is exactly the kind of thing an operator would want written into the note's own free-text context before the shift starts, since nothing else feeds it there automatically. The finalized BEO never moves to reflect it. For a private event that still needs the document read in full — table numbers, timing, service notes for that specific room — the team reads the BEO directly; the pre-shift note briefs, it does not replace it.

Why keep seating outside the BEO's boundary at all?

Because a signed BEO exists to be a fixed point the client and the kitchen can rely on, and a floorplan exists to reflect what a room actually looks like right now — those are different jobs. Keeping the two apart means the room can flex without anyone questioning whether the contract changed underneath it.

For a two-room private event this separation earns its keep twice over: each room can be walked, adjusted, and re-walked independently, right up to service, without either room's changes needing sign-off from the other room's document. Floor plans carry particular weight in a multi-room function, since different teams may be preparing separate spaces for the same event at the same time, and a shared BEO is what keeps those teams working from one operational reference.

What should a pre-event briefing actually cover?

A short list that holds up, whatever tool is running the event:

• Walk the floorplan for each room separately, since a table swap in the dinner room says nothing about the reception room's layout.
• Note anything that changed since finalization — a moved bar, a swapped entrance — in the pre-shift note's free-text context, not as an edit to the BEO.
• Have the team read the BEO itself for the room-specific detail the note leaves out, especially on a large or unusual layout.
• Treat each room's floorplan as something that can move freely between the walkthrough and the doors opening.

Holding a pre-event briefing to walk the team through the plan together, so questions surface before they cause problems on site, is a habit worth keeping for any private event, and it matters more when two rooms are running at once.

A restaurant group weighing its event tools can read more about how a BEO, a floorplan, and a pre-shift note fit together on the private dining software for groups page.

For the closely related question of what happens the moment a table changes after the BEO is signed, see the floor plan changes after the BEO is final. For the broader question of which channel carries which kind of day-of change, see which channel carries each day of change.

In short

The finalized BEO is the fixed record of what was agreed. The floorplan is the live record of where the tables actually are. A pre-shift note briefs the floor from the finalized BEO, plus whatever the operator adds by hand — it does not track seating changes on its own. In a two-room event, treat each room's layout as something that can move freely, and treat the signed BEO as something that only changes when someone deliberately publishes a new version.