The pre-shift note vs. the BEO: why servers need both

A pre-shift note is not a shorter BEO. It is a different document, built for a different moment: the five to fifteen minutes before service starts, when a floor team needs the handful of facts that change what they do tonight. The BEO is built for a different moment too — the days before, when the kitchen, the room, and the vendors need to agree on everything at once.

Most of the time, the note is enough. A server does not need the full run-of-show to carry plates and pour wine correctly. But some nights the note is not enough, and knowing which nights those are is a manager's judgment call, not a system setting.

What does a pre-shift note actually contain?

It is composed from the venue's live menu, the items 86'd for that service day, whatever the manager adds by hand, and the finalized BEOs for that venue on that day. From each BEO it pulls the floor-facing view — the one already stripped of cost — and folds in the event title, guest count, run of show, and the allergens present in that menu, drawn from a closed list rather than free text written in the moment. If a BEO or its snapshot does not resolve to a real record, the note leaves it out rather than guessing. A service day with no finalized BEO gets the note it always gets, built from the menu and the 86 list alone.

That is a deliberate, narrow summary. It is meant to be read once, fast, standing up.

What does a BEO contain that the note leaves out?

A BEO is a complete operational document: guest count, room setup, the full menu, bar service, AV needs, vendor timelines, and billing, serving as the actual script for everyone working the event. A pre-shift note pulls a slice of that — the floor's own audience view — but it does not carry the kitchen-only fields, the AV or vendor timeline, or the section-by-section detail a captain needs to run a complicated room. Different teams commonly work from simplified, role-specific versions of one master document precisely because each department only needs its own slice — but a slice is not the whole document, and for a private event the whole document still matters.

When is the note not enough on its own?

When the event has structure the note was never built to carry: a mixed format (a plated course followed by a buffet), a ceremonial moment like a toast, a seating chart with named guests, or a guest with a documented dietary restriction that needs more than a one-line allergen flag. A captain managing a private event with several segments has to align with the full run-of-show, not just the pre-shift summary, because a briefing meant for the day's essentials was never built to carry that level of detail. The same logic applies to allergies: the accommodation belongs on the BEO itself, and front-of-house needs to be trained to read it there, because the note alone will not carry that operational weight.

A private dining captain role at a serious kitchen typically spells this out directly — reviewing the BEO and any additional event or timeline notes is treated as separate work from running the pre-shift meeting, not a redundant step.

When should a manager point staff back to the actual BEO?

Whenever the note's summary and the event's complexity stop matching. A short list that holds up:

• The event has more than one service style in one room (plated plus stations, or a reception before a seated dinner).
• There is a documented dietary restriction beyond a standard allergen flag.
• The event includes named-guest seating or VIP handling that the floor needs to see, not just be told about.
• There is a ceremonial moment — a toast, a presentation, a specific pacing instruction — that changes when food or drink should move.
• The BEO has vendor or AV timing that affects when the room is usable.

On any of these, five minutes with the printed BEO, not just the note, is the honest answer. The note is built to summarize; it was never built to replace the source it summarizes.

What if the room changes after the BEO is final?

A seating or table change does not require re-finalizing the BEO, and the floor still needs a direct re-brief on what moved — that is its own, narrower problem, covered in what actually needs to change when a party grows and a table moves.

How does a signed BEO become tonight's note in the first place?

That handoff, from a finalized document to the daily habit of a pre-shift briefing, is worth understanding on its own, and the mechanics are covered in from a signed BEO to tonight's pre-shift note. See how Craft drafts pre-shift notes from the venue's live menu, the 86 list, and the finalized BEO for that service day — and where that draft still points staff back to the document itself.

In short

The pre-shift note is a fast, reliable summary of a finalized BEO, built for a floor team standing up before service. It is not the BEO, and it was never meant to carry kitchen-only fields, full run-of-show detail, or the nuance a private or complex event needs. When an event has more than one moving part, send staff back to the document itself.