Private dining and banquet event software: one house, one book

Updated September 15, 2026.

Banquette is private-dining and banquet event software for restaurants, private clubs, resorts and wedding venues: inquiries, event contracts with e-signature, BEOs (banquet event orders), two-chef menu approval and print-first kitchen sheets.

One record carries each party from the first inquiry to the signed contract, the BEO and the printed kitchen sheet. It was built inside an award-winning restaurant with twenty-six years of private dining.

What does Banquette run?

The parts of the house, with one record underneath.

What does the calendar hold?

The calendar carries a lane for every venue on the book. Rooms inside a venue share that lane, but the database refuses a second party in a room that is already booked, and a buyout collides with everything. Each party’s guarantee deadline, 48 hours before the start in the venue’s time zone, is computed; the office locks the count. Staff can subscribe their phone calendars to the book, one way.

How do inquiries and events stay on one book?

One property holds its restaurants, halls and rooms on a single book, with every inquiry and party on it. A house moving off another system brings its history: a Daily Events Report export (spreadsheet or PDF), brought in by us during onboarding.

The House plan adds the notes reader (in preview): paste the call, get the draft. It is a rules-based parser, not AI, that runs for now against a sample repertoire in the browser, and it does not yet write to the live book.

How are event contracts drafted and signed, and deposits recorded?

Contracts draft from the party’s own record, and the terms are fixed by a SHA-256 hash. The host signs on a private page, with no login, by typing their full name; each signature adds a row to an append-only record the database will not let anyone edit or delete, with the typed name, email, time, IP address and browser. The general manager or the events manager countersigns, and the event is contracted. It is a built-in e-signature, not a DocuSign integration.

Money is kept, not taken: the office records deposits and balances, contracts carry installment schedules, each installment reads paid, part, due or overdue, and one queue shows the money due across the book. Banquette processes no payments. More on the host’s private page and the signing.

How does the kitchen approve a menu?

The law of two signatures: a party’s menu becomes sellable only when two different chefs have signed it. Each signature is tied to a fingerprint of the courses, so changing any course voids the ink and the chefs sign again; a price change does not. Only a chef may sign; the general manager may set a menu but not sign it. The first send of a contract is refused while the party’s menu is short of its two signatures, though a contract for a party with no menu yet can still be sent. More in the two-chef menu signatures.

Menu Studio keeps the house’s menus. Taking one onto a party copies it, and the copy needs its own two signatures.

What goes on the BEO and the kitchen sheet?

Every party has a printable BEO, the banquet event order, built from its live record: the menu, the count to cook to, outside vendors with their load-in times, notes, the money from the standing agreement and who to call. Anything the record cannot read prints as unknown, never as a guess. A photo, scan or PDF of an old BEO can sit beside it; Banquette keeps the file and reads nothing from it. New to the term? Read what a BEO is and what goes on one.

Kitchen paper is print-first, because the pen wins on the line. The sheet for a date comes from the house’s own book: each party’s menu, the count to cook to (the locked guarantee, otherwise the expected count) and every guest’s dietary note, with ruled lines left for the pen, in the house’s masthead. The guest menu prints as one letter page with the house’s name at the top and no prices. More in BEOs and print-first kitchen sheets.

What do the host and the guests see?

The host gets a private page, a link the house issues, with no account and no password, in four tabs: the evening, the order, the guests and the invoice, a live ledger of what is paid and due. See the client portal with no login.

Each guest answers on a link of their own: coming or not, how many seats, and one note for the kitchen. The host sees that a guest told the kitchen something, never what. See guest RSVP without an account. The private pages carry the house’s name, and invitations come from a banquette.events address under the house’s name.

Who is Banquette for?

What doesn’t Banquette do yet?

• No card processing or online payments, no receipts and no numbered invoices.
• No numbered or versioned BEOs, and hosts do not approve a BEO.
• No integrations with a POS, accounting software, a CRM, OpenTable, Resy or SevenRooms, or Gmail and Outlook, and no public API. The calendar feed is one way.
• No native app and no offline use: it is a web app that works in a phone’s browser.
• No per-guest meal choice, and no seating named guests at tables.
• No reading of uploaded files, and no self-serve sign-up.

How does Banquette compare with other event software?

Side by side, from public sources listed on each page, including where each one is stronger: Banquette and Tripleseat, Banquette and Perfect Venue, Banquette and SevenRooms and Banquette and Planning Pod. See also Tripleseat alternatives and every comparison. The prices are on the pricing page.

Questions about Banquette