The short answer
A BEO, or banquet event order, is the operational document that spells out every detail of a single catered event: guest count, menu, room setup, timeline, staffing, rentals, and billing. The caterer or venue writes it once the booking is confirmed, then distributes it to the kitchen, floor, bar, and outside vendors so everyone works from the same numbers.
If you have 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. A banquet event order, usually just called a BEO, is a single working document that spells out every detail of a catered event, 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.
This guide covers what a BEO is, every section that belongs on one, how it differs from the proposal and contract it comes from, when it gets written and locked, and the numbering conventions that keep the wrong version off the pass.
Key takeaways
- A BEO is operational, not contractual. It tells your team what to do; the contract is what the client agreed to pay for.
- It is written after the booking is confirmed and finalized once the guaranteed guest count is in, commonly 72 hours to 7 business days out.
- Everything that costs money or takes time belongs on it: menu, setup, timeline, staffing, rentals, AV, and dietary needs as counts.
- Every version needs a BEO number and a revision marker, or the kitchen will eventually cook from the wrong sheet.
- Event order, function sheet, and banquet order all refer to the same document. The name changes by property, the job does not.
What Is a BEO, Exactly?
A BEO 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 simple question asked by everyone working that day: what am I supposed to do, when, and for how many people?
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. Every function needed one sheet that the kitchen, the banquet captain, the bar, and the AV tech could each read and act on. Independent caterers and off-premise operations adopted the same document because the problem is identical once you are running more than one event at a time.
The distinguishing feature of a BEO is that it is written for execution, not persuasion. A proposal describes a beautiful evening. A BEO says 180 guests, 14 rounds of 10 plus a head table of 12, salad plated at 7:15, entree counts 96 beef and 72 salmon and 12 vegan, bar closes at 10:45. Same event, completely different register.
- Usually one to three pages per event, often with a floor plan or diagram attached
- Built from the signed proposal and contract, then finalized once the headcount is locked
- Read by the kitchen, the floor, the bar, and any outside vendor touching that event
- Reissued with a new revision number whenever a material detail changes
BEO, Event Order, Function Sheet: The Same Document
One reason this document confuses newcomers is that it goes by different names depending on where you trained. They all describe the same artifact, and you will hear several of them in the same conversation if the room has people from hotels and independents both.
If you are hunting for a template and only finding results under a different name, this is why. Pick the term your team already uses and stay consistent, because the value of the document depends on everyone knowing which sheet is the sheet.
| Term | Where you will hear it | Notes |
|---|---|---|
| Banquet event order (BEO) | Hotels, convention centers, country clubs | The most common formal name, and the one most software uses |
| Event order (EO) | Restaurants and smaller venues | Same document, shorter name, common where there is no banquet department |
| Function sheet | UK and Commonwealth properties, some US hotels | Traditional hotel term, occasionally covering a whole group's functions |
| Banquet order | Older hotel operations | Interchangeable with BEO |
| Catering order form | Drop-off and corporate catering | Leans toward the order itself rather than the full operational plan |
| Run of show or run sheet | Production and event planning | Related but narrower: the minute-by-minute timeline only, no menu or billing |
What Goes on a Banquet Event Order
A complete BEO reads like a script for the day. The rule of thumb is simple: if it costs money or takes time, it belongs on the document. If it lives only in an email thread, it will be missed.
The table below is a section-by-section reference. Not every event needs every row, but a BEO that skips several of these is usually the one that generates the panicked phone call at 4pm.
| Section | What goes in it | Who leans on it most |
|---|---|---|
| Header | BEO number, revision, event date, business or property name | Everyone, for version control |
| Client and contacts | Client name, on-site contact and mobile, planner, billing contact | Captain, sales manager |
| Event basics | Event type, date, start and end times, venue and room | Everyone |
| Guest count | Expected count, guaranteed count, and the set-for number | Kitchen, captain |
| Timeline | Load-in, doors, cocktail hour, each course, program moments, last call, breakdown | Captain, kitchen, bar, AV |
| Menu | Courses or stations with kitchen-facing dish names, counts per selection | Kitchen |
| Dietary and allergens | Restrictions as counts, plus how each is plated and flagged | Kitchen, captain |
| Bar and beverage | Package, brands, service window, bartender count, cash or hosted | Bar |
| Room setup | Table style and count, linens, chairs, staging, dance floor, floor plan reference | Setup crew, venue |
| Rentals and AV | Specialty rentals, microphones, screens, uplighting, delivery and pickup windows | AV, vendors |
| Staffing | Roles, counts, call times, and out times | Manager, payroll |
| Vendor list | Photographer, band, florist, cake, with arrival times | Captain |
| Financial summary | Subtotal, service charge, tax, deposits received, balance due | Sales, accounting |
| Notes | Anything unusual: access quirks, house rules, client sensitivities | Everyone |
BEO vs Proposal, Contract, and Invoice
These documents cover different moments in the same booking, and mixing them up is a common source of confusion for anyone new to catering paperwork. They share data, but they are written for different readers and they do different jobs.
The practical consequence: never send a client a BEO when they asked for a quote, and never let your kitchen work off a proposal. The catering proposal sells, the contract binds, the BEO executes, and the invoice collects.
| Document | Answers | When it is written | Signed? |
|---|---|---|---|
| Proposal | What are you offering and what does it cost? | After the inquiry, before the booking | No |
| Contract | What did both parties agree to, including deposit and cancellation? | To confirm the booking | Yes, by both parties |
| BEO | What exactly happens on the day, and for how many? | After booking, finalized at the guarantee | Sometimes, to confirm details |
| Invoice | What is actually owed now? | After the event, or per the payment schedule | No |
| Run of show | What happens minute by minute? | Alongside the BEO for complex programs | No |
When a BEO Gets Written, Revised, and Locked
A BEO is not a one-and-done document. It has a life cycle, and most of the pain in catering operations comes from treating it as if it does not.
The first draft usually appears once the contract is signed, built directly from the proposal so the menu and pricing already match rather than being re-keyed and re-guessed. From there it absorbs changes: the client adds a dessert station, the room changes, the ceremony moves outdoors. Each of those should produce a new revision, not a quiet edit to a file someone else has already printed.
The pivotal moment is the guarantee. Most contracts require the client to confirm a final guaranteed guest count some fixed number of days before the event, commonly 72 hours to 7 business days. That number is what you bill against and what the kitchen preps to, and many operations then set the room for the guarantee plus a small percentage. Once the guarantee is in, the BEO gets finalized and distributed, and further changes become exceptions rather than routine.
After the event, the BEO becomes the reference for reconciling the invoice: what was actually served, what was added on the day, whether staffing ran over. Keeping the final revision filed with the event is what makes that reconciliation a five-minute job instead of an argument.
- Draft: created from the signed contract and proposal, as soon as the booking is confirmed
- Revisions: reissued each time a material detail changes, with a new revision marker
- Guarantee: final guest count confirmed in writing, commonly 72 hours to 7 business days out
- Final: distributed to kitchen, floor, bar, and outside vendors, then locked
- Post-event: filed with the event and used to reconcile the final invoice
Numbering and Revision Control
This is the part most template downloads leave out, and it is the part that prevents the worst failure mode in catering operations: two versions of the same BEO in circulation, with the kitchen holding the old one.
Every BEO should carry a unique number and a revision marker in the header, on every page. The number identifies the event, the revision identifies which version of the truth you are holding. A common convention is a sequential number per event, sometimes prefixed by year, with revisions as R1, R2, R3. When you reissue, the revision goes up and the old version comes out of circulation.
The second half of the discipline is distribution. When a revision goes out, it goes to everyone who had the previous one, with a one-line note on what changed. Sending a fresh PDF with no indication of what moved means people will assume nothing did, and skim it.
- Put the BEO number and revision in the header on every page, not just page one
- Increment the revision on any change to counts, timing, menu, or room
- State what changed when you reissue, so readers know where to look
- Pull or clearly supersede the previous version rather than letting both circulate
- Keep the final revision with the event record for post-event reconciliation
Who Creates a BEO and Who Reads It
The caterer or catering sales manager typically drafts the first version once a client has signed, pulling numbers straight from the proposal. For an off-site caterer or a solo operator, that is the same person who sold the event, which is exactly why a structured document matters: you are handing your own future self a briefing.
From there the document fans out, and different readers care about completely different parts of it. Understanding who reads what is the fastest way to write a BEO that actually gets used rather than skimmed.
- Chefs and kitchen staff: menu, counts per selection, dietary flags, and course timing
- Banquet captains and servers: timeline, room setup, service style, and program moments
- Bartenders: package, brands, service window, and whether it is hosted or cash
- Setup crew: table counts, linens, staging, and the floor plan
- Venue staff: house rules, load-in access, and their own room diagrams to cross-check
- Rental and AV vendors: equipment lists and delivery and pickup windows
- Sales and accounting: the financial summary, for reconciling the final invoice
How a BEO Changes by Event Type
A generic BEO template is a fine starting point and a poor working document, because the sections that matter shift substantially with what you are running. A wedding lives or dies on the run of show and vendor meals. A conference lives on room turns and AV. A drop-off lives on drive time and whether anyone remembered the chafing fuel.
If you are adapting a template, the fastest improvement you can make is to add the two or three sections your event type actually needs and delete the ones it never uses. The downloads below are already split this way.
| Event type | Sections that carry the weight |
|---|---|
| Wedding | Run of show from vendor arrival to send-off, head table, entree counts by selection, cake cutting, vendor meals |
| Corporate or conference | Program blocks with room turns, food and beverage per break, dietary counts, AV and tech, PO and tax-exempt status |
| Off-premise or drop-off | Depart, arrive, and ready as separate times, site power and water, production quantities, load list with a return column |
| Hotel banquet | Multi-function grid, master account and group code, guarantee and set-for percentage, house versus outside AV, labor fees |
| Small or simple event | One page: details, timeline, menu, setup, staffing, totals |
Common BEO Mistakes That Cause Day-Of Problems
Almost every BEO failure traces back to one of a handful of patterns. None of them are exotic, and all of them are cheaper to prevent than to fix at 5pm on a Saturday.
The most frequent is a mismatch between the guaranteed count and what the document says, usually because the guarantee arrived by text and never made it onto a numbered revision. Close behind is the menu written in proposal language, where the kitchen gets "Autumn Harvest Station" instead of the six dishes that make it up. Then there are timelines built too loosely, with no buffer between cocktail hour and dinner, so the room never gets flipped in time.
- Guest count on the BEO does not match the confirmed guarantee, so the kitchen preps wrong
- Menu listed by package name only, with no detail on components, sauces, sides, or substitutions
- Allergy and dietary needs written as prose in an email instead of counts on the document
- No buffer time between cocktail hour and dinner service, so the room never turns
- Multiple slightly different versions circulating with nothing marked as current
- Staffing listed without call times, so people arrive when they think they should
- Load-in and access details missing for off-premise events, where they matter most
Download the free template
A Word version to edit, an Excel version with the line-item math wired up, and a filled-in sample so you can see a finished one. Yours to keep, no signup.
BEO templates by event type
The same document changes shape depending on what you are running. Each of these is laid out for its own job, not renamed from a single file.