Catering

How to Write a Banquet Event Order (BEO)

How to write a banquet event order: the fields every BEO needs, a sample layout, and how the kitchen, floor and office use it before and during the event.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. What a BEO is and who uses it
  2. The fields every BEO needs
  3. Writing each block well
  4. Dietary and allergen details
  5. Food safety on the BEO
  6. How each team uses the BEO
  7. Common BEO mistakes
  8. Versions and changes
  9. Using the BEO on the day
  10. Example: a short BEO for a private dinner
  11. Tools and templates
  12. Frequently asked questions
  13. References
Catering: How to Write a Banquet Event Order (BEO)Article coverCATERINGHow to Write a BanquetEvent Order (BEO)Ava for RestaurantsInsightsCatering: How to Write a Banquet Event Order (BEO)Article coverCATERINGHow to Write aBanquet Event Order(BEO)Ava for Restaurants

Key takeaways

  • A banquet event order (BEO) is the single source of truth for an event: if it is not on the BEO, it does not happen.
  • Every BEO needs the same core blocks: event facts, timeline, menu with counts, dietary meals, beverage, staffing, equipment, billing and contacts.
  • Dietary and allergen details belong on the BEO by name, because a short list of allergens causes most serious reactions[1].
  • Food safety responsibilities, including who checks temperatures and any time-control rules, should be written on the BEO[2].
  • Version every change, have the client sign off, and distribute the final BEO to every department a few days before the event.

What a BEO is and who uses it

A banquet event order, often shortened to BEO, is the document that turns a sold event into instructions. Hotels and banquet halls have used them for decades; restaurants that cater or host private events need the same thing. The BEO tells the kitchen what to cook and when, the floor team how to set up and serve, the bar what to pour, and the office what to bill.

Without one, details live in email threads, in the catering manager's head and on sticky notes. The kitchen preps from the quote, the floor sets up from a phone call, and the invoice reflects something else. A BEO replaces all of that with one page, or a few, that everyone reads the same way.

Rule of the house: if it is not on the BEO, it does not happen. Changes go through the BEO, not through a text to the chef.

The fields every BEO needs

The standard blocks of a banquet event order.
BlockFields
HeaderBEO number, version and date, event name, client, salesperson or event manager
Event factsDate, venue or room, guest arrival, service start and end, guaranteed count, expected count, service style
ContactsClient on-site contact and mobile, planner or venue coordinator, your event lead
TimelineLoad-in, setup complete, doors, each course or service window, toasts, cake, last call, breakdown, departure
MenuEach item with quantity or per-person count, preparation notes and serving style
Dietary mealsGuest name or seat, meal, allergens excluded, allergens contained
BeverageBar type, brands or packages, start and end times, permit and server training notes
Room and setupTable layout, linens, buffet or station positions, AV or stage needs, floor plan attachment
StaffingRoles, names, arrival times, uniform
Equipment and rentalsChafers, serviceware, rentals and who supplies them; return and pickup arrangements
Food safetyPerson responsible for temperatures, holding method, time-control labels if used, handwashing setup
BillingPrice basis, deposit paid, balance due, service charge and gratuity lines, PO number, tax status
Sign-offClient approval with date, and internal approval by kitchen and event lead

Keep the same order on every BEO. When a cook or server has seen twenty BEOs laid out the same way, they find the information they need in seconds, which matters at 6 pm on a Saturday.

Writing each block well

  1. Event facts in one glance

    Put the date, room, count, service style and start time in large type at the top. Anyone glancing at the board should know the shape of the event.

  2. A timeline in minutes, not phrases

    Write 6:00 doors, 6:45 salads served, 7:15 entrées, 7:45 toasts, 8:00 cake. Avoid 'dinner after speeches'.

  3. Menu with counts

    List each dish with its count or per-person quantity, plus notes such as 'sauce on the side' or 'carved at station'. Use the dish names your kitchen uses, not marketing names.

  4. Dietary meals by name

    List each special meal by guest name or seat number, with what it excludes and what it contains. Do not write 'two GF' without names if service is plated.

  5. Staffing with names

    List roles and names with arrival times. The event lead's name goes at the top.

  6. Billing that matches

    State the price basis, deposit received, balance and add-ons using the same wording as the contract and invoice.

