Every confirmed event becomes a clear banquet event order drawn from the same details the guest approved — no re-keying between the proposal and the kitchen sheet. One BEO renders for three audiences: the kitchen sees courses, counts, and allergens; the floor sees timing and setup; the guest sees their event, not your operations. It prints cleanly, works on a phone during service, and reads in English or Spanish.
The BEO is built from the event's approved details — menus, counts, spaces, timing. What sales sold and what service runs are finally the same document.
Kitchen, floor, and guest versions are one BEO with audience-scoped sections — a toggle, not three layouts to keep in sync by hand.
Allergen and dietary notes ride the relevant courses on the kitchen render, not a footnote on page four.
BEOs print cleanly for the pass and read comfortably on a phone walking the floor. Today's event pages keep working when the walk-in has no signal.
The same BEO renders in either language, written properly. The whole brigade works from the same sheet.
A banquet event order — the operational document a kitchen and floor team run an event from: menu and courses, counts, timing, room setup, and special notes. In Excellent it is generated from the confirmed event's approved details, not written from scratch.
Yes — by design. One BEO renders per audience: the kitchen version carries courses, counts, and allergens; the floor version carries service details; the guest version shows their event beautifully without your internal operations.
The BEO renders from the event's current approved details, so an updated count or course is reflected the next time it is opened or printed — no separate document to chase.
Free to build — no card, no countdown. $360 per location per month when you go live, with every feature on this page included.