The difference between a relaxed host and a frazzled one is rarely cooking skill. It's that the relaxed host made every decision before the day: how many people, how much food, who can't eat what, and what happens in which order. Here's a timeline-based approach that turns a dinner party, birthday, or holiday gathering from a memory test into a checklist.
Two weeks out: guest list and RSVPs that ask the right question
Everything in menu planning derives from two numbers — how many guests, and how many of them have dietary restrictions. So your invitation should collect both. Alongside "can you come?", ask explicitly: "Any allergies or foods you don't eat?"
Most guests with restrictions won't volunteer them unprompted — they don't want to be a burden — and then politely eat almost nothing at your party. Asking in the RSVP does three things: it normalizes answering, it gives you time to design around the answers, and it signals that everyone will be able to eat, which is itself great hosting.
Tip: Mazir's event builder generates an RSVP link for each event. Guests confirm attendance and enter their dietary restrictions in the same tap — and those restrictions feed straight into the allergen cross-check on your menu.
One week out: structure the menu by course, not by dish
Don't brainstorm dishes — fill a structure. A reliable skeleton for a dinner-style event:
- Arrival bites (1–2 items): things that survive sitting out — olives, dips, crudités. Buys you kitchen time.
- Starter or salad (1): fully preparable in advance.
- Main (1, plus 1 alternative if you have vegetarians or a major allergen at the table): choose something that holds — braises, roasts, and bakes beat à-la-minute pan-frying for groups.
- Sides (2–3): at least one starch, at least one vegetable, at least one served cold or room-temperature.
- Dessert (1): make-ahead only. Nobody wants to whisk zabaglione while their guests sit without them.
Now audit the structure against your RSVP data: every guest should be able to eat the arrival bites, at least one starter, a main, and dessert without asking for modifications. Design the default to be safe rather than preparing special plates — a special plate is one kitchen mix-up away from failure, and it makes the guest feel singled out.
One week out: calculate quantities per guest
Scale by person, then round up once at the end — not per dish, or you'll cook for an army. Reasonable per-adult baselines for a dinner event:
| Component | Per adult |
|---|---|
| Main protein | 150–200 g (250 g if it's the star, e.g. a roast) |
| Starch side | 120–150 g cooked |
| Vegetables / salad | 150–200 g |
| Arrival bites | 4–6 pieces |
| Dessert | 1 portion + 10% extra total |
Count children as half portions, hearty eaters as 1.5, and add one whole spare portion per eight guests. For a buffet, increase variety, not volume — more different dishes, same total grams per person.
Three days out: assign every dish to a person and a time
Write next to each dish: who makes it, when, and where (your oven is a scarce resource — two dishes that both need it at 200°C at 6 p.m. is a plan that fails at 6 p.m.). If guests offered to bring something, assign them a specific slot in the structure ("a cold vegetable side for 10") rather than accepting mystery contributions — and note their dish's allergens as "unknown" unless they tell you.
Then build one consolidated shopping list from the final menu, scaled to your final headcount, and shop once. The day before, cook everything that holds: braises taste better on day two anyway.
Day of: run the plan, don't rewrite it
- Post the menu where helpers can see it, with allergen labels per dish for the buffet table.
- Give every dish its own serving utensil — it keeps allergen-safe dishes actually safe.
- Resist last-minute substitutions on dishes that guests with allergies will eat; if you must substitute, re-check the label.
- Accept that one thing will go slightly wrong, and that with everything else decided, you'll have the spare attention to handle it — that's the whole point of the system.
Frequently asked questions
How do I ask guests about allergies without making it awkward?
Put it in the invitation as a routine question for everyone, not a targeted one: "Let me know about any allergies or foods you avoid so I can plan the menu." When everyone is asked, nobody feels like a special case. An RSVP form with a dedicated field works even better than free text.
How many dishes do I actually need for a party?
Fewer than you think. For a sit-down dinner: 1–2 bites, a starter, one main (plus one alternative), 2–3 sides, one dessert. For a buffet of 15+: roughly one dish per 3–4 guests, balanced across the same categories.
What's the biggest mistake first-time hosts make?
Choosing dishes that all demand attention in the final hour. Judge every candidate dish by one question: "can this be 90% done before the doorbell rings?" If not, it needs a very good reason to stay on the menu.
Build your next event menu in Mazir
Multi-course menu builder, guest RSVP links that collect dietary restrictions, automatic allergen cross-checks, cooking assignments, and a shopping list scaled to your headcount.
Try Mazir