Dietary and allergen details

The BEO is where dietary requests either reach the right guest or get lost. When the Food Allergen Labeling and Consumer Protection Act passed, eight major allergens accounted for 90 percent of US food allergies and serious allergic reactions[1]. Sesame became the ninth major allergen under the FASTER Act, with FDA requirements applying from January 1, 2023[3].

Share of US food allergies accounted for by the eight major allergens when FALCPA passedSesame was added as the ninth major allergen in 2023
Share of US food allergies accounted for by the eight major allergens when FALCPA passedDonut chart. Eight major allergens: 90%.Eight major allergens: 90%90%
  • Eight major allergens 90%

Source: US Food and Drug Administration, 2004[1]

Show the data
ItemValue
Eight major allergens90%

Write allergens using the nine major allergen names, not loose terms like 'no nuts'. For example: 'Seat 14, Jordan Patel: grilled fish, rice, greens. Excludes tree nuts, peanuts, sesame. Contains fish.' The kitchen prepares from it, the expeditor checks plates against it and the server delivers to the right seat. For the full process, see catering for dietary restrictions and allergies.

Food safety on the BEO

A BEO should say who is responsible for food safety at the event and how food will be held. Certified management makes a difference: CDC found 80 percent of restaurant norovirus outbreaks occurred in restaurants without a certified kitchen manager[4], and an infected food worker was implicated in 70 percent of norovirus outbreaks with known contributing factors[5].

  • Name the person responsible for temperature checks and the log.
  • State the holding method for each part of the menu: chafers, cold wells, or time as a control.
  • If using time as a control, note the rule; under Virginia's food regulation, for example, food must be marked with the time four hours after it leaves temperature control and discarded at that time[2].
  • Note handwashing arrangements at the venue.
  • Note the leftovers rule agreed with the client.

How each team uses the BEO

Who uses each part of a BEO.
TeamUses the BEO toKey fields
KitchenOrder, prep, cook, pack and plateMenu with counts, dietary meals, timeline, holding method
Floor or event staffSet up, serve and break downRoom setup, timeline, staffing, dietary seats
BarStock and staff the barBeverage block, times, count
OfficeBill, collect and reconcileBilling block, count, add-ons, PO
Event leadRun the event and manage changesEverything, plus contacts

Hold a short BEO meeting a few days before each large event: kitchen, floor lead and event manager read the BEO together and flag questions. It takes ten minutes and prevents most surprises.

Common BEO mistakes

Most BEO failures are not missing documents but vague ones. These are the errors that cause the most trouble on the day.

  • Counts that disagree: the menu says 85, the header says 90 and the invoice says 88. Use one count field and reference it everywhere.
  • Timelines written as sequences without times, so the kitchen cannot plan when to fire courses.
  • Dietary meals listed as totals without names or seats for plated service.
  • Beverage notes such as 'open bar' without brands, hours or limits, which leads to arguments at the bar and on the invoice.
  • Equipment lists that do not say who supplies each item, so the venue and the restaurant each assume the other is bringing chafers.
  • No named event lead, so questions on the day go to whoever looks busiest.
  • Old versions left on the kitchen board next to the new one.

Review a sample of past BEOs after a busy month and check them against what actually happened. Wherever the event drifted from the document, the BEO template probably needs a clearer field.

