A COMPLETED BEO EXAMPLE

The BEO, filled in.From details to a clear handoff.

A banquet event order example shows how confirmed booking details become a usable event brief. This fictional 120-guest reception includes room setup, menu quantities, service times, team responsibilities, and revision notes. Use the sample to check your own handoff, then adapt the blank template to your venue.

Read the completed example ↓Get the free fillable template ↗

By Venuine · Updated October 30, 2026

ILLUSTRATIVE SAMPLE · NOT A REAL BOOKING

Banquet event order: reception example

This invented event is a training and planning example. The contacts, date, team roles, and quantities are illustrative. It is not a Venuine customer record or a substitute for your signed agreement.

Harbor Hall · ReceptionEvent reference: SAMPLE-001 · Version 3 · Internal planning copy

Fictional example

Event and date: Reception · Saturday, June 12, 2027

Guest count: 120 guests · Final count confirmed June 5

Spaces: Garden Room: reception · Terrace: welcome drinks

Day-of contacts: Client coordinator: Morgan · Venue lead: Alex
Confirm phone numbers in the working copy.

Access window: Vendors 12:00–16:00 · Guests 17:00–22:00
Breakdown 22:00–23:00

Layout and service: 12 rounds of 10 · Assigned seating
Plated dinner · East aisle kept clear

Run of service and responsible team
Time	Confirmed action	Owner / check
12:00	Vendor load-in through the service entrance; protect guest routes.	Venue lead checks access with suppliers.
15:00	Tables, chairs, linens, place settings, and signage ready.	Operations checks approved layout revision 3.
16:15	Team briefing: timeline, meal allocations, changes, and escalation contact.	Banquet captain confirms department receipt.
17:00	Welcome drinks on terrace. Use the client-approved foyer plan if weather requires.	Venue lead decides with the client coordinator.
18:00	Guests seated; plated dinner follows the agreed service sequence.	Banquet captain coordinates with kitchen.
19:15	Speeches; pause clearing while speakers use the microphone.	Service team coordinates with the AV contact.
22:00	Guest departure, supplier pickup, and breakdown begin.	Operations completes closing checks.

Confirmed services and quantities
Item	Quantity / instruction	Verification
Dinner	108 standard meals + 12 vegetarian meals = 120 guest meals.	Kitchen receives the final meal allocation and assigned seats.
Dietary requirements	Collect specific requirements securely; attach the approved meal plan.	Kitchen confirms whether requests can be accommodated. Do not infer allergy safety from a menu label.
Guest setup	12 round tables, 120 guest chairs, 120 place settings. Record supplier equipment separately.	Operations cross-checks actual room measurements and approved occupancy.
AV	One microphone; supplier confirms arrival, setup, and sound check.	Named supplier contact and backup arrangement in the working brief.
Charges and payment	Carry approved package, extras, tax, service charge, and payment status from the agreement.	Sales verifies totals. This sample does not present invented prices as real venue rates.

Revision and approval notes

Version 3: meal allocation changed to 108 standard and 12 vegetarian; the total remains 120. The venue lead rechecks the attached seating plan and distributes the current copy to kitchen, service, operations, and AV. Older copies are marked superseded.

Before release: record who reviewed each department's details, when the client confirmed changes, and which items remain open. Do not mark a field approved just because it appears in this example.

What makes this BEO useful?

One consistent guest count

The meal split adds up to the confirmed attendance. Tables, chairs, meal quantities, and seating should all describe the same event.

An owner for each action

“Sound check” needs a time and someone responsible. List the operational owner and the person to contact if the plan changes.

A current revision

A changed meal allocation is useful only if the kitchen gets it. Include the revision number, distribution list, and acknowledgement process.

How would a hotel or catered dinner differ?

A hotel may need separate arrival, meeting, reception, and accommodation references. Offsite catering may need loading access, kitchen facilities, transport, and equipment-return details. Keep the clear structure and add the requirements of the actual event. Check service windows before adapting this sample's timeline.

Check your BEO before the handoff

Start with the agreement. Confirm the event date, spaces, services, and later changes against the approved booking.
Reconcile the numbers. Compare guest totals, meal allocations, table quantities, equipment, and charges.
Resolve open decisions. Give every unresolved item an owner and decision date. Make uncertainties visible.
Brief the team. Each department confirms receipt of the current version and flags conflicts before event day.
Control changes. Record what changed, who approved it, and who needs the replacement brief.

A BEO is an operational brief. Keep the signed agreement and the event handoff connected, and follow your business's approval process when a change affects the agreed service.

From an example to your own event

The fillable BEO template gives you a blank starting point. The BEO definition guide explains its purpose. If your team repeatedly retypes confirmed booking details, explore Venuine's BEO and event handoff workflow and request a walkthrough using one of your own event scenarios.