You were told a banquet event order fits on one page. Sometimes it does. A forty-cover board dinner with a set menu and two microphones can be summarised on a single sheet, and the floor manager will thank you for it. A three-hundred-guest gala with a stage change, a live band, three dietary tracks and a sponsor who wants a branded bar will not, and pretending otherwise is how lines get dropped. "One page" is a discipline, not a page count.
So what is the document, exactly? The Events Industry Council's APEX glossary defines the BEO as a form most often used by hotels to provide details to the personnel concerned with a specific food and beverage function or event room set-up. In plain terms: the quote says what was sold, the BEO says who does what, where, at what time, with what equipment. Kitchen, floor, technical, security and outside vendors all work from the same sheet. If it is not on the BEO, it does not happen.
Where the BEO comes from, and what it is not
The term is North American hotel vocabulary. The MPI event industry glossary describes it as a detailed operations document used by hotels and venues to deliver meeting and event services, typically covering room setup, food and beverage, timing, guaranteed counts and special instructions. In the UK the same sheet is usually called a function sheet. French venues say feuille de fonction, Spanish ones hoja de evento or orden de servicio. Same object, different label.
Two things it is not. It is not the quote: prices appear on it, but the BEO is not where you negotiate. And it is not the full contract. Cvent's own guidance for venues, in its article on banquet event orders, calls it a mini-contract that only covers the planner's use of meeting space and banquet services, drafted by the catering sales manager or event manager and reviewed by both sides before signature. Cancellation terms, liability and payment schedule live in the master agreement. The BEO points to them; it does not restate them.
Who writes it varies. In a hotel it is the catering sales manager. In an independent venue it is often the same person who sold the event, which is fine as long as operations gets a veto before the client sees it.
The sections that have to be there
The list below is longer than any single event needs. Strip what does not apply, but do it deliberately, section by section, so that an empty heading tells the reader "nothing here" rather than "someone forgot".
| Section | What goes in | Who fills it in | Who reads it first |
|---|---|---|---|
| Header and contacts | Event name, date, client, on-site client contact with mobile, venue lead, guaranteed and expected count, rooms booked | Sales | Everyone |
| Run of show | Time, action, owner, location, one line each, from first delivery to last vehicle out | Sales with operations | Floor manager, technical |
| Room set and floor plan | Configuration (rounds, theatre, classroom, standing), table count, stage, buffet stations, exits kept clear, numbered plan attached | Operations | Set-up crew, security |
| Food and beverage | Menu by course, counts per option, service times, dietary requirements and declared allergies by seat or by name, bar package and brands | Sales, checked by the chef | Kitchen, bar, servers |
| Audiovisual and technical | Microphones, screens, sound, lighting, power feeds, who supplies, who installs, who strikes, client connectors | Technical lead | Technical, external AV vendor |
| Staffing | Roles, arrival and departure times, zone assignment, briefing time, staff meal | Operations | Floor manager, HR or agency |
| Logistics and access | Delivery address, loading dock hours, vehicle passes, parking, accessibility, building restrictions | Operations | Vendors, security, reception |
| Billing and guarantee | Total, deposit received, balance due date, items billed on consumption, guarantee deadline and what happens after it | Sales, checked by finance | Floor manager (on-site questions), finance |
| Special notes | VIPs, cultural or religious requirements, surprises planned by the client, sensitive topics, anything said out loud during the sale | Sales | Everyone |
Allergens: the one section you cannot leave to memory
In the United States, the FDA's page on food allergies lists nine major food allergens (milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame) and notes that FALCPA's labelling rules do not apply to most foods sold at retail or food-service establishments that are not pre-packaged with a label. For a plated dinner there is no label, so the BEO has to do that job. Whatever the client told sales about a guest's allergy has to reach the pass in writing, per seat or per named guest, or it did not reach it at all. The FDA Food Code, the model that state and local regulators adopt, is the reference your health inspector will be working from.
UK venues work under a different frame. The Food Standards Agency's allergen guidance for food businesses covers how allergen information has to be provided for food served on the premises, and its introduction to Natasha's Law applies to prepacked-for-direct-sale items such as boxed lunches or wrapped sandwiches at a conference. If your venue sells both, your BEO has to carry both sets of information.
Capacity: write the configuration next to the number
A room does not have one capacity. It has one per layout. NFPA's explainer on how to calculate occupant load makes the point that occupant load factors are chosen based on how the space is used, not on the occupancy classification of the building, and that a conference room is not treated as an assembly occupancy unless it is expected to hold fifty or more people. Rounds of ten and theatre rows in the same ballroom give different figures. Write the layout and the count side by side on the BEO so the floor manager can check them against the posted limit without calling anyone.
Where it goes wrong on the day
Most event-day incidents we hear about from venues are version failures rather than creative ones. The document existed; the wrong copy was in someone's hand.
- Several versions in circulation. V2 went to the whole team by email, V3 only to the floor manager after a client change, V4 was printed at 7 a.m. and never sent. Each team works from its own version. Date and number every issue, and withdraw the old one explicitly.
- The PDF attachment. A PDF is frozen at the moment it leaves the outbox. Any change after that requires a re-send, and re-sends are exactly what people skip under pressure.
- Vendors left off the list. The caterer, the AV company, the florist and the band need the run of show as much as your own staff, and they are the ones most likely to be working from a phone call.
- Copy-paste from last month. Reusing a similar event's BEO saves twenty minutes and imports one wrong line: an old allergy, a previous client's contact, a delivery window that no longer exists. Use a template with mandatory blank fields instead.
- Guarantee versus actual. The client guaranteed 180, confirmed 210 by text to the salesperson, and the kitchen still has 180 on paper. The change was real; the document was not updated. Any count change after the guarantee deadline goes on the BEO first and into the conversation second.
None of these require software to fix. They require one owner of the document and a rule that nothing changes verbally.
Who signs off, who gets a copy, and when
A workable circuit has four passes. Sales drafts from the signed quote. Operations and the chef read it for feasibility: can the room turn in the time allowed, can the kitchen plate three menus for that count, is the power feed real. The client reviews it and signs, which is the step Cvent describes as both parties signing off at the bottom. Then it goes out to everyone who will touch the event, internal and external, with a note saying which version this is.
The client sign-off tends to happen a few working days before the event, once the guarantee is in, and later changes are pushed as a short "what changed" note rather than a full re-issue. Hotels with a contractual guarantee deadline lock the count at that date and treat anything later as a billable variation. Whatever you choose, write the deadline on the BEO itself.
Distribution is not one list. Kitchen wants menu, counts, allergies and service times. Technical wants the run of show and the equipment list. Security wants the plan, the count and the access windows. Reception wants the client contact and arrival details. Sending everyone the full document is fine; sending everyone the same highlighted sections is better.
Paper, spreadsheet, or software
A Word template works for a venue doing a handful of events a month, with one person writing and one person reading. It stops working when three people edit, when the client changes the count twice, or when the BEO has to be rebuilt from a quote that already contains every line. At that point the document should be generated from the quote, not retyped from it. That is how event management in Joinways handles it: the signed quote becomes the function sheet, changes are versioned, and each team sees its own sections. If you are comparing tools, our venue management software buyers' guide lists what to check, and the Tripleseat alternative page covers the BEO side specifically. The full cycle, from inquiry to function sheet, is on our venue management software page.
Whatever the tool, the test stays the same. Hand the sheet to someone who knows nothing about the event. If they can run it, it is done.
Frequently asked questions
- Is a banquet event order legally binding?
- It depends on what you sign. In US hotel practice the BEO is reviewed and signed by the venue and the client, and Cvent describes it as a mini-contract limited to meeting space and banquet services. The master agreement still governs cancellation, liability and payment. Treat the BEO as the operational annex to the contract, not a replacement for it, and make sure the two documents do not contradict each other.
- How far ahead should the BEO be sent to the team?
- Late enough that the count is stable, early enough that the kitchen can order and staffing can be adjusted. That usually means a client-approved version a few working days out, then short change notes rather than full re-issues. If your contract sets a guarantee deadline, tie the final BEO to that date and write the date on the document.
- What is the difference between a BEO and a function sheet?
- Nothing structural. BEO is the North American hotel term, function sheet the usual UK term, and French and Spanish venues say feuille de fonction and hoja de evento. All of them are the operational document that turns a signed quote into instructions for kitchen, floor, technical and vendors. Use whichever your team already understands.
