What is a BEO? A guide for wedding venues

A BEO, or banquet event order, is the operational document that tells an event team exactly what was sold and how to execute it: the date, the timeline, the confirmed guest count, the room setup, the menu and bar plan, the service details, and which vendor is responsible for what. Venue coordinators, banquet managers, catering teams, wedding planners, and the vendors on the floor all work from it on event day.

A complete BEO has seven sections: event overview and contacts, spaces and setup, timeline and operating windows, guests and tabletop and seating, food and beverage and service, vendor roster and venue rules, and approvals and open items. The BEO is not the contract and not the proposal. It is the current operational source of truth, and it should never be an old attachment buried in email.

For a wedding venue, the BEO connects sales to the floor. It turns the couple’s booked choices into instructions that setup staff, banquet captains, kitchen teams, and vendor contacts can follow without guessing.

What does BEO stand for?

BEO stands for banquet event order. The term comes from hotel banquet departments, where one order sheet told the kitchen, the setup crew, and the service staff what a booked function needed. Wedding venues, caterers, and planners use the same name and the same idea today. Some teams call it an event order, a function sheet, or a run sheet. The purpose is identical: one document that turns a booking into instructions.

What should a BEO include?

A useful BEO is specific enough to answer a floor team’s next question. A vague line such as “standard reception setup” only works until the couple, room, or package differs from the standard. Each section should name the decision, its owner, and the timing that affects execution. At minimum, a wedding venue BEO should include:

• Event overview and contacts: couple, date, event type, confirmed guest count, booked spaces, coordinator, planner, and who can approve a change on the day.
• Spaces and setup: every room and outdoor area in use, access times, ceremony orientation, table plan, chair style, staging, power, weather backup, and room turnover.
• Timeline and operating windows: venue access, vendor load-in, setup completion, guest arrival, ceremony, cocktail hour, meal service, formalities, last call, strike, and pickup.
• Guests, tabletop, and seating: final count with breakouts for adults, children, vendor meals, and accessibility needs, plus table sizes, linens, place settings, and reserved seating.
• Food, beverage, and service: selected menu, confirmed dietary needs, service style, meal timing, bar plan, cake handling, and staff meals.
• Vendor roster and venue rules: each business, lead contact, arrival window, work area, and the access, parking, power, noise, and cleanup rules that affect them.
• Approvals, charges, and open items: what is final, what is still open, who owns each open decision, and any approved addition that changes the price.

Event overview and contacts

The overview identifies the couple, event date, event type, confirmed guest count, booked spaces, and the venue coordinator. It should also name the planner or primary client contact and explain who can approve a change on the day. Teams get into trouble when a nickname, outdated count, or missing decision maker leaves staff unsure which wedding or instruction they are handling.

Spaces and setup

This is the venue’s core section. The coordinator records every room and outdoor area in use, access times, ceremony orientation, table plan, chair style, staging, power needs, weather backup, and room turnover. “Use the garden” is not enough if setup needs to know the aisle direction, reserved rows, signing table, and rain call. The common event day failure is a layout that exists in a diagram but never reaches the crew setting the room.

Timeline and operating windows

The timeline covers venue access, vendor load-in, setup completion, guest arrival, ceremony, cocktail hour, room reveal, meal service, formalities, last call, guest departure, strike, and pickup. The venue coordinator writes the operating times, then reconciles them with the planner’s run of show and each vendor’s arrival window. A timeline can look complete while still failing to reserve elevator access, loading space, room turnover, or enough time between setup and guest arrival.

Guests, tabletop, and seating

This section holds the final guest count and the counts that do not fit inside one headline number. Adults, children, vendor meals, accessibility needs, high chairs, and place settings can affect different teams. The coordinator also records table sizes, linen choices, place settings, head table details, reserved seating, and any room reset. A total guest count without these breakouts can produce the right number of meals and the wrong number of chairs or settings.

Food, beverage, and service

For a venue with in-house catering, the BEO names the selected menu, dietary accommodations, service style, meal timing, bar plan, beverage service, cake handling, and staff meal instructions. It should separate confirmed dietary needs from general preferences and show where special meals go. Mistakes appear when the menu changed after a tasting, the service time moved without the kitchen seeing it, or the seating plan and dietary list identify guests differently. Caterers who build the food section in more depth can follow the catering BEO guide.

