The BEO, Explained: What Goes In It and Who Needs to See It

The banquet event order is the least glamorous document in the wedding business and the one most likely to determine whether Saturday goes well. Everything upstream of it — the tour, the proposal, the months of planning calls — produces decisions. The BEO is where those decisions become instructions that a kitchen, a setup crew, and a bar team can execute without asking anyone a question.

When a BEO is good, the event runs quietly and nobody thinks about it. When it's incomplete, the failure is rarely dramatic. It's a linen colour that doesn't match the photos, a vegetarian entrée that was mentioned on a call and never written down, a bar that closes an hour before the client expected. Small things, each one, and each one visible to a couple who has been imagining this day for a year.

What a BEO is for

A BEO translates an agreement into operations. The contract says what the client bought. The BEO says what the staff does about it — how many of what, where, when, and in what order. It is written for people who were not in any of the planning conversations and will not have time to ask.

That framing settles most arguments about what belongs in it. If a line-level staff member would have to guess or ask, it belongs in the BEO. If they wouldn't, it probably doesn't. A BEO is not a summary of the relationship; it's a set of instructions clear enough to be followed by someone reading it for the first time at seven in the morning.

The essentials

Start with the frame: event name and date, client and on-site contact, spaces in use, and a timeline with real times — vendor load-in, staff call, guest arrival, ceremony, cocktail hour, dinner service, speeches, dancing, last call, breakdown. Include final guaranteed guest count and the number you're actually setting for, since those are frequently different by design.

Then the food and beverage detail: menu by course, exact counts, and every dietary restriction and allergy with the guest and table it belongs to. Service style, whether that's plated, buffet, family style or stations. Bar package, open or cash, start and end times, specific brands where the client selected them, whether a signature cocktail is involved and what goes in it. Cake handling and cutting time. Vendor meals, how many and served when.

Then setup: the room layout with table count and configuration, linens by colour and size, place settings, china and glassware, staging and dance floor, AV and microphones, and the placement of anything the client is bringing themselves. Finally, the commercial detail: pricing by line, service charge, tax, deposits already received, balance outstanding, and who is authorised to approve additional charges on the day.

Who needs to see it

The kitchen needs counts, courses, timing and allergies. The setup crew needs the layout, linens, and load-in schedule. Bar staff need the package, hours and brands. Service staff need the timeline and the table map. The event captain needs all of it. The client needs to approve it, and outside vendors need the slice that concerns them — the photographer needs the timeline, the florist needs delivery access and placement, the band needs the staging and power.

This is where BEOs most often fail, and it isn't a writing problem. The document is correct; the distribution isn't. A revision goes out to the kitchen but not to the florist. The client approves a change over the phone that never reaches the setup crew. Everyone is working from a BEO, but not all of them from the same one.

The version problem

A BEO is not written once. It is drafted weeks out, revised as details firm up, and revised again in the final ten days when guest counts land and the client makes their last decisions. Each revision has to reach every party who received the previous one.

Do that with emailed PDFs and the arithmetic is unforgiving. Three revisions across seven recipients is twenty-one deliveries that all have to land, be opened, and replace whatever the recipient had before. Miss one and you have a kitchen cooking to a count that changed on Tuesday. The most common day-of failure in this business is not a mistake — it is someone competently executing an old version of the plan.

A working rule

The useful test for a BEO is whether an experienced person who has never met the client could run the event from it. Not with your help on the phone — from the document alone. If they'd need to call you to find out when the bar closes, whether the head table gets different linens, or which guest has the shellfish allergy, then the BEO isn't finished, however long it is.

The Vowsoft Solution

In Vowsoft, the BEO isn't a separate document someone assembles from the event details. It's generated from them. Menu selections, guest counts, timelines, floor plans, dietary restrictions and pricing already live on the event record, so the BEO reflects the current state of the event rather than a snapshot of when someone last rebuilt it.

When something changes, the BEO changes with it, and the people who need to know are working from the updated version rather than an attachment that may or may not have been opened. Client approvals are captured against the event with a name and a timestamp. Vendors and staff see the detail relevant to them. There's still exactly one BEO for Saturday, and everyone is holding it.