What a great BEO actually contains

Every event that goes wrong in service went wrong on paper first. The banquet event order — the BEO — is where sales' promises become the kitchen's plan, and most of the friction between the two teams traces back to a BEO that was vague, stale, or missing the one number that mattered.

Here is what a complete BEO contains, and the habits that keep it true.

What is a BEO?

A banquet event order is the single internal document that tells everyone working an event exactly what was sold: the timeline, the room and its setup, the menu with counts, the beverage plan, the staffing, and the money. It is written by the sales side and executed by the kitchen and floor. If the proposal is the promise to the guest, the BEO is the contract between sales and service.

Who is the BEO for?

The people running the night: the chef, the sous who actually cooks the party, the floor manager, the lead server, and the bar. It is an internal document — the guest never sees it. That means it should be written in the kitchen's language, with counts and times, not marketing prose.

One BEO, one event, one version everyone holds. The failure mode is three photocopies with three different guest counts.

What sections does a complete BEO contain?

1. The header. Event name, date, location and room, service start and end, the salesperson who owns it, and the on-site contact with a phone number that will be answered during service.
2. The timeline. Every time that matters: vendor load-in, staff briefing, guest arrival, each course or station, toasts or speeches, last call, guests out, breakdown. Times drive the kitchen; write all of them.
3. The room and setup. Layout, table count and shape, linen, place settings, AV, and anything unusual — the cake table, the gift table, the band's footprint.
4. The menu, with counts. Each course, each choice within it, and the count per choice. Guaranteed count and final count, clearly labeled — and the date the final count locks.
5. Allergies and dietary needs, by seat or by name. "Two vegetarians" is a guess; "Seat 12, Rivera, celiac" is a plan. This section has the highest stakes on the page.
6. The beverage plan. Open bar, listed pairings, or consumption — and what happens when the host's limit is reached, so the decision is made before service, not during it.
7. Staffing. Counts per role and call times. The floor manager should staff from the BEO, not from memory of similar parties.
8. The money summary. Contracted total, deposits received, balance due, and how the balance is settled. Service sees what was paid for; billing sees what was served.
9. The change log. What changed since the last version, dated. This is the section that ends the "nobody told the kitchen" conversation.

What do kitchens say is usually missing?

Ask any chef who works events and the same answers come back:

• Final counts that arrive after ordering. The final count is a deadline for the guest, and the BEO should show the date it locks.
• Allergies without names or seats. The information exists at booking; it gets lost in transcription.
• Times for everything except the food. The BEO says 7:00 PM dinner and nothing about the twenty-minute toast planned between courses.
• Changes that never reach the printed copy. The account manager agreed to a champagne upgrade on Tuesday; the pass finds out Saturday.

Each of these is a versioning problem, not a talent problem.

When should the BEO be finalized and reissued?

Publish the first version the day the contract is signed, and reissue it on every change, however small, with the change noted and dated. The dangerous document is not the early draft — everyone knows it is a draft — but the stale "final" that one person quietly annotated.

This is why the BEO should be generated from the booking itself rather than maintained by hand. When the guest count, the menu, and the payments live in one system, the BEO is a view of the truth, not a transcription of it — every edit lands in the next printed version automatically. That is how Excellent builds them; you can see a BEO come together in the demo.

Does the BEO replace the pre-shift briefing?

No — it feeds it. The BEO is the reference; the briefing is where the floor team hears the three things that make this party different and asks questions. A team that briefs from a great BEO sounds coordinated to the guest because it is. How groups run that briefing consistently across locations is its own subject — we cover it in Training a fine-dining floor team across locations.

The short version

• One BEO per event, versioned, with a dated change log.
• Header, timeline, room setup, menu with counts, allergies by name, beverage plan, staffing, money summary.
• Final-count deadline printed on the document.
• Reissue on every change; never annotate by hand.
• Generate it from the booking so it cannot drift from the truth.