Planning the week
Building a weekly meal plan that actually holds
Most weekly meal plans fall apart by Tuesday. Not for lack of willpower — because they are built as if the week were predictable. Here is the opposite method.
A weekly meal plan holds when it is deliberately incomplete: date only three meals, keep two dishes with no fixed day, and leave two evenings open. The three dated meals cover the nights you actually cook; the two floating dishes absorb whatever the week throws at you, so the plan never has to be rebuilt.
- Three dated meals, two meals with no fixed day, two evenings left open.
- One dish that comes back as leftovers the next day, planned that way from the start.
- The grocery list comes after the plan, never the other way round.
Why complete meal plans fail
Planning seven dinners means signing up for seven evenings with the energy, the time and the appetite you imagined on Sunday. One surprise — a meeting that runs long, a sick child, a change of mind — and it is not one meal that goes: the whole plan loses its credibility. By Wednesday nobody looks at it.
A partial plan is not a failed plan. It is the only kind that survives a real week. Most tools do the opposite: they want seven filled slots before they are useful at all.
A plan you are not allowed to break is a plan you abandon.
The three-dated-meals method
The idea is to plan what is certain and name what is not, instead of leaving the gaps blank — a blank gap is a decision postponed until 7 pm.
1. Spot your two difficult evenings
Every week has them. Training night, the night someone gets home late. Do not put anything to cook there: write “pasta”, “leftovers” or “everyone for themselves” explicitly. That is a planned meal, not a failure.
2. Date three meals, no more
Choose them by the energy available, not by theoretical variety: one long dish on the day someone is home, two thirty-minute dishes elsewhere.
3. Keep two dishes with no fixed day
These are your jokers. They are on the grocery list, the ingredients are in, but they have no slot. You place them once the week takes shape.
A full example
Here is a real week for two adults and one child, with training on Tuesday and a late evening on Thursday.
| Day | Meal | Why |
|---|---|---|
| Monday | Shepherd’s pie | One dish, large batch, feeds again |
| Tuesday | Shepherd’s pie leftovers | Training night — nothing to cook |
| Wednesday | Fish pie and greens | Someone is home to use the oven |
| Thursday | Pasta, sauce from the cupboard | Late return — chosen, not endured |
| Friday | No fixed day: roast chicken | Joker — moves if the week moves |
| Weekend | Open | Decided on the spot, with what is left |
Five decisions made on Sunday, two jokers, two open days. No evening without an answer.
Then the grocery list, in that order
The list comes after the plan — but it is not limited to it. Three streams feed it: the ingredients from the plan, the everyday “we’re out of that” (washing powder, coffee), and the opportunistic (what you pick up because it is in season). A tool that only derives the list from recipes misses two streams out of three.
- From the plan: the ingredients of the three dated dishes and the jokers.
- From the everyday: whatever runs out, added through the week by anyone at home.
- From opportunity: the market, the offer, the craving.
Three traps to avoid
Chasing maximum variety
Cooking a dish you love two weeks running is not a planning failure. It is what makes the system sustainable.
Planning lunches at the same time
Lunch answers to different constraints (school, office, leftovers). Mixing it into dinner doubles the decision load for no gain.
Rebuilding the plan from scratch every week
Start from last week and change two dishes. A weekly meal plan is not an original work.