Who prepares the BEO?

Usually the salesperson or event/conference services manager who owns the client relationship, in consultation with culinary and AV. It's then reviewed in the venue's weekly BEO meeting and distributed to every department involved.

When should a BEO be finalized?

Common practice is to distribute the first version 10–14 days out and lock F&B guarantees 72 hours before the event. Equipment and crew lines should be locked earlier — as soon as they're reserved — because gear and people, unlike menus, can be claimed by other events.

Is a BEO the same as an invoice or a contract?

No. The contract is the legal agreement, the BEO is the execution spec, and the invoice reconciles what actually happened — final counts, on-consumption bar, overtime. A clean BEO with per-line pricing makes the invoice a formality instead of a dispute.

What software do venues use for BEOs?

Sales-and-catering tools generate the document itself. The gap they leave is operational: reserving the actual equipment and crew behind each line. Venues that run gear-heavy events pair BEOs with rental-operations software like Filmo, where rooms, inventory and staff sit in one calendar with live availability.

Resources · Blog/May 19, 2026·7 min read

Banquet Event Order (BEO): What It Is + Free Template

The BEO is the single document your banquet, kitchen, AV and setup crews execute from. Here's what belongs in it, how to keep it honest — and a template to copy.

A banquet event order (BEO) is a one- or two-page document that tells everyone involved in an event — banquet captain, kitchen, AV techs, setup crew, billing — exactly what was sold and how to execute it: date and times, room and setup style, menu and service, equipment, staffing and payment terms. It's the contract's operational twin: the client signs the contract, the teams run the BEO.

What is a banquet event order?

Hotels, conference centres and standalone venues all run on the same principle: the person who sold the event is not the person executing it. The BEO is the handover. When it's complete, the banquet team sets the room without calling sales, the kitchen fires courses on schedule, and the AV tech knows which microphones go where. When it's vague, every department improvises — and the client watches them do it.

A BEO is written per event, per day. A three-day conference with a welcome reception, two plenary days and a gala dinner is at least four BEOs, usually numbered and reviewed together in the weekly BEO meeting between sales, banquets, culinary and AV.

What goes into a BEO?

Section	What it covers
Event header	BEO number, event name, client and on-site contact, salesperson, date issued and revision number
Schedule	Access/setup time, doors, service times course by course, breakdown deadline
Room & setup	Which space, setup style (banquet rounds, theater, U-shape…), head count, floor plan reference
Food & beverage	Menu per course, dietary requirements and counts, bar package, service style, tasting notes
AV & equipment	Every item by name and quantity — screens, PA, microphones, stage decks, uplights, power drops — and who supplies each one
Staffing	Banquet servers and captains, chefs and stations, AV techs, setup/strike crew, security — with call times
Billing	Pricing per line, service charge and tax, deposit received, payment terms, master account or on-consumption
Signatures	Client sign-off and the internal distribution list — who gets every revision

How to create a banquet event order

Start from the signed contract or proposal — the BEO operationalises what was sold, it never contradicts it.
Number it and version it. "BEO #214 rev 3" ends arguments; "the latest email" starts them.
Write the schedule backwards from doors: if doors open at 18:00 and the room takes 3 hours to set, setup starts at 15:00 — which decides crew call times.
List equipment by item and quantity, not by vibe. "2× wireless handheld, 1× lectern mic, 1× 4×3m LED wall" — and mark anything sub-rented from a partner.
Attach counts to every dietary line. "Some vegetarians" is how kitchens get burned.
Route it for sign-off: client first, then distribute to banquets, culinary, AV and front desk — every revision, to the same list.
Lock it at an agreed cut-off (commonly 72 hours out for F&B counts) and make late changes expensive enough to be rare.

Free BEO template: the blocks to copy

Recreate these blocks in your document tool or venue software and you have a working BEO. The order matters — it mirrors how teams read it on the day:

Header: BEO # / revision / date issued — Event name — Client + on-site contact & mobile — Salesperson/planner.
Event basics: date, space(s), guaranteed head count vs. expected, setup style.
Timeline table: time | activity | department responsible — from crew access to strike complete.
F&B block: menu per course, per-line counts, dietaries, bar terms, service style.
Equipment block: item | qty | source (house / client / sub-rental) | notes — one line per item.
Staffing block: role | count | call time | cut time.
Billing block: line items, service charge %, tax, deposit, balance due date.
Sign-off block: client signature + date, internal distribution list.

BEO vs. function sheet vs. contract

Document	What it is	Who it's for
Contract	The legal agreement — spaces, dates, minimums, cancellation terms	Client and venue management
BEO	The operational spec for one event on one day — the execution document	Every department working the event
Function sheet	Largely a synonym for BEO (more common in UK/EU hotels); some venues use it as the daily digest of all BEOs in the building	Operations teams

The BEO mistakes that sink event days

AV listed as intentions, not inventory: "projector and sound" on the BEO, while the actual projector is double-booked in the ballroom next door.
No versioning — three revisions circulating at once, and the kitchen executes rev 1 while the client signed rev 3.
Crew missing entirely: the BEO says the room flips from conference to gala in 90 minutes, but nobody booked the six-person turn crew it takes.
Sub-rented equipment with no owner: the LED wall arrives, but nobody agreed who receives it, checks it and sends it back — so it bills for three extra days.
Dietary counts without seats: eight vegan meals confirmed, zero indication of which tables they're on.
The distribution gap: sales updates the BEO on Thursday, banquets prints on Wednesday.

From BEO to execution: closing the operational gap

A BEO is a promise. Whether the venue can keep it depends on questions the document itself can't answer: is that PA free that night, or on another BEO? Which setup crew is on shift? Did the sub-rental get confirmed? That's why venues pair the BEO with an operations system — one calendar where spaces, every piece of equipment and every crew member are booked against real availability, so the event order and reality can't drift apart. The BEO stays the language teams speak; the system makes sure it's true.

Banquet event order FAQs

What is a banquet event order?: A banquet event order (BEO) is the operational document for a single event — schedule, room setup, menu, equipment, staffing and billing on one or two pages. Sales writes it from the signed contract; banquets, kitchen, AV and setup crews execute from it.
Who prepares the BEO?: Usually the salesperson or event/conference services manager who owns the client relationship, in consultation with culinary and AV. It's then reviewed in the venue's weekly BEO meeting and distributed to every department involved.
When should a BEO be finalized?: Common practice is to distribute the first version 10–14 days out and lock F&B guarantees 72 hours before the event. Equipment and crew lines should be locked earlier — as soon as they're reserved — because gear and people, unlike menus, can be claimed by other events.
Is a BEO the same as an invoice or a contract?: No. The contract is the legal agreement, the BEO is the execution spec, and the invoice reconciles what actually happened — final counts, on-consumption bar, overtime. A clean BEO with per-line pricing makes the invoice a formality instead of a dispute.
What software do venues use for BEOs?: Sales-and-catering tools generate the document itself. The gap they leave is operational: reserving the actual equipment and crew behind each line. Venues that run gear-heavy events pair BEOs with rental-operations software like Filmo, where rooms, inventory and staff sit in one calendar with live availability.