Vendor roster and venue rules

The roster names each business, its lead contact, arrival window, work area, and dependencies. Venue notes should include the rules that affect execution, such as access points, parking, power, flame restrictions, noise limits, cleanup ownership, and pickup timing. A phone number alone does not tell the dock attendant whether the florist arrives before rentals or whether the DJ needs access before the room is dressed.

Approvals, charges, and special notes

The BEO should show which details are final, which remain open, and who owns each open decision. The coordinator records approved additions and routes any commercial change through the venue’s normal proposal, contract, or invoice process. A casual note should not quietly create a new promise, and an operational revision should not hide a charge the client has not approved.

A BEO is not a document. It is an agreement. Six private copies of an agreement is another word for a dispute.

Who prepares the BEO, and when?

The venue coordinator or banquet manager prepares the venue’s BEO. A venue usually creates it after the event is booked, once the sold package, spaces, date, and initial count are known. It starts incomplete by design. Planning meetings, tastings, floor plans, vendor confirmations, and client decisions add the operating detail over time.

The couple or planner confirms client decisions such as the count, layout, menu, and timeline. Banquet, culinary, bar, facilities, and sales leads review the parts their teams must deliver. Outside vendors confirm their own arrival, setup, and service details rather than asking the coordinator to invent them.

The BEO lifecycle in four steps

1. Create the BEO when the event books, carrying over the sold package, spaces, date, and initial guest count.
2. Fill in each section as planning meetings, tastings, floor plans, and vendor confirmations settle the details.
3. Hold a BEO review meeting before the event. Each unresolved item leaves with one owner and a deadline.
4. Lock the final guest count at the contract deadline, distribute the current version, and log every approved change after that with an alert to the affected teams.

The useful version of the review meeting is a decision meeting, not a read aloud. The team checks open items, timing conflicts, count mismatches, weather plans, access constraints, and ownership.

The final guest count deadline is set by the venue’s own contract and operating needs. After that deadline, the coordinator locks the count used for staffing, food, tabletop, and room setup, while still recording approved changes. Late revisions need a clear alert and acknowledgement, because replacing a file in one inbox does not replace the copy already printed at the service station.

Why do BEO versions drift?

Version drift starts when each team keeps a private copy. The venue writes one BEO. The caterer keeps another. The planner maintains a master timeline that quotes both. Then the guest count changes, the ceremony moves indoors, or meal service shifts. Someone updates their copy first, and each team arrives with a document that was correct at a different moment.

One version, many authors

The stronger model gives the event one current record and lets each owner maintain the section they know. The caterer owns Food. The florist owns Floral. The venue owns Spaces and Setup. Shared facts such as the timeline, guest count, seating, and vendor roster should be referenced from that record instead of copied into fresh documents.

Even with a shared record, a venue needs change discipline. Record who changed a material detail, confirm its effect with the affected teams, and label printed copies with a clear issue date. One version of the truth is a working practice, not merely a file location.

What is the difference between a BEO, a proposal, and a contract?

The proposal describes the venue’s offer before booking. It usually organizes the package, spaces, services, and price so the couple can decide what to buy. Once accepted, those sold choices become the starting point for planning.

The contract is the legal agreement. It sets the parties’ obligations, payment terms, policies, and other binding conditions. The BEO is the execution document derived from what was sold, plus the operational decisions made during planning. It tells the team how to deliver the event.

A BEO should agree with the proposal and contract, but it should not silently rewrite them. If a planning change affects price, scope, or a contract term, the venue should document and approve that change through its established process. Then the approved result should flow into the BEO used by the floor.

How Everbook handles the BEO

In Everbook, the BEO is created automatically when a proposal books. The booked proposal becomes an event record, so the BEO starts with the details already agreed. The technical reasoning behind that handoff is explained in the event that builds itself.

Each vendor authors their own section of one shared record. The venue owns Spaces and Setup, while other trades maintain their work. Vendors see their own section and the information that has been shared with them. This approach fits teams that want sales and execution connected. Venues that only need a static document can still use a simpler template. The broader workflow is covered on the Everbook platform.