Large Parties Without the Panic: Set Menus, Deposits, and Final Numbers
A table of eighteen is not nine tables of two. It needs a different booking process, a different menu decision, and a deposit conversation you can defend when the numbers drop.
Guestavo
9 min read
A group of eighteen is booked for Friday at seven. Fourteen arrive. Nobody told you, and you have four covers of prepped food sitting in the walk-in, plus a section of the room you turned away walk-ins for.
That is the failure mode that makes owners nervous about groups, and it is almost always a process problem rather than a guest problem. The people who booked did not set out to cost you money. They just had four friends drop out on a Thursday and no obvious moment where telling you was part of the plan.
A table for two needs a name, a time, a phone number, and nothing else. A group of eighteen needs a menu decision, a deposit, a confirmed headcount, a seating plan, and a named person who is responsible for all four. Running the second through the process you built for the first is where the trouble starts.
Where the line sits
Most kitchens have a number where a booking stops being a table and starts being an event. It is worth deciding what yours is instead of discovering it mid-service.
For a lot of restaurants the line sits somewhere between eight and twelve. Below it, the kitchen can absorb a group ordering a la carte alongside everything else. Above it, eighteen separate mains landing at once will wreck the pass and slow every other table in the room.
Your line depends on your kitchen, not on convention. A pizzeria with a big oven handles twenty far more easily than a place doing four-component plates with two chefs. Watch a couple of large tables go through service, note where the wheels start to come off, and set your threshold just below that.
Once you have the number, everything above it goes down a different path. Same warmth, different questions.
Set menu or a la carte
This is the decision that determines whether the night is calm or frantic, and it is worth being honest about who benefits.
A set menu helps the kitchen enormously. Prep is known, portions are counted, and the food goes out together instead of in a slow trickle while the first four people watch their friends eat. It also makes the bill predictable, which matters more than people expect, because splitting a la carte over eighteen guests at the end of a long evening is where service goes to die.
A la carte helps the guest. People want what they want, and a group of colleagues with a vegetarian, someone avoiding gluten, and a person who came specifically for the ribeye will resent a fixed choice.
The workable middle for most venues is a limited menu: two or three options at each course, chosen in advance, priced as a package. The kitchen gets predictability, the guest gets a real choice, and dietary requirements get handled properly rather than improvised at the table.
A rough guide that holds up in practice:
- Up to your threshold: full a la carte, treat it like any other table.
- Above the threshold on a quiet night: limited menu, pre-ordered by course.
- Above the threshold on your busiest service: set menu, no exceptions, and say so at the point of enquiry.
- Private hire of a room or the whole venue: set menu plus a minimum spend.
The worst version of this conversation happens two days before, when the group has already imagined ordering freely. Say it in your first response to the enquiry: groups of twelve or more choose from our group menu, here it is. Nobody argues with a rule they heard at the start.
Deposits that are fair in both directions
A deposit is the thing that makes the booking real, and the same logic that protects you also protects the guest from a venue that quietly gives their room away.
Charge per head rather than a flat fee. A flat 100 EUR means very little to a party of thirty and feels heavy to a party of ten. Somewhere in the range of 10 to 25 EUR per person is common for a restaurant group booking, and for a set menu at a higher price point, some venues take the full menu cost up front. Whatever you pick, the deposit should always come off the final bill. A deposit that vanishes into your pocket regardless of attendance reads as a fee, and guests remember it.
Then be specific about the deadline. Vague terms ("cancellations may incur a charge") are the ones that turn into arguments, because neither side knows what was agreed. Concrete terms are easier to enforce and easier to accept:
- Deposit refunded in full if cancelled more than seven days before.
- Half refunded between seven days and forty-eight hours.
- Not refunded inside forty-eight hours, because the food is bought and the tables are held.
- Headcount reductions after the cut-off treated the same way as a partial cancellation.
Fair also means you keep your side. If you have to cancel for a kitchen flood or a staffing disaster, refund everything without being asked, and help them find somewhere else if you can. Groups talk. A venue that handled a cancellation gracefully gets recommended anyway.
If you want to see what large-party no-shows actually cost you across a year, our no-show calculator puts a number on the empty covers, which makes the deposit conversation much easier to have with yourself.
The final numbers conversation
This is the step most venues handle worst, and it is the cheapest one to fix.
Pick a cut-off, typically forty-eight or seventy-two hours before the booking depending on your ordering cycle, and make it the moment the headcount is locked. After that point, the number you have is the number you charge for. If two people drop out on the day, you still cook and bill for the confirmed count, because the ingredients are already in the building.
The part that makes this work is the reminder rather than the policy behind it. Do not wait for the organiser to remember. Message them a few days out with the number you currently hold and ask them to confirm or adjust it. Most people will answer within the hour, and the ones who were going to drop from eighteen to fourteen tell you now instead of at the door.
Downward moves are the ones worth planning for. Groups shrink far more often than they grow. Building a small buffer into the seating plan means a party of twenty that becomes eighteen still looks intentional rather than gappy.
And put it in writing. Not a contract, just a clear confirmation email: date, time, headcount, menu, deposit paid, balance due, cut-off date, and what happens if numbers change. One message that both sides can point to later.
Seating logistics
A long table of eighteen is not the same room as three tables of six, and the difference matters to the group more than it does to you.
One long table means everyone feels like they are at the same event, but people only ever talk to the four humans nearest them. Round tables of eight or ten produce better conversation and worse cohesion. If the group is a birthday or a family celebration, ask them which they want. If it is a company dinner where the host wants to make a speech, they need sightlines, so one long table or a horseshoe wins.
Practical things that go wrong with large parties and are easy to prevent:
- Access: eighteen people arriving at once will clog your entrance. Decide where they wait and who greets them.
- Noise: a large group is loud, and the four-top next to them will not enjoy it. Put them somewhere the volume works, or accept that you are trading one table's experience for another's.
- Service ratio: one server cannot run eighteen covers at the pace they run twelve. Staff it properly or the food arrives cold.
- Payment: agree the method in advance. One card, or split evenly, or a pre-paid package. Deciding at eleven at night with a queue at the till is a bad plan.
Why the process has to be different
Everything above comes down to a single idea: a group booking is a small contract, and a table for two is a promise.
A table for two can be handled by a form, a confirmation, and a reminder. If it falls through you lose two covers and refill them from the walk-in queue. A group of eighteen involves prepped food, held tables, extra staff on the rota, and a room you may have shaped around them. Losing it late is not a small hole, and you cannot fill it with the couple who wandered in at eight.
So the process needs more structure. A named contact rather than "the office". A written confirmation rather than a note in the diary. A deposit rather than trust. A cut-off rather than hope. None of it is unfriendly if you present it warmly and early, and groups who book events regularly expect it, because every venue that handles them well works this way.
Guestavo lets you hold a group booking against a specific resource (a private room, a long table, a section) and send the organiser a reminder before your cut-off, over the channel they actually read. When they reply, it lands in the shared inbox where whoever is working can pick it up.
The short version
Set a headcount threshold and treat everything above it differently. Decide the menu format at the point of enquiry, not the week of. Take a per-head deposit that comes off the bill, with refund dates written in days rather than adjectives. Chase the final number instead of waiting for it. Plan the seating, the noise, the service ratio, and the payment method before the group arrives.
Do that and a party of eighteen becomes one of the best bookings in your week. Big spend, single sitting, and a room full of people who will remember where they had the night.
Keep reading
- Bookings
How to Cut Restaurant No-Shows Without Charging a Deposit
No-shows cost the average restaurant thousands a year. Most of them are forgetfulness, not malice, and reminders fix the majority.
- Bookings
No-Shows in Salons and Clinics: Why a Restaurant Playbook Won't Work
When a client skips a 90-minute appointment with a named practitioner, you lose the slot, the practitioner's hour, and the chance to refill it. Here is what actually reduces that.
- Bookings
Planning for Seasonal Peaks and the January Dead Zone
December pays for January, Valentine's fills one night, and most restaurants staff both by feel. A forecast built from last year's numbers beats a hunch every time.