Who's Cooking Tonight? (And When Should They Start?)

In most households, "who is cooking" is the question that breaks more meal plans than recipe choice ever does.

You planned chicken thighs for Wednesday. You assumed you were cooking them. Your partner assumed they were cooking them. Now it is 6:30, the chicken is still in the fridge, and you are looking at each other in the kitchen having the same conversation you had two weeks ago.

The meal plan is fine. The coordination around it is the failure point.

The calendar is not enough

A meal plan that says "Wednesday: chicken thighs" tells you what is happening. It does not tell you who is responsible, who needs to start defrosting at noon, or what time the meal is supposed to land on the table.

Most recipe apps treat the meal plan as a calendar of dishes. That works fine if there is exactly one cook and exactly one eating time. It falls apart the moment the household has more than one cook, more than one schedule, or more than one mealtime.

Which describes basically every family that is not living alone.

What cook assignment solves

When the meal plan includes a cook assignment, a few things become possible.

The right person knows it is their turn. If you and your partner trade off, the calendar says it out loud. Wednesday is yours. Thursday is theirs. No ambiguity to relitigate at 6pm.

The right person gets the reminder. "Start defrosting the chicken at noon" is useful to the cook and noise to everyone else. If the app knows who is cooking, the reminder goes there and only there.

The kids can take a turn. Teaching a teenager to cook one night a week is a different conversation when the plan assigns them a recipe, walks them through the prep, and reminds them when to start. It stops being a parent-managed activity.

Notifications should work backwards from the meal

The simplest meal-plan notification is "your meal is today." This is almost useless. By the time you see it, the planning window is over.

A better version works backwards from when you want to eat. If dinner is at 6:30 and the recipe takes 90 minutes including a 30-minute marinade, the right notification fires around 4:30. Start the marinade if you want to eat by 6:30.

This sounds small. It is not. The reason most home cooks miss their target time on weeknights is not that the recipe is hard. It is that they started thirty minutes too late and they did not realize until they were stirring something and noticed it was 7pm.

I built Flour Power to calculate these notifications from the recipe's total time and the eating time you set. The math is not complicated. It just has to be done, and most apps do not do it.

What it looks like in practice

Imagine a household of four with one teenager learning to cook.

Monday is sheet pan chicken at 6:30, cooked by parent A. Tuesday is pasta at 6:00, cooked by the teenager. Wednesday is slow cooker carnitas at 7:00, cooked by parent B. Thursday is leftovers. Friday is takeout.

Wednesday morning, parent B (and only parent B) gets a notification at 8am: "Carnitas in the slow cooker, start by 10am for 7pm dinner." If they miss it, a follow-up fires at 10am. The rest of the family is not getting these notifications because they are not relevant.

Tuesday at 5pm, the teenager gets the pasta reminder. Not at 8am, because pasta takes thirty minutes. They get a step-by-step cooking flow when they start, with timers built in.

Nobody coordinates this verbally. The plan is the source of truth.

A note on notification fatigue

There is a real risk of building a system that buries people in alerts. The opposite of "no notifications" is not "lots of notifications." It is the right notifications for the right person at the right time.

A few rules I follow.

Only fire for people who are actually cooking. If you are not the assigned cook tonight, the system stays silent toward you.

Only fire when action is needed. "Start the marinade" is useful. "Tonight's dinner is chicken thighs" sent at 8am is not, because you knew that when you planned the week.

Turn-off-able per meal type. Some households want reminders. Some want a calm app that shows the plan and lets them get to it on their own time. Both should work.

The honest caveat

Cook assignment only works if your household will actually use it. If you and your partner trade off cooking informally based on who is less tired, encoding it in advance might feel like overhead. The feature shines when there is a pattern worth encoding. If your pattern is "whoever is home first," do not bother.

The meal plan is not just a list of dishes. It is a small piece of household coordination, and household coordination is a multi-person problem.

A tool that treats every family member as one user with one calendar is solving the wrong problem.