BEO software and print-first kitchen sheets
Updated September 15, 2026.
Banquette is BEO software that prints a banquet event order for every party from its live record, and a kitchen prep sheet for the day with each party’s menu, the count to cook to and every guest’s dietary note.
- Every party has a printable event order: menu, the count to cook to and whether it is guaranteed, outside vendors with load-in times, notes, money and who to call.
- Your existing BEO can ride along as a photo, scan or PDF. It is stored beside the order and never read.
- The kitchen sheet carries each party’s menu, the count to cook to and every dietary note, with ruled lines for the chef’s own hand.
- Not yet: numbered or versioned BEOs, BEO approval on the host’s page, or OCR of uploads.
What does Banquette’s banquet event order carry?
A banquet event order, or BEO, is the working document for one event; if the term is new, start with what a BEO is and what goes on one. In Banquette every party has its own, built from the party’s live record rather than filled into a template.
| Section | What prints |
|---|---|
| Menu | The party’s menu, course by course |
| Counts | The count to cook to, marked guaranteed, locked or expected |
| Outside vendors | Who is coming in, and their load-in times |
| Notes | The party’s notes |
| Money | What the standing agreement states |
| Who to call | The party’s named contact, with phone and email |
Every page carries a running header and footer. Anything the book could not read prints as unknown, because a BEO that guesses is worse than none: the kitchen cooks from it.
Can we keep the BEO we already use?
Yes, beside the generated one. Staff attach a phone photo, a scan or a PDF to the party: JPEG, PNG or PDF. The server checks what each file actually contains, and turns away SVG and HTML by name. Phone photos are shrunk in the browser first. Each sheet may be up to 2 MiB, and 120 MB in all for the organization.
The upload never feeds the order. Banquette reads nothing from it (there is no OCR), so the event order and the kitchen sheet come only from the book. Take a sheet down and the file is destroyed, while a record that it existed stays. That matters: a photographed BEO can carry a card number in its margin.
What goes on the banquet kitchen prep sheet?
One day of the house’s live book, printed for the line, party by party.
| On the sheet | What it holds |
|---|---|
| Each party’s menu | Courses and dishes |
| The count to cook to | The guarantee once one is set, marked locked or not; otherwise the expected count |
| Every dietary note | Each guest’s note; guests who declined are left off |
| Ruled lines | Room for handwritten notes |
| Parties per sheet | One, two or three, or continuous |
| Masthead and footer | The house’s own |
On screen, the Production board totals dishes across rooms from today forward.
Where does the count come from?
From the office, which locks the guarantee; Banquette only works out the 48-hour deadline. A guest who declines does not lower the count, and the RSVP asks for no entrée choice, so there are no per-guest pre-orders to total.
Where do the dietary notes come from?
From the guests, each attending guest leaving one note under “Anything the kitchen should know” on their own RSVP link, no account needed. The host sees only that a note was left.
Why print-first?
Because the line cooks from paper. Banquette was built inside a working restaurant, and the sheet is made for a clipboard at the pass, ruled for a pen. It serves restaurants with private dining rooms and clubs and resorts with a banquet kitchen alike.
Who signs off the menu before it is sold?
Two different chefs. The event order prints whatever menu the party holds, but that menu becomes sellable only when two different chefs have signed it. Each signature is tied to a fingerprint of the courses, so changing a course voids them; a price change does not. The first send of a contract is refused while the party’s menu lacks both signatures or is partly unreadable, though a party with no menu yet can still be sent. See the two-chef menu signatures.
Floor plans and the setup sheet
The room gets its own paper. Tables lay out from the guest count (balanced rounds, with an optional head table and dance floor), then move by hand: drag them, turn a round into a sweetheart table, save a layout as a template and apply it to a party as a copy. Each room prints a setup sheet with a table schedule.
Plans print to scale only where the room’s dimensions are recorded; otherwise they say “not to scale.” Tables are not assigned named guests.
How do other BEO tools handle the kitchen copy?
From the vendors’ own pages, checked September 15, 2026.
- Tripleseat documents an internal BEO without pricing, and a batch export of chosen layouts, such as the Kitchen Sheet, for a date range (help articles from 2023). Its e-signature field can go on a BEO. More in Banquette and Tripleseat, compared.
- Planning Pod starts from seven pre-built BEO layouts, including kitchen and front-of-house versions, downloads print-ready PDFs one at a time or in batches, and can send any BEO for the client’s e-signature from an emailed link with no account. More in Banquette and Planning Pod, compared.
- Perfect Venue’s own blog says it generates the BEO from the event, with a full finance breakdown, and can download it without finances for the kitchen; its Enterprise-only Custom Documents include a Chef BEO template. More in Banquette and Perfect Venue, compared.
Where they are stronger: Tripleseat and Planning Pod can put the client’s e-signature on the BEO itself, and all three offer more than one version of the BEO, such as a kitchen or internal copy. Banquette’s kitchen sheet covers the whole day’s parties, with the dietary notes guests wrote themselves.
Sources: Tripleseat, internal BEO; Tripleseat, batch printing; Tripleseat, signature fields; Planning Pod, banquet event orders; Planning Pod, signatures for BEOs; Perfect Venue, BEO software; Perfect Venue, custom documents.
What Banquette’s BEO software doesn’t do (yet)
- No permanent BEO number and no version history.
- No BEO approval on the host’s private page with no login, which shows the party itself.
- No reading of uploads: no OCR of photos, scans or PDFs.
- No import of BEO documents from another system.
- No per-guest entrée choice, and no seating of named guests at tables.
- No integrations with a POS, accounting or reservation system, and no native app: it is a responsive web app.
Questions about BEOs and kitchen sheets
What is BEO software?
BEO software builds the banquet event order, the working document for one event, from the event’s own record rather than a retyped template. In Banquette every party has one: menu, counts, outside vendors, notes, money and who to call.
Can we upload the BEO we already use?
Yes. Staff attach a phone photo, a scan or a PDF to the party, up to 2 MiB a sheet. It is stored beside the generated order and never feeds it: Banquette reads nothing from the file, and there is no OCR.
Are BEOs numbered or versioned, and does the host approve one?
No. Each party has one event order, printed from its record as it stands, with no permanent number and no version history. The host’s private page shows the party itself, with no step for approving a BEO.
Does the count lock automatically 48 hours out?
No, the office locks it. Banquette computes the 48-hour guarantee deadline in the venue’s time zone. Once the office locks the guarantee, a different number is refused. The kitchen sheet cooks to the guarantee once one is set, and says whether it is locked; before that, to the expected count.
Where do the dietary notes on the kitchen sheet come from?
From the guests. Each guest who answers yes on their own RSVP link can leave one note for the kitchen. Every staff seat can read the notes and the kitchen sheet prints them; the host sees only that a note was left, never what it says.
Can we import BEOs from our old system?
No. BEO documents do not import. During onboarding we bring in your Daily Events Report export, spreadsheet or PDF, and your existing BEO sheets can be attached to each party as uploads.
A plain guide to the banquet event order and what goes on one.
A party’s menu becomes sellable only when two different chefs have signed it.
Each guest answers on their own link, with one note for the kitchen.
Flat monthly, per property: Solo is $249 a month, House is $499.