A banquet event order — a BEO — is the document that turns a booked event into a plan your team can actually execute. Hotels have entire banquet departments to produce them. As an independent caterer, you are the sales team, the kitchen, and the banquet manager, which means the BEO is doing more work for you, not less: it is the one page that keeps a 75-guest lunch from becoming a 75-guest scramble.

This guide walks through how to write a BEO from scratch, section by section, with a worked example you can copy. If you would rather not start from a blank page, grab the free BEO template or fill one in on screen with the free BEO generator — but read this first, because a template only helps if you know what belongs in each box.

What a BEO is (and what it is not)

A BEO is a working operational document. It gathers the client and event details, a timeline, the full menu with counts, beverages, staffing, setup, and a billing summary into a single sheet that everyone works from on event day. Industry glossaries list a dozen names for the same thing — function sheet, event order, run sheet, kitchen order — but the job never changes: one authoritative page so the kitchen, the service team, and the venue are never guessing.

It is not a contract. The contract is the legal agreement — pricing, deposit terms, cancellation policy, signatures — and it protects the deal. The BEO is the execution document, and it protects the event. You generally need both: the contract to get paid, the BEO to run the day. Confusing the two is where problems start, because a signed contract from three weeks ago does not tell your prep cook how many gluten-free plates to make tomorrow.

Errors on a BEO are expensive in a specific way: they surface at the worst possible moment, in front of the client, with no time to fix them. A guest count that is 10 low means 10 people without lunch. A missing dietary note means an allergic guest served the wrong dish. A timeline without a load-in time means your van arrives after the venue’s doors are locked. None of these are exotic — they are all just information that never made it onto the sheet.

Build it section by section

A complete BEO has the same core sections every time. Here is what goes in each, in the order you should fill them.

Event and client details

Start with who, when, and where: client or company, on-site contact with a phone number you can actually reach on the day, the event date, start and end times, the venue, and the guest count. Be disciplined about that last field — it must be the final guaranteed count, not the estimate from the proposal. Everything downstream keys off this number, so if it is wrong, the whole sheet is wrong.

Timeline

Give every line a clock. Load-in, setup, guest arrival, each course or service point, and breakdown, each with a time. “Setup, then service” is not a timeline; “Load-in 8:00, tables set by 10:30, guests 11:30, lunch service 12:15, coffee 1:00, breakdown 2:00” is. If the venue has a hard out — a time you must be off the property — write it at the bottom in bold so nobody forgets it exists.

List every course and item, the quantity you are preparing, and dietary notes attached to the specific dish. The dietary column is not optional and it does not live in an email thread — if a note is not on the sheet your kitchen prints, it effectively does not exist. Break out vegetarian, vegan, gluten-free, and allergy plates as their own counted lines so prep can see them at a glance.

Beverages

Note what is served and how: hosted or cash bar, coffee and tea service, water, and any specific requests. If there is alcohol, this is also where you flag who is responsible for service and whether a bartender is staffed (which ties into the next section).

Staffing

List each role, how many people, and their call time. This section does double duty: it is your labor plan and your labor cost, and it is also the line item the client reads to understand the service level they are paying for. Undershoot it and your team drowns; overshoot it and your margin evaporates. The BEO is where you get it right on paper before the day.

Setup and equipment

Describe the room in a sentence or two — “rounds of 10, head table for four, buffet along the north wall” — and then tick what has to physically be there: tables, linens, AV, bar, dance floor, staging. This is the section the venue and your load-in crew read first.

Billing summary

Close with the numbers: subtotal, tax, total, deposit collected, and balance due. Even though the money lives in your contract and invoices, restating it here means there is zero ambiguity on event day about what is still owed. The balance-due line is the one clients look at first.

A worked example: a 75-guest corporate lunch

Picture a mid-size company booking a plated lunch for 75 in a downtown event hall. The BEO header reads: Client — Meridian Software; Contact — Jordan Rivera, (555) 123-4567; Date — Thursday, September 17; Venue — Riverside Hall; Guests — 75 (guaranteed).

The timeline runs load-in 9:30, kitchen and buffet staged by 11:15, guests arrive 12:00, plated service 12:20, dessert and coffee 1:15, breakdown by 2:30, off property by 3:00 (venue hard out).

The menu lists a starter salad (75), two entrée choices — herb chicken (50) and roasted vegetable orzo (25, of which 8 are gluten-free and 4 are vegan) — and a dessert (75). Because those dietary counts are on the sheet, the kitchen plates exactly eight gluten-free meals, not “a few.”

Staffing is a chef, two cooks (call time 9:30), and four servers (call time 11:00). Setup is rounds of 10 plus a head table, house linens, and a coffee station; no bar, no AV. The billing summary shows a $4,200 subtotal, 7% tax, a $4,494 total, a 50% deposit already collected ($2,247), and a $2,247 balance due on completion.

That single page is now everything the kitchen, the servers, and the client need. You can produce exactly this in the BEO generator in a few minutes and print it.

Distribution and kitchen handoff

A BEO only works if the right people see it in time. Get it to the kitchen at least a day ahead so prep can plan counts and order shortfalls — not the morning of, when there is nothing they can do about a surprise 20 extra covers. Give the service team a copy at their call time so they can read the timeline before doors. Many caterers also send a copy to the client a few days out to confirm the count and the menu in writing; it is the cheapest insurance you will ever buy against a day-of dispute.

Treat the guaranteed count as a cutoff. Once the BEO is distributed, changes should go through you and be re-issued, not whispered to a server on the floor. One source of truth, one version everyone is holding.

The mistakes that cost the most

Three errors do the most damage, and all three are just missing information. A stale guest count — carrying the proposal estimate instead of the final guarantee — throws off food, staffing, and cost in one move. Dietary notes stranded in email instead of on the menu line lead directly to the wrong plate in front of the wrong guest. And a timeline with no times turns event day into improvisation. Fix all three by treating the BEO as the single place the truth lives, and by updating it the moment anything changes.

A fourth, quieter mistake is doing this by hand once you are busy. A template is perfect for your first events (start with the free template). But once you are writing several BEOs a month, retyping the same client, the same menu you already priced, and the same deposit you already collected is both slow and error-prone.

From blank page to one-click BEO

The progression most caterers follow is simple: template, then generator, then software. When you are booking regularly, nxcatering builds the BEO for you — one click turns an accepted proposal into a finished banquet event order with the client, menu, counts, and deposit already filled in, so there is nothing to retype and nothing to transcribe wrong. It is part of the same flat plan that handles your proposals, invoices, and payments; the pricing page covers exactly what is included. Before the BEO, of course, comes the proposal that won the booking — see how to write a catering proposal.

Whichever stage you are at, the principle holds: put every detail on one sheet, give every step a time, and keep a single source of truth. Do that and the BEO does what it is supposed to — it makes event day boring, in the best possible way.