How to meal plan a week that survives Wednesday
Plan for the number of meals you will really cook, give each day a job instead of a named recipe, choose dishes that share ingredients, and derive the shopping list from the plan rather than writing it from memory. Then leave one slot deliberately empty, because every week contains one surprise.
1Count the meals you will actually cook
Before choosing a single recipe, count. Not seven — the real number. Subtract the day you are out, the meal someone else makes, the evening that always turns into toast. Most households plan seven dinners and cook four or five.
This one subtraction fixes more than anything else here. Planning for meals you were never going to cook is the main reason food gets thrown away, and throwing food away is the main reason people decide meal planning "doesn't work for us".
2Start from what already repeats
Write down the three or four things you can cook without looking anything up. The chilli. The roast chicken. The pasta you have made two hundred times. Those are the spine.
A plan built entirely from new recipes is a plan you have never tested: every meal carries the risk of a missing ingredient, an unfamiliar timing and a dish nobody wanted. One new thing a week is plenty.
3Give each day a job, not a recipe
Instead of pinning a named dish to a named day, give the day a job. One day is the long cook. The next eats it again. The middle of the week gets the fifteen-minute thing, because that is when a week is most likely to go wrong. One day is the cupboard and the freezer.
Jobs are portable. If a day collapses, the job moves and nothing is rewritten. A named recipe pinned to a fixed date has no such flexibility, which is why so many plans have to be thrown out whole.
4Choose things that overlap on purpose
Pick meals that share two or three ingredients. Not because it is virtuous — because it is what turns a plan into one shop.
Coriander is the standard example: a bunch is enough for three meals and rots after one. Same for a tin of chipotle, a bag of tortillas, half a bunch of celery. After you have chosen, look for the ingredients that appear once and only once, and ask whether something else could use the other half.
5Write the list from the plan, not from memory
This is the step that quietly takes twenty minutes and is the real reason people give up.
By hand it means going through every recipe, adding up what appears more than once, scaling from "serves 4" to however many are actually eating, and reordering the whole thing so you are not walking back to the produce aisle for the third time. It is arithmetic, it is boring, and it is completely mechanical — which makes it the one part genuinely worth handing to software.
6Leave one slot deliberately empty
Not "we'll see". Empty, on the plan, on purpose.
Every week contains one surprise: a late meeting, a friend passing through, a day when nobody can face cooking. A plan with no slack spends that surprise by breaking. A plan with one empty slot absorbs it and the rest survives.
Questions people ask next
How long should meal planning take?
Ten to fifteen minutes once a week, and less after a month, because most of it is things you already repeat. If it reliably takes an hour you are choosing recipes rather than planning — cut the new dishes to one.
What do I do when the plan breaks?
Move the meal, do not rewrite the week. The food is already bought; the plan only needs reordering. That is exactly why the days get jobs rather than fixed dates.
Is meal planning actually cheaper?
Usually, though not for the reason people expect. The saving comes from buying fewer duplicates and throwing less away, not from clever budgeting.
Do I need an app for this?
No. Paper works. An app earns its place only if it removes the arithmetic in step five and then gets out of the way.