BEO Template: How to Create a Perfect Banquet Event Order (+ Free Template)

The BEO template — short for Banquet Event Order — is the single most important operational document in catering. It's your kitchen's playbook, your floor captain's checklist, and your client's confirmation that every detail has been captured. A sloppy BEO leads to wrong guest counts, missing equipment, and cold food. A tight one keeps your entire team aligned from load-in to breakdown.

If you've ever shown up to an event and realized the dietary notes didn't make it to the kitchen, or that nobody packed the chafing fuel, you already know why BEOs matter. This guide breaks down every section of a professional Banquet Event Order, explains what belongs where, and shows you how to create BEOs that your team actually reads.

For caterers who want to skip the spreadsheet formatting and generate BEOs automatically from event data, CaterCamp's BEO software builds them in minutes — populated directly from your CRM.

---

What Is a BEO (Banquet Event Order)?

A Banquet Event Order is a detailed operational document that communicates every logistical detail of a catered event to your team. Unlike a catering proposal — which is a sales document sent to clients — the BEO is an internal execution plan.

Quick answer: A BEO includes the event header (client, date, venue, guest count), complete menu with dietary notes, beverage service details, a minute-by-minute timeline, room setup notes, staffing assignments, equipment list, special instructions, and a client signature block. It is the operational blueprint for executing a catered event.

Every person involved in your event should have access to the BEO: the executive chef, sous chefs, prep cooks, servers, bartenders, delivery drivers, and the event captain. When everyone works from the same document, mistakes drop dramatically.

---

Who Uses a BEO?

BEOs aren't just for large catering companies. Every catering professional benefits from a structured event order:

• Full-service catering companies — for multi-course plated events, galas, and weddings
• Corporate caterers — for recurring lunch programs, board meetings, and conferences
• Wedding caterers — where the stakes (and emotions) are highest
• Personal chefs — even intimate dinner parties benefit from a concise run sheet
• Hotel banquet departments — where BEOs originated and remain the industry standard

The format scales to any event size. A 20-person dinner party BEO fits on one page. A 500-guest gala might run four pages. The structure stays the same.

---

Section-by-Section Breakdown of a BEO

1. Event Header

The header is the first thing anyone reads. It answers the five Ws instantly.

Include:

• BEO number — unique identifier for tracking (e.g., BEO-2026-0147)
• Client name and primary contact phone/email
• Event name (e.g., "Johnson–Patel Wedding Reception")
• Event type (wedding, corporate, social, nonprofit gala, etc.)
• Event date and day of week
• Event start and end time
• Venue name and full address
• Guaranteed guest count and expected guest count
• On-site contact (if different from client — often a wedding planner or corporate event coordinator)
• BEO version number and date created

The guaranteed guest count is critical. This is the number you prep, staff, and charge for. Make it prominent — your kitchen and purchasing team rely on it.

2. Menu and Food Section

This section translates your proposal's menu into kitchen-actionable detail.

Structure by course:

• Cocktail hour / passed appetizers
  • Item name, quantity per guest, total quantity
  • Prep notes (e.g., "assemble on-site, served room temp")
• First course
  • Plating description, portion size
• Entrée
  • If guest-choice: how selections are tracked (place cards, table assignments, pre-selected)
  • Protein portions, sauce quantities
• Sides and accompaniments
  • Specify serving vessels (e.g., "roasted vegetables in 4 half-hotel pans")
• Dessert
  • Plated vs. buffet vs. dessert station

Dietary notes — directly attached to the menu section:

• Number of guests with dietary restrictions
• Specific accommodations by type: "3 gluten-free, 2 vegan, 1 severe nut allergy (table 7, guest: Sarah Chen)"
• How dietary meals are identified (colored plate marker, separate course fire, server-delivered)

Dietary details belong here, not buried in a footnote. Your chef needs them at the exact moment they're reading the menu. If you use CaterCamp's dietary database, guest allergies auto-populate on the BEO — no manual re-entry.

3. Beverage Service

Separate beverage details from food so your bar team has a clean reference.

Include:

• Bar type: Open, hosted, cash, consumption-based
• Bar hours: Start and end time (e.g., "5:00 PM – 10:00 PM, last call 9:45 PM")
• Signature cocktails: Recipe, garnish, glassware
• Wine service: Varietals, pairings by course, bottles per table vs. poured by server
• Beer selection: Draft vs. bottled, quantities
• Non-alcoholic options: Mocktails, sodas, sparkling water, coffee/tea service timing
• Bar supplies: Ice (lbs), garnish list, napkins, stirrers
• Liquor liability notes: Wristband system, ID check protocol

If the client is providing their own alcohol, note it clearly and specify who is responsible for delivery, chilling, and liability.

4. Event Timeline

This is the minute-by-minute run sheet that keeps every team member synchronized.

Example timeline for a 6:00 PM wedding reception:

Build buffer time into every transition. If the planner says cocktail hour is 5:30, your team should be staged and ready by 5:15. Timelines that run tight collapse when one thing goes wrong.

5. Room Setup and Floor Plan Notes

Your team needs to know the physical layout before they arrive.

Include:

• Table layout: Round tables for 10, rectangular head table for 12, sweetheart table, etc.
• Buffet/station placement: Which wall or area, traffic flow direction
• Bar location(s): Main bar, satellite bar, dessert bar
• Kitchen/staging area: Where your team preps, plates, and stores backup food
• Power access: Outlet locations for warming equipment, espresso machines, etc.
• AV/entertainment coordination: Where the DJ/band is relative to your stations
• Guest flow notes: Entrance path, where guests congregate during cocktail hour

