Operations
Banquet event order (BEO): a complete guide
The BEO is the operational contract for an event and the most error-prone document in most venues. Here is what belongs on one, who needs it, and why the way you produce it matters more than the format.
The short answer
A banquet event order (BEO) is the document that tells every department exactly how an event will run: the client and contact details, date, spaces, full timeline, guest count, menu and beverage service, setup and layout, audiovisual and staffing requirements, and the pricing and payment status. It is distributed to operations, kitchen and management ahead of the event and is the single reference everyone works from on the day.
- A BEO is an operational document, not a sales one.
- It covers client, timing, spaces, counts, menu, setup, staffing and money.
- It goes out roughly a week ahead, with a final version closer in.
- Generating it from the booking is what keeps it accurate.
What a banquet event order is
A banquet event order is the operational specification for a single event. Once the contract is signed and the details are agreed, the BEO is the document that translates all of it into instructions the people working the event can act on.
It matters because an event involves departments that do not talk to each other continuously. The kitchen needs covers and service times. The floor team needs the layout and the timeline. The bar needs the beverage arrangements. Management needs the payment status. Without one authoritative document, each department works from whatever it was last told, and those versions drift.
It is worth being clear about what a BEO is not. It is not a contract, though it often references one. It is not a proposal. It is not a client-facing sales document. It is a work order, and confusing it with a sales document is how BEOs end up too polished to be useful and too vague to be actionable.
What to include on a BEO
The contents vary by venue, but this is the set that covers the great majority of operations. If a department cannot do its job from your BEO, something on this list is missing.
- BEO number and version, with the date it was issued. Version confusion is the most common BEO failure.
- Client name, organisation, and the day-of contact, which is frequently not the person who signed.
- Event date, type and the specific spaces in use.
- Full timeline: vendor load-in, setup complete, guest arrival, service times by course, speeches, end time, teardown.
- Guaranteed guest count, and the date it was confirmed.
- Menu in full, including courses, substitutions and any tasting decisions.
- Dietary requirements and allergies, with the number of covers each affects.
- Beverage arrangements: bar type, package, timing, and who is being charged.
- Room setup and layout, including table configuration, seating and staging.
- Audiovisual and equipment requirements, and who is supplying them.
- Staffing: how many, in which roles, and their call times.
- External vendors: florist, photographer, entertainment, with arrival times and contacts.
- Pricing summary and payment status, including what remains outstanding.
- Special instructions and anything specifically promised during planning.
Who gets it and when
Distribution matters as much as content. A perfect BEO that reaches the kitchen the morning of the event has failed.
| Recipient | What they act on | When they need it |
|---|---|---|
| Kitchen | Covers, menu, dietary requirements, service times | Far enough ahead to order; typically 7 to 10 days, with the final count per your guarantee terms |
| Floor and service team | Timeline, layout, staffing, special instructions | About a week ahead, with the final version at the pre-event briefing |
| Bar | Beverage package, timings, billing arrangement | About a week ahead |
| Audiovisual and technical | Equipment list, setup times, technical contacts | A week or more ahead, longer for complex setups |
| Management and accounts | Pricing, payment status, outstanding balance | A week ahead, so balances are chased before event day |
| Client | A confirmation summary, not the full operational document | At final confirmation, usually two weeks out |
Why BEOs go wrong
The failure modes are consistent across venues, and all of them come from the same root cause: the BEO is a copy of information that exists elsewhere.
Version drift is the most common. A change is agreed, someone updates the printed copy in the office, and the kitchen is still working from the version issued last Tuesday. Nobody did anything wrong, and the event runs on two different sets of facts.
Transcription error is the most expensive. The guest count on the booking is 145. The BEO says 154. It was typed, and digits transpose. The kitchen orders for 154 and the error is discovered at service.
Staleness is the most insidious, because it is caused by good intentions. Regenerating a BEO by hand takes half an hour, so when a small change comes in three days out, people amend the copy rather than reissue. Do that twice and no version anywhere is fully correct.
None of these are solved by being more careful. They are solved by removing the copy.
If regenerating your BEO is expensive, your team will amend instead of reissue, and your BEOs will be wrong. Cheap regeneration is the whole game.
Generating the BEO instead of writing it
Every field on a BEO already exists somewhere: on the booking, in the contract, in the planning notes. Writing a BEO is therefore not authoring; it is assembly. And assembly done by a human is slow and lossy.
When the BEO is generated from the booking record, three things change. Producing it takes seconds instead of half an hour. The numbers on it are by definition the numbers on the booking, so transcription error disappears. And because regeneration is free, the correct response to a late change becomes reissuing rather than amending.
That third consequence is the one that matters most and is least obvious. Most BEO errors in well-run venues are not mistakes; they are rational responses to the cost of doing it properly. Remove the cost and the behaviour fixes itself.
A workable BEO process
If you are establishing or rebuilding a BEO process, this sequence works for most venues running more than a couple of events a week.
- Keep the details on the booking. As things are agreed during planning, record them on the event record rather than in email. The BEO can only be as good as the record it derives from.
- Issue a draft about two weeks out. Circulate internally so departments can flag anything impossible before it is too late to fix. This is the step most venues skip and most regret skipping.
- Confirm the guaranteed count. Per your contract terms, usually between three and seven days out. Record the number and the date it was confirmed.
- Issue the final BEO. Generated fresh from the booking, clearly versioned, distributed to every department. Not an amended copy of the draft.
- Reissue on any change. Any change after final issue produces a new version, not a pen mark. Note what changed so departments can scan for it.
- Brief from the BEO. The pre-event briefing works through the document. This catches the last misunderstandings and makes the BEO the shared reference in practice, not just in theory.