The floor plan changes after the BEO is final. Do you have to re-sign anything?

A host calls two days before a private dinner and asks for one more table. Or the room itself changes shape — a wall goes up, a stage comes out, three two-tops become one long table for twelve. The BEO is already final. Does someone have to unwind that and get it signed again?

No. Seating and the floor plan sit outside the finalized BEO. Understanding exactly where that boundary sits — and what still has to happen on the floor side — is the difference between a smooth reseat and a service team standing at the host stand with the wrong chart in hand.

Does a floor plan change require re-finalizing the BEO?

No. Event seating is assigned against the event and the elements on its floor plan, and it is not locked to a finalized BEO snapshot. Finalizing a BEO freezes the rendered content of that document — the menu, the run of show, the guest count, the allergens on file — as a snapshot with its own hash, so the team that studies it days ahead is looking at exactly what was approved, not a moving target. But the floor plan and the seat assignments live in a different part of the system entirely. Moving a table, adding one, or reseating a party doesn't touch that frozen BEO content, so there is nothing to re-finalize.

This matters because it removes a bad reflex: treating every last-minute room change as a document problem that needs a new signature. It isn't. It's a floor problem, and floor problems get solved on the floor.

What's the actual sequence when a table gets added or moved?

First the floor plan itself changes, then the seats get reassigned against the new layout, then the floor team gets a fast, direct re-brief. The floor plan is made of physical elements — tables, stations, sections of room — and seating is assigned against those elements. If a table is added, that's a new element on the plan. If a party grows or a table moves, seats get reassigned to reflect it. None of that step touches the BEO's own content or its signature. It's a change to a separate, editable layer that was never locked in the first place.

What still needs attention is getting the change to the people setting the room and running service. A chart that changed in the office and never reached the floor is not useful to anyone standing at the host stand at seven o'clock.

How is this different from a BEO content change?

A BEO content change — a new dish, a different room, an added course — is a change to the signed document itself, and that follows its own path. Once a document carries a signature, Excellent will not let it be re-finalized in place; getting a revised version in front of people means publishing a new one, a visible step rather than a quiet edit underneath a signature someone already gave. That's deliberate — it keeps the page from moving under a signature that already exists.

A seating change is a different kind of change. It never touched the signed content in the first place, so there's no version to supersede and no signature to protect. The distinction is worth holding onto: if what changed is what the room is serving, who's attending, or what's promised, that's BEO territory and it follows the re-sign path. If what changed is where people are sitting, that's floor-plan territory and it doesn't.

What note does the floor actually need?

The floor needs to be told about the new layout directly, separate from whatever pre-shift note covers the rest of the night. A pre-shift note is drafted from the finalized BEO's own floor-facing view — the guest count, the run of show, and the allergens on file, all read from the frozen snapshot the team was actually handed. That's a good source for what was promised. But it's built from the BEO's own content, and a seating change made after the fact isn't part of that snapshot, so it won't show up there on its own. If the room shifted this afternoon, the crew still needs to hear about it directly — a printed updated chart, a walk-through before doors, whatever gets the new layout in front of the people setting tables and taking guests to them.

A short example: suppose a fourth table gets added the morning of the event because two more guests confirmed late. The BEO's guest count and menu don't move. What moves is the floor plan and the seat assignment for that table. The team needs the new chart before the room opens — not a revised BEO, because there isn't one.

What goes wrong if this gets skipped?

The risk isn't a paperwork problem — it's a service problem. If the floor is still working from the layout that was true when the BEO was drafted, and a table moved or was added since, guests get seated against a chart that no longer matches the room. That's not a signature failure. Nothing was broken about the document. It's a briefing failure, and it's fixed the same way any briefing gap is fixed: by telling the people doing the work what changed, before they're doing it. Training a floor team to treat a layout change as its own briefing step, distinct from the nightly pre-shift note, is exactly the kind of habit Excellent Craft is built to support.

In short

A floor plan change — a moved table, an added one, a full reseat — does not require re-finalizing the BEO, because seating isn't locked to the BEO's frozen snapshot in the first place. What it does require is a fast, direct note to the floor team, separate from the standard pre-shift note, because the BEO's own content won't reflect a room change made after it was finalized. Keep BEO content changes on their own re-sign path, and keep seating changes on the floor's own path, and neither one has to wait on the other.

For the related question of a same-day guest or table change that also doesn't touch the signed document, see same-day BEO changes and table swaps, and for how the finalized BEO becomes tonight's briefing in the first place, see from a signed BEO to tonight's pre-shift note.