Who prepares the BEO?

Usually the salesperson or event/conference services manager who owns the client relationship, in consultation with culinary and AV. It's then reviewed in the venue's weekly BEO meeting and distributed to every department involved.

When should a BEO be finalized?

Agree the deadlines with the venue, client and suppliers. Equipment, staff, catering counts and content may have different cut-offs. Distribute a usable version early and record approval for changes after each deadline; do not assume one standard time fits every event.

Is a BEO the same as an invoice or a contract?

They serve different purposes. The BEO describes execution; the invoice records charges; the agreement defines the terms accepted by the parties. Make sure the approved BEO and later changes remain consistent with that agreement.

What software do venues use for BEOs?

A venue may use a document template or a sales-and-catering system for the BEO. Filmo can support the underlying equipment, spaces, crew services and order records. Keep the document version aligned with those records and verify the resource plan when it changes.

Resources · Blog/April 7, 2026·Updated October 23, 2026·7 min read

Banquet Event Order (BEO): What It Is + Free Template

The BEO is the single document your banquet, kitchen, AV and setup crews execute from. Here's what belongs in it, how to keep it honest — and a template to copy.

A banquet event order (BEO) is an operational document that records the agreed event requirements: dates and times, room layout, food and service, equipment, staffing and billing instructions. It gives each department a common plan and a way to identify the current revision.

What is a banquet event order?

The BEO is a handover between the person agreeing the event and the departments delivering it. Review it with banquets, catering, AV and setup leads so each knows its scope, dependencies and current revision. Missing detail should become an assigned question before the event.

Choose a document structure that makes each function clear. For example, a three-day conference could have separate BEOs for a reception, plenaries and dinner, plus a master schedule linking them. Number the documents and agree who owns each revision; there is no universal page or document count.

What goes into a BEO?

Section	What it covers
Event header	BEO number, event name, client and on-site contact, salesperson, date issued and revision number
Schedule	Access/setup time, doors, service times course by course, breakdown deadline
Room & setup	Which space, setup style (banquet rounds, theater, U-shape…), head count, floor plan reference
Food & beverage	Menu per course, dietary requirements and counts, bar package, service style, tasting notes
AV & equipment	Every item by name and quantity — screens, PA, microphones, stage decks, uplights, power drops — and who supplies each one
Staffing	Banquet servers and captains, chefs and stations, AV techs, setup/strike crew, security — with call times
Billing	Pricing per line, service charge and tax, deposit received, payment terms, master account or on-consumption
Signatures	Client sign-off and the internal distribution list — who gets every revision

How to create a banquet event order

Start from the agreed proposal and record any approved changes before distributing the operational plan.
Number it and version it. "BEO #214 rev 3" ends arguments; "the latest email" starts them.
Write the schedule backwards from doors: if doors open at 18:00 and the room takes 3 hours to set, setup starts at 15:00 — which decides crew call times.
List equipment by item and quantity, not by vibe. "2× wireless handheld, 1× lectern mic, 1× 4×3m LED wall" — and mark anything sub-rented from a partner.
Record dietary requirements and counts, with the catering lead responsible for checking and communicating them through the agreed process.
Agree who approves the BEO, who receives it and how each department acknowledges a revision.
Agree cut-off dates with the client and suppliers. After a cut-off, record the requested change, feasibility, price impact and approval before updating the plan.

Free BEO template: the blocks to copy

Copy these fields into your document tool and fill them in for the event. Keep the revision number and distribution list visible so the team can identify the version it is using.

Header: BEO # / revision / date issued — Event name — Client + on-site contact & mobile — Salesperson/planner.
Event basics: date, space(s), guaranteed head count vs. expected, setup style.
Timeline table: time | activity | department responsible — from crew access to strike complete.
F&B block: menu per course, per-line counts, dietaries, bar terms, service style.
Equipment block: item | qty | source (house / client / sub-rental) | notes — one line per item.
Staffing block: role | count | call time | cut time.
Billing block: line items, service charge %, tax, deposit, balance due date.
Sign-off block: approver, approval date, revision accepted and internal distribution list.

BEO vs. function sheet vs. contract

Document	What it is	Who it's for
Contract	The legal agreement — spaces, dates, minimums, cancellation terms	Client and venue management
BEO	The operational spec for one event on one day — the execution document	Every department working the event
Function sheet	A term some venues use for the operational event sheet or a daily summary; confirm the meaning with the venue	Operations teams

The BEO mistakes that sink event days

AV listed as intentions, not inventory: "projector and sound" on the BEO, while the actual projector is double-booked in the ballroom next door.
No versioning — three revisions circulating at once, and the kitchen executes rev 1 while the client signed rev 3.
Crew missing from the plan: a short room-change window is promised without checking the required staffing and access.
Sub-rented equipment with no owner: nobody is assigned to receive, inspect and return it by the agreed deadline.
Dietary counts without seats: eight vegan meals confirmed, zero indication of which tables they're on.
The distribution gap: sales updates the BEO on Thursday, banquets prints on Wednesday.

From BEO to execution: closing the operational gap

The BEO states requirements; the operational team still has to reserve resources and confirm suppliers. Check each equipment line, working period and space booking against the current plan. When a revision changes quantity, dates or scope, repeat those checks and record who approved the change. Keep the BEO revision linked to the event records.

Banquet event order FAQs

What is a banquet event order?: It is the operational specification for an event: schedule, room setup, menu, equipment, staffing and billing instructions. Keep it aligned with the agreed scope and identify the current revision for every department.
Who prepares the BEO?: Usually the salesperson or event/conference services manager who owns the client relationship, in consultation with culinary and AV. It's then reviewed in the venue's weekly BEO meeting and distributed to every department involved.
When should a BEO be finalized?: Agree the deadlines with the venue, client and suppliers. Equipment, staff, catering counts and content may have different cut-offs. Distribute a usable version early and record approval for changes after each deadline; do not assume one standard time fits every event.
Is a BEO the same as an invoice or a contract?: They serve different purposes. The BEO describes execution; the invoice records charges; the agreement defines the terms accepted by the parties. Make sure the approved BEO and later changes remain consistent with that agreement.
What software do venues use for BEOs?: A venue may use a document template or a sales-and-catering system for the BEO. Filmo can support the underlying equipment, spaces, crew services and order records. Keep the document version aligned with those records and verify the resource plan when it changes.