Free BEO template (banquet event order)

What a BEO is, and how caterers use it

A BEO — a banquet event order — is the working document a catering business runs an event from. It is not the proposal you send to win the job and it is not the invoice you send afterward. It is the single sheet that sits between them: once a client says yes, the BEO gathers every detail the day actually depends on into one place, so the kitchen, the servers, the captain, and the client are all working from the same facts.

The format is not sacred, and you will see plenty of BEO examples that look different from each other. What matters is that a good BEO answers the same questions every time: who is this for, when does each thing happen, what are we making and for how many, who is working, what do we need to bring, how is the room laid out, and what is owed. The template above puts each of those into its own section so nothing gets remembered in the truck at 6am instead of written down the week before.

Fill it in the moment the job is booked

The best time to start a BEO is the day the deposit lands, while the conversation is fresh. Pull the menu and the guest count straight off the accepted quote so the counts match what the client agreed to pay for. Then add the operational layer the client never saw: the load-in time, the call times for your crew, the rentals you need to order, and how the buffet and bar sit in the room. A BEO written a week out is calm; a BEO written the night before is a scramble that skips things.

Counts drive everything else

The guaranteed count is the number the client commits to pay for, and it is the number you cook and staff to. Keep it separate from the expected count, because they drift, and always cook to the guarantee plus a small buffer rather than to the hopeful number. Every downstream list — the shopping, the prep, the number of servers, the count of chafers and place settings — scales off that one figure. Get the count right and the rest of the BEO more or less fills itself in.

The timeline is the part that saves the event

A menu can be excellent and the event can still fall apart on timing. Write the run of show as clock times, not vague phases: when the truck loads in, when setup has to be finished, when guests arrive, when service starts, when each course fires, and when teardown begins. Assign an owner to each line so “someone” is never responsible for the thing that gets missed. On the day, the timeline is what a captain holds in one hand while running the floor with the other.

Common mistakes to keep off your BEO

The mistakes that hurt most are almost always omissions. Forgetting the consumables — chafing fuel, serving utensils, foil pans, gloves, trash bags — is the classic one, because they never show up on the menu but the event stops without them. Leaving the dietary and allergy notes off the menu section is another; a nut allergy discovered at service is a genuine emergency, not an inconvenience. And a BEO with no billing summary quietly loses money: if the deposit and the balance due are not written down with dates, they are easy to under-collect.

One more: treat the BEO as a living document up until the cutoff, then freeze it. Changes are normal — a count moves, a course changes, the client adds a bar. Update the one BEO and make sure the whole crew is reading the current version, rather than letting three different printouts circulate. When you outgrow filling this in by hand, that single-source-of-truth job is exactly what BEO software is for.