Guest Experience

Restaurant Group Dining: Running Large Parties Without Chaos

Most large parties that go wrong were already going wrong days before they sat down. The menu gets chosen at the table, the kitchen learns the counts when fourteen tickets print at once, and the host stand has no plan for twelve people arriving over forty minutes. My view is simple: restaurant group dining is an operations problem, and it can be solved with a pre-order, a kitchen sheet and a clear arrival plan.

I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success and solutions engineering. Today I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco, and I built Regular, the hospitality operating system, inside that restaurant, one service at a time. Here is how I think about large parties from the floor. You can find me on Instagram.

Why Large Parties Strain Every Station at Once

A two-top that runs late is a small problem. A party of fourteen that runs late is a problem for the host, the bar, the kitchen and the servers in the next section, all at the same moment.

Picture a typical Friday. The group was booked for 7:00. Six people arrive on time, four drift in by 7:20, and the organiser walks in at 7:35. Meanwhile the host stand is crowded, the bar is pouring a round of fourteen cocktails, and the server is taking orders one guest at a time while their other tables wait. When the order finally fires, the kitchen gets fourteen mains in one ticket in the middle of the second seating.

None of that is a staffing failure on the night. In my experience, it comes from three decisions nobody made in advance: what the group will eat, how the kitchen will know, and where the guests go when they walk in. Make those decisions before the day and the night mostly runs itself.

The rest of this article walks through each of them in the order they happen.

Build a Group Menu Guests Can Choose From in Advance

A good group menu for restaurants is shorter than the regular menu and built for volume. I'd start with a set format: a choice of three starters, three mains and one shared dessert, at a fixed price per guest. That keeps the decision easy for guests and the counts predictable for the kitchen.

Choose dishes your kitchen can plate ten at a time without the pass backing up. A main that needs individual temperatures and a long rest is a risk for fourteen. A braise, a fish that cooks in minutes or a pasta that holds well is usually safer. Include at least one vegetarian main and make sure the kitchen knows which dishes can be adjusted for common allergies, so you are not inventing substitutions at the table.

Set a threshold and write it down. Many restaurants put parties above a certain size, often ten or twelve, on the set menu by default. Whatever number you pick, apply it consistently so the reservation team is not negotiating it case by case. Put the price, what is included and what is extra, such as drinks and service charge, in writing before the date is confirmed.

How to Collect Pre-Orders, Allergies and Headcounts Before the Day

A large party pre-order only works if it has deadlines. I'd suggest two: menu choices and allergies due 72 hours before, final headcount confirmed 48 hours before. That gives the kitchen time to order and the floor time to set the room.

The usual way this breaks is the forwarded spreadsheet. The organiser emails it around, half the guests reply to the organiser, and someone retypes it the afternoon of the event. Allergies get lost in that chain more often than anything else.

A better approach is to let each guest choose for themselves through one link, with allergies captured next to their name. This is the job Group Events in Regular does: a secure portal where large parties pre-select from the group menu, with kitchen sheets, estimates and daily digests for the manager. Whatever tool you use, the principle holds. The guest enters their own choice once, and the restaurant reads it without retyping.

Allergy handling is where you should check your local rules and your own written procedures. A pre-order captures the information; it does not replace confirming it with the guest on the night.

The Kitchen Sheet and the Pre-Shift Huddle for Groups

The kitchen should know the group's counts before service, not at fire time. A useful kitchen sheet fits on one page and shows the counts per dish for each course, the seat number for each choice, any allergy flagged by seat, and the planned time each course fires.

Seat numbers matter more than people expect. Knowing there are five fish and nine pasta helps the line. Knowing the fish goes to seats 2, 5, 8, 11 and 13 helps the runners, and keeps a server from auctioning plates around the table.

Then hold a five-minute huddle before doors. Cover who owns the table, who runs food for it, when the first course fires relative to the last arrival, whether the bar is preparing a welcome drink, and which seats carry allergies. I learned the value of this kind of handover in software, where onboarding a large account went well only when sales, implementation and support had agreed who owned what before the kickoff call. A restaurant group is the same shape.

Plan the group's pacing against the rest of the book too. I wrote more about that in pacing service without rushing guests.

Greeting a Large Party at the Door Without Stalling the Host Stand

The arrival is where a group can block the room for everyone else. Technology should put the headcount, the organiser's name, the allergies and the table on the host's screen before service. It should not put a tablet between the host and the guest, with names being checked off one by one at the door while the next couple waits.

Here is the routine I'd use at your next service:

  1. Before doors, set the table for the final headcount plus one spare setting.
  2. Learn the organiser's name and greet them by name when they arrive.
  3. Choose a staging spot away from the host stand, such as a corner of the bar, for early arrivals.
  4. Offer early arrivals the welcome drink or water there so the wait feels intentional.
  5. Send a second staff member to walk the group to the table, so the host stays at the stand.
  6. Have the server confirm allergies by seat number, quietly, rather than asking the whole table.
  7. Tell the organiser when the first course will land and who to find if anything comes up.

Step two does more than it looks. The organiser often carries the stress of the evening, and being recognised at the door tells them the restaurant has it handled.

Following Up With the Organiser So They Book Again

The organiser is the guest who decides whether the group comes back, and often whether next year's team dinner or birthday comes to you. Treat them as the account, not as one diner among fourteen.

Send a thank-you the next day, from a person, to the organiser alone. Name one thing that went well, ask one honest question about what could have been better, and offer to hold a date for the next occasion. Keep it short. I covered the wider approach in email that starts with a thank-you.

Then record what you learned in the guest record: the date, the headcount, the menu they chose, the allergies, any friction at arrival. When the organiser calls about private dining planning next season, the person answering can pick up where you left off instead of starting from zero.

If you want to see how pre-selection, kitchen sheets and follow-up fit together with the rest of your reservations and service, you can look at every app in Regular or book a Regular demo. Either way, start with the deadlines. They do most of the work.

Frequently Asked Questions

How far in advance should a restaurant collect pre-orders for a large party?

A practical approach is two deadlines: menu choices and allergies about 72 hours before the event, and a final headcount about 48 hours before. That gives the kitchen time to order and prep, and the floor team time to set the room. Put both deadlines in writing when the booking is confirmed so the organiser can share them with guests early.

What should a group menu for restaurants include?

Keep it shorter than the regular menu: for example, three starters, three mains and one shared dessert at a fixed price per guest. Choose dishes the kitchen can plate in volume, include at least one vegetarian main, and know in advance which dishes can be adjusted for common allergies. State clearly what is included and what costs extra, such as drinks.

How do you seat a large party without blocking the host stand?

Set the table for the final count before doors, and keep a staging spot away from the host stand, such as a corner of the bar, for early arrivals. Greet the organiser by name, and have a second staff member walk the group to the table so the host can keep welcoming other guests.

What size counts as a large party at a restaurant?

It varies by room and kitchen, but many restaurants treat parties of about ten or twelve and above as large parties with a set menu and pre-order. The right threshold is the size at which your kitchen and one server section start to strain. Pick a number, write it down and apply it consistently when taking reservations.

Regular

Run the Night Your Regulars Remember

One suite of apps that connects your reservations, POS and schedule, from before the meal to the next visit.