If the venue has provided a floor plan, attach it. If not, sketch one. Your captain and setup crew should be able to visualize the room before they walk in.

6. Staffing Assignments

Name your team and assign roles. No ambiguity.

Example:

Include shift start/end times and specific responsibilities. "Server" isn't enough — your captain needs to know who's covering which section. If you manage staff availability across multiple events, CaterCamp's staff scheduling module prevents double-bookings and sends shift reminders automatically.

7. Equipment and Rental List

List everything your team is packing on the truck — and everything the rental company is delivering.

Your equipment:

• Chafing dishes (quantity and size)
• Serving utensils, tongs, ladles
• Hotel pans and lids
• Cambro containers
• Cutting boards, knives, kitchen tools
• Propane, Sterno, butane
• Extension cords, power strips
• First aid kit, fire extinguisher

Rental company items:

• China pattern and count
• Flatware count
• Glassware types and count
• Linen (tablecloths, napkins, runners — colors/sizes)
• Tables, chairs (if not venue-provided)
• Delivery and pickup time for rentals

Cross-reference this list against your truck pack. Missing a single hotel pan of short ribs or a case of wine glasses can derail service. CaterCamp's equipment tracking lets you assign inventory to events so nothing is double-booked or forgotten.

8. Special Instructions

This is the catch-all for anything that doesn't fit neatly into another section.

Common entries:

• "Client's grandmother is bringing a homemade cake — store in cooler, slice and plate at 7:30 PM"
• "Venue prohibits open flame — use electric chafing dishes only"
• "Load-in via service entrance on Oak Street, code #4521"
• "Photographer wants a 5-minute 'food beauty shot' before guests enter — plate 1 setting at 5:45 PM"
• "Client's dog will be present — confirm no chocolate items on dessert station below 3 feet"
• "Parking: 2 reserved spots in loading zone, street parking for staff"

These details seem minor until they're missed. A good BEO captures every conversation you've had with the client, planner, and venue.

9. Client Approval and Signature

The final section confirms the client has reviewed and approved the BEO.

Include:

• A statement: "By signing below, you confirm that the details in this Banquet Event Order are accurate and approved."
• Client printed name and signature
• Date signed
• Your company representative signature
• A note about the amendment process: "Changes after this date may incur additional charges and are subject to availability."

Get the BEO signed at least 7–10 days before the event. This gives your team time to purchase, prep, and pack without last-minute surprises.

---

BEO Template vs. BEO Software

A spreadsheet or Word-based BEO template works — until it doesn't. Here's where manual templates create problems:

• Re-typing event data you already captured in emails or your CRM
• Version control chaos — which BEO-v3-FINAL-FINAL.docx is the real one?
• No connection to your menu costs — the BEO says "pan-seared salmon" but you have no link to ingredient quantities or pricing
• Manual dietary tracking — copying allergy notes from emails into the BEO by hand
• No team distribution system — emailing PDFs and hoping everyone reads them

CaterCamp's BEO generator solves every one of these. When you create an event in CaterCamp, the BEO auto-populates from your CRM data: client info, menu selections (pulled from your menu builder with food costing), dietary flags, staffing assignments, equipment lists, and timeline. One click generates a polished, print-ready BEO. Update the event record and the BEO updates with it — no re-typing, no version confusion.

Your kitchen team, servers, and captain all access the same live document. Changes are tracked and timestamped. When you're running 8 events in a weekend, that consistency is the difference between smooth execution and chaos.

---

BEO Best Practices for Catering Professionals

• One BEO per event, no exceptions. Even a 15-person drop-off deserves a documented order.
• Distribute early. Your chef needs the BEO 48–72 hours before the event for purchasing and prep planning.
• Print physical copies. Digital is great for creation, but on-site your captain needs a printed BEO that doesn't need Wi-Fi or a charged battery.
• Review with the client by phone. Don't just email the BEO for signature — walk through it verbally. You'll catch mistakes that nobody notices in text.
• Debrief after every event. Note what the BEO got right and what was missing. Feed those lessons into your next template.
• Keep BEOs archived. They're your operational history. Repeat clients expect you to reference last year's event details.

---

Frequently Asked Questions

What does BEO stand for?

BEO stands for Banquet Event Order. It's the standard operational document used across the catering and hospitality industry to communicate every detail of an event to the execution team.

What's the difference between a BEO and a catering proposal?

A catering proposal is a sales document — it presents your menu, pricing, and terms to win the booking. A BEO is an operational document — it tells your team exactly how to execute the event after it's been booked. The proposal comes before the contract; the BEO comes after.

How far in advance should a BEO be finalized?

Finalize the BEO 7–10 days before the event. This gives your kitchen enough lead time for purchasing and prep, while being close enough to the event that guest counts and details are firm.

Should the client see the BEO?

Yes. Clients should review and sign the BEO to confirm accuracy. However, you may have an internal version with additional operational details (cost notes, staff pay rates) that the client doesn't see.

How do I handle BEO changes after the client signs?

Document all changes as a BEO addendum with a new version number and date. Have the client approve the revision. Note any cost implications. A clear amendment process — ideally outlined in your proposal's terms and conditions — prevents disputes.

---

Start Building Better BEOs Today

A well-structured BEO is the foundation of flawless event execution. Use the section-by-section framework above to build your own template, and watch your team's on-site performance improve immediately.

When you're ready to stop re-typing event data into spreadsheets, start your free trial of CaterCamp. Our BEO generator pulls directly from your CRM — menus, dietary flags, staff assignments, equipment, and timelines — so you spend less time formatting documents and more time cooking great food.