If you work weddings or corporate events, sooner or later a venue coordinator will ask for "the BEO" — and if you've never written one, it's not obvious what they want. This guide covers what a banquet event order is, what goes in one, and gives you a free template you can copy into your next event. No signup required.
What Is a Banquet Event Order?
A banquet event order (BEO) is the single document that tells everyone working an event exactly what was agreed: the menu, the room setup, the timeline, the headcount, and who's responsible for what. Venues, caterers, and hotels treat the BEO as the operational source of truth — the kitchen cooks from it, the banquet captain sets the room from it, and billing reconciles against it.
BEO stands for "banquet event order." You'll also hear "banquet event order form" or just "event order." Despite the word banquet, BEOs aren't only for banquets — venues use them for weddings, conferences, galas, corporate dinners, and anything else with catering and a room setup.
The BEO's job is simple: kill ambiguity. If the couple was promised passed hors d'oeuvres at 6:30 and a champagne wall, the BEO is where that's written down so the people executing the event — most of whom never talked to the client — get it right.
Who Prepares the BEO?
Usually the venue's catering or event manager drafts the BEO, then the client (or their planner) reviews and signs it. If you're an independent event planner, you'll spend a lot of time reviewing BEOs — checking them against what your client actually bought — and occasionally writing your own event orders for vendors when the venue doesn't provide one.
That review step matters more than it sounds: the most common (and expensive) BEO failure is drift between what the client accepted in the proposal and what made it onto the BEO. Headcount changed twice, the upgraded linens got dropped, the vegan meals doubled — and nobody reconciled the documents.
What Goes in a Banquet Event Order
Every venue formats BEOs differently, but a complete one covers:
- Event header — event name, BEO number, date issued, event date, day-of contacts (client, planner, venue manager) with phone numbers
- Times — vendor access/setup, guest arrival, meal service, last call, hard end, breakdown
- Guest count — guaranteed number, expected number, and the date the final guarantee is due
- Room & setup — rooms in use, floor plan, tables/seating layout, linens, staging, dance floor, AV
- Food & beverage — courses and menu items, service style (plated, buffet, stations, passed), dietary counts, bar package and brands, cake handling
- Staffing — servers, bartenders, captains, coat check, security
- Billing — pricing summary, service charge, tax, deposit received, balance due and due date
- Signatures — client and venue sign-off, so the BEO is the operative agreement for execution
Free Banquet Event Order Template
Copy this structure into a document, or adapt it to your own layout. It's the same skeleton hotel and venue BEOs use:
| Section | Field | Details |
|---|---|---|
| Header | Event name / BEO # | |
| Event date | ||
| Client contact (day-of phone) | ||
| Planner contact (day-of phone) | ||
| Venue contact (day-of phone) | ||
| Times | Vendor setup access | |
| Guest arrival | ||
| Meal service begins | ||
| Bar last call | ||
| Event end / breakdown complete | ||
| Guests | Guaranteed count | |
| Final guarantee due date | ||
| Room | Room(s) / floor plan | |
| Table layout & seating | ||
| Linens / decor notes | ||
| AV & staging | ||
| Food & beverage | Menu (by course) | |
| Service style | ||
| Dietary counts (veg / vegan / GF / allergies) | ||
| Bar package & brands | ||
| Cake / dessert handling | ||
| Staffing | Servers / bartenders / captain | |
| Billing | Subtotal / service charge / tax | |
| Deposit received | ||
| Balance due + due date | ||
| Sign-off | Client signature + date | |
| Venue signature + date |
Two tips that save real pain: give every revision a version number (BEO #1042-v3) so nobody executes from a stale copy, and bold anything that changed since the last version.
BEO Example (Filled In)
Here's what the core of a real BEO looks like for a 150-guest wedding reception:
BEO #2214-v2 — Rivera/Chen Wedding Reception · Saturday, Oct 17, 2026 Times: Vendor access 12:00 PM · Guests 5:30 PM · Dinner 7:00 PM · Last call 10:30 PM · Out by 12:00 AM Guests: 150 guaranteed (final guarantee due Oct 7) · 12 vegetarian, 4 gluten-free, 2 allergies (shellfish) Room: Grand Ballroom · 15 rounds of 10 · ivory linens, gold chargers · dance floor 20×20 · uplighting (12, warm amber) F&B: Plated — burrata & heirloom tomato / choice of short rib or miso salmon / wedding cake (outside vendor, cake-cutting included) · Premium bar package, champagne toast at 8:00 PM Staffing: 12 servers, 3 bartenders, 1 captain Billing: $21,400 subtotal · 22% service charge · deposit $8,000 received · balance due Oct 10
Every number in that block came from somewhere — the proposal the couple accepted. Which brings up the real workflow question.
How to Create a Banquet Event Order (Without Re-Typing Everything)
The honest answer: a BEO is a derivative document. Everything in it — menu, counts, times, pricing — was already agreed somewhere else: in the quote your client accepted and the contract they signed. Creating a BEO is mostly an exercise in transcribing those decisions accurately.
So the practical steps:
- Start from the accepted proposal, not from memory. Line items, quantities, and prices should transfer exactly.
- Add the operational layer — times, room setup, staffing — that a client-facing proposal doesn't carry.
- Version it every time anything changes, and re-issue to everyone executing.
- Reconcile before the final guarantee date: proposal vs. BEO vs. invoice. Discrepancies found ahead of the event are conversations; discrepancies found after are disputes.
This is where most BEO mistakes are born: the proposal changed (the couple upgraded the bar, cut the late-night snack) and the BEO didn't follow. If your quoting tool keeps version history on every quote revision and locks what the client accepted, step 4 becomes a five-minute check instead of an archaeology dig. That's the part QuotePilot handles — we're a quoting and proposal tool, not a BEO generator, but the accepted, versioned proposal it maintains is exactly the source document your BEO transcribes. Add a photo-rich designed proposal and your client sees the same line items your BEO will inherit.
Need the client-facing document first? Our free proposal generator builds one in the browser — no signup — and the invoice generator does the same for the billing side.
BEO vs. Proposal vs. Contract
Three documents, three jobs — planners get burned when one tries to do another's job:
- The proposal/quote is client-facing: what they're buying and for how much. It's a sales document.
- The contract is legal: terms, cancellation, liability, payment schedule.
- The BEO is operational: instructions for the people executing the event.
The proposal and contract get signed once. The BEO keeps evolving until the final guarantee — which is why it carries version numbers and needs reconciling against the other two before event day.
FAQ
What does BEO stand for? Banquet event order. Some venues call it an event order (EO) or function sheet — same document.
What is a BEO in catering? The instruction sheet the kitchen and banquet staff execute from: menu, counts, service style, timing, dietary needs, and billing for a catered event.
Who signs the banquet event order? Typically the client (or their planner, with authority) and the venue's catering manager. Signature makes it the operative execution document.
When should a BEO be finalized? Venues usually require sign-off 7–14 days before the event, aligned with the final guarantee date for headcount. Changes after that point often incur fees.
Is a BEO legally binding? It's generally treated as an addendum to the catering contract — the contract sets the legal terms, and the signed BEO specifies the deliverables. If the two conflict, that's a problem to fix before the event.
Do I need banquet event order software? For the BEO itself, a well-versioned document is fine at most volumes. The tooling that actually pays for itself sits one step upstream — keeping quotes, revisions, and invoices accurate and in sync, so the BEO you transcribe from is right. That's the job QuotePilot does for event planners.