What Is a BEO? Banquet Event Order, Template & Example

A BEO (banquet event order) is the internal work order for a single event: it turns the signed contract into the exact instructions the kitchen, service team, setup crew and front office need on the day. It lists the timing, room and setup, menu with quantities, beverages, equipment, staffing and billing details, and every department works from the same version.

Hotels and conference venues call it a BEO. Caterers and independent venues more often say function sheet, event order or kitchen sheet. The names differ; the job is the same. This guide explains what goes on a BEO, shows a filled example, walks through the BEO workflow from inquiry to final invoice, and covers the mistakes that cost events their smooth run.

BEO meaning in one minute

• BEO stands for banquet event order. It is sometimes written as "banquet event orders" (plural) when a multi-day or multi-room event has one BEO per function.
• Who writes it: the catering or event sales manager, once the client has confirmed the details.
• Who reads it: executive chef, banquet captain and servers, setup crew, AV, front office and accounting.
• When it is final: usually after the client guarantees the guest count, typically a few days before the event. Changes after that go out as a revised BEO with a new version number.
• What it is not: it is not the contract. The contract is the legal agreement with the client; the BEO is the operational instruction to your own team, although many venues ask the client to sign the BEO to confirm the details.

BEO vs. function sheet vs. run sheet vs. event contract

These four documents get mixed up because they describe the same event. They answer different questions for different readers.

In practice the BEO contains a short timeline, and the run sheet references the BEO for menu and setup. For large events with speeches, entertainment and technical cues, keep a separate run sheet; our event run sheet templates show the format.

What goes on a BEO: the checklist

A complete BEO answers every question a department might otherwise call sales about. Use this as a checklist.

1. Header and event facts

• BEO number and version (for example BEO 1042, revision 3), date issued
• Event name, type (wedding, conference lunch, gala) and client or company
• On-site contact with phone number, plus the internal sales or event manager
• Date, room or rooms, and the event window including setup and teardown
• Expected, guaranteed and set guest count

2. Timeline

• Setup complete, doors, reception, seating, each course or break, speeches, end of service, teardown
• Deliveries and vendor arrival times

3. Room setup

• Setup style (banquet rounds, classroom, theater, U-shape, cocktail)
• Number of tables and chairs, head table, stage, dance floor, registration desk
• Linen colors, centerpieces, signage
• A floor plan reference or attachment

4. Food

• Menu items per course or station, grouped in service order
• Quantities per item, derived from the guaranteed guest count
• Service style (plated, buffet, family style, passed canapés)
• Dietary counts: vegetarian, vegan, gluten-free, kosher, halal, and named guests with allergies
• Allergens per dish

5. Beverages

• Package or consumption bar, open and close times
• Brands or wine selections, corkage, toasts
• Non-alcoholic options and coffee service

6. Audio-visual and equipment

• Microphones, projector and screen, lectern, lighting, power for bands or DJs
• Rentals and who delivers and collects them

7. Staffing

• Number of servers, bartenders, captains, chefs and runners with call times
• Staff-to-guest ratio for the service style; see the event staffing guide for benchmarks

8. Billing

• Prices per item or per person, room rental, service charge, taxes
• Deposits received, balance due, payment method, billing contact
• How add-ons on the night will be recorded and charged

9. Notes and signatures

• Special requests, VIPs, security, accessibility needs
• Client signature confirming the BEO, if your venue uses one

BEO example: a filled banquet event order

Here is a compact example for a corporate dinner. Real BEOs are often longer, but the structure is the same.

Two details make this BEO usable: every food line carries a quantity the kitchen can produce against, and every change since revision 1 is visible in the version number. Prices and names above are illustrative.

Who uses BEOs

Hotels

The BEO is the backbone of hotel banqueting. The catering sales team issues it, the weekly BEO meeting walks through upcoming events with the chef, banquet manager, AV and front office, and revised BEOs are redistributed when details change. Guest rooms usually sit in the property management system; the BEO covers everything that happens in the function space. The full process from inquiry to invoice is covered in our hotel banquet planning guide.

Event venues

Wedding venues, conference centers and private-event spaces use BEOs to hand events from sales to operations, especially when several events run in different rooms on the same day.

Caterers

Off-premise caterers often call it a function sheet or event order and add what a hotel takes for granted: load-in times, vehicle and route, equipment packing lists and the site contact at an unfamiliar venue. The kitchen side usually spins off a separate production list from the BEO.

Restaurants with private dining

Restaurants selling group dinners and buyouts use a lighter BEO: set menu, headcount, room, deposit and timing, so the kitchen can prep without disrupting regular service.

The BEO workflow: from inquiry to final invoice

1. Inquiry. Date, guest count, event type and budget come in by form, email or phone. Check room availability before anything else.
2. Proposal. Menu options, room, packages and pricing go to the client. See catering quote examples for formats that convert.
3. Contract and deposit. The client signs and pays a deposit. The date and room are now definite.
4. BEO. Once menu, timing and setup are chosen, sales turns the contract into the BEO and distributes it to all departments.
5. Changes and guarantee. The client adjusts details; each change produces a new BEO revision. The guaranteed guest count usually locks a few days before the event.
6. Event day. Kitchen produces, service executes, the captain records add-ons such as extra bar hours or additional guests.
7. Final invoice. Accounting bills the guarantee or actual count, whichever applies, plus add-ons, minus deposits.

The weak points are steps 5 and 7. A change that reaches sales but not the kitchen, or an add-on that the captain notes on paper but accounting never sees, is where money and goodwill are lost.

Common BEO mistakes

• No version control. Three printouts of different revisions in the kitchen, at the bar and in the office. Always print the revision number and date on every page, and collect old copies.
• Quantities left to the kitchen. "Buffet for 120" is not a production instruction. Write the quantity per item, and resolve packages into their components.
• Dietary needs as a footnote. Allergies belong next to the dish and the seat, not in a notes field at the bottom.
• Timeline missing setup and teardown. The setup crew and the next event in the same room need these times more than the client does.
• Billing terms unclear. Guarantee vs. actual count, service charge and add-on rates must be on the BEO so the final invoice matches what was agreed.
• Late changes by phone. A change the chef hears about on the phone but that never makes it into a revised BEO will be missed by someone else.

Digital BEOs and BEO software

Most BEOs still start life as a Word or Excel template copied from the last event. That works until the details start moving: every guest-count change means recalculating quantities by hand, re-sending the file and hoping everyone threw away the old copy. With several events a week, the spreadsheet becomes the error source.

BEO software solves this by generating the BEO from the booking itself. When the proposal, the booked menu, the room and the guest count live in one record, the BEO is a live view of that record rather than a separate file. Change the guest count and the quantities, staffing and invoice change with it; share a link and everyone sees the current version.

In Univents, for example, the function sheet is built automatically from the booked items, grouped by category in service order with quantities per line, stays editable for wording, exports as a print-ready PDF and can be shared with the kitchen or outside partners through a link that needs no login. The same booking feeds production and packing lists and staff scheduling.

If you are comparing tools, the banquet software guide covers hotel and venue systems with BEO management, and best catering software 2026 compares 12 catering platforms side by side.

Free BEO template

If you are not ready for software, start with a clean template. Our free BEO template contains every section from the checklist above: header with version number, timeline, setup, food with quantities and allergens, beverages, AV, staffing, billing and notes. Fill it in once per event and print the revision number on every page.

Frequently asked questions

What does BEO stand for?

BEO stands for banquet event order. It is the internal work order for a single event that tells the kitchen, service, setup, AV and accounting teams exactly what to deliver, where and when, based on the signed contract with the client.

What is a BEO in a hotel?

In a hotel, the BEO is the document the catering sales team issues for every function in the meeting and banquet space. It covers the room setup, timing, menu, beverages, AV, staffing and billing, and is reviewed in the weekly BEO meeting with the chef, banquet manager and other departments.

What is the difference between a BEO and a function sheet?

None in substance. BEO is the hotel and banquet term; caterers and independent venues usually call the same document a function sheet, event order or kitchen sheet. Caterers' versions often add logistics such as load-in, vehicles and packing lists.

Is a BEO a contract?

No. The contract is the legal agreement with the client covering price, minimums, deposits and cancellation terms. The BEO is the operational instruction to your own team. Many venues ask the client to sign the BEO to confirm the details, which makes it part of the paper trail but does not replace the contract.

What should be included on a BEO?

A BEO should include the event facts and version number, contacts, date and room, guest counts, a timeline including setup and teardown, room setup, menu items with quantities and allergens, dietary counts, beverages, AV and equipment, staffing with call times, billing terms, and special notes.

Who prepares the BEO?

The catering or event sales manager usually prepares the BEO after the contract is signed and the client has chosen the menu and setup. In connected systems, the BEO is generated automatically from the booked items and updated whenever the booking changes.

When is a BEO finalized?

A BEO is finalized once the client guarantees the guest count, typically a few days before the event, depending on the venue's policy. Changes after that are issued as a revised BEO with a new version number and redistributed to every department.

What is BEO software?

BEO software generates banquet event orders from the booking instead of from a copied template. Menu, room, guest count and pricing live in one record, so a change updates the BEO, quantities, staffing and invoice together, and everyone works from the current version through a shared link.

Next step

Take your last three events and check them against the checklist above: where did the kitchen or service have to call sales for an answer? Those gaps are what your BEO template should close first. If you want the BEO to build itself from the booking, try Univents free for 7 days, no credit card required.