The BEO template every caterer should steal (and what to add)

A Banquet Event Order is the single most important operational document in catering. Everything else is a proposal, an invoice, or a record. The BEO is what keeps the kitchen, the FOH team, and the driver on the same page on event day.

Most BEO templates you can download from the internet are thin. They capture the event details but they do not capture the decisions. A good BEO is a decision log, not a data dump. Here is what belongs in one.

You can skip ahead and grab the free Caterforia BEO template from the resources page if you want the fillable PDF and Google Doc versions. The rest of this post walks through why each section matters.

Section 1: Event header (the obvious stuff, done well)

• Event name and ID. The ID matters because it ties the BEO to the invoice and the prep sheet. Do not skip it.
• Date and day of week. Day of week in words. "Saturday" is less likely to be misread than "2026-05-18."
• Service times. Guest arrival, service start, service end, vendor load-out. These are four different times and confusing them creates chaos.
• Venue address including dock access notes. If the loading dock is on a side street, write the side-street name.
• Head count, final. If this number changes after BEO print, the BEO gets reprinted. No pen overrides.
• On-site lead name and mobile. One person. One number. Not a team contact list.

The header section should fit on the top quarter of a letter-size page. It should be the first thing anyone checks.

Section 2: Staffing plan

List every position by role, not by name. "FOH Server - 6 positions" not "John, Maria, Kevin, etc." Names go on the shift schedule, not the BEO. The reason: BEOs get printed 10 days out. Shift assignments settle 72 hours out. Putting names on the BEO forces reprints.

For each role include:

• Call time and end time, in venue local time
• Uniform standard (e.g., "all-black, long-sleeve, aprons provided")
• Transportation expectation (self-drive vs. crew van)

Also include a labor cost summary line. Not per person, just the rolled-up event labor number. This is for the on-site lead to know if a last-minute "can we add a greeter?" ask is in the budget.

Section 3: Menu, with allergens

This section is where bad templates fail. A good BEO menu section looks like this for each course or station:

Appetizer station (passed, 45 min)

• Stuffed mushroom (vegetarian, contains: dairy)
• Mini beef skewer (contains: soy, sesame)
• Vegetable spring roll (vegan, contains: gluten, sesame)

Three rules:

1. Allergens in italics, inline. Do not put them in a separate table on page 5. The prep cook sees them where they matter.
2. Dietary tags (vegetarian, vegan, gluten-free) before allergens. A vegetarian who reads "stuffed mushroom" and sees "(vegetarian)" in italics is reassured. A vegetarian who has to flip three pages to verify is annoyed.
3. Every item has a par count. "Stuffed mushroom, 200 pieces (plus 10% contingency)." The kitchen builds from this number. Not from headcount divided in their head.

Section 4: Timing and flow

This is the section most BEO templates completely miss. It is a chronological flow of the event.

Event flow

• 3:00pm: Crew arrives at venue
• 3:15pm: Tables set (FOH)
• 3:15pm: Hot line setup (BOH)
• 4:30pm: Passed apps on floor
• 4:35pm: Guest arrival
• 5:45pm: Guests called to buffet
• 7:00pm: Coffee and dessert service begins
• 8:30pm: Event end (stated)
• 9:00pm: Full tear-down complete
• 9:30pm: Crew departure

Two benefits. First, a cook wondering "when do the apps need to be out of the warmer?" has an answer without asking. Second, if the client asks on-site for a 15-minute delay, the lead can scan this section and know exactly which downstream times shift.

Section 5: Special instructions and known issues

This is the section where you write down everything the sales team learned during client discovery that is not obvious from the rest of the BEO. Examples:

• "Client requested server name tags — we have ordered."
• "MOB has a severe tree-nut allergy. Pesto and pesto-adjacent items removed from menu."
• "Venue has no refrigeration. Stage cold apps in van until 4:15pm."
• "Client is particular about buffet plating; lead should do a walkthrough at 5:30."
• "Groom's brother gave the notice. He will sign off on final count. Not the couple."

This section is almost always the difference between an event that feels smooth and an event where the client felt like their specific asks did not land.

Section 6: Post-event checklist

Three things, on the back of the page:

1. Breakage or loss. Items that did not come back from the event. Who, what, cost. Goes into the next invoice cycle.
2. Staff debrief notes. Two lines maximum. "Front door check-in was slow." "Van 3's AC is failing again." These feed operations planning for the next similar event.
3. Client-facing issues flagged. Anything that should go on the follow-up call. "Guest complained about vegan option selection." "Client asked about doing their year-end party with us."

Put this on the BEO so the on-site lead fills it out before they leave. If it is a separate form, it does not get filled out.

The two things most templates forget

Final approvals trail. Who signed off on the final head count, and when? Who approved the added bar at 48 hours notice? The BEO should have three signature lines on the front: sales, client, operations. This is for your own audit trail if a dispute comes up. It does not need to be legally binding; it needs to exist.

Route detail (for off-premise). If this is a drop-off or a multi-venue event, the BEO should reference the route ID and the driver. Not the full route, which belongs on the driver's own sheet. Just enough to tie a post-event dispute ("the food got there cold") to the actual delivery record.

What the Caterforia BEO does automatically

If you are running Caterforia proposals and BEOs, the BEO template we ship does all the following without manual work:

• Menu allergen flags propagate from recipes automatically. You tag almond flour as containing tree nut once, and every item using it inherits that flag forever.
• Staffing plan pulls from the shift schedule, so updating one updates the other.
• Event-flow time rows are added from a library of templates (drop-off, full-service plated, full-service buffet, cocktail reception) and then edited per event.
• Post-event checklist is a server-side form on the driver PWA, so "fill it out before you leave" is a system requirement, not a hope.

And because the BEO is a living document, when the client adds 10 guests three days out, the menu par counts adjust automatically, the labor plan regenerates, and everyone who needs a new printed version gets one.

Get the template

The BEO template we use as our starting point is downloadable free from /resources. Use it as a starting point, not a law. The best BEO is the one that matches how your team actually runs events, which is what Caterforia helps you build toward once the template is in front of you.

Start at $1 a month to try the integrated version.