A Banquet Event Order (BEO) is the shared operational plan that tells your kitchen, floor, bar, and management teams exactly how to prepare and deliver a booked event. It turns client agreements into one current version of guest count, menu, timeline, room setup, staffing, and special requirements—so every department works from the same information on the day.
In restaurants, hotels, and event venues, a BEO is also called an event sheet, function sheet, or event order. Despite the word “banquet,” it applies to weddings, corporate dinners, conferences, private celebrations, and any function that needs more than a calendar booking to run smoothly.
What a BEO includes
A useful BEO answers the same questions every time: what was sold, who is coming, what must happen, when, and who is responsible. Core fields typically include:
Event identity — name/type, date, room or space, start and end times, setup and access windows
Client and day-of contacts — booking contact plus who can decide on the floor during service
Guest counts (three numbers, not one) — contracted minimum, guaranteed final count, and prepared count (guarantee + overage); plus the deadline when the guarantee locks
Package and sold services — what the client bought, plus agreed extras or exclusions
Menu, beverages, and dietary needs — final dishes, service format, portion counts, allergies, substitutions
Operational timeline — setup, staff briefing, guest arrival, courses, speeches/cues, bar close, breakdown
Room setup and suppliers — layout, equipment, AV, delivery windows, external contacts
Staffing and ownership — leads for kitchen, floor, and bar; key tasks with owners and deadlines
Documents, BEO number, and revision — approved menu and floor plan, plus a version ID so kitchen and floor are not working from two different “finals”
Depth can vary by venue size and event complexity. What must not vary is having one place where the current answers live. For a full field-by-field breakdown, see the longer guide: Banquet Event Order for restaurants and venues.
BEO vs event sheet vs contract
In practice, BEO, event sheet, function sheet, and event order usually mean the same operational record. The name changes by region and venue type; the job does not.
They are not the same as a proposal or an event contract:
Document | Job |
|---|---|
Proposal | What the client can buy |
Contract | Commercial and legal terms (deposits, cancellation, liability, payment) |
BEO | How the team delivers what was sold on the day |
They must agree. If a guest-count, price, or concession change is commercial, route it through your contract or change-order process—do not let a new BEO quietly override the deal. Client sign-off on the BEO is useful; the primary readers on the day are still kitchen, floor, bar, and the manager running the room.
Multi-function tip: if the booking includes ceremony, cocktail, dinner, and a room flip, give each function its own times and setup line. One vague “event 4–11pm” block is how resets and staffing get missed.
Three guest counts—and one version
Most day-of arguments about “numbers” are really three different numbers sharing one label:
Contracted minimum — what the client pays for even if fewer people arrive
Guaranteed final count — usually locked a set number of days out (often 48–72 hours; follow your house policy)
Prepared count — guarantee plus your cook/overage buffer (commonly a few percent)
Bill on the prepared count and the client argues. Cook to the contracted minimum and you run out. Put all three on the BEO so kitchen, sales, and finance stop guessing which figure they are looking at.
Dietary and allergen meals belong on the BEO itself—guest or seat, the dish they get, and how the plate is identified in service—not only in an email thread nobody opens on the pass.
Version control matters more than layout polish. Give every issue a BEO number and revision. Issue an early draft when the booking confirms, tighten it about 7–10 days out, then re-issue whenever something material changes. If the kitchen has Tuesday’s sheet and the floor has Thursday’s, you do not have a BEO—you have a dispute waiting to happen.
When a restaurant needs a BEO
You need a Banquet Event Order whenever more than one person must act on the same set of event details—and those details can change.
Typical triggers:
Private dining, weddings, corporate events, or conferences with a multi-stage timeline
Kitchen production that depends on a final menu and accurate headcount
Floor and bar teams that need service format, dietary flags, and timing cues
External suppliers (AV, décor, cake, entertainment) sharing the space with your staff
Multiple events in the same week, or overlapping use of rooms and crew
A small restaurant hosting an occasional group of 20 may keep a lighter record. Even then, one consistent event sheet for guest count, menu, timing, and special requests prevents the “which WhatsApp was final?” problem. As soon as staffing, dietary meals, or room setup become non-trivial, a proper BEO pays for itself. Related reading: how to organize restaurant event operations and how many servers you need for 100 guests.
Who uses the BEO on the day
A BEO only works if the right roles can open the current version during setup and service.
Role | What they use the BEO for |
|---|---|
GM / event or restaurant manager | Overall readiness, client decisions, timeline calls, escalation |
Kitchen | Final menu, portion counts, dietary meals, production and service times |
Floor / service lead | Guest count, seating, service format, course timing, special requests |
Bartenders / bar lead | Beverage package, open/close times, special drink notes, service cues |
The person who signed the contract is often not the day-of decision-maker. The BEO should name who can approve a late guest-count change, a menu swap, or a delayed speech—so the team is not hunting through email while guests are arriving.
Common mistakes
Treating the booking confirmation as the plan — A reserved date and estimated headcount are not enough for production or staffing.
Multiple “final versions — No revision ID; menu in email, layout in a PDF, dietary notes in chat. Departments reconstruct different events.
One headcount field — Mixing contracted, guaranteed, and prepared numbers into a single “covers” line.
Vague dietary notes — “Allergies confirmed” without dish, quantity, and how special plates are identified in service.
No owner for open tasks — “The team will handle it” leaves gaps that only appear during setup.
Freezing the BEO too early—or updating it offline — Changes after “final” still happen; if they land outside the shared record, the floor works from yesterday’s plan.
FAQ
What does BEO stand for?
BEO stands for Banquet Event Order. It is the operational document or digital event record restaurants and venues use to plan and deliver an event.
Is a BEO the same as the event contract?
No. The contract sets commercial and legal commitments. The BEO is the operational delivery plan. They must match; the BEO should not silently rewrite the deal.
Is a BEO only for banquets and hotels?
No. Restaurants, wedding venues, conference spaces, and caterers use BEOs (or event sheets) whenever kitchen, floor, and management must coordinate from one plan.
Who prepares the Banquet Event Order?
Usually the event or restaurant manager coordinating the booking. Kitchen, floor, sales, and bar contribute their sections; one person remains accountable for completeness and currency.
Do you need software to use a BEO?
No. A clear shared document can work for simpler venues. Software becomes useful when guest counts, menus, tasks, and staffing change often and must stay connected without retyping the same details into multiple files.
Next step
If you need the full operational checklist—fields, ownership, update timing, and how a static template reaches its limits—read the complete guide: Banquet Event Order (BEO): what every restaurant and venue should include.
Manage My Restaurants Events is being built so the event itself is the central record: menus, tasks, staff, and documents stay attached to one current plan instead of scattered files. Use it when your team already knows what a BEO should contain—and needs that plan to stay connected as details change.