A banquet event order, usually called a BEO, is the operational document that tells a hotel team how to deliver an event. It connects the commercial promise to the work required in the room, kitchen, banquet operation, AV, engineering, housekeeping, front desk, security, and finance.
The BEO is not simply a menu or a contract summary. It is a controlled execution record: what happens, where, when, for how many people, with which resources, under whose ownership, and according to which approved revision.
What does BEO stand for?
BEO stands for Banquet Event Order. Hotels and venues may use related terms such as event order, function sheet, banquet order, or catering event order. The name varies, but the purpose is similar: coordinate the details needed to execute a meeting, wedding, banquet, reception, conference, or other hosted event.
What is a BEO used for?
A BEO gives departments a shared operating picture. It is used to:
- confirm event date, room, times, setup, and attendance;
- document menus, service style, guarantees, dietary needs, and timing;
- describe layouts, staging, AV, décor, vendors, and access;
- assign owners to setup, service, changes, billing, and escalation;
- communicate approved changes through controlled revisions;
- give the day-of team a source of truth for checkpoints and exceptions.
The BEO should make execution clearer. If a department still has to infer a critical detail from an email or ask which attachment is current, the workflow is incomplete.
BEO versus contract
A contract defines commercial and legal terms such as deposits, cancellation, payment, liability, room-block commitments, and approved remedies. A BEO defines operational delivery such as room setup, menu, timing, AV, staffing, vendors, and special instructions.
They must agree, but they do different jobs. If the BEO changes a price, concession, guarantee, or material commercial term, route the change through the property's approved contract or change-order process. Do not use a BEO to quietly override a contract.
What should a BEO contain?
1. Event identity and ownership
Include event name, client or organization, date, property, primary contact, event-services owner, department owners, and the controlled revision number.
2. Function schedule and space
List each function separately with room, start and end time, guest access, setup, service, breakdown, room flip, and reset. Ceremony, cocktail hour, reception, breakout, meal, and after-party details should not be hidden under one generic event line.
3. Guest count and guarantees
Show expected attendance, final guarantee, maximum planning count, guarantee deadline, seating assumptions, VIPs, accessibility needs, dietary counts, vendor meals, and any approved overage or contingency rule. Use the hotel's approved guarantee and purchasing procedures rather than inventing a universal buffer.
4. Room layout and setup
Attach the approved diagram and state setup style, furniture, stage, dance floor, buffet, bar, registration, exhibits, storage, service lanes, accessibility route, power, and room-flip requirements. Capacity should be checked against the actual layout, not only the room's maximum.
5. Food, beverage, and service
Document menu selections, service style, meal release, break times, bar hours, replenishment, dietary and allergen handling, cake or specialty items, culinary owner, and billing treatment.
6. AV, production, décor, and vendors
List equipment, technician coverage, test time, presenter files, microphones, screens, lighting, power, cable paths, staging, décor, vendor arrival, load-in, storage, insurance, escort, and teardown. Link to a detailed AV plot or vendor matrix when the BEO would become unreadable.
7. Billing and commercial exceptions
Identify master-account items, attendee-pay items, deposits, concessions, upgrades, service charges, taxes, parking, internet, commissions, and change-order approvals. The BEO should reflect the approved deal without becoming an uncontrolled contract rewrite.
8. Timing, checkpoints, and escalation
Add room-ready, AV-tested, vendor-load-in, registration, meal-release, program-cue, room-flip, and breakdown checkpoints. Assign one owner to each and identify who can decide when a guest count, vendor, room, or timing issue changes.
Who creates and uses a BEO?
The author may be a sales manager, catering manager, event services manager, or coordinator. The document is then reviewed and used by the people who own delivery:
- sales and event services for scope, client decisions, and changes;
- banquet and culinary teams for setup, service, menus, and timing;
- AV, engineering, housekeeping, and security for technical and access needs;
- front desk and reservations for guest, room-block, and arrival context;
- finance for billing, deposits, concessions, and approved changes;
- the client or planner for the decisions they must confirm.
The exact distribution list depends on the event. Send the controlled issue to the departments affected by the work, not automatically to everyone or only to the sales office.
How to review a BEO
Review in dependency order:
- Confirm event identity, date, rooms, owners, and revision.
- Check expected and guaranteed attendance against capacity and purchasing.
- Review each function's time, setup, service, and transition.
- Verify menu, dietary, AV, vendor, accessibility, and access details.
- Compare billing and concessions with the approved commercial record.
- Confirm open decisions, deadlines, department acknowledgement, and escalation.
- Check that the diagram, run-of-show, vendor matrix, and BEO use the same revision.
BEO revision control
Every controlled issue should show:
- revision number;
- issue date and time;
- author and approver;
- change summary;
- affected departments;
- open decisions and owners;
- the approved diagram or supporting document version.
Do not label an issue “final” while a material decision remains open. For a late change, record the request, impact, approver, new revision, and acknowledgement from each affected department.
Copyable BEO readiness checklist
- [ ] Event identity, date, rooms, owners, and revision are correct.
- [ ] Each function has its own time, setup, service, breakdown, and owner.
- [ ] Expected, guaranteed, and maximum attendance are separated.
- [ ] Layout, capacity, circulation, accessibility, AV, and service lanes are confirmed.
- [ ] Menu, dietary, bar, vendor-meal, and timing details are complete.
- [ ] Vendor access, staging, power, storage, and teardown are assigned.
- [ ] Billing, concessions, deposits, and change rules match the approved deal.
- [ ] Day-of checkpoints and escalation owners are clear.
- [ ] All affected departments acknowledge the controlled issue.
Start with the BEO checklist by event type, use the free BEO template when a document is the right fit, and evaluate BEO software versus templates when revision volume or handoff risk grows.
Frequently asked questions
What does BEO stand for in hotels?
BEO stands for Banquet Event Order, the operational document used to coordinate the details of a hotel event.
Is a BEO the same as a contract?
No. A contract defines commercial and legal commitments; a BEO defines the operational plan for delivering the event.
Who uses a BEO?
Sales, event services, banquet, culinary, AV, engineering, housekeeping, front desk, security, finance, and the client or planner may use the parts relevant to their work.
When should a BEO be finalized?
The timing depends on event complexity, purchasing, staffing, vendor, and property procedures. Set deadlines backward from the first irreversible operational commitment, and issue a controlled revision when material changes occur.
Can a BEO replace a template or software?
A BEO is the operational document. It can be created from a template or managed in software; the right choice depends on event volume, revision frequency, collaboration, approvals, and handoff risk.