It is ten past six. The fridge has half a cabbage, some yoghurt and a packet of chicken you are no longer confident about.

You planned this. On Sunday you wrote out seven dinners, felt briefly excellent about yourself, and did a big shop. By Wednesday two of the meals had not happened, the coriander had turned, and the plan had quietly become a list of things you failed to cook.

The plan was not too ambitious. It was the wrong shape.

Plan four dinners, not seven

Seven recipes means seven sets of ingredients, seven methods and seven evenings that have to go roughly to plan. Households do not get seven of those in a row.

A week that survives contact with a Tuesday looks more like this: four nights you cook something, one night you eat what you cooked on Tuesday, one night that comes out of the cupboard in ten minutes, and one night nobody cooks at all.

The repeat night and the fast night are going to happen anyway. The only question is whether you planned them or lost to them.

That is the whole trick, and it is why plans that look lazier work better. You are not planning fewer meals. You are planning the same seven and only shopping for four.

Give every meal a day

Picking seven meals for “this week” and leaving them in a pool feels flexible. It is the original problem wearing a hat: someone still has to choose at six o’clock, with everyone hungry.

Assign each meal to a named day, and do it against what the week already holds. Late meeting Thursday? Thursday is the fast night. Swim club Tuesday, back at seven? That is the twenty-minute pasta, not the thing that needs an hour in the oven.

This is the step most people skip, and it is the one that turns a list into a plan. It also means the answer to “what’s for dinner” is already written down, which is worth more than the cooking time it saves.

Keep a rotation of about twenty meals

The slow part of meal planning is not writing the plan. It is staring at nothing trying to remember what your family eats.

Write down every meal your household genuinely eats and enjoys. Most people stall somewhere between fifteen and twenty-five, and that is plenty: at four cooking nights a week, twenty meals is a five-week rotation, which is far enough apart that nobody notices.

• Six that take under 25 minutes. These carry the bad weeks.
• Six mid-week standards everyone will eat without negotiation.
• Four that make good leftovers. Chilli, curry, a traybake, a big pot of something.
• Four you cook when there is time, for weekends.

New recipes go in one at a time, when you feel like it. A plan built entirely out of things you have never cooked is a plan with no floor under it.

Turn the plan into one shopping list

A meal plan that does not produce a shopping list has done half a job. The gap between the two is where the third ingredient of Thursday’s dinner goes missing.

Go through the four recipes, write down what each needs, check what is already in the house, and shop once. Grouping the list by aisle instead of by recipe is a small thing that saves a surprising amount of walking, for the same reason shared lists work better sorted by shop than by person.

Decide who is cooking, not just what

In most households the person who writes the plan is also the person who cooks it, and that is usually the same person who noticed the yoghurt was running out.

Put a name against each cooking night when you write the plan. It takes ten seconds and it changes what the plan is: no longer one person’s intentions, but something the house agreed to.

If that division is a live subject in your kitchen, it is worth reading why doing half the work is not the same as carrying half the load, because planning the food is most of the job and it is invisible.

Paper, spreadsheet or app

All three work. They fail differently, which is the useful part.

If a paper chart on the fridge is working for your house, keep it. The honest reason to move is the shopping list: retyping the plan into a list every Sunday is the step that stops happening in about week three.

Getting past week three

Almost everyone manages two weeks. The third is where it goes, and usually for one of four reasons.

1. The plan had no slack. Fixed by the four-night shape above.
2. Nobody could see it.A plan on one person’s phone is that person’s plan.
3. The shop did not match the plan. One list, built from the plan, or the plan is fiction.
4. It needed rebuilding from scratch each week. Hence the rotation. Sunday should be picking four, not inventing seven.

Swap, do not abandon

When a night goes wrong, move that meal to the fast night and push the fast night forward. The plan bends. What kills it is treating one missed dinner as evidence the whole thing failed.

Common questions