Versions and changes

  • Give every BEO a number and a version: BEO 2214 v1, v2, v3.
  • Mark changes clearly, such as 'count changed from 85 to 92' at the top of the new version.
  • Send each new version to the client for sign-off and to every team that received the last one.
  • Lock the BEO at the final count date; changes after that follow your final headcount and guarantee rules.
  • Remove old versions from the kitchen board when a new one goes up.
  • File the final version with the invoice, the temperature log and any notes from the event.

Using the BEO on the day

The BEO is a working document during the event, not a file for afterwards. Print copies for the kitchen board, the event lead and the bar, and keep a digital copy on the event lead's phone.

  1. Pre-shift briefing

    The event lead reads the BEO aloud to the team: timeline, sections, dietary seats, bar rules and any client requests.

  2. Kitchen checkpoints

    The expeditor ticks off each course against the BEO counts and checks every dietary plate against its line before it leaves.

  3. Record changes as they happen

    If the client adds guests or shifts the timeline, the event lead writes it on the BEO with the time and the client's initials.

  4. Count guests

    Record the actual guest count at the agreed time for overage billing.

  5. Close-out notes

    After the event, the lead notes what went well, what went wrong and anything the next BEO for this client should include.

Those close-out notes are valuable. The next time the client books, you start from a BEO that already knows they like coffee served earlier, or that the venue's freight elevator closes at 10 pm.

Example: a short BEO for a private dinner

Example (fictional): BEO 1043 v3. Saturday, private dining room, 6:30 to 9:30 pm. Guarantee 36, expected 38. Plated, three courses. Contacts: host on site, the restaurant's event lead. Timeline: 6:30 arrival with passed canapés, 7:00 seated, 7:10 starter, 7:45 main, 8:30 dessert and coffee, 9:30 close. Menu: beet salad 38, choice of short rib 24 or halibut 14, chocolate tart 38. Dietary: seat 7 gluten-free (no bread, tart replaced by sorbet); seat 22 sesame allergy (no sesame dressing, kitchen notified). Beverage: house wine package, two bottles per table of six, beer on request. Staffing: captain plus three servers, 5:30 arrival. Billing: per-person price, 20 percent deposit received, service charge as per contract, balance due on the night.

Everything a cook or server needs fits on one page. Anything not on it is a question for the event lead, not an improvisation.

Tools and templates

You can build a BEO template in a word processor or spreadsheet, but catering software that generates BEOs from the quote prevents re-typing errors and keeps versions straight; see catering software and order management. Whatever tool you use, keep the layout fixed and print it large enough to read on a kitchen board. Use the BEO's planned staff hours and counts for job costing after the event, as described in catering profit margins.

Clients notice the difference a BEO makes. An event that runs to the written plan, with the right meal at the right seat, is the strongest argument for the next booking, and a good start to keeping repeat catering clients.

Frequently asked questions

What is a BEO in catering?

A banquet event order: the document that lists everything about an event, including timeline, menu with counts, dietary meals, beverage, setup, staffing, equipment and billing, so every team works from the same plan.

What should a BEO include?

Event facts, contacts, a timeline, menu with counts, dietary meals by name, beverage, room setup, staffing, equipment and rentals, food safety responsibilities, billing and sign-off.

Who signs the BEO?

The client approves it, and internally the kitchen lead and event lead confirm it. Every new version should be signed off again.

When should the BEO be final?

At the final count date, usually a few days to two weeks before the event. Changes after that should follow your written change and count rules.

References

  1. US Food and Drug Administration (2004). Food Allergies (opens in a new tab) ↑

  2. Virginia Administrative Code, Virginia General Assembly (2026). 12VAC5-421-850. Time as a public health control (Virginia Food Regulations) (opens in a new tab) ↑

  3. US Food and Drug Administration (2023). Food Allergies (opens in a new tab) ↑

  4. Centers for Disease Control and Prevention (2026). Outbreaks and Certified Managers (opens in a new tab) ↑

  5. Centers for Disease Control and Prevention (2014). Norovirus is the leading cause of disease outbreaks from contaminated food in the U.S. (CDC press release) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo