Family weekly plan — how you really plan for four mouths

When you have a family with kids and cook without a plan, daily life looks like this: 5:30 PM, you're standing in front of the fridge, one child is whining, another doesn't want what you had in mind, your partner isn't home yet, and you're wondering whether it's going to be spaghetti again tonight. The answer is usually: yes.

That's not a failure — it's the raw result of «pushing every decision to the moment». With three young children and two working parents, you make about 6 micro-decisions per meal: what, with which sides, who won't eat what, what's still in the fridge, what still needs buying, how long it all takes. 6 times a day, 42 times a week.

A weekly plan cuts that down to 7 times — you plan once a week, and after that the decisions are gone. That's not «living more strictly», that's «taking the load off your head». The variable you gain is energy after work — cooking without searching, without arguing, without comfort-buys at the supermarket at 6:15 PM.

The hard question isn't «should I plan», but «how do I plan without it feeling like office work». Three family weekly-plan mistakes you should avoid:

Mistake 1: Too many new recipes per week. If you pull 5 new recipes from the cookbook every week, you're exhausted after three weeks. Rule of thumb for weekly plans that last: 2–3 familiar family favourites + 1–2 new recipes per week. The familiar ones are the pillars (schnitzel day, pasta day), the new ones are the little adventures. That keeps variety in without you having to figure out in 8 minutes every evening what you're even cooking.

Mistake 2: Giving the kids no say. If the weekly plan comes purely from you and the child says «I don't like that» at every meal, the plan is ineffective — no matter how nice it looks on paper. A workable solution: once a week, briefly, let the child choose along. That can be: «Pick a main dish for Thursday from these three options» (3 options, not «anything»). It gives the child a bit of autonomy without the whole week turning into a negotiation.

Mistake 3: Not sharing the plan. If only you have in your head what's planned for Wednesday, the plan collapses the moment you're sick or unexpectedly working late. A family weekly plan has to be shared — on the fridge, in an app, somewhere every adult and ideally the older child can look. «What's for dinner today?» then answers itself.

In most families, not everyone eats the same thing. One child doesn't like mushrooms, another doesn't like sauce, the adult doesn't eat pasta after 7 PM (digestion argument). That's normal — but cooking 4 dishes in parallel isn't a solution either.

The principle that comes up in almost all family studies: «components instead of complete dishes». Instead of a finished casserole that's either eaten whole or not at all, you cook 3 components separately, and everyone mixes their own at the table.

Example: a «bowl night» with rice, a braised vegetable (e.g. sweet potato with curry spice), roasted chickpeas, avocado, a yoghurt topping, and flatbread. You cook one meal, but everyone gets their own component selection:

• Child 1 (doesn't like curry): rice + chickpeas + avocado + bread.
• Child 2 (doesn't like legumes): rice + sweet potato + avocado + yoghurt.
• Adults: everything together.

One meal, four variations, without you actually having cooked four dishes. This works especially well for: bowls, tacos / wraps, soups with toppings, pasta buffets, pizza with individual toppings, make-your-own sushi nights. These meals communicate «you choose» all on their own — and that takes a lot of conflict off the table.

For children with a particularly narrow palate («only likes 5 things»): the bowl principle lets them pick their 5 things without feeling isolated. That's psychologically more important than the purely nutritional question.

In mangia, every family has a family workspace — a shared area where the weekly plan and shopping list are visible to everyone. Inside it you create one profile per child — with a name, that's all it takes to start.

The profile fills itself in through what happens at the table: after every meal you mark as cooked, you can briefly note for each child whether it went down well — eaten, tried, refused. From these responses mangia builds a taste profile per child.

The point of these child profiles isn't «collecting data», it's «filtering the inspiration». When you search for a «Thursday evening idea» and have it sorted for one child, the recipes that landed in the past rise to the top — what flopped repeatedly slips down. You get 30 suggestions instead of 300, and you can decide instead of search. Learning in the background, without you having to maintain lists.

The child profiles stay within your family workspace — they never leave your family, are not used for advertising, and can be deleted at any time.

Three parts of mangia that work together in a family:

Browse (= inspiration). When you don't know what to cook: open Browse mode. Tinder-style, one recipe after another — you swipe right (interests me) or left (not today). mangia learns over time what the family likes, and filters suggestions based on the child profiles + past weeks.

Weekly plan. From the «swiped-right» recipes plus your fixed stars (schnitzel day) you build the plan. By drag-and-drop onto the days of the week. Visible to everyone in the family workspace.

Shopping list. From the weekly plan, mangia automatically builds a shopping list. Identical ingredients are combined (onion 3 times in the plan = 3 onions on one line, not 3 separate entries). The list is shared in real time with your partner — whoever is in the shop ticks off; the other sees it immediately.

This trio is the real benefit. Browse alone is nice. The weekly plan alone is a spreadsheet. The shopping list alone would just be another list app. Together they're what a family week needs.

The question comes up often: «Do my partner and I each need an account, or is one enough?» Answer: everyone has their own account, both in the same family workspace — that's the path mangia is built for.

Concretely: you create the «Smith Family» workspace, your partner joins with their own login. Advantage: separate personal preferences (you like it spicy, your partner doesn't), your own push settings, personal activity traceable in the Balance — and yet a shared weekly plan and a shared shopping list. One Pro licence in the workspace is usually enough for both.

Child profiles don't need their own account — they simply live in the family workspace. A 4-year-old needs no login, just a profile that you, as the adult, maintain.

A little tip for children who can already read (from around age 7): don't give the child full access, but let them see the family view on a tablet at the table. The child sees the plan, can tap «tomorrow» and see the picture. It feels like their own account, but it's just the shared view — it sidesteps the data-protection topic while still giving the child a sense of «mine».