What is a BEO? The banquet event order, explained
A Banquet Event Order — BEO — is the one-page constitution of a catered event: every commitment made to the client, translated into instructions a kitchen, a captain, and a driver can execute without calling anyone. If it's not on the BEO, it doesn't exist.
What a complete BEO contains
- Header: event name, date, BEO number, venue + room, contact with day-of phone
- Counts: guaranteed guest count, expected count, and the guarantee deadline
- Timeline: load-in, setup complete, guest arrival, service start, bar close, breakdown
- Menu: every item with portions and dietary flags — vegan/GF counts as numbers, not vibes
- Service style: plated / buffet / stations / passed, with staffing implications spelled out
- Bar: package, brands tier, hours, who's buying (host vs. cash)
- Setup: floor plan reference, rentals, linens, equipment list
- Money: pricing summary, deposits received, balance due and when
- Special instructions: the cake in the walk-in, the allergy at table 4, the speech at 7:40
Who reads it — and that's the point
Sales writes it, but the BEO is written for the kitchen (what to produce, how much, when), the captain (how the room runs), the client (what they agreed to), and the office (what to invoice). One document, four readers, zero “I thought you meant.”
Version discipline is the whole game
Events change — counts move, the toast moves, the bar package upgrades. The failure mode is a kitchen cooking from Tuesday's BEO while the client approved Thursday's. Rules that prevent it: every change bumps a revision number and a changelog line; the client signs the final revision; the BEO locks at the guarantee deadline(typically 72 hours out); after lock, changes are exceptions with a price, not edits.
In CaterOps the BEO is built from the event rather than typed again: open the event, go to its BEO tab and press New BEO. Each version you send is saved (v1, v2 and so on), the client signs on their own link, and the kitchen's prep list is built from the same BEO on the event's Prep tab, so the two can't disagree.