Isn't the pre-shift note enough? When to pull the BEO instead

A new manager asks this most often after a rough private event: the note had the count, the room, and the allergens, so why did the floor still need to go find the actual BEO? The short answer is that the note carries one view of the document, built for a fast read at line-up. It is not the document, and it was never meant to be.

This matters most on nights with a private event mixed into regular service, because that is exactly when a server might assume the note covers everything. Knowing which facts travel into the note and which stay behind on the signed page is what keeps someone from working off a summary when the moment calls for the source.

What does the pre-shift note actually carry from the BEO?

It carries the front-of-house view: the event title, the guest count, the run of show, and the allergens present in that menu. Those facts are read from the BEO's finalized snapshot, not whatever the document happens to say if someone edited it since. A note about tonight's events reflects what was actually finalized, not a live draft that might have moved.

Why doesn't a good summary cover everything the floor needs?

Because the note is one audience view of a document built to hold more than one. A BEO is commonly split into role-specific views — the kitchen gets a version with menu detail, dietary notes, and service timing, while the floor gets a version built around room setup, guest flow, and arrival times. The note draws from the floor's own view of that document, already stripped of cost, and folds in a fixed set of facts: title, count, run of show, allergens present. That is a deliberate, narrow slice of a document that holds a great deal more. A private event usually has more riding on it than that slice covers, which is exactly why the floor still needs the source document in hand for one, not a paraphrase of it.

Why isn't reading a fast summary the same as being briefed?

Because a summary is built to be fast, and fast means something gets left off the page. A dedicated pre-event briefing is a recognized supplement to the BEO, not a stand-in for it — a common failure is assuming staff will read the full document thoroughly instead of getting that live briefing, which only works if the underlying document is still there to check. A BEO is meant to work as a production sheet precise enough that anyone touching the event can do their job without a call back to the office. Compress all of that into a paragraph and it stops doing that job, which is the one thing a note was never meant to replace.

When should the floor still pull the actual BEO?

A private event is the case to watch for, because it is the case where the note's fixed slice of facts is least likely to be the whole story a server needs. The note tells a server there is an allergen in tonight's menu. It does not tell a server which guest that allergen belongs to, or walk through a room-specific run of show beyond the summary line. Trade guidance on writing BEOs recommends a dedicated, clearly flagged section for dietary restrictions and severe allergies rather than folding them into general notes — a reminder that an allergen line in a one-page note is a pointer, not the full picture. When a shift is a private event with real weight to it, that pointer is the cue to go get the document itself, not the end of the briefing.

What if the BEO changes after the note already went out?

It doesn't change quietly. A signed document cannot be re-finalized once it carries a signature that hasn't been withdrawn — a changed version has to be published as a new one, not slipped underneath a signature someone already gave. So if the count, the room, or the run of show has moved since the note went out, that change shows up as a new version, not a silent edit to what the floor already read. Verification checklists used before service flag exactly this risk: an outdated version can still be in circulation after a late amendment or a client change, which is why the signed document itself, not a summary of it, is what gets checked before doors.

For the day-to-day mechanics of how the note draws from the BEO and the 86 list, see the pre-shift note vs. the BEO and from a signed BEO to tonight's pre-shift note. If you want to see exactly what the draft pulls in and what it leaves for the floor to check on paper, see how Craft drafts the note.

The short version

The note carries the floor's own view of the finalized BEO: title, count, run of show, and the allergens present in the menu. That is a fixed slice of a longer document. Use the note for a standard shift. For a private event, treat the note as the starting point and go find the signed document itself before line-up.