A banquet event order is the one page that turns a booked event into a running one. It is the single document the kitchen, the floor, and the client all point at when there is a question on the day — and the reason a well-run caterer never has the conversation that begins "but I thought you said...". Here is everything a BEO has to carry, why each section earns its place, and the one field that quietly prevents the most expensive mistakes.
What a BEO actually is
A banquet event order — BEO, sometimes called a function sheet or event order — is the operational contract for a single event. Not the sales proposal, not the invoice. It is the document that translates "60-cover wedding, Saturday" into something a brigade can execute without you standing over them: who arrives when, what comes out of the kitchen in what order, how the room is set, what the client is paying for, and who signed off.
The proposal sells the event. The BEO runs it. The two are different documents written for different readers — one persuades a client, the other instructs a team — and the most common operational failure in small catering is trying to run a kitchen off a sales quote that was never built to carry a timeline.
The eleven sections every BEO needs
A complete BEO answers every question a chef, a server, or the client could ask on the day — before they ask it. Eleven sections do that.
1. Event header
Event name, date, venue and room, event type (wedding, corporate, private dinner), and the on-site contact with a phone number that will actually be answered during the event. The header is what everyone reads first; make the date and venue impossible to misread.
2. Guest count — and the guarantee
Two numbers, not one: the expected count and the guaranteed count. The guarantee is the floor the client pays for whether or not those guests show up, agreed a set number of days before the event. You cook and you bill to the guarantee (or the actual count if higher). A BEO that lists only "60" invites the post-event argument about the twelve who never arrived.
3. Run-of-show timeline
The minute-by-minute spine of the event: load-in, kitchen ready, guest arrival, canapés, speeches, each course fired and served, cake, breakdown. Everyone on the team works to this clock. A weak BEO has a start time and a finish time; a strong one has the fifteen moments in between that actually decide whether the food is hot.
4. The menu, course by course
Every dish, in service order, with portions per guest where it matters. This is the section the kitchen lives in, so it has to match your costed recipes exactly — not a prettier marketing version. If the menu on the BEO and the menu you costed are different documents, your food cost is fiction.
5. Dietary & allergens
The named exceptions: table 4 has two gluten-free, the head table has one severe nut allergy, six vegetarian across the room. This is the section that prevents an ambulance. List the count, the requirement, and where the guests are sitting, and make it the most legible block on the page. Allergen handling is a whole discipline of its own — see allergen-safe menu design — but it starts with the BEO carrying the exceptions clearly.
6. Beverage
What is being served, who is pouring, whether it is your responsibility or the venue's, and corkage if the client brought their own. Beverage is where responsibility blurs between caterer and venue; the BEO is where you make it unambiguous.
7. Staffing
How many chefs and how many servers, with call times and roles. This is also the line where most of the event's cost lives — banquet labour, not food, is the big number — so the staffing block on the BEO should match the staffing you priced into the quote. Getting the ratio right is its own topic; the BEO just records the decision.
8. Setup & floor plan
Table layout, cover count per table, linen, china and glass, buffet or station positions, the kitchen or prep area you have been given. A sketch beats a paragraph. The kitchen needs to know where the pass is; the floor needs to know where table 9 is.
9. Equipment & rentals
Everything hired or hauled: chafers, ovens, generator, marquee, the china and glass if not the venue's. This doubles as the load list — the thing the team checks against the van before leaving, and against the van again before driving home. The 12% of catering revenue lost to mismanagement is mostly this list, uncounted.
10. Charges & payment
The financial summary the client signs: per-head price × guaranteed count, itemised extras (rentals, service charge, travel), deposit paid, balance due and when. Not the cost breakdown — the client never sees your food cost — just the agreed charges. (How those charges are built is a separate craft: see catering cost per head.)
11. Sign-off
Client name, signature, date. A signed BEO is the thing that ends "but I thought...". It is not bureaucracy; it is the line between a disagreement you can resolve and one you cannot.
A worked example, condensed
A real BEO for a 60-cover plated wedding runs to a page or two. Condensed to its spine, it reads like this:
| Section | Entry |
|---|---|
| Event | Okereke Wedding · Sat 12 Sep · Riverside Barn |
| Count | Expected 62 · Guaranteed 60 (signed 10 Sep) |
| Timeline | 14:00 load-in · 17:30 canapés · 19:00 mains · 21:00 cake · 23:00 breakdown |
| Menu | 4 courses, in service order, matched to costed recipes |
| Dietary | 2 GF (table 4), 1 nut allergy (head table), 6 veg |
| Staffing | 3 chefs (call 14:00), 6 servers (call 16:30) |
| Charges | 60 × $105 + rentals + service · deposit paid · balance due day-of |
| Sign-off | Client signature + date |
Every person working the event can answer their own questions from that page. That is the whole job of a BEO: to make the event runnable without you.
Why a sales quote is not a BEO
The proposal that won the booking is optimised to persuade: hero photos, a tempting menu, a headline price. None of that helps a chef at 17:00 on the day. A BEO is optimised to instruct: counts, times, exceptions, who does what. Run the kitchen off the quote and three things go wrong — the timeline is missing, the dietary exceptions are buried in an email, and the menu on the quote is the marketing version, not the costed one. The BEO exists precisely to close those three gaps.
For the broader picture of how professional venues structure event documentation, the Cornell Nolan School of Hotel Administration publishes hospitality operations research on the same banquet and event-management practices a small caterer scales down.
In ProChefDesk
The Event tool builds the BEO from the booking you already entered: multi-function timeline, menu costed against your real recipes, guaranteed-guest count, dietary and allergen flags, staffing, itemised charges and a payment schedule. It prints a clean client proposal and an internal kitchen production sheet from the same event — two documents, one source of truth, no retyping. Open the app to build one.
What to do this week
- Take your next booked event and write the eleven sections, even roughly. Notice which ones you did not have an answer for — those are the gaps that bite on the day.
- Add the guarantee. Set the date it is due and the count it locks. Bill to it.
- Separate the menu the client sees from the menu the kitchen cooks — and make sure the kitchen's version is the one you costed.
- Get a signature. A BEO without sign-off is a draft, not an order.
The point
A BEO is not paperwork for its own sake. It is the difference between an event you run and an event that runs you. Eleven sections, one signed page, and the team can execute a wedding without finding you mid-service to ask where table 9 is or which two guests are gluten-free. Build the document once, reuse the structure for every event, and the day stops being improvised.