BEO basics
What Is a BEO?
BEO stands for Banquet Event Order. If you've never used one, it's the single document that tells your staff exactly what's supposed to happen for a private event - the plan the kitchen, bar, and floor staff all work from on the day itself.
The short definition
A BEO is an internal planning document that lays out everything your staff needs to execute a booked private event correctly: the event timeline, room setup, food and beverage details, staffing assignments, AV or equipment needs, and any special instructions. It's written by the venue, for the venue - the customer typically never sees it.
Think of it as the difference between agreeing to host an event (the contract) and actually knowing how to run it (the BEO). A signed contract tells you the event is happening and what the customer is paying. A BEO tells your bartender what time to start pouring and your kitchen when the entrées need to hit the table.
What a BEO typically includes
- Event name, date, and time, including setup and teardown windows
- Guest count and room or space assignment
- Food and beverage selections, packages, or menus
- A run-of-show timeline: doors open, guest arrival, service start, speeches, last call, teardown
- Staffing notes - who's covering the event and what their responsibilities are
- AV, equipment, or setup requirements (tables, chairs, sound system, decor restrictions)
- Allergies, dietary restrictions, or special requests
- Internal notes for staff only - VIP flags, known issues, manager reminders
How a BEO is different from an inquiry, proposal, contract, and deposit
These are five different documents that show up at five different stages of booking a private event. Confusing them is common if you're new to running private events - here's how they differ:
| Document | Direction | Purpose |
|---|---|---|
| Inquiry | Customer → Venue | The customer's first request: what kind of event, roughly when, roughly how many guests. |
| Proposal | Venue → Customer | The venue's offer: packages, pricing, room, and what's included, sent for the customer to review. |
| Contract | Venue ↔ Customer, signed | The legally binding agreement: price, deposit terms, cancellation policy, both parties' signatures. |
| Deposit / payment record | Customer → Venue | Proof of payment securing the date - a receipt, not a plan for how the event runs. |
| BEO | Internal, venue staff only | The operational plan: exact setup, timeline, food and beverage, staffing, and day-of details. |
The most important distinction: a BEO is not a substitute for a signed contract. A BEO doesn't establish payment terms, cancellation policy, or legal liability - it's an operations document, not a binding agreement. Read more in BEO vs. Event Contract.
When a BEO gets created
A BEO is typically finalized after the contract is signed and the deposit is paid - once the booking is confirmed, not before. It's often built directly from the details already collected during the inquiry and proposal stages, then refined as the event date approaches and specifics (final guest count, menu selections, timeline) are locked in, usually a few days to a week before the event.
Ready to build a BEO?
Use our free copyable template to build your first BEO by hand, or see how VenueSprocket generates one automatically from your event details.
Frequently asked questions
Who writes the BEO - the venue or the customer?
The venue writes it. A BEO is an internal operations document for your staff, not something the customer fills out or signs.
Does every private event need a BEO?
A small, simple booking might not need one. Once multiple staff or departments are involved, a BEO prevents details from getting lost between booking and event day.
Is a BEO a legal document?
No. It's an internal operational document, not a signed legal agreement. Payment and cancellation terms belong in the event contract, not the BEO.