How to Use a BEO (Banquet Event Order) Effectively

A BEO (Banquet Event Order) is the master document for a catering event. It holds every detail your team needs to get the order right: what food, for how many people, at what time, where, and how it gets set up.

If you're doing drop-off catering for offices, you probably don't need one. But once your program grows into bigger events, knowing how a BEO works helps you look professional and avoid expensive mistakes.

What is a BEO?

The format is standard, and every BEO has the same sections.

• Event details: customer name, company, event type, date, time, location
• Guest count: guaranteed number and any expected overage
• Menu: every item being served, with quantities and dietary notes
• Service details: buffet vs. plated, self-serve vs. staffed, setup requirements
• Beverage service: drinks included, bar setup if applicable
• Logistics: delivery time, setup time, contact person on-site, access instructions
• Equipment: chafing dishes, serving utensils, linens, plates, anything you're providing
• Pricing: itemized breakdown including food, delivery, service, equipment, tax
• Payment status: deposit collected, balance due date, payment method
• Special instructions: anything else the team needs to know

BEOs come from hotel banquet departments, where one event touches the kitchen, banquets, AV, and the bar. For a restaurant, a stripped-down version does the same job: everyone on your team knows exactly what needs to happen.

When do restaurants need BEOs?

You need a BEO for:

• Events serving 50+ people: too many details to keep in your head
• Full-service catering: your team sets up, serves, and breaks down
• Multi-course events: timed courses, cocktail hour + dinner, etc.
• Events with equipment: chafing dishes, linens, serving staff, anything beyond food drop-off
• High-stakes events: weddings, galas, corporate board dinners, anywhere a mistake is unacceptable

You probably don't need a BEO for:

Standard drop-off catering, boxed lunch deliveries, and small orders under 25 people. A good order management system with packing lists covers drop-off, online ordering handles boxed lunches, and a detailed order confirmation is enough for the small stuff. If you're mostly drop-off, the order details in your catering software do the same job as a BEO, and you only need the formal version once an event gets too complicated for an order ticket.

How to create effective BEOs

Keep it to one page

A 5-page BEO doesn't get read. Fit it on one page (front and back if you must), with sections, headers, and enough white space that someone can scan it in the kitchen.

Use a consistent template

Same format every time, so your team always knows where to look. Don't redesign it per event.

Include timing details

The most important section of a BEO is the timeline:

Without a timeline, your team is guessing.

Get customer sign-off

Send the BEO to the customer for approval 3-5 days out. It's your final confirmation of every detail, it heads off day-of surprises, and it doubles as a lightweight contract.

Distribute to every team member involved

Kitchen, delivery, setup. Everyone gets a copy and everyone works from the same document.

BEO template for restaurants

Here's a practical template adapted for restaurant catering:

BANQUET EVENT ORDER

Event: [Event name/type] Client: [Name] | Company: [Company] Date: [Date] | Time: [Start - End] Location: [Full address] On-site contact: [Name + phone] Guest count: [Guaranteed count] (setup for [count + 10%])

MENU

Dietary accommodations: [Vegetarian count, GF count, allergies]

BEVERAGES [Beverage details]

SERVICE STYLE: [Buffet / Plated / Stations / Drop-off]

EQUIPMENT PROVIDED

• Chafing dishes ([qty])
• Serving utensils
• Plates/napkins/silverware
• Linens
• [Other]

TIMELINE [Prep start] → [Load] → [Depart] → [Arrive/setup] → [Service] → [Breakdown] → [Depart]

PRICING

Payment: Deposit of $[amount] collected [date]. Balance of $[amount] due [date].

Special instructions: [Any additional notes]

Client approval: _____________ Date: _________

BEO vs. catering software order details

For most restaurant catering (drop-off and pickup), you don't need the full BEO workflow. Catering software captures the same information:

FlashCater's order management covers drop-off. If you graduate to full-service events that need real BEOs, platforms like Caterease specialize in that workflow.