Banquet event order: the one document that runs a hotel meeting or wedding
A banquet event order aligns the kitchen, banquet and front desk on one document. Learn how to manage versioning, guarantee numbers and billing rules to prevent disputes and ensure smooth execution.
Contents
Key takeaways
- A BEO exists because the kitchen, banquet, technical service and front desk otherwise each work from a different email, and each email is true only for its sender.
- Expected, guaranteed and actual are three different numbers, and the document must say which one the invoice uses.
- Only the event manager issues a version, only the client's named contact may request a change, and every reissue carries a number, a time and a one-line reason.
- The billing block is written before the event, not reconstructed afterwards: it names who may sign, what goes to the master account and what does not.
- A document nobody has read is not a plan, so distribution is followed by a weekly event meeting and a spoken briefing at shift handover.
A banquet event order (BEO) is the single written instruction for one hotel event: the room, the timings, the set-up, the menu and drinks, the equipment and staff, the guaranteed numbers and the billing rules. It is issued in numbered versions and signed by the client and by the departments who must deliver it.
The sales manager promised a 19:00 start, the kitchen planned for 19:30, the technician booked the screen for 18:00 and the front desk is telling guests 20:00. Four emails, four truths, one event. The banquet event order is the document that replaces all four.
This article explains what a BEO contains, who owns it, how changes are versioned, how the guarantee number works and how the document becomes the bill. After reading it, you can rebuild your own BEO against seven blocks and spot the gaps before the client does.
What is a banquet event order, and why does one document run the event?
A banquet event order is the operational instruction for a single event: what happens, when, in which room, for how many people, at what price and who is responsible for each part. It is the version that counts, and anything not on it does not happen.
The failure it prevents is not carelessness but parallel truth. Sales, kitchen, banquet, technical service and the front desk each hold a partial and locally correct picture of the same evening. The sales email is accurate about price, the kitchen's note is accurate about the menu, and neither knows what the other promised. One document ends that.
A BEO is an operational document, not a contract. The contract fixes price, deposit, cancellation and liability; the BEO fixes execution, and the two must agree on numbers and terms. It covers meetings, weddings, gala dinners, day delegate groups and the food and beverage part of a residential group, in the same structure. When the group itself needs quoting, the pricing side is a separate exercise: how to quote a hotel group: rates, free places, deposits and terms.
One person owns the document: the event or banquet manager owns the BEO and its versions. Each department head owns the accuracy of their own block and signs that they have read it. The name varies by hotel and by country: function sheet, event order, or "banket föyü" in Turkish. The name is not the point; the completeness and the version control are.
The test of a real BEO is simple. A document written after the event is a report, not a plan. Ask whether the kitchen could buy and roster from it three days out. If they could, it is a plan.
What sections does a banquet event order contain?
A working BEO has seven blocks: the event header, the timing plan, the room set-up, the menu, the drinks, the equipment and staffing, and the billing instructions. Each block answers a question a different department will ask on the day.
The header carries client and company, the named contact who is present on the day, event name, date, room or rooms, booking reference, version number and issue time. The timing plan is not only start and end: it lists supplier access, set-up start, rehearsal, doors, service time per course, speeches, cake cutting, music curfew, breakdown and load-out.
Room set-up uses the hotel's own vocabulary: theatre, classroom, U-shape or rounds, with exact counts per table, plus stage, dance floor, registration desk, signage and accessibility. The menu describes each course precisely: plated or buffet, service temperature, vegetarian and allergen handling per dish, children's meals, staff meals and the tasting reference. Allergen handling deserves its own routine, covered in food allergies in hotel restaurants and buffets: a guest safety routine.
Drinks state package or consumption, what is included and excluded, corkage, bar closing time, last order and water on the tables. Equipment and staffing list screens, projectors, microphones, laptop connections, power, lighting, heating and cooling, Wi-Fi and lectern, plus the number of waiters, captains, kitchen brigade, technicians, security and cloakroom staff. The billing block names the deposit received, who pays for what, which extras are allowed or forbidden, who may sign on the night, master account versus individual payment, and service charge and taxes as set in the contract.
The seven blocks and who confirms each one
| Block | What it fixes | Who confirms it |
|---|---|---|
| Header | Identity, room, version, named contact on the day | Event manager |
| Timing plan | Access, set-up, service per course, curfew, load-out | Event manager with banquet and technical service |
| Room set-up | Layout, counts per table, stage, signage | Banquet manager |
| Menu | Courses, service style, allergens, children and staff meals | Chef |
| Drinks | Package or consumption, bar hours, corkage | F&B manager |
| Equipment and staffing | AV, power, climate, headcounts per role | Technical service and banquet manager |
| Billing | Deposit, routing, who may sign, allowed extras | Front office manager with sales |
What is the difference between expected, guaranteed and actual numbers?
Expected is what the client forecasts when booking, guaranteed is what the client commits to by the hotel's cut-off and what the hotel buys, cooks and staffs for, and actual is who came through the door. The BEO must carry all three and say which one the invoice follows.
The guarantee protects the kitchen. Food is purchased and staff rostered against it, so the hotel charges the guaranteed number even if fewer guests arrive, on the terms written in the contract. It also protects the client: it fixes the minimum the client will be charged, and it gives the hotel a basis for adding tables if more arrive, subject to space and notice.
The cut-off is hotel practice, not law, so it must be agreed in writing and printed on the document rather than assumed by either side. The actual count is recorded on the night by the banquet captain, per course and per bar, because it is the evidence for the bill and the input for next year's planning.
Children, staff, suppliers, photographers and entertainers are usually counted and charged separately. List them explicitly instead of folding them into the headcount. For buffets, the guaranteed number is also the quantity planning input: covers drive how much is produced, and the gap between guaranteed and actual is where waste or shortage begins, as explained in buffet food waste in all-inclusive hotels: measuring it and planning quantities from covers.
Who may change a BEO, and when does it lock?
Only the event manager issues a new version, and only the client's named contact may request a change. The document locks at the cut-off for numbers and earlier for anything that has to be bought, built or rostered.
Version control is mechanical, not optional. Every reissue gets a new number, date and time and a one-line reason; superseded versions are marked as such and kept, never deleted. Page one carries a change log: what changed, who asked, who accepted, and what it costs.
Locks come in two speeds. Early locks apply to room set-up changes, AV and external suppliers, special orders and extra staffing. Late movement is still possible for seating within the agreed room, some drink choices and minor timing shifts. A change after the cut-off may carry a charge, and the BEO must say so before the client signs, not on the invoice.
When a change is agreed, the event manager reads the changed lines back to the client and the client confirms in writing, so the change exists in one place only. The departments hold the version they acknowledged; if two versions are in circulation, the newer number wins and the older one is collected.
Watch outA verbal change is not a change
If a client says "we will be twenty more" in the corridor, the hotel writes it down with the name, the time and who accepted it, and confirms it in writing before anyone buys or builds for it. Unwritten changes are the most common source of a disputed invoice and of a room set for the wrong number.
How does the BEO reach the kitchen, banquet and technical service?
It reaches them twice: as a distributed document each recipient acknowledges, and as a spoken briefing. A document nobody has read is not a plan.
Use a distribution list with named recipients rather than department names, so that "the kitchen has it" becomes "the chef has version three". The weekly event meeting reads every event of the coming week line by line, with sales, kitchen, banquet, technical service, front desk and housekeeping in the room. The daily briefing reads the day's events at shift handover, together with the changes made since the last version.
Each department works from its own extract, not the whole document. The kitchen works from a production sheet derived from the BEO, so the line cook sees quantities and timings rather than billing instructions. The front desk gets its own extract: where the event is, when it starts, which entrance guests use, where to park, and who to call. Technical service walks the actual room before the event: screen height, sightlines, power, microphone coverage and the noise path to the nearest guest room.
Pre-event read-back, the day before
Checklist
- Version number and issue time match the one the client signed
- Guaranteed number confirmed and the kitchen production sheet matches it
- Room set-up matches the layout and table counts
- Allergen list for every dish confirmed by the chef
- AV and power tested in the actual room
- Staffing roster names the captain and the technician
- Billing block names who may sign on the night
- Front desk extract printed and briefed
- Change log empty or read aloud at the briefing
How does the BEO become the bill?
The billing block tells the cashier, before the event, which charges go to the master account, which go to individual guests and who is allowed to add anything. The invoice is then a reconciliation against the document, not a reconstruction from memory.
Open the master account before the event and take the routing instruction from the BEO, not from whoever is standing at the desk at midnight. Every extra consumed on the night is signed by the named client contact on a numbered check that references the event, so the charge has a person and a document behind it. The mechanics of the master folio itself belong to the group booking process, covered in hotel group bookings: block, rooming list and master folio.
Reconcile line by line: the guaranteed number, the actual covers, drinks consumed, equipment and staffing hours, and any change charges agreed after the cut-off. Room blocks, rooming lists and the room part of a residential group stay in the group booking process; the BEO carries only the food, beverage and space it describes.
Close the master account within the hotel's own routine and, where possible, before the client leaves the building, so that disagreements are settled with the people who were in the room. The recurring failure is the same every time: a charge discovered a week later, no signature, no reference. The BEO, with its signed checks and change log, is the hotel's main defence.
What to do next
Take one upcoming event and rewrite its BEO against the seven blocks, then read the billing block against what the front desk would actually have charged. Where the two do not match, the document is not finished. The BEO is not paperwork around the event; it is the event, written down early enough for the kitchen to buy for it, the technician to build for it and the cashier to bill from it.
Frequently asked questions
Is a banquet event order the same as a function sheet?
Yes in substance. Function sheet, event order and BEO are names for the same operational instruction, and hotels use them differently. The test is not the name but whether the document carries timings, set-up, menu, drinks, equipment and staffing, numbers and billing, and whether it is versioned.
Does a BEO replace the contract with the client?
No. The contract fixes price, deposit, cancellation and liability; the BEO fixes execution. They must agree on numbers and terms, and where the BEO changes something the contract set, the change belongs in writing with the client's acceptance.
What happens if more guests arrive than the guaranteed number?
Hotel practice is to seat and serve them if space, food and staffing allow, and to charge for the extra covers; if they cannot be served, the guaranteed number still stands. The BEO should say which of these applies before the event, and the captain records the actual count on the night.
How far in advance should the BEO be issued?
A draft at the point of booking, a confirmed version at the hotel's own cut-off for numbers, and a final version early enough for purchasing, rostering and external suppliers. There is no single rule: the hotel sets the cut-off and prints it on the document, and anything that needs buying locks earlier than anything that only needs arranging.
Who signs the BEO?
The client's named contact signs to accept the version, and each department head acknowledges the block they must deliver. A signature means agreement to that version at that time, not agreement to every future change, which is why each reissue is signed again.