If you've ever handed a chef a printed contract and a napkin sketch of a floor plan on event morning, you already understand the problem this document solves. So what is a BEO? A banquet event order, usually just called a BEO, is a single working document that spells out every detail of a catered event, guest count, menu, room setup, timeline, staffing, AV, and billing, so your kitchen, servers, bartenders, and venue staff are all reading from the same page instead of piecing it together from texts and memory.
The BEO is standard practice across hotel banquet departments, catering companies, and event venues for one reason: it moves the details that live in a client's head and a sales email into a format the operations team can actually execute. A caterer running three events on the same Saturday cannot rely on remembering which one wanted chiavari chairs and which one wanted a taco bar closing at nine. The BEO carries that weight instead. It is also the document that most exposes the gap between a caterer still stitching this together in Word and Excel each week and one working from a system built for it.
What Is a BEO, Exactly?
A BEO, short for banquet event order, is the operational blueprint for a single catered event. It is not marketing material and it is not a legal contract, though it pulls facts from both. Think of it as the answer to a very specific question your staff will ask on event day: what exactly are we setting up, cooking, serving, and tearing down, and in what order.
The term comes out of hotel banquet and convention service, where a property might run a wedding, a corporate luncheon, and a nonprofit gala in three different ballrooms on the same afternoon. Independent caterers, planners, and small venues have adopted the same document because the underlying problem is identical at any scale: once details exist only in a phone call or a string of emails, something gets missed.
- Also called an event order, function sheet, or banquet order depending on the venue or region
- Typically one to three pages per event, often with a floor plan or diagram attached
- Built from the proposal and contract, but finalized closer to the event once headcount is locked
- Read by the kitchen, the floor, the bar, and any outside vendor touching that event
What Goes on a Banquet Event Order
A complete BEO reads like a script for the day, starting with the basics: client name, event type, date, arrival and end times, guest count, and the guaranteed minimum you'll bill against. From there it moves into the room, specifying the setup style, such as banquet rounds of ten, cocktail rounds, theater rows, or a head table with a dance floor, along with linens, chair type, and any staging or podium placement.
The menu section is where a BEO earns its keep. It lists food by course and by kitchen-facing name, not the pretty language from the proposal, plus the bar package, service style (plated, buffet, family style, stations), and dietary counts by number of guests, not a single footnote. A working timeline, a staffing plan, and a short billing snapshot round out the rest, so a captain can run the floor without ever needing to call the office.
- Event basics: client, event type, date, start and end times, guest count and guarantee
- Room and setup: table style and count, linens, chairs, staging, dance floor placement
- Menu and service: courses or stations with kitchen-facing names, bar package, service style
- Timeline: load-in, cocktail hour, meal service by course, program moments, breakdown
- Rentals and AV: microphones, projector and screen, uplighting, chargers, specialty rentals
- Dietary flags: gluten-free, vegan, nut allergy, and kids' meal counts by number, not a note
- Billing snapshot: deposit received, balance due, service charge, gratuity, payment terms
Who Creates a BEO and Who Reads It
The caterer or event manager typically drafts the first version once a client has signed the contract, pulling numbers straight from the proposal so nothing gets re-keyed and re-guessed. For an off-site caterer working inside someone else's venue, the venue's own coordinator often reviews or co-signs the BEO to confirm it matches their room rules, load-in access, and any in-house restrictions on candles or outside alcohol.
From there the document fans out. Chefs use it to build prep lists and plating counts. Banquet captains and servers use it to run the floor without improvising. Bartenders use the bar section to know what to pour and when last call is. Rental and AV vendors check their delivery window and equipment list against it before a truck ever leaves the warehouse.
- Caterers and catering sales managers draft the BEO from the signed proposal and contract
- Chefs and kitchen staff use it for prep, plating counts, and course timing
- Banquet captains and servers run the floor and the timeline from it
- Venues cross-check it against their own room diagrams and house policies
- Rental and AV vendors confirm delivery windows and equipment lists against it
BEO vs. Proposal, Contract, and Invoice
These four documents cover four different moments in the same booking, and mixing them up is a common source of confusion for anyone new to catering paperwork. The catering proposal is the sales document, built to win the booking, showing menu options, packages, and pricing before anything is signed. The contract locks in the catering contract terms once the client commits: deposit amount, cancellation policy, liability language, and signatures from both sides.
The BEO comes next and is purely operational, the play-by-play your team runs on the day itself, finalized once the guest count is guaranteed. The invoice closes the loop afterward, reconciling the deposit against add-ons, gratuity, and the final balance. A lot of small operators end up retyping the same guest count and menu into four separate Word and Excel files across these stages, which is exactly the kind of duplicate work a shared client and event record is built to eliminate.
- Proposal: what you're offering and what it costs, used to win the booking
- Contract: deposit, cancellation policy, liability terms, signed by both parties
- BEO: the operational play-by-play your team executes on event day
- Invoice: the final bill reconciling deposits, add-ons, and balance due
How a BEO Gets Written
Most caterers writing a banquet event order start from the signed contract and proposal so the guest count, menu, and pricing already match rather than being re-typed by hand. From there, the guaranteed guest count gets confirmed with the client by the deadline in your contract, often 72 hours out for hotel banquet teams and 5 to 7 business days for independent caterers who shop and prep, since that number sets how much food gets ordered and prepped.
The menu gets written out course by course, station by station, with real dish names instead of package labels, and the timeline gets built in actual minutes rather than loose blocks like dinner around seven. Once every section is filled in, the document goes out to the kitchen, floor staff, and any outside vendor, and it gets locked so a last-minute edit doesn't create two conflicting versions floating around on event day.
- Start from the signed contract and proposal so the numbers already match
- Confirm the final guaranteed guest count by your contract's deadline, commonly 72 hours to 7 business days out
- Write the menu by course or station with real dish names, not package labels
- Build the timeline in actual minutes, not vague blocks like dinner around seven
- Attach a floor plan for any room with more than one setup zone
- Distribute the finalized version to every vendor and staff member, then lock it
Common BEO Mistakes That Cause Day-Of Problems
The most frequent failure is a mismatch: the BEO shows one guest count while the kitchen preps to a different one because the guarantee got updated by text message and never made it back onto the document. A close second is a menu section that lists only the package name, leaving the kitchen guessing at sauces, sides, or the client's actual entree split.
Timelines cause just as much trouble when they're built too loosely, with no buffer between cocktail hour and dinner service, so the room never gets flipped in time. And in shops still working out of Word or Canva, it's common for three slightly different copies of the same BEO to be circulating between an email thread, a printout on the truck, and whatever version the chef has taped to the cooler, none of them clearly marked as final.
- Guest count on the BEO doesn't match the confirmed guarantee, so the kitchen preps wrong
- Menu listed by package name only, with no detail on sauces, sides, or substitutions
- Allergy and dietary counts missing or buried in an email instead of on the document itself
- No buffer time built between cocktail hour and dinner service, so the room never turns
- Multiple slightly different versions circulating with no single one marked final