How to plan a dinner party: a timeline that works
- The short answer
How do I plan a dinner party without it taking over my week?
Send the invitation about three weeks ahead, lock the number four days before, and choose a menu with one dish that can be finished in advance. Almost all dinner-party stress comes from an unknown headcount and from cooking something new in front of an audience, fix those two and the rest is shopping.
A dinner party goes wrong in predictable places, and none of them are the cooking. They are the count, the timing, and the last forty minutes before people arrive.
The timeline
Three weeks out: send the invitation
Far enough ahead that people are free, close enough that they can see the date on their calendar. Include the date, the start time, roughly where, and whether it is a full meal, that last one prevents someone eating beforehand or arriving starving. Ask for a reply by a specific day rather than "let me know".
Two weeks out: decide the menu around one make-ahead dish
Pick a main that improves on standing, a braise, a stew, anything baked, so the oven is not the bottleneck while guests are in the room. Cook nothing for the first time on the night. If you want to try a new recipe, make it once in the week before, which also tells you the real timings.
One week out: collect the dietary constraints
Ask once, in writing, of everyone rather than of the person you assume has a restriction. One question attached to the invitation, "anything you do not eat?", gets you allergies, vegetarians and the person who quietly hates coriander, all before you shop.
Four days out: lock the number
Chase anyone who has not replied, and treat a maybe as a no for shopping purposes. Cooking for eight when six arrive is a mild waste; cooking for six when eight arrive is a genuine problem. This is the single highest-leverage moment in the whole plan.
The day before: shop, and do every job that can be done cold
Chop, marinate, make the dressing, lay the table, chill the drinks. Anything done today is a minute you are not spending in the kitchen while people stand around holding coats.
Two hours before: send the address and finish the slow dish
A short message with the exact address and any door or parking detail lands when people are about to travel, not a fortnight earlier when they will lose it. Get the main to the point where it only needs heat.
Thirty minutes before: stop cooking
Everything that remains should be reheating or assembly. Pour yourself a drink and change. Guests take their reading of the evening from the host, and a host still frying at the door sets a tone that takes an hour to recover from.
How many people
Six is the number most home tables handle well: one conversation, everyone audible, one oven. Eight works if the table is genuinely big enough that people are not managing their elbows. Above ten the room splits into two conversations, which is fine, but plan for it and stop trying to hold a single table together.
Count your chairs before you count your guests. The table is the real capacity, not the invitation list.
On splitting the cost
If you are hosting, hosting includes paying, and asking for money afterwards changes what the evening was. The exception is a night that was framed as shared from the start: a group buying an expensive cut together, or a supper club where everyone contributes. In that case say the number in the invitation, before anyone commits, rather than producing it at the end.
- Decide the money question before you send the invitation, never after.
- If you ask for a contribution, name the amount up front: a vague "we will split it" is what people resent.
- "Bring a bottle" is a contribution people are happy with, and it removes your drinks problem.
The forty minutes that decide the evening
Arrivals are staggered, the first guest is early, the last is thirty minutes late, and this is when hosts do their worst cooking. Have something on the table that requires nothing from you, olives, bread, anything that lets an early guest occupy themselves, and accept that the meal starts when the food is ready rather than when everyone is present.
Waiting for a late guest punishes the six who arrived on time. Start.
Common questions
How far in advance should I invite people to a dinner party?
About three weeks for a weekend dinner with six to eight people. Less than a week and you are competing with plans already made; more than a month and the date sits too far out to feel real, and people forget to put it in a calendar. For a large or seated occasion, six weeks is safer.
How do I ask about dietary requirements without making it awkward?
Ask everyone the same short question at the moment they are invited, "anything you do not eat?", rather than singling anyone out later. Asking as part of the RSVP makes it routine, gets you an answer in writing, and means you have it before you shop rather than the night before.
What do I do when people do not reply to a dinner invitation?
Set a reply-by date in the invitation, then chase individually about four days before. A direct one-to-one message gets an answer where another message in a group thread does not. Treat anyone still undecided at that point as a no for shopping, and tell them they are welcome if they turn out to be free.
Should I tell guests the exact address in the invitation?
Say the neighbourhood in the invitation so people can judge the journey, and send the exact address a couple of hours before. Invitations get screenshotted and forwarded far beyond the guest list, and the precise address is only genuinely useful on the day.
How much food should I make per person?
For a main course, plan on roughly 200g of protein and 150g of vegetables or starch per person, then add one extra portion for every six guests rather than scaling everything up. People eat less at a long seated dinner with several courses than they do at a single-dish supper.