# Banquet event order (BEO) template for larger catered events

*Guides · Mays Team · August 15, 2026*

![Mays cover card: Banquet event order (BEO) template for larger catered events — One signed sheet for the kitchen, the floor and the client](https://mays-uploads.s3.us-east-2.amazonaws.com/site/blog__catering-beo-banquet-event-order-template__cover.7427502a1d.png)

A boxed lunch for 24 needs an order form and a pack-out check. A rehearsal dinner for 80 in your back room, or a buffet at someone else's venue with servers and a bar, needs more: a room layout, a timeline by the minute, staff by role, rentals, and a bill that matches what was agreed. Hotels and banquet halls put all of that on one document, the **banquet event order** (BEO), and everyone works from it: the kitchen, the floor, the bar, and the client who signs it.

For smaller drop-off jobs, use our [catering order form and event sheet](https://www.mays.app/blog/catering-order-form-event-sheet-template): it's lighter and faster. Use the BEO when the event has **staff on site, more than one course or service, rentals, or a guaranteed count**.

*This is general information, not legal or tax advice. Check your license, your health department's rules for off-site events, and your state's rules on service charges.*

## The rules that make a BEO work

- **One version.** The BEO has a version number and a date. When anything changes, you issue a new version and the old one goes in the bin. The kitchen never works from an email thread.
- **The client signs it.** The signature is what turns "about 80" into a guaranteed count you bill for.
- **Every section has an owner.** The chef owns the menu block, the event lead owns the timeline and the floor, the owner or manager owns billing.
- **It goes out on a set day.** Final BEO to every department a fixed number of days before the event, with the final count due before that. Pick the numbers once and print them on every BEO.

## Page 1: the event

**BEO #** ______ **Version** ______ **Issued** ______ **Event lead** ______

| Field | Example |
| --- | --- |
| Client and day-of contact (name, cell) |  |
| Event name and type | Rehearsal dinner |
| Date, guest arrival, service start, end | Sat; arrive 6:00, dinner 6:45, end 9:30 |
| Location and room | Back room / client venue address |
| Load-in and load-out times, dock or entrance |  |
| Expected count / **guaranteed count** / due by | 85 / ___ / Wed noon |
| Service style | Plated / buffet / family style / stations |
| Bar | None / beer and wine / full / client-supplied |
| Allergies and diets | Counts and names, with the course they affect |

**Guaranteed count rule** (write yours on the BEO). An example: "The count received by the due date is the minimum billed. We prepare a few portions over the guarantee."

## Page 2: room and setup

| Item | Detail |
| --- | --- |
| Tables | 10 rounds of 8, 1 head table of 6 |
| Linen and colors |  |
| Buffet or station layout | Sketch below or attached |
| Bar location |  |
| Gift, cake or display tables |  |
| Audio, microphone, screen | Client / venue / you |
| Signage and place cards |  |
| Setup complete by | 5:15 |

Sketch the room under the table: doors, the kitchen or service entrance, the buffet line, the bar, and where guests queue. Put the buffet away from the door guests come in through, so the line doesn't block arrivals.

## Page 3: the run of show

Work backwards from the moment the food lands on the table.

| Time | What | Who | Done |
| --- | --- | --- | --- |
| 2:00 | Load van; rentals checked against page 5 | Event lead |  |
| 3:30 | Arrive, load in, kitchen or hot boxes set | Lead cook |  |
| 4:00 | Tables, linen, buffet and bar set | Floor team |  |
| 5:15 | Walk-through with the client | Event lead |  |
| 5:30 | Staff meal and pre-shift: menu, allergies, timeline | Event lead |  |
| 6:00 | Doors; passed appetizers, bar open | Servers, bartender |  |
| 6:45 | Dinner served; allergy plates first, by name | Lead cook |  |
| 7:45 | Toasts; clear dinner | Servers |  |
| 8:00 | Cake cut and served | Servers |  |
| 9:15 | Last call | Bartender |  |
| 9:30 | Breakdown, load out, venue walk-through | Everyone |  |

## Page 4: food and drink

| Course | Item | Portion | Count | Allergens | Hot / cold | Held at |
| --- | --- | --- | --- | --- | --- | --- |
| Passed |  |  |  |  |  |  |
| Salad |  |  |  |  |  |  |
| Main |  |  |  |  |  |  |
| Vegetarian main |  |  |  |  |  |  |
| Allergy plates |  |  |  |  |  |  |
| Dessert |  |  |  |  |  |  |
| Bar |  |  |  |  |  |  |

Check every line against your [allergen matrix](https://www.mays.app/blog/restaurant-allergen-matrix-template), including sauces, dressings and garnishes. The Food Code's nine major food allergens are milk, egg, fish, crustacean shellfish, tree nuts, wheat, peanuts, soybeans and sesame (§1-201.10, [2022 FDA Food Code](https://www.fda.gov/food/fda-food-code/food-code-2022)).

**Holding:** time/temperature control for safety food stays at 135°F or above, or 41°F or below (§3-501.16(A)), on the buffet and in the hot boxes. A buffet held by time instead needs written procedures; the rules and the four-hour limit are in the [catering order form post](https://www.mays.app/blog/catering-order-form-event-sheet-template), and the [hot holding guide](https://www.mays.app/blog/hot-holding-cooling-food-safety-cafe) covers the rest. Put a probe and a log sheet on the buffet, and write a reading every hour.

## Page 5: staff, equipment and rentals

| Role | Your ratio | How many | Names | Call time | Out time |
| --- | --- | --- | --- | --- | --- |
| Event lead | 1 per event | 1 |  |  |  |
| Cooks |  |  |  |  |  |
| Servers | guests per server |  |  |  |  |
| Bartender | guests per bartender |  |  |  |  |
| Dish / runner |  |  |  |  |  |

Write down your own ratios after each event and adjust them: plated service needs more servers than a buffet, and a full bar more bartenders than beer and wine.

| Equipment or rental | Qty | From | Back by |
| --- | --- | --- | --- |
| Chafing dishes and fuel |  |  |  |
| Hot boxes, coolers |  |  |  |
| Plates, flatware, glassware |  |  |  |
| Linens |  |  |  |
| Tables, chairs |  |  |  |
| Probe thermometer, log sheet, sanitizer, test strips |  |  |  |
| Handwashing setup (if the venue has none near service) |  |  |  |

## Page 6: billing and signatures

| Line | Amount |
| --- | --- |
| Food: guarantee × price per guest |  |
| Bar: package or consumption |  |
| Rentals and delivery |  |
| Staffing, if billed separately |  |
| Service charge (%), and what it covers |  |
| Sales tax |  |
| Deposit received |  |
| **Balance due, and when** |  |

**Service charges aren't tips.** The federal regulations put it plainly: *"A compulsory charge for service, such as 15 percent of the amount of the bill, imposed on a customer by an employer's establishment, is not a tip"*, and *"where negotiations between a hotel and a customer for banquet facilities include amounts for distribution to employees of the hotel, the amounts so distributed are not counted as tips received"* ([29 CFR 531.55(a)](https://www.ecfr.gov/current/title-29/section-531.55)). So a service charge on a BEO is your revenue: if you pass some of it to the staff, it goes through payroll as wages, not as tips, and your accountant should know how you split it. Say on the BEO what the charge is for; some states and cities have their own disclosure rules. A tip the client adds on their own, on top, is a tip. Our [tip pooling guide](https://www.mays.app/blog/tip-pooling-new-restaurant-owners) covers who can share tips.

**Signatures:** Client ______ Date ______ / Event lead ______ / Chef ______

## After the event

Within two days: final bill with the actual count if it went over the guarantee, a thank-you call, and a short note on the BEO itself: what ran late, what ran out, what was left over. File it; the next event with that client starts from it.

## Where Mays fits

Mays catering covers the order side and runs with our team's setup, with payment through a connected Square account.

- **The lead and the order.** Leads move through **Pending assignment**, **Quote sent**, **Quote accepted**, **Paid**, **In prep**, **Ready** and **Delivered**. Each one keeps the event date and time, guest count, address, delivery notes and dietary notes, and **Catering → Orders** moves paid jobs through **Start prep**, **Mark ready** and **Mark delivered**.
- **Packages** set a price per serving, minimum and maximum guests, what's included and dietary tags.
- **The event on the schedule.** Add it to the day's **Events** row with the BEO number in the note, and put the call times from page 5 in as shifts or **Open shift (unassigned)** for people to claim. See [Schedule events and birthdays](https://www.mays.app/help/scheduling/schedule-events-and-birthdays) and [Open shifts](https://www.mays.app/help/scheduling/open-shifts).
- **The load-out and buffet checks.** Build page 5's equipment list and the hourly buffet temperatures as a template under **Tasks → Templates** with **Number** answers for temperatures and a **Photo** of the setup, and send it on the day with **Tasks → Create Task → From Template**. See [One-off tasks](https://www.mays.app/help/tasks-checklists/one-off-tasks).

What Mays doesn't do yet: there's no BEO document. A lead has one package and one free-text dietary note, with no courses, room setup, run of show, rentals, staffing plan, version number or client signature, and catering jobs don't appear on the schedule on their own. Keep the BEO itself as a document, and use Mays for the lead, the payment, the shifts and the checks.

## One signed sheet

Get the count guaranteed, put the whole event on one versioned BEO, have the client sign it, and send it to everyone on the same day. On the night, nobody is guessing.

[**Start your free trial**](https://go.mays.app/register): 30 days, every module, no card needed. Catering is set up with our team, so [book a walkthrough](https://www.mays.app/book?from=blog-catering-beo-banquet-event-order-template) and we'll connect it with you.

## Related help articles

- Scheduling: [Schedule events and birthdays](https://www.mays.app/help/scheduling/schedule-events-and-birthdays) — Mark catering orders, inspections and other one-off days on the schedule, with a morning reminder for that day's staff. Birthdays show on the schedule too.
- Scheduling: [Open shifts and dropping a shift](https://www.mays.app/help/scheduling/open-shifts) — Pick up extra shifts from Open shifts in the app, or drop a shift so a coworker can take it — your manager approves every claim.
- Tasks & checklists: [Creating one-off tasks](https://www.mays.app/help/tasks-checklists/one-off-tasks) — Need something done today that isn't on a checklist? Create a one-off task for one person or the whole location, on the web or in the app, or straight from a chat message.
- Tasks & checklists: [Creating a checklist template](https://www.mays.app/help/tasks-checklists/create-a-checklist-template) — Build an opening, closing or cleaning checklist once as a template — groups, tasks and answer types — and Mays turns it into your team's task list in the app.
- Tasks & checklists: [Task answer types](https://www.mays.app/help/tasks-checklists/task-response-types) — Every task has an answer type that decides how staff complete it. Tick a box, take a photo, enter a number or text, pick an option, record a location, count stock or fill in a form.

Canonical: https://www.mays.app/blog/catering-beo-banquet-event-order-template
