Family meals: organising one without it turning into a negotiation

There is a precise moment when a family meal tips over. It's not at dessert, when someone brings up a topic everyone agreed to avoid. It's three weeks earlier, in a message that says: "Should we all get together for something in November?"

From there, two scenarios unfold. In the first, one person alone decides the date, the place and the menu, and everyone adapts while grumbling a little. In the second, everyone is asked their opinion, and the conversation splits into eleven directions before quietly dying two weeks later.

A family meal is not a cooking problem. It's a coordination problem, with one twist: the participants aren't interchangeable, they share a history, and certain constraints don't get said out loud.

Three obstacles that have nothing to do with food

Travel times aren't symmetrical. In an extended family, there is almost always someone driving three hours while others drive twenty minutes. Until this imbalance is named, it turns into silent irritation. Young children, elderly relatives, people who no longer drive at night: each of these cases changes what counts as a "good" time.

Shared custody schedules structure the calendar. In a blended family, one weekend out of two is simply unavailable, and often not the same one for everyone. This is a hard constraint, non-negotiable, and one that a classic poll never captures because it offers dates without asking why they don't work.

Dietary needs have become a real topic. Coeliac disease, vegetarianism, a nut allergy, diabetes: this is no longer the exception. The problem isn't the constraint itself, it's that it surfaces the night before, by text, once the shopping is already done.

A family meal rarely fails on what's eaten. It fails on what nobody dared say in time.

Ask about the format before asking about the date

Most organisers start with "who's free on the 14th?" That's too late: you're asking people to arbitrate before defining what's being arbitrated.

Before any date is proposed, three decisions need to be made, and they go quickly once you spell them out.

What kind of meal? A three-hour lunch, a dinner that runs late, a brunch, a buffet where people mingle. This choice determines who can realistically travel, whether children will be there, and how much work falls on the host. An 11am brunch brings in families with young kids who would decline a late dinner; a dinner brings in people who work Saturday mornings.

Whose home, and who cooks? These are two separate questions, and confusing them is the number one cause of host burnout. You can host without cooking everything. A potluck, where each person brings an assigned dish decided in advance, works fine — as long as the assignment actually happens, or you'll end up with six desserts and no starter.

How many people, exactly? "The family" is a fuzzy set. Partners, new partners, adult children bringing someone along, the cousin passing through: every ambiguity turns into three unexpected place settings. Fix a named list before talking about dates.

The single round: ask everything at once

The method that works comes down to one principle: one message, all the questions, one individual reply. No back-and-forth thread, no bouncing questions around, no "and what do you think?"

Here is the set of questions that covers 95% of cases in a family of twenty.

1. Of the four proposed weekends, which are possible, which are impossible, and which are possible but tricky? (Three levels, never two.)
2. Lunch or dinner, if you had the choice?
3. How many people are you bringing, first names included?
4. Are there any diets, allergies or dislikes we should know about in your group?
5. How are you getting there, and how long is the trip?
6. Do you need somewhere to stay overnight, or are you heading back the same evening?
7. What can you bring: starter, main, dessert, drinks, nothing at all (that's a valid answer)?
8. Is there a finishing time beyond which it becomes difficult for you?

Question 8 is the one nobody asks, and it prevents the most tension. Grandparents, families with early bedtimes, and people with a long drive home all have a cut-off time. Knowing it in advance lets you set the aperitif at noon rather than 1:30pm.

Question 7, with the "nothing at all" option, matters too. It gives an honourable way out to someone going through a busy stretch, and it avoids the last-minute store-bought dish that never actually shows up.

Reading the answers without getting it wrong

Once the answers are in, the temptation is to count votes and pick the date with the most "yes." That's a classic misreading.

What to look at first are the impossibilities, not the availabilities. A date where three people answered "impossible" is dead, no matter how many "yes" it collects. So start by eliminating, then choose among what's left.

Next, look at the tricky answers. They carry the useful information. If five people marked "tricky" for the same Saturday, there's a shared reason: a match, a local festival, a long weekend. A short message to one of these people is enough to find out, and often to shift the date by a week and solve five problems at once.

Finally, weigh things by travel distance. If date A works for everyone except the family coming from far away, and date B works for everyone except two neighbours, date B costs less collectively. This reasoning happens naturally once travel times are on the table, and never when they aren't.

Announce the decision as a decision

Once the date is set, one step remains that many people botch: announcing it firmly.

A message like "so I'm thinking maybe the 15th, does that work for you?" reopens the discussion you just closed. You're back to square one.

The right message contains five elements, and nothing else:

• The date and time, stated plainly, no conditional. "Sunday November 15th, 12:30pm, at Martine's."
• What drove the choice, in one sentence. "It's the only date that works for everyone, and it avoids the long weekend."
• Who's coming, number and first names. This allows for immediate corrections.
• Who's bringing what, named individually.
• An indicative end time. "We'll start winding down around 5pm." This reassures people with a drive ahead, and no one feels obliged to leave.

A reminder five days before, with the address, entry code and a phone number, is all that's needed after that. No daily reminders: it's a meal, not a house move.

What changes when the collection is automated

This whole method can be done by hand. Eight questions to twenty people means twenty replies to read, copy and cross-reference. Budget two hours, and do it all again for the next occasion.

That's exactly the work OuiCanPlan takes off your hands. You describe the meal in one sentence — "family lunch in November, twenty-two people, three special diets, families with shared custody" — and the questions suited to that context are sent to each person, in their own language, via email. You then get the possible dates ranked, dietary constraints grouped together, and who's bringing what, without ever opening a spreadsheet.

Two details matter especially for a family. First, everyone answers on their own: no one sees anyone else's replies. The organizer sees who has responded, but never the individual content; proposals do not name anyone. This makes it possible to say "that weekend is tricky for us" without having to justify it in front of everyone. Second, the results are real and ad-free: it's your answers, aggregated, and nothing else.

The special case of big occasions

An ordinary meal tolerates a bit of approximation. A wedding anniversary, a christening or a first Christmas after a loss doesn't, because the emotional stakes multiply the cost of every misstep.

Three adjustments for these occasions:

Double the notice period. Six weeks instead of three. People book time off, reserve trains, give notice to an employer.

Add a question about who's missing. "Is there someone you'd like to see invited who isn't on the list?" This question prevents the lasting hurt of being forgotten, and it costs ten seconds.

Plan a weather or venue backup, and announce it alongside plan A. "If we're more than twenty-five, we move to the village hall, it's already booked." A backup plan announced in advance doesn't dampen enthusiasm, it removes anxiety.

A successful meal is a meal decided quickly

What wears people down in a family meal is neither the cooking nor the washing-up. It's the period of uncertainty, those three weeks where everyone waits for someone else to decide, where messages pile up and the organiser ends up feeling like they're begging for answers.

Cut that period down to three days, and the event goes back to being what it should be: a lunch with people you love. Ask all the questions at once, give three days to answer, decide firmly, announce clearly. The rest is just cooking — and honestly, cooking was never the problem.