A wedding banquet event order (BEO) is more than a menu and room setup sheet. It is the operating agreement between the couple, the sales team, banquet operations, culinary, engineering, and every vendor who touches the event.
Boutique hotels often win weddings because the experience feels personal. That advantage disappears when the final BEO leaves important decisions in email threads or in someone’s memory. The checklist below focuses on the controls that prevent avoidable day-of surprises.
The 10 wedding BEO controls
1. Separate the ceremony and reception timelines
Do not use one combined “event time” field. Capture the ceremony start, guest arrival, processional, cocktail hour, reception entrance, meal service, speeches, cake cutting, first dance, and planned end time separately.
The distinction matters because room resets, vendor access, sound checks, and staffing often happen between functions. Assign an owner to each transition and record the latest decision time.
2. Record vendor access and load-in windows
List every vendor who needs access: planner, florist, decorator, band or DJ, photographer, videographer, rental company, cake baker, transportation provider, and specialty entertainers.
For each vendor, capture:
- arrival and departure window;
- loading entrance and parking instructions;
- freight elevator or service corridor requirements;
- on-site contact;
- items the hotel is expected to provide;
- teardown and storage responsibilities.
This prevents a florist, rental truck, or entertainment crew from arriving during a guest-facing moment with no approved path to the room.
3. Document the rain and weather backup plan
A rain plan should name the alternate space, layout, decision deadline, guest communication owner, and any cost or menu implications. “Move indoors if needed” is not operationally specific enough.
Include the trigger for the decision, who has authority to make it, and how the revised BEO reaches every department. If outdoor power, tenting, heaters, umbrellas, or weather-sensitive décor are involved, list those dependencies separately.
4. Capture dietary and allergen exceptions as service instructions
Do not bury dietary information in a guest-count note. Record the number of meals, guest names or seat identifiers where appropriate, allergy severity, substitute menu, plating instructions, and the person responsible for confirming delivery.
The final BEO should distinguish preferences from allergies and should make it possible for banquet staff to identify the correct meal without announcing private guest information in the room.
5. Create a VIP and family seating control
Weddings frequently include parents, grandparents, wedding-party members, cultural leaders, or other guests who need special seating or service considerations. Record the seating plan, reserved tables, accessibility requirements, meal exceptions, and any protocol the banquet team needs to know.
If the couple has not finalized seating, write “pending” with an owner and deadline. A blank field creates more risk than an explicit open item.
6. Define AV cues and the entertainment handoff
List microphones, speakers, screens, lighting, power, music playback, presentation files, and the person calling each cue. A run-of-show should show who announces the next activity and who confirms the room is ready.
For bands and DJs, include sound-check timing, volume limits, equipment footprint, power requirements, breaks, and teardown access. For speeches or slideshows, identify the final file owner and the time by which it must be tested.
7. Control photography and videography movement
Some properties have restrictions around guest rooms, kitchens, service corridors, or historic spaces. Record where photography is allowed, when the couple can access private areas, how vendor movement intersects with service, and whether any lighting or drone restrictions apply.
This protects the guest experience while giving the couple and vendors a clear operating boundary.
8. Lock bar service timing and cutoff rules
The BEO should specify package type, hosted versus cash-bar rules, service start and stop times, last call, signature drinks, non-alcoholic options, consumption limits, and the person authorized to approve an extension.
If the bar is moving between spaces, include the transfer time and staffing plan. If minors or guests with special service needs are expected, include the required service controls without adding unnecessary personal information.
9. Assign the billing approval owner
Capture the contracting party, billing contact, authorized approver, deposit status, final guarantee deadline, included items, exclusions, service charges, taxes, and the process for approving changes.
Every extra item should have a decision owner. “Client to confirm” is not enough unless the BEO also records what must be confirmed and by when.
10. Version and redistribute every final change
The final BEO should show a version number, issue date and time, author, summary of changes, and distribution list. Do not rely on a filename such as Wedding-BEO-final-final-2.pdf to communicate revision history.
When a change affects food, setup, staffing, AV, engineering, or billing, route it to the responsible department and record acknowledgement. The latest version must be easy to identify at the event command point.
A practical 72-hour sign-off workflow
Use the final three days to close decisions rather than discover them:
- 72 hours out: confirm guest guarantee, room assignments, menus, vendors, timeline, and billing items.
- 48 hours out: issue the working BEO, run a cross-functional review, and list every unresolved item with an owner.
- 24 hours out: perform the final room, AV, vendor-access, dietary, and weather-plan check.
- Event day: use the approved BEO and run-of-show at the operations briefing; record only controlled changes.
- After the event: capture changes, service issues, and billing exceptions for the next wedding template revision.
Final pre-send checklist
- [ ] Ceremony and reception times are separated.
- [ ] Room diagrams and setup styles are attached.
- [ ] Guest guarantee and meal counts are final or assigned to an owner.
- [ ] Dietary and allergen exceptions have service instructions.
- [ ] Vendor access, load-in, parking, and teardown are documented.
- [ ] AV, entertainment, cues, and final files are tested.
- [ ] Rain plan and decision authority are clear.
- [ ] Billing approver and change-order process are clear.
- [ ] Revision number and distribution timestamp are visible.
- [ ] Each affected department has acknowledged the final version.
Start with a BEO template, then use the wedding venue BEO workflow to map the full sequence from inquiry to event closeout.