Catering BEO guide: menus, head counts, costing, and prep sheets

A catering BEO is the live operational record that tells the sales team, kitchen, service crew, venue, and planner what food was sold and how it will be delivered. It should connect the current menu and guest count to dietary needs, service timing, costing, and prep sheets, so every team works from the same approved details.

BEO stands for banquet event order. A catering banquet event order translates a booked proposal into instructions for producing and serving the event. The proposal explains the offer, the contract records the agreement, and the BEO explains execution.

A prep sheet is a kitchen view of that record. It converts menu choices and the live count into the work required for each dish. If the BEO and prep sheet rely on separate copies, a late count or menu change can reach the event manager without reaching the chef.

What belongs in a catering BEO

A useful catering BEO answers the next question for each person touching the wedding. A banquet captain needs service order and timing. A chef needs the menu, count breakouts, and dietary detail. A sales lead needs confirmation that approved choices match the proposal. A headline guest count and a list of dish names are not enough.

Event identity and the live count

Start with the couple, event date, venue, catering lead, planner, and the current approved guest count. Break out any groups that change production or service, such as vendor meals, children’s meals, or special meals. Label whether a count is pending or confirmed. The kitchen should never have to infer which number is the working number from an email thread.

Menu and dish detail

Record each selected dish in the order the team will produce and serve it. Include the service style, relevant components, accompaniments, and approved substitutions. A tasting may replace a sauce, remove a passed item, or change a side. Those decisions belong beside the dish, not only in tasting notes that production never sees.

Dietary needs and special meals

Dietary detail must tell the kitchen what to make and the service team where it goes. Record the need, the approved meal, the guest or table identifier used by service, and the person responsible for confirming delivery. Keep allergies distinct from preferences. A vague note such as “gluten free guests” leaves the kitchen without a production count and the captain without a delivery plan.

Service style and timing

State whether the meal is plated, buffet, station based, or family style. Then connect kitchen timing to the event timeline: access, setup, cocktail service, room opening, meal service, formalities, clearing, and breakdown. If the planner moves speeches ahead of dinner, the BEO must show what that means for fire time and service readiness, not merely display a new reception time.

Tabletop, rentals, and venue dependencies

List the place settings, serving pieces, linens, tables, power, water, refrigeration, loading access, waste plan, and rental responsibilities that affect catering. Name the owner for each dependency. Off premise teams need this detail early because the menu can be correct while the site still lacks the equipment, access window, or service ware required to deliver it.

Crew calls and operating ownership

The BEO should identify the catering lead, kitchen lead, banquet captain, and the handoffs each owns. Include crew arrival, setup, meal service, clearing, and departure windows. When a client or vendor asks for a day of change, the team should know who can approve it, who records it, and who must acknowledge the effect.

How the BEO moves from booking to prep

The booked proposal sets the starting point

The first BEO should begin with what the couple accepted: the initial menu, service style, event date, location, and working count. Copying those choices into a new document creates an immediate opportunity for drift. A stronger process carries the sold details forward and marks unanswered planning items as open.

The tasting resolves menu decisions

After the tasting, record each accepted change against the menu item it affects. Confirm whether the change alters a dish component, dietary meal, service step, rental need, or commercial scope. The event manager should route a price or scope change through the normal approval process before treating it as an instruction for the kitchen.

The live count drives production

As replies arrive, update the shared guest count and the breakouts used by each dish. The prep sheet should read those current values. It should not depend on someone remembering to revise a separate kitchen workbook. Good review practice checks that the total, entrée choices, dietary meals, vendor meals, and place settings reconcile before production begins.

Late changes need acknowledgement

A late change is complete only after the current record changes and every affected owner sees the effect. A smaller count can change food preparation, staffing, tabletop, and the invoice. A later service time can change kitchen sequencing and crew calls. Record the change, its owner, and the teams that confirmed it.

Costing and prep sheets are connected views

Costing and prep answer different questions. Costing shows what each dish is built from and supports the price offered to the client. Prep translates the approved menu and live count into production work. They should share the same dish definition, even though sales and kitchen staff use different views.

Consider a couple who changes an entrée after the tasting and later adjusts the guest count. If the recipe, proposal, BEO, and prep sheet are independent files, the event manager must remember every copy. If they read one approved menu and count, the kitchen gets the current requirement without reconstructing the sale.

One BEO across caterer, venue, and planner

The caterer should own the Food detail. The venue should own spaces, setup, and site rules. The planner should coordinate the shared timeline and client approvals. Everyone still needs the facts that cross those boundaries. The venue BEO guide explains how that broader event record serves the floor.

Everbook uses this ownership model. A booked proposal becomes one event record with a Food section for the caterer. Head count, dietary needs, service timing, and place settings stay on that record. Caterers can price dishes from components and print prep sheets from the live count in Catering Orders. The catering product page describes the trade workflow, while the platform overview shows how other vendors read their own shared sections.

That connected approach fits a wedding caterer that wants the sale, event order, and production work to stay in agreement. A team that only needs a static kitchen document may prefer a simpler template. Software does not replace review discipline. It gives each owner a current place to record and verify the decision.

A BEO review checklist for this week

• Choose one upcoming wedding and confirm that the menu, live count, dietary breakout, and service timing agree.
• Ask the chef and banquet captain which BEO notes still require them to guess. Turn those notes into named fields or clear instructions.
• Assign an owner to every open menu, rental, access, staffing, and timeline decision.
• Confirm that every prep sheet comes from the current count and approved menu, not an earlier attachment.
• Set a clear method for alerting the kitchen, service lead, venue, and planner when a material detail changes.