From a signed BEO to tonight's pre-shift note

A BEO gets signed. Then what happens to it? The document does not sit still in a folder waiting for the event date. It becomes the source for the note that briefs the floor before the shift starts.

This matters because the two documents are written for different readers at different times, and it is easy to lose track of how they connect once the BEO is locked. The BEO is the record of what was agreed. The pre-shift note is what a server or line cook actually reads a few minutes before doors open. Understanding the connection between them helps you trust both.

This post walks through that handoff: what a finalized BEO carries forward into a pre-shift note, what stays untouched, and where the connection stops.

What does finalizing a BEO actually do?

Finalizing a BEO writes an immutable snapshot of exactly what is on the page at that moment, along with a hash of that content, stamped with who finalized it and when. Later edits produce new versions, but they do not reach back and change what the snapshot says. This is what makes a finalized BEO safe to hand to a team days in advance — the version they studied is recoverable exactly as they saw it, not reconstructed from memory or a guess about what changed since.

Once a document carries a signature, Excellent will not let it be quietly re-finalized. Any real change means publishing a new version, which is visible, rather than moving the content underneath a signature someone already gave.

How does the finalized BEO reach the pre-shift note?

The pre-shift note is drafted from the finalized BEO, not the live working document. In Excellent, pre-shift notes are composed from the venue's live menu, the items 86'd for that service day, whatever the operator adds by hand, and the finalized BEO or BEOs on the books for that venue that day. Those BEO facts are read from the frozen snapshot, so the note can only ever say what the team was actually handed — not a draft that got tweaked after the fact.

Of the BEO's different audience views, the note reads the front-of-house one: the floor's own view, with cost already stripped out. From that view it pulls the event title, guest count, run of show, and the allergens present on the menu, drawn from a fixed list rather than free text typed in under pressure. If a BEO's event or snapshot cannot be resolved to a real record, it is left out rather than guessed at, and a service day with no finalized BEO gets exactly the pre-shift note it would have gotten anyway.

This fits a broader habit in the trade. Pre-shift meetings typically run ten to fifteen minutes and are used by the kitchen and floor to align on the 86 list, specials, and anything unusual coming in that night. Reviewing the current 86 list specifically is what lets a server tell a table an item is gone before they order it. The finalized BEO's contribution to the note is one more fact in that same short meeting, not a separate briefing held apart from it.

Does a team running a private event still need the BEO itself?

Yes. The pre-shift note is a briefing, not a replacement for the document. A team running a private event still reads the BEO for the full detail — timing, service style, specific requests. The note exists for the rest of the floor and kitchen, the staff who are not working that private event directly but need to know a large party with particular allergens is in the building tonight.

Does changing the seating chart after finalizing mean the BEO has to be redone?

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 a BEO is final does not require re-finalizing the document. If the room gets reconfigured the week of the event — a table moves, a head count shifts the layout — that seating change stands on its own. It does not reopen the signed agreement, and it does not force a new BEO version just to reflect where the tables ended up.

This is worth knowing because it removes a false worry: that any floor adjustment triggers a paperwork chain back through the client. It does not. The signed BEO stays the record of what was agreed with the guest. The floorplan is a separate, more current picture of the room.

Why keep the BEO fixed instead of letting it update live?

Because a pre-shift note, or a kitchen reading a BEO days later, needs a fixed target to read from. If the BEO could change after signature, whoever prepared earlier in the week would be working from a version that no longer exists. Treating a signed BEO as a firm agreement, with any later change handled as a separate, documented update rather than a silent edit, is standard practice for this reason. Clear version numbering on any post-signature update is common advice too, so a kitchen or floor team can tell at a glance which copy is current. A frozen snapshot with an explicit finalize step is one way to get that same clarity.

A short summary

A finalized BEO freezes its content the moment it is signed. That frozen content feeds directly into the pre-shift note — guest count, run of show, allergens, all read from the same snapshot the client saw. Seating and floorplan changes afterward run on their own track and do not force the BEO to be redone. The BEO is the agreement; the pre-shift note is what gets said out loud before the doors open. If you are building the habit of using the BEO as real training material for the floor, the 72-hour banquet server training checklist covers the earlier stretch of that same event. Excellent Craft drafts that pre-shift note directly from the finalized BEO's floor view — you can see Excellent Craft to look at how that draft comes together.