Banquet Event Orders (BEOs): the operational document that runs the room

A BEO is an internal operations document that captures every detail of a single event: time, room, headcount, menu, beverages, AV, staffing, setup style, billing, and any client-specific requests. It is generated by the planner or sales coordinator after the contract is signed, then circulated to every department that has to deliver something on the day.

It is not a quote (that's the proposal), not a contract (that's the signed agreement), and not a public-facing run sheet (that's a stage-by-stage timeline aimed at the show crew). The BEO is the bridge — sales hand it to ops, ops execute it, and finance settles against it.

Templates vary by venue and segment, but a usable BEO covers the same eight blocks regardless of whether the event is a 60-pax wedding, a 400-pax gala or a multi-day corporate offsite.

• Event header — date, room, event type, BEO number, version and last-updated stamp.
• Client & contact — billing entity, on-site contact, after-hours number.
• Timeline — bump-in, doors, service, speeches, last drinks, bump-out.
• Setup & layout — floor plan reference, table count, setup style (theatre, cabaret, banquet, cocktail), staging.
• Food & beverage — menu by course, dietaries by guest, bar package, consumption vs package billing.
• AV & production — gear list, technician calls, power requirements, comms.
• Staffing — front-of-house, bar, kitchen, security, supervisor, call times.
• Billing & notes — final pricing, deposits taken, balance due, special instructions, approvals.

Headcounts move, dietaries trickle in, and the kitchen needs a final number 48 hours out to order produce and roster commis. Every change to F&B has a knock-on cost, which is why most disputes after an event start in this section of the BEO. A BEO that captures dietaries per-guest (rather than as a free-text note) is the version that survives an audit on a 300-pax night.

The point of the BEO is that one document drives every department, but each reader scans for different things:

• Kitchen — cover count, courses, dietaries, service times.
• Floor / banqueting — setup style, table plan, service flow, staffing.
• Bar — package vs consumption, cellar pull, last drinks.
• AV / production — gear, calls, power, run order.
• Finance — billed items, deposit position, post-event variances.
• Client-facing planner — the one accountable for any field on the document.

A BEO is the master record for a single event. A run sheet is a minute-by-minute timeline derived from the BEO, used by the floor and stage crew during service. A production schedule is the multi-day, multi-event view that shows bump-in, rehearsals, show, and bump-out across crews and rooms. They're related, but you don't substitute one for another — the BEO is what gets signed off; the run sheet and production schedule are how it's delivered.

Most teams still build BEOs in Word or Google Docs, copying last week's file and editing every field. That's where errors creep in — a stale headcount, an old menu line, a setup style that doesn't match the floor plan attached. Modern event-ops platforms generate the BEO from the same record that holds the contract, the menu, the gear list and the staffing, so a change in one place updates the document everywhere it appears.

Cadence Ops models the BEO as a live view across an event's data — client, timeline, F&B, AV kit, crew, costs — rather than a separate document that has to be kept in sync. Print or PDF when the venue still wants paper; share a link when the kitchen and bar want the latest version on a tablet at service.