Events & banquets
Banquet Seating with Meal Selections
How to plan banquet seating with pre-selected meals: collecting choices, floor plans, seat assignments, chef counts, server maps, allergies and late changes.
By Tim Lenahan, Founder, Bubs · Updated
Banquet seating with meal selections means planning a plated function so that every guest has an assigned seat and a pre-chosen entrée, and the kitchen and servers know which plate goes to which seat. It is how a club serves a 160-guest member-guest dinner or a wedding with three entrée choices without servers walking the room asking "who had the salmon?" It is also one of the most error-prone jobs in banquets, because the information lives in three places — the floor plan, the RSVP list and the kitchen's count — that are usually maintained separately.
This guide covers why per-seat meal service matters, how to collect meal choices, how to build the floor plan and seat assignments, how to turn them into kitchen counts and server maps, how to handle allergies and late changes, and how to keep the whole thing in one place. For a printable layout, use the banquet seating chart template.
Why per-seat meal service matters
Without seat-level meal data, a plated dinner with a choice of entrée runs one of two ways:
- Auctioning plates. Servers carry out a mix and ask each guest what they ordered. Slow, awkward, and it guarantees the last guests at each table get whatever is left.
- Place-card codes only. Guests carry a symbol or color on their place card; servers read it. Better, but it depends on the card being right and on the kitchen's count matching the cards.
With seat-level data, the kitchen knows how many of each plate to fire per table, and servers know which seat gets which plate before they leave the kitchen. The room is served in one pass, allergies are handled at the seat, and the chef's count matches the room.
Collecting meal choices
Methods
| Method | Works well for | Watch out for |
|---|---|---|
| RSVP card with entrée boxes | Weddings, formal outside events | Illegible cards, missing choices, manual keying |
| Online RSVP form | Weddings and large member events | Guests who never submit |
| Member event sign-up in the club app | Member dinners, member-guests, holiday events | Members registering guests without their choices |
| Host collects and submits a list | Corporate events | Late lists, names that don't match the seating |
Practices
- Collect the choice with the name. "Two chicken, one salmon" for a party of three is useless for seating. Each guest's choice must be attached to that guest.
- Collect dietary restrictions at the same time, in a separate field from the entrée choice.
- Set a deadline that aligns with the guaranteed count deadline in the contract.
- Have a default. Decide in advance what a guest who never chose receives — usually the first entrée, or the chef's choice.
- Limit choices. Three entrées plus a vegetarian option is manageable; six is a kitchen problem.
Building the floor plan
The floor plan is the map everything else hangs on.
- Start from a room template. Most clubs have a handful of standard layouts per room — rounds of 8 or 10, a head table, a dance floor, a stage. Start from the closest one.
- Adjust for the event. Add or remove tables to match the guaranteed count, position the head table, buffets, bars and band.
- Number tables and seats consistently. Seat 1 at each table should be in the same position relative to a fixed point in the room (for example, the seat facing the stage), and seats numbered clockwise. This is what lets a server find "table 12, seat 4" without thinking.
- Check sightlines and service paths. Servers need aisles to reach every seat; guests at the back should see the head table.
- Leave room for late additions — an empty seat or two per section, or a spare table that can be set quickly.
Assigning seats
The host usually decides who sits where; the club's job is to make the assignments usable.
- Get the seating as a list of guest name, table and seat, not a picture of a hand-drawn chart.
- Match every seated guest to their meal choice. Guests with a seat and no choice get the default; choices with no seat are a missing guest or a spelling mismatch — resolve them before the kitchen count is final.
- Seat the head table explicitly. It is usually served first.
- Flag special seats: children's meals, vendor meals, high chairs, accessibility needs.
From seating to kitchen counts and server maps
Once every seat has a guest and a meal, three documents follow. They should be generated from the same data, not built separately.
The chef's production sheet
Totals of each dish per course across the room, plus special plates listed by table and seat. For example: 96 filet, 52 salmon, 12 vegetable risotto, and table 7 seat 3 gluten-free, table 14 seat 8 nut allergy.
The fire plan
For large rooms, the kitchen fires in waves by section, and each wave's plates are counted by table. The head table and the tables nearest the kitchen typically go first.
The server map
Each server's section, with a seat-by-seat list of plates and flags. A server carrying a tray to table 9 knows: seats 1, 2, 5, 6 filet; seats 3, 7 salmon; seat 4 risotto; seat 8 filet, no sauce.
Place cards and entrée indicators
Place cards remain useful even with a server map. A discreet mark on the card — a small icon or letter for each entrée — lets servers confirm the plate at the seat. Keep the key simple, print it on the server map, and generate the cards from the same seating list so they can't disagree with the kitchen.
Allergies and dietary restrictions
Allergies are the part of per-seat service where errors have real consequences.
- Record the restriction on the seat, not only on the guest list, so it follows the guest if they move.
- Put it on every document — the chef's sheet, the fire plan, the server map and, where appropriate, the ticket that reaches the line.
- Handle allergy plates separately. Plate them in a distinct area, carry them separately, and have the captain confirm at the table.
- Confirm at service. The captain checks each flagged seat as the course is delivered.
- Treat dietary information as sensitive. Share it with the people serving the guest, not on a list posted on the wall.
Managing changes
Changes after the seating is set are routine: a guest cancels, a plus-one appears, two tables swap. Each one ripples through the plan.
- After the guarantee deadline, route every change through the banquet captain or catering manager.
- Update the seat, not a side list. A change made on the seating plan updates the counts, the server map and the place cards together. A change made on a sticky note updates nothing.
- Re-issue the chef's count when changes affect it and have the chef confirm the new numbers.
- Day-of changes go to the captain, who adjusts the server map and tells the kitchen.
When per-seat service doesn't apply
Not every function needs a seat-by-seat plan. Match the planning to the service style:
| Service style | Seating | Meal data needed |
|---|---|---|
| Plated with pre-selected entrées | Assigned seats | Meal per seat, allergies per seat |
| Plated, single menu | Assigned tables, open seats | Counts per table, allergies per guest |
| Choice at the table (server takes orders) | Open or assigned | Counts per table after ordering; no pre-selection |
| Buffet or stations | Open seating | Total counts, allergy labels on the line |
| Family style | Assigned tables | Platters per table, allergy plates per guest |
| Cocktail reception | None | Total counts per passed item and station |
Choice at the table — servers take each guest's entrée order after they sit — avoids collecting choices in advance but puts pressure on the kitchen, which cannot prep to known counts. It works best with smaller rooms and a menu the kitchen can fire to order. For buffets and stations, the dietary work moves from the seat to the labels on the line and a chef or captain available to answer questions.
Member events versus outside events
Member-hosted events at a club add a few wrinkles:
- Members register themselves and their guests, often through the club app, choosing each person's meal as they register.
- Seating may be open or assigned. Some member dinners assign tables by group; others let members choose.
- Charging — meals go on the member's account, including their guests' meals.
- Waitlists for popular events need their own meal choices ready when a spot opens.
For outside events, the host provides the seating and choices, and the billing follows the contract. See the BEO guide.
How Bubs handles banquet seating and meal selections
In Bubs, the floor plan, the seat assignments and the meal choices are one plan attached to the event. See events and banquets.
- The floor plan editor places tables as shapes in the booked room, with seat counts, rotation and room features, and managers can save layouts to reuse.
- Each seat holds a guest and a meal — a menu item with its modifiers — validated against the event's menu, with a note for dietary needs that travels with the plate to the kitchen.
- Members register for club events in the member app, choosing a meal for themselves and their guests.
- The kitchen receives each course as a fire round in which every plate carries its "Table 4, seat 2" label, and the chef sheet totals the plan per course, station and meal against the live tickets.
- The BEO — full and in server, kitchen and captain views — reads the same plan, so a change to a seat changes every document at once.
See also the kitchen display and the glossary entry for banquet event order.