How to Write a Banquet Event Order

A banquet event order is the internal production sheet for a single event. It is not the catering contract and it is not the invoice, though it draws from both. Once a client signs off on pricing and terms, the BEO becomes the working document your kitchen, floor staff, bar, and any outside vendors use on the actual day. Everyone touching the event should be able to open it and know exactly what they are responsible for without a phone call to the office.

Because it is an operations document first, precision matters more than polish. A BEO that says dinner at seven is less useful than one that says cocktail hour five to six, doors to the ballroom six, salad course six fifteen, entree six forty five, cake cutting eight thirty. The goal is to remove every judgment call from the day of the event, so write it as if the person reading it has never spoken to the client.

Start with the header block, since it is what every reader checks first to confirm they have the right event. Include the client or company name, the on-site contact and cell number for the day of, event name or occasion, date, and a BEO or event number if you track those. List the venue and specific room, because a caterer working multiple ballrooms in the same building needs the exact space, not just the property name.

Guest count deserves its own line with two numbers: the guaranteed count and the expected or set count. Most catering contracts specify guests are billed at whichever is higher, and the kitchen needs to know the guarantee to order proteins and produce, commonly due from the client 72 hours out for hotel banquet teams and 5 to 7 business days for independent caterers who shop and prep. Note the event type too, since a corporate lunch, a plated wedding dinner, and a bat mitzvah reception all carry different service assumptions even at the same headcount.

This is the section that prevents the wrong floor plan from being built. Name the setup style explicitly, rounds of ten, rounds of eight, classroom, theater, u-shape, banquet rows, or a mixed layout with a head table and a dance floor. Specify linen color and size, chair type if you offer options like chiavari versus banquet chairs, and any staging, dance floor, or podium placement with rough dimensions if the room is tight.

Attach or describe the floor plan, and give a load-in and load-out window for anyone bringing in rentals, florals, or a DJ rig. Then build the timeline in fifteen minute increments for anything client-facing: doors open, cocktail hour, program moments like toasts or a keynote, meal service by course, and load-out. A vague timeline is the single most common cause of a BEO falling apart on site, because staff improvise when they do not know what happens next.

List the menu by course in the order it will be served, not the order it appears on your proposal. For a plated dinner that means passed hors d'oeuvres, first course, salad, entree choices with the client's final split by protein, and dessert, each with the actual dish name the kitchen uses, not the pretty client-facing description. For buffet or stations service, note chafer counts, replenishment timing, and which stations open and close when.

Flag every dietary restriction and allergy by guest count, not just noted once at the bottom, since the kitchen needs to know if it is preparing three gluten-free plates or twelve. Cover the bar separately: open, cash, or consumption bar, house pour brands, beer and wine selections, corkage if applicable, and the exact start and last-call time. If a specialty cake or dessert is being cut and plated by your staff rather than a vendor, note that here too.

Every event needs a staffing count tied to the guest count and service style, since a plated dinner for a hundred fifty needs more captains and servers than a buffet for the same headcount. List roles and call times: chef, sous, servers, bartenders, captain, and any lead who owns the room. If you are subcontracting bartending or a rental company for tables and chairs, name the vendor, the contact, and their delivery window on this BEO so your floor staff knows who to expect at the door.

AV and rentals belong here too even if another vendor supplies them. Note microphone count and type, projector or screen needs, uplighting, a DJ or band's power and space requirements, and any specialty rentals like a champagne wall or a photo booth footprint. If your venue has a house AV package, state what is included versus what the client is paying to add.

Close with the financial summary: food and beverage subtotal, service charge or gratuity percentage, tax, any room or facility fee, and the total due. State the deposit already paid and the balance due date so the day-of team is not fielding billing questions. If the client is adding items after the contract was signed, like an extra hour of bar service or additional stations, note them as an addendum with the updated total rather than editing the original figure silently.

Finally, include a revision date and version number on every reissue, since a BEO that changes three times before the event needs a clear record of which version is current. Route the final version for sign-off from the client or your internal event lead before it goes to the kitchen and floor, and keep a signed copy on file. This is also where a shared document trail earns its keep, since chasing a signature by email is slower than a single approval link everyone can click.