Events
How to plan a group dinner that actually happens
Table size, reservations, dietary constraints, and price signaling — the specific things that sink restaurant plans for six or more.
· 9 min read
Group dinners fail differently from group trips. A trip collapses over months, from sequencing. A dinner collapses in a week, and usually over one of four things: the table you could not book, the price nobody mentioned, the dietary constraint that arrived too late, or the fact that a table of eleven is not a conversation.
The order below is built around the one constraint people consistently discover last.
The table decides the guest list
Most people plan a dinner in this order: figure out who is coming, then find somewhere to eat. For groups above about six, that is backwards, because restaurant capacity for large parties is far more constrained than it looks from the outside.
Roughly what changes as the number grows:
- Up to about six is an ordinary reservation, bookable online, often available the same week.
- Seven to ten frequently means calling rather than booking online, a narrower set of available times, and sometimes a limited menu.
- Above tenoften means a set menu, a deposit, a minimum spend, or a private room — and a booking window measured in weeks.
So establish the approximate headcount early, and let it determine which places are even candidates. A shortlist assembled without knowing whether you are nine or fourteen is a shortlist you will have to throw away.
Work backwards from the reservation window
The deadline for your poll is not a matter of taste. It is set by when you need to call the restaurant, which is set by how far out that restaurant books. If the place you want takes reservations three weeks ahead and fills them, your date has to be settled more than three weeks ahead, and everything else compresses to fit.
Say this in the invitation rather than keeping it to yourself. “I need to call them Monday, so voting closes Sunday night” is a deadline with a visible reason, and people treat those very differently from arbitrary ones.
Lock the number before you book it
Book for the number you are confident about, not the number who expressed interest. Reserving for twelve and arriving with eight is worse than reserving for eight: it visibly costs the restaurant a table, it is increasingly likely to come with a cancellation fee, and it is the single fastest way to become someone a good restaurant will not seat again.
The mechanism that gets you a real number is the same one that works for trips — a deadline with a consequence attached. “I’m booking for whoever has said yes by Sunday” converts a soft maybe into an actual answer, because it makes clear that not answering is itself a decision.
If people are likely to drop late, book slightly under and ask whether the restaurant can add a chair. Most can add one more easily than they can absorb three empty seats.
Dietary constraints are a filter, not a vote
Collect them before you build the shortlist, not after. A vote that produces a winner one person cannot eat at is the worst available outcome: legitimate and unusable.
Ask specifically and privately. “Any allergies, or anything you don’t eat?” sent to each person gets much better information than the same question posted to a group thread, where announcing a restriction feels like imposing on everyone. Be clear that you want both the hard constraints and the strong preferences, and that they will be treated differently — an allergy rules a place out, a mild dislike just means checking there is something else on the menu.
Then check the actual menu rather than the cuisine. “There’ll be something vegetarian” is an assumption that fails often enough to be worth thirty seconds of verification.
Put the price in the invitation
Every option on the shortlist should carry a per-head estimate, including drinks if drinks are likely. “About $55 each with a glass of wine” costs you nothing to write and gives people a graceful exit while declining is still free.
Without it, the person for whom this is a stretch finds out at the table, where their options are to overspend quietly or to say so in front of everyone. They will nearly always overspend, and they will nearly always be busy next time. The reason the dinner group shrinks is rarely that people stopped liking each other.
Decide the split before anyone orders, too — announced at the start it is a fair question, announced with the check it is a bill.
A table of eleven is not a conversation
The thing nobody plans for. At a long table, you can realistically talk to the two people beside you and the one opposite. Everyone else may as well be at a different restaurant, and the seating you fell into at the start is the seating you have for three hours.
If the point of the evening is catching up with specific people, this matters more than the food. Some ways to handle it:
- Round beats long. A round table of eight sustains one conversation far better than a rectangle of eight.
- Two tables of six beat one of twelve, if the venue allows it and especially if people move between courses.
- Check the noise.A room that is pleasantly lively for four is unworkable for ten — you end up shouting at your immediate neighbor and nodding at everyone else. Reviews mention this; it is worth reading for.
- Consider not going out.A dinner at somebody’s home, potluck or otherwise, is cheaper, has no reservation constraint, no noise problem, and people can move around. For a large group it is frequently the better evening, and the only reason it gets skipped is that hosting feels like more work than it is.
The last twenty-four hours
Confirm with the restaurant and with the group on the day before. Both matter: restaurants do lose bookings, and people do forget.
Send one message with everything needed in it — name, address, time, and the split arrangement. Not a thread to scroll, one message. And tell people a time fifteen minutes earlier than the reservation, because a party of eight told to arrive at seven arrives at seven twenty, and many restaurants only hold a table for fifteen minutes.
The order that works
- Rough headcount first — it determines which venues are possible at all.
- Collect dietary constraints privately, before the shortlist exists.
- Build three or four options that fit the headcount and the constraints, each with a per-head price.
- Set the voting deadline from the reservation window, and say why it is that date.
- Book for the confirmed number, not the interested number.
- Announce the split method before anyone orders.
- Confirm the day before, and tell people fifteen minutes early.
Keep reading
- Organizing a birthday for someone who is not organizing itThe guest list problem, surprise logistics, gift coordination, and how to plan around a person without them noticing or being left out.
- How to pick a date everyone can actually makeWhy open-ended date questions stall, how many options to offer, and how to close a group scheduling decision in two days instead of two weeks.
- Why group chats are terrible at making decisionsGroup chats are built for conversation, not for closure. A look at the specific failure modes — and the small structural changes that fix them.
Running one of these decisions yourself?
planit sends the poll, chases the stragglers, and closes on a deadline. Your friends vote from their inbox — no account required.
Start a poll →