A VIP cancels and the count changes after the BEO is final. What does the note say?

A VIP guest cancels the afternoon of the event. The room count on the signed BEO says forty; the actual count tonight will be closer to thirty-two. The document is final, the client has signed it, and the kitchen has already ordered off it. Nobody wants to reopen that page a few hours before doors.

The good news is that you are not supposed to. A finalized BEO is meant to stay exactly as it was when it was signed. What changes is not the document. It is the note the floor reads before the shift starts.

This post walks through what stays frozen, what the pre-shift note actually carries, and why re-finalizing the BEO is the wrong tool for a same-day count change.

What stays frozen on the finalized BEO?

Everything the client signed, exactly as it was rendered at the moment of finalizing. Finalizing a BEO writes an immutable snapshot of the rendered content along with a hash of it, and the document is marked final and points at that snapshot from then on. Once a document carries a signature, the system will not let it be re-finalized — a changed version has to be published separately, which is visible, rather than moved quietly underneath a signature someone already gave. So the count of forty stays on the BEO. That is the record of what was agreed, not a live count.

Why doesn't the operator just re-finalize the BEO with the new count?

Because the document is not built to be edited quietly, and a same-day count change is an operating detail the floor needs tonight, not a change to what the client agreed to. The finalized snapshot is the reference for what was sold and confirmed. Reaching for a new finalized version would mean either overwriting the signed record, which is refused once it is signed, or publishing a fresh one and having it re-signed. The same reasoning applies to a seating change: assigning tables and seats happens against the event and its floorplan, and moving a table does not require touching the finalized BEO at all.

Formal catering contracts commonly set a guarantee deadline in advance of the event and bill on the guarantee or the actual count, whichever is higher — which is exactly why the number on the signed document is a commercial record, not a live headcount, and why a cancellation close to service does not rewrite it.

What does the pre-shift note pick up instead?

The pre-shift note is drafted from facts gathered for the service day: the venue's live menu, the items 86'd that day, whatever the operator adds by hand, and the finalized BEO or BEOs on the books for that venue and day. Those BEO facts are read from the frozen snapshot rather than the live document, so the note can only ever say what the team was actually handed. From the BEO, the note reads the front-of-house view — the event title, the guest count, the run of show, and the allergens present on that menu, drawn from a closed list rather than free text. This is where the changed count belongs — not rewritten into the BEO, but carried forward into tonight's note as the operating number the floor should actually work from.

If you haven't seen how a pre-shift note is built from a finalized BEO under ordinary circumstances, pre-shift note vs. the BEO covers that baseline. This post is about what happens when the count on that BEO stops matching the room.

What should the note itself say?

Say the current number plainly, and say where it came from, without touching the BEO's own count. A short, direct line does the job: state tonight's expected count, note that it is down from what is on the BEO, and give the reason only if it changes anything operationally — for instance, if a table is coming out of the room instead of sitting with an empty chair. Restaurant pre-shift meetings are the mechanism for relaying same-day facts like an 86'd item, a VIP guest, or a large party, from whoever knows first to the people running the floor, and a solid pre-shift structure closes with the team confirming they have the 86 list along with any other operating detail before doors open.

A short version, written the way you would actually hand it off:

• Tonight's count: 32, down from the BEO's 40 (VIP cancellation, same-day).
• Table changes: none — same floorplan, one seat held open rather than pulled.
• 86 list: carries over as usual from the kitchen.
• BEO reference: unchanged, still the signed 40-count document on file.

What if the room itself needs to change, not just the count?

That is a separate situation with its own answer — see a party grows and a table moves after the BEO is final for how a seating or table change gets re-briefed without reopening the document. A guest count drop on its own, with the same tables in the same layout, usually does not need that step at all.

The plain summary

The finalized BEO records what was signed: forty guests, agreed and locked. When a VIP cancels close to service, that number does not move on the document, and re-finalizing it once it carries a signature is not how the system works. What moves is the pre-shift note, which already exists to carry same-day facts like this one from the office to the floor. Excellent Craft is where that note gets drafted, from the finalized BEO, the 86 list, and the day's menu, in one pass.