A Banquet Event Order is the single operational document that turns a signed event contract into instructions every department can execute. It states what is happening, where, when, for how many, what is served, how the room is set, what equipment is needed, who is working and how it is billed — and kitchen, banqueting, front office, AV, housekeeping and finance all work from that same document.
Banqueting is the most detail-dense revenue in a hotel. A guest room has a handful of variables; a wedding for two hundred has several hundred, each with an owner and a deadline. The BEO exists because no operation can hold that in conversation.
When function errors happen, the cause is almost never that someone did not care. It is that two people were working from different versions of the truth.
On this page
Why the BEO is the control document
A contract is a commercial agreement. It is not an instruction to a chef. The BEO is the translation layer between what was sold and what gets delivered, and it serves three distinct audiences at once:
- Operationally it tells every department exactly what to do and when.
- Commercially it defines what the client has agreed to pay for, which is what the invoice is built from.
- Legally it is the record of what was agreed — including allergen information, which matters enormously if something goes wrong.
That is why a BEO should have exactly one live version at any moment, carry a revision number, and be generated from the booking record rather than typed out separately. A BEO re-keyed from the diary into a document is a second source of truth, and second sources of truth are where function errors are born.
What belongs on a BEO
Use this as a template checklist. Anything missing here is something a department will have to ask about — or assume.
| Section | Must contain |
|---|---|
| Identification | BEO number, revision number, issue date, event name, client and company, on-site contact with mobile number, account manager or coordinator |
| Date & timings | Event date, guest arrival, service times for each element, finish time, plus access, setup and breakdown windows |
| Space | Room or rooms, setup style, capacity, floor plan reference, adjoining spaces for registration, breakouts or pre-drinks |
| Numbers | Expected, guaranteed, over-catering allowance, and the final number with the date it was confirmed |
| Food | Every course and item with service time, menu numbers or codes, canapé and buffet composition, children's and crew meals |
| Beverage | Package or consumption basis, specific wines and quantities, bar opening and closing, drinks vouchers, corkage |
| Dietary & allergen | Recorded separately, named to guest or table, with the service plan for delivery |
| Equipment & AV | Staging, lectern, screens, projection, microphones, lighting, dance floor, linen colour, centrepieces, signage |
| Staffing | Numbers by role with start and finish times, supervisor named, security or cloakroom where required |
| Other departments | Accommodation block, parking, front office instructions, housekeeping requirements, maintenance or engineering support |
| Billing | What is charged, to whom, deposits received, balance due, master account versus individual settlement, payment terms |
| Notes | VIPs, sensitivities, cultural or religious requirements, previous history with the client |
Timings win arguments. The most common cause of a function running badly is not a missing item but a missing time. "Canapés on arrival" is not an instruction. "Canapés passed from 18:45, replenished 19:15, cleared 19:45" is.
The lifecycle: enquiry to invoice
- Enquiry. Date, space, headcount and budget captured; availability provisionally held with an expiry date so the diary is not silently blocked.
- Proposal. Menus, spaces and pricing offered against the brief, with the hold expiry stated.
- Contract. Signed agreement with deposit schedule and cancellation terms. The booking converts from provisional to confirmed in the diary.
- Planning. Detail is built up over weeks — menu tasting, floor plan, running order, AV requirements, supplier bookings.
- BEO issue. Typically seven to ten days out, distributed to every department.
- Function meeting. The BEO is walked through by all departments together.
- Final numbers. Guaranteed headcount confirmed in writing at the cut-off; final BEO revision issued.
- Execution. Setup checked against the BEO before guests arrive, not while they arrive.
- Close-out. Actual consumption, extras and variances captured on the day.
- Invoice. Billed from the BEO plus signed on-the-day extras, ideally within days rather than weeks.
Guaranteed numbers and cut-offs
The guaranteed number is the minimum headcount the client agrees to pay for, whether or not those guests attend. It is confirmed in writing by an agreed cut-off — commonly 48 to 72 hours before the event — and it is the number the kitchen orders and preps against.
Three conventions make this work:
- An over-catering allowance above the guarantee, so late arrivals are absorbed. The percentage should be a written policy, not a chef's private judgement.
- Billing on the higher of guaranteed or actual attendance.
- A written cut-off in the contract, enforced consistently. A cut-off that moves for every client is not a cut-off, and it makes accurate purchasing impossible.
Track guaranteed versus actual attendance across events. A persistent gap tells you either that clients are over-estimating or that your cut-off is too early to be useful.
Dietaries and allergens
This is the section where a mistake stops being an inconvenience and becomes a medical emergency. Treat dietary preference and allergen requirement as two different fields with two different standards.
- Preferences — vegetarian, vegan, pescatarian, religious requirements — are catered choices, planned into the menu.
- Allergens are a safety control. They must be recorded against a named guest and table where possible, communicated to the kitchen in writing, and carried through to a service plan so the correct plate reaches the correct person.
Declarable allergen lists differ by jurisdiction. The European Union requires declaration of 14 named allergens under Regulation 1169/2011, including celery, mustard, lupin, molluscs and sulphites. The United States defines 9 major food allergens, sesame having been added on 1 January 2023. If you operate across regions, build to the longer list rather than maintaining two standards.
Practical service disciplines that belong in the SOP behind the BEO: allergen plates identified at the pass and carried separately, the server delivering them briefed by name and seat, and a verbal confirmation with the guest at the table.
Room setups and audio-visual
Setup style should be stated in a standard vocabulary the whole team uses — theatre, classroom, boardroom, U-shape, cabaret, banquet rounds, hollow square, reception — together with the capacity for that style in that room, because capacity is a property of the combination, not the room alone.
Always specify: table size and count, cover spacing, top table arrangement, staging position and height, dance floor size and location, lectern and microphone positions, screen size and sightlines, power requirements and cable routes, and the position of registration or cloakroom.
Attach the floor plan to the BEO rather than describing it in prose. Where AV is supplied externally, the BEO must name the supplier, their access time and who is responsible for their power, rigging and supervision.
The function meeting
A weekly function meeting is where BEOs stop being paper. Kitchen, banqueting, front office, housekeeping, AV, maintenance and finance walk the coming period's events together.
The value is not the reading — it is the collisions the meeting surfaces:
- Two events sharing a wall with incompatible noise profiles
- A conference load-in clashing with a wedding setup on the same service lift
- A menu requiring oven capacity already committed to another function
- Staffing peaks that exceed available team on a given evening
- Maintenance work scheduled into a space that is now sold
Every clash found in that meeting is an incident that does not happen.
Change control
Events change. That is normal. What must be controlled is how they change.
- One channel. Changes come through the coordinator, not directly to the chef or the AV technician. A change made in a corridor is a change nobody else knows about.
- Revision numbers. Every reissue increments, carries a date and time, and marks what changed. Departments should be able to see the difference at a glance.
- Reissue to everyone. Partial distribution guarantees that one department works from a superseded version.
- Late-change policy. Define what can still change inside 24 hours and what cannot, and what it costs. Without it, the answer is decided under pressure by whoever is asked.
- Destroy the old copies. On the day, superseded printouts are a hazard. Whoever distributes the revision collects the previous one.
Billing from the BEO
The BEO is the invoice's source document. If the two disagree, the client will trust the BEO — they signed against it.
Capture on the day, not in arrears: consumption bar totals, extra covers served, additional equipment, overtime beyond the contracted finish, damages and corkage. Each extra should carry a signature from the client's on-site contact at the time it is incurred, because an unsigned extra discovered a week later is usually written off.
Invoice promptly. Banqueting receivables age badly, and the memory of what was agreed fades fastest on the client's side.
Post-event close-out
A short, honest close-out converts one event into better delivery on the next:
- Guaranteed versus actual attendance, and the variance
- Actual food and beverage cost against the quoted package
- Overtime and agency hours against plan
- Breakages, losses and damages
- What went wrong operationally, recorded without blame
- Client feedback and the rebooking conversation while goodwill is fresh
Feed the cost outcome back into F&B control. A banqueting package that consistently misses its margin is a pricing problem, not a kitchen problem — and only the close-out data will prove which.
Where BEOs fail
- Two versions in circulation. The single most common cause of function error.
- Verbal changes. Agreed with the client in the room, never written down, never reaching the kitchen.
- Vague timings. "During the speeches" is not a service time.
- Allergens buried in general notes rather than held as a controlled, named field.
- No named on-site client contact, so the team cannot get a decision at 19:00 on a Saturday.
- Setup checked as guests arrive. The check must happen with enough time to fix what it finds.
- Extras never captured, quietly eroding the margin on an otherwise successful event.
Frequently asked questions
What is a Banquet Event Order (BEO)?
The single operational document translating a signed event contract into instructions every department executes — covering timings, space, numbers, food and beverage, equipment, staffing and billing.
What information belongs on a BEO?
Identification and revision number, date and timings, room and setup, guaranteed numbers, full F&B schedule with service times, dietary and allergen detail, equipment and AV, staffing, billing instructions and notes.
When should the BEO be issued?
Typically seven to ten days before the event, reviewed at a weekly function meeting with all departments present, with a final revision after the guaranteed-numbers cut-off.
What is a guaranteed number?
The minimum headcount the client agrees to pay for, confirmed in writing at a cut-off — commonly 48 to 72 hours out. Billing is on the guarantee or actual attendance, whichever is higher.
How should allergens be handled?
Separately from dietary preferences, named to guest and table, communicated in writing to the kitchen and carried through to a service plan. Note that declarable lists differ — 14 allergens in the EU under Regulation 1169/2011, 9 in the United States since sesame was added in January 2023.