Banquet Event Order in Hotel RFPs (Plain English Definition + Examples)

Definition

A Banquet Event Order (BEO) is the operational document the hotel produces for each meeting/F&B function within an event — listing setup time, room layout, attendee count, menu, AV, service staff, billing instructions — signed by the planner as the day-of source of truth.

In European MICE sourcing, banquet event order sits inside a broader workflow that includes the brief, the longlist, the shortlist, the contract negotiation, and the post-event reconciliation. Understanding it in isolation is not enough — what matters is how it interacts with the other levers a planner can pull. The definition above is the textbook version; the sections below explain how it actually behaves in real RFPs.

Why Banquet Event Order matters

If it's not on the BEO, it's not happening. The contract is the strategic agreement; the BEO is the operational execution. Most MICE issues at delivery (wrong room setup, missed dietary, AV gaps) trace back to a planner who didn't read the BEO carefully 7-10 days before the event. Always demand BEOs 14 days out; review and sign within 7.

Example

Day-2 lunch BEO: 12:30-14:00, ballroom rounds of 10, 200 attendees, 24 gluten-free + 6 vegan, plated 3-course, 8 servers, soft drinks station, hosted bar 13:00-14:00, billing to master account. Planner reviews, flags 2 missing kosher meals, hotel reissues BEO with kosher → no day-of crisis.

Where Banquet Event Order appears in contracts

BEOs are separate operational documents (not part of the master contract) but reference the contract for rates and billing. Each function gets its own BEO. Sign them — don't just read them.

Related terms

Deeper reading