Planning Dinners When Every Kid Eats Differently

If you have more than one child, you probably know this dinner. One kid only eats beige food. One won't touch anything that's "touching." One just declared themselves vegetarian. Someone has a nut allergy, so that's non-negotiable. And you, the adult, would like to eat something with flavor at least once this week.

The default response is to cook several dinners, which is exhausting and teaches everyone that the kitchen is a restaurant. The opposite response, "you eat what's served or nothing," often turns dinner into a nightly standoff.

There's a middle path that a lot of families land on, and it starts with changing what you plan. Instead of planning a dish, you plan a dinner that everyone can build their own version of.

(Disclosure: I make FamSync, a family organizer app with a meal planner. It comes up once near the end. The method below doesn't need any app.)

First, a useful frame: who decides what

A lot of pediatric dietitians use a framework from feeding specialist Ellyn Satter called the Division of Responsibility. Very roughly: the parent decides what food is offered, when and where. The child decides whether to eat and how much of what's offered. (The Ellyn Satter Institute's "How to Feed" section goes into detail.)

Why this matters for planning: it means your job isn't to get every kid to eat every food. Your job is to put a reasonable, balanced dinner on the table that includes at least one thing each person will reliably eat. What happens on their plate after that is theirs.

That takes a lot of pressure off. And it gives you a very concrete planning rule.

The one rule: every dinner has a "safe food" for every person

A safe food is something a given person will reliably eat without a fight. Rice. Bread. Plain pasta. Cucumber slices. Yogurt. Cheese. Fruit.

When you plan a dinner, check that each person at the table has at least one safe food on it. That's it. The rest of the meal can be new, spicy, green or adventurous. A kid who knows there will always be something they like is far more willing to sit at the table and try a bite of the thing they don't.

Over time, repeated low-pressure exposure is one of the most reliable ways kids come to accept new foods, and research on it suggests it usually takes many more tries than parents expect. (One example: the Colorado LEAP study on repeated exposure in preschoolers, which reviews this literature.) So the broccoli you serve tonight next to a safe food isn't wasted, even if it comes back untouched.

The base-and-toppings method

This is the workhorse. You cook one base and a handful of components, and everyone assembles their own plate.

Some examples that work for most families:

• Taco night. Tortillas or rice, a protein, and bowls of cheese, beans, lettuce, salsa, avocado. The plain-cheese-quesadilla kid and the extra-hot-sauce adult are eating the same dinner.
• Pasta bar. Plain pasta, then butter and parmesan, a tomato sauce, a pesto, roasted vegetables on the side. Pick your own.
• Rice bowls. Rice, a protein (chicken, tofu, eggs), and toppings: cucumber, edamame, shredded carrot, soy sauce, sesame.
• Baked potato night. Potatoes, then chili, cheese, broccoli, sour cream, bacon bits.
• Breakfast for dinner. Eggs, toast, fruit, maybe pancakes. Few kids say no.
• Build-your-own pizza. Store-bought dough or flatbreads, a few toppings. Bonus: kids cook.
• Sheet pan dinner, components separated. Chicken, potatoes and vegetables on one pan, just not mixed. The "nothing touching" kid is fine.

Notice the pattern: the base is almost always a safe food for someone, the components are where adults get flavor, and nobody is cooking a separate meal.

Handling allergies and hard rules

Picky is negotiable. Allergies and medical diets are not, and they should shape the plan before anything else.

A few habits that help:

• Write the hard rules down. Allergies, intolerances, religious or ethical restrictions. Make sure every adult who cooks (including grandparents and sitters) can see them.
• Make the allergy-safe version the default when it's easy. If one kid can't have nuts, a nut-free pesto for everyone is simpler than two pestos.
• Keep the allergen out of shared components. In a base-and-toppings dinner, the risky item is its own bowl, served last, with its own spoon.
• Re-check packaged foods. Recipes change. A quick label check at the store saves a bad night.

A weekly template that cuts the decision fatigue

Most of the pain of family dinners isn't cooking. It's deciding, every single day, at 5pm, with three people asking what's for dinner. A loose weekly template removes most of that:

The theme tells you the shape of dinner without locking you into a recipe. "It's Tuesday, so it's a bowl" is a much easier starting point than a blank page.

Give each kid a vote (and a veto)

Kids are much more cooperative about dinners they had a say in. A simple system:

• Each kid gets to pick one dinner a week from a list of family-approved options.
• Each kid gets one veto a week, used before the plan is set.
• On their pick night, they help cook. Even a 5-year-old can stir, wash vegetables or put cheese on pizza.

Do this at a weekly family check-in (if you don't have one, here's a 15-minute Sunday family meeting format) and build the grocery list in the same conversation.

Keep a "what each person likes" list

This sounds overly organized, but it pays for itself within a month. Keep a simple list for each person:

• Loves: reliable safe foods
• Will eat: fine but not excited
• Won't eat: current dislikes (expect this to change)
• Can't eat: allergies and hard rules

When you plan, glance at the list. When you're stuck, it tells you exactly which base-and-toppings dinner will work this week. And when a grandparent asks "what does she eat these days?", you have an answer.

Where an app can help

Meal planning around several kids is basically a puzzle: this week's evenings, everyone's likes and dislikes, the hard rules, what's already in the fridge. That kind of puzzle is what I built FamSync's meal planner to handle. You tell it what each person likes, dislikes and can't eat, and it plans a week of dinners around all of them (no AI involved, just rules that always respect the allergies). You can also scan a recipe from a photo or paste a link, and the missing ingredients go straight to the shared grocery list. The meal planner is part of FamSync Premium; the shared, aisle-sorted grocery list is in the free version.

But a notebook and the weekly template above will get you most of the way. The real change is the mindset: one dinner, built so everyone has a way in.

The short version

• You decide what's offered. They decide whether and how much.
• Every dinner has a safe food for every person.
• Plan base-and-toppings dinners so people assemble their own plate.
• Allergies and hard rules shape the plan first.
• Use a weekly theme template to kill the 5pm decision.
• Each kid gets one pick and one veto a week.
• Keep a short likes and dislikes list per person, and update it.

Reid is a parent and makes FamSync, a family organizer app, as a solo developer. Get FamSync on the App Store.