How to write the beverage section of a BEO

Start with the decision, not the document

A banquet event order, or BEO, is the working plan for an event. The beverage section should let a bar lead prepare and execute the approved service without hunting through a message thread. Start with the event version, guest count, service windows, venue access, and a person authorized to approve changes.

Keep the beverage section attached to the master event plan. It does not replace the venue contract, licensing requirements, or safety plan. If two documents disagree about service time, resolve that conflict before the team arrives. Put the revision date and approving role on the first page.

Write fields that answer floor questions

Organize the page around decisions the crew will actually make. “Full bar” is not an operating instruction. The menu, station map, and service method need enough detail that two people would set up the same room.

• Scope: confirmed guests, planning attendance, service start and stop, drinks included, and exclusions.
• Stations: station ID, location, queue approach, accessible service point, power, water, drainage, and storage access.
• Menu: approved recipe version, serving vessel, garnish, finishing steps, zero-proof alternatives, and allergen communication.
• Inventory: batch quantities, package sizes, usable stock, purchase quantity, supplier owner, and delivery check.
• People: lead, bartenders, barbacks, runners, call times, relief coverage, and escalation route.
• Close: last-call decision owner, alcohol-security plan, waste handling, rental return, and inventory reconciliation.

Give ice, glassware, and cold storage their own lines. Record the planning assumption and who verified it. Do not hide those quantities inside a general supplies total or treat a generic online ratio as a venue-specific answer.

A fictional beverage BEO, in miniature

The 198 serves above comes from a fictional allocation: 120 guests × 2.5 planned beverage servings × 60% for this recipe × 1.10 contingency. It is inventory math, not advice about how much a guest should drink. The remaining menu allocation needs a separate plan.

Make the handoff explicit

Use a status for every unresolved item: proposed, awaiting confirmation, or approved. A blank cell looks too much like an accidental omission. Assign an owner and a deadline to anything that can stop service, including venue access, permits, supplier delivery, and refrigeration. Keep a scope matrix with deliverable, owner, due date, status, and dependency, then add attire and briefing requirements where the crew will find them.

At the final review, read the BEO alongside the staffing sheet, run of show, and procurement list. Check that the call times, quantities, and recipe versions match. Then issue one current copy and mark earlier versions superseded.

Before you release it

Ask the person receiving the document to walk through arrival, opening, the first busy period, a rest break, and breakdown. If they need to guess where an item is or who can approve a substitution, add that answer. Keep contact details in the controlled working copy, not in a public template.

The blank toolkit gives you the field structure. Fill it with confirmed decisions, then have the responsible operator review it. A completed template is not evidence that the venue, legal, accessibility, or food-safety requirements have been met.

Connect the rest of the plan