The BEO cover page and the pre-shift note: a printable chart for new hires

A new server gets handed two pieces of paper on the same night: the cover page of the BEO for the private event in the back room, and the pre-shift note posted near the kitchen. A trainer who cannot explain the difference in one minute will spend the rest of service answering questions those two pages should have already answered.

Here, "BEO cover page" means the front page of the banquet event order for one specific event — the summary a server reads first, before the full run of show. Below is a chart a trainer can print and hand to anyone starting this week, plus a plain explanation of each row.

What does the chart actually show?

Here is the side-by-side, in order:

• Audience — BEO: kitchen, floor, bar, and setup staff working that one event. Pre-shift note: everyone on shift that day.
• Source — BEO: the finalized, signed banquet event order for that event. Pre-shift note: drafted fresh each service day, pulling from whatever BEOs are finalized for that day.
• Lifespan — BEO: fixed once finalized; stays exactly as signed. Pre-shift note: covers one service day, then it is replaced.
• What it covers — BEO: guest count, room, timing, and the run of show for one event. Pre-shift note: the day's specials, menu changes, any 86'd items, and a summary of the day's finalized events.
• Who owns edits — BEO: only a new, published version changes it. Pre-shift note: whoever drafts the day's note, from what is current at draft time.

What does the BEO cover page actually contain?

It contains what a kitchen and floor need to run one private event: guest count, room, timing, and the run of show. Finalizing a BEO writes a stamped, immutable record of exactly what was on the page at that moment, with a note of who finalized it and when — that record is what the cover page reflects. Later edits produce new versions rather than reaching back to change what that record says, so a cover page a server reads on Thursday for Saturday's dinner will not have quietly changed by Friday night. For the full section-by-section breakdown of what belongs on a BEO, see what a great BEO actually contains. A BEO's distribution list commonly reaches the client, the planner, the chef and kitchen staff, the beverage manager, banquet captains, and venue managers.

What does the pre-shift note actually contain?

It contains a short summary for one service day: the venue's live menu, anything 86'd, whatever the operator adds by hand, and facts pulled from the BEOs finalized for that day. Those BEO facts come from the finalized, frozen record rather than a document that might still be moving, so the note can only say what the team was actually handed. From the BEO it folds in the event title, guest count, run of show, and any allergens in that menu, drawn from a fixed list rather than free text. A team working a private event still reads the BEO itself; the note is a briefing, not a replacement. A pre-shift meeting is typically brief, held around staff meal, and covers the day's specials, menu changes, and any private events on the books. See how that note gets drafted in Excellent Craft.

Why does the lifespan differ so much?

Because the two documents answer different questions on different schedules. The BEO answers what was agreed for one event, and that answer has to hold still, since a kitchen and a client both relied on it. The pre-shift note answers what the floor needs to know before tonight's service, and that resets every day because tonight's specials and tonight's private events are not yesterday's. A trainer's plain rule for new hires: never treat the pre-shift note as a substitute for reading the actual BEO on a private event you are working.

Who can edit which one?

The BEO cover page changes only through a new, published version, never a mark-up of the page a team already read. A signed document is never reopened underneath the team that read it; getting a changed version in front of people means publishing a new one, visibly. The pre-shift note changes every time it is drafted, since it pulls fresh facts at draft time. Nobody should hand-edit a BEO cover page; a note posted by the kitchen is expected to read differently the next day.

How does this play out on a real night?

Suppose a VIP guest cancels in the afternoon and the party size drops before service. The signed BEO for that event stays exactly as signed — nothing about it changes. What updates instead is tonight's pre-shift note, since it is redrawn fresh each day from the current facts. A separate walk-through of exactly that situation is in a VIP cancellation and the pre-shift note. Or suppose the room assignment for an event shifts two days out. Seating changes do not require re-finalizing the BEO at all — that boundary is covered in floorplan changes after a BEO is final.

A short summary for the wall

• Read the BEO for one event's real detail: guest count, room, run of show.
• Read the pre-shift note for tonight's shape: specials, 86 list, which private events are on.
• Never mark up a BEO cover page by hand.
• Expect the pre-shift note to read differently the next day.