Banquet Event Order (BEO): A Club Guide

A banquet event order (BEO) is the document that tells every department at the club exactly what happens at a function: the room, the times, the guest count, the menu course by course, the bar, the setup, the audio-visual, the staffing, the special requests and the billing. It is the contract between the catering office and the operation. When the BEO is complete and current, a wedding for 180 runs like a Tuesday. When it is wrong, the kitchen fires 150 plates for 180 guests and the captain finds out at the salad course.

This guide covers what a BEO contains, how it moves from inquiry to invoice, how to manage changes and the guaranteed count, how different roles use it, and how to keep it the single source of truth. For a printable starting point, use the BEO template. See also the glossary entry for banquet event order.

What a BEO contains

A complete BEO has these sections. Clubs format them differently; the content is consistent.

From inquiry to invoice

A function moves through a predictable life cycle. The BEO is created early and changes at every step.

1. Inquiry. A member or outside client asks about a date. The catering office checks room availability and holds the date.
2. Proposal. Menus, pricing, room fees and minimums go to the client.
3. Booking and deposit. The client signs a contract and pays a deposit. The first draft BEO is created.
4. Planning. Menu tastings, floor plan, bar selections, AV, timeline. The BEO is revised as decisions are made.
5. Final details and guarantee. The client confirms the guaranteed count and final details by the contract deadline. The BEO is final and distributed.
6. Service. The operation runs from the BEO.
7. Final bill. Actual consumption (bar, overages) is added; the balance is invoiced and deposits are applied.

Deposits received before the event are a liability — the club has not yet provided the service — and become revenue when the function is served. See club month-end close.

The guaranteed count

The guaranteed count is the number of guests the client commits to pay for. It protects the club from preparing and staffing for guests who don't arrive.

• Deadline. The contract sets when the guarantee is due — commonly a few business days before the event, so the kitchen can order and the office can schedule staff.
• Billing. Most contracts bill the greater of the guaranteed count or the actual count served.
• Kitchen preparation. Many kitchens prepare a small overage above the guarantee to cover late additions; the policy should be written down so the chef isn't guessing.
• Pre-selected entrées. When guests choose entrées in advance, the guarantee has two parts: the total, and the count of each entrée. A change of one guest's entrée after the deadline is a kitchen event, not just a billing one.
• After the deadline. Increases may be accepted subject to availability; decreases are usually not accepted.

Managing changes

The most dangerous BEO is an out-of-date one. Changes arrive by email, phone and in person, and every department needs to know.

• Number every revision. Revision 3 replaces revision 2, and the header says so.
• Mark what changed. Highlight or list changes at the top so the chef doesn't have to compare two documents line by line.
• Re-approve material changes. Changes to count, menu or price should be approved by the client, just as the original was.
• Redistribute with sign-off. Each department head confirms they have the current revision.
• Freeze at the deadline. After the guarantee deadline, changes go through the catering manager only.
• One source. If the BEO lives in a word-processing file emailed as attachments, someone will work from an old copy. Keep one live BEO everyone reads.

How each role uses the BEO

The same information, sliced differently:

Printing the full BEO for everyone works but buries each role's details. Role-specific views — a kitchen sheet with production counts, a captain's sheet with the seat map, a server's section sheet — reduce errors, provided they are all generated from the same BEO rather than typed separately.

Chef production counts

The kitchen needs a production sheet derived from the BEO: how many of each dish to prepare, per course, and when to fire each course. For a plated dinner with pre-selected entrées, that means totals across the room — for example, 104 chicken, 58 salmon, 18 vegetarian — plus special plates for each dietary restriction, labeled with the table and seat.

The production count should be generated from the seating and meal selections, not re-keyed. A chef working from a count typed separately from the seat map will, sooner or later, be out by one table.

Billing and the member account

Club functions fall into two billing patterns:

• Member-hosted events — a member's anniversary dinner, a member's daughter's wedding — are often charged to the member's house account, possibly with a deposit and a payment schedule.
• Outside events — a corporate outing, a non-member wedding — are invoiced to an outside client with a deposit schedule and a final invoice.

Either way, the BEO's billing section should match the contract and the invoice, and the final bill should apply deposits received and show the guarantee versus actual count. For member-hosted events, check whether the club's food and beverage minimum policy counts event spend. For 501(c)(7) clubs, outside events are nonmember income; see the nonmember income guide.

The weekly BEO meeting

Most clubs with a busy banquet calendar hold a standing BEO meeting — weekly in season — where the catering manager walks every department through the coming events.

• Who attends: catering or events manager, executive chef or banquet chef, banquet captain, bar manager, setup or facilities lead, and the controller or accounting contact for billing questions. The golf professional attends when an event overlaps a tournament.
• What is reviewed: every event in the next seven to fourteen days, in date order — the current revision, counts, menu and dietary needs, timeline, setup, staffing and anything still open.
• What comes out: a list of open items with owners and deadlines, confirmation that every department has the current revision, and staffing and ordering decisions for the week.
• What it catches: double-booked rooms or equipment, events whose guarantee is overdue, menus that need product the kitchen hasn't ordered, and setups that collide with a morning event in the same room.

Keep the meeting short by working from the live BEOs rather than printed copies, so nobody is reviewing yesterday's version.

Common BEO failures

• Counts that don't match. The BEO says 180, the floor plan seats 176, the kitchen prepared for 172.
• Allergies in the wrong place. The restriction is in an email, not on the BEO or the seat map.
• Timeline drift. The band's schedule changed; the kitchen's firing times didn't.
• Bar charges disputed. Consumption bar totals without a record of what was poured.
• Deposits lost. A deposit recorded as revenue when received, then again when the final bill is paid.
• The wrong revision. One department worked from yesterday's copy.

How Bubs handles BEOs

In Bubs, a function is an event with a status from inquiry through booked, confirmed, in service and completed, and its BEO is a live view of the event rather than a separate document. See events and banquets.

• One source, several views. The BEO is generated from the event itself — the room booking, the floor plan, the per-seat meal selections, the menu and the billing — in a full version and in role views for the server, the kitchen and the captain.
• Chef production counts come from the seat plan and are reconciled against live kitchen tickets as each course fires, per station and per meal.
• Courses fire to the kitchen in rounds, with every plate carrying its table and seat so the right plate reaches the right guest.
• Billing follows the host: a member-hosted event can go on the member's account; an outside event is invoiced with a deposit schedule and paid through a branded online payment page. Deposits are held as a liability and recognized as revenue when the event is served.
• The room is booked so that two functions can never be sold the same space at the same time.

See also the banquet seating with meal selections guide, the kitchen display and the BEO template.