Planning Last updated July 14, 2026

Plan meals before shopping

Not financial advice. This is general information about personal finance, not advice tailored to your situation. We’re a finance tracker app, not a licensed financial advisor. The examples in this article are illustrative. For decisions that affect your specific finances, talk to a licensed financial planner.

For most households, food is the #2 or #3 monthly expense. The waste is not in the ingredients — it is in the patterns: the unscheduled top-up shop on day 4, the takeout that replaced a planned dinner, the produce that went bad because nothing in the fridge matched. A 20-minute weekly meal plan closes most of those gaps, and it does not require cooking skill or dietary expertise to do.

What does a meal plan actually do?

A meal plan is a short list of the dinners (and usually the lunches) you will cook for the next 5–7 days, written before you go shopping. The plan does three things, all of them mechanical:

Removes the “what’s for dinner” decision from the hungry hour. The 6pm version of you, who has been at work for nine hours, will always choose the option with the least friction. A plan gives that person something to follow instead of something to invent.
Aligns the shopping list with the meals. The list becomes a function of the plan, not a function of whatever looked good in the shop. The result is fewer duplicate ingredients and less waste.
Makes the budget predictable. A planned shop has a known cost. An unplanned shop has a guess. The first one is auditable; the second one is not.

A plan is not a meal-prep guide. You are not cooking seven portions on Sunday and living off containers. You are deciding, in advance, what the next seven dinners are, and shopping for those. Some of them can be 20-minute meals. Some of them can be repeats. The point is the decision, not the cooking complexity.

A 7-day dinner plan you can adapt

The plan below is built for two adults, two dinners from leftovers, and one flex night. The flex night is the point: plans that try to specify every day die in week 3.

Day	Dinner	Core ingredients	Uses leftovers from
Mon	Stir-fry chicken + vegetables	Chicken thigh, frozen veg, soy sauce, rice	—
Tue	Fried rice	Rice, egg, spring onion, leftover veg from Mon	Mon
Wed	Tomato pasta + sausage	Pasta, canned tomato, sausage, onion	—
Thu	Sandwiches + soup	Bread, cheese, canned soup	—
Fri	Pan-fried fish + rice	White fish, rice, frozen peas, lemon	—
Sat	Tacos / wraps	Tortillas, mince, onion, salsa	—
Sun	Flex night	Whatever is in the fridge, or eggs-on-toast, or order in	Friday’s veg

Two structural rules are doing most of the work:

Two dinners are deliberate leftover nights. Tuesday uses Monday’s rice. Friday’s leftover veg becomes Sunday’s omelette or fried rice. Without these, the plan breaks the moment you cook too much on any single day.
Sunday is a flex night on purpose. If the week slips — a long day, a dinner out, a low-energy evening — Sunday is where the slippage is absorbed. Plans that include no flex day fail because the flex day is unavoidable.

The plan is also deliberately cheap. The proteins are mostly chicken thigh (cheaper than breast), white fish (cheaper than salmon), and one tin of beans or lentils for the wraps. The vegetables are mostly frozen. Frozen vegetables are picked at peak ripeness and lose less nutrition than the “fresh” produce that has spent three days in transit.

The 3-list system

The plan is only useful if it drives a clean shopping list. The 3-list system is the simplest way to get there:

“What we have” — fridge, freezer, pantry. A quick walk-through at the start of the planning session. Most of what you need is already in the kitchen; the plan should use it.
“What we’re making this week” — the meal plan. 5–7 dinners, 5–7 lunches if you pack, plus breakfast staples.
“What we need to buy” — only what is on the first two lists, minus what is already on the third. The list is the function; the plan and the pantry are the inputs.

The third list is the only one you take to the shop. It is also the list you compare against the receipt when you get home — any item on the receipt that is not on the list is a candidate for the “impulse” tag in the pattern report, and any item on the list that is not on the receipt is a planning miss for next week.

Why plans fail, and how to plan for that

The reasons meal plans fail are predictable, and most of them are absorbed by the plan itself if the plan is built with the failure in mind:

A long day at work. The flex night absorbs this. The plan is allowed to include “order in” once a week without it being a failure.
A leftover night you forgot was a leftover night. A fridge inventory on Wednesday evening catches this. The plan should be visible (a paper on the fridge, a note in the phone), not memorised.
A recipe that needs an ingredient you forgot. The shopping list is the only place that can save you. Use it.
A dish that nobody ate. This is the most important failure mode. If a meal gets 50% eaten and 50% thrown out, the plan is wrong, not the household. The next plan should make smaller portions of that dish, or replace it with something the household actually eats.

The discipline is to look at the failures honestly. A plan that is re-built every week, with the previous week’s failures in mind, gets steadily better. A plan that is abandoned after one bad week never gets the chance.

The “last-minute takeout” trigger

The single most expensive day in a household’s food budget is the day a plan failed. The pattern is consistent: long work day, fridge is empty, energy is low, takeout is ordered. The order is often 3–5x the cost of the home-cooked equivalent.

The fix is a pre-made fallback that is cheaper than the order and faster than cooking from scratch. A useful pre-made fallback:

Eggs + bread + cheese (a 5-minute meal that costs a fraction of an order).
A frozen meal you actually like, kept in the freezer for exactly this trigger.
A simple pasta with butter and parmesan (3 ingredients, 10 minutes).
A bowl of rice with a fried egg, soy sauce, and spring onion (5 minutes, USD 0.50).

The fallback is not a punishment. It is a permission: when the plan fails, the fallback is what you reach for. The order is the third option, not the first. Once the fallback is the default, the takeout line on the budget shrinks without anyone feeling deprived.

Pantry staples that make a plan possible

The plan above assumes a few pantry staples are always in the kitchen. A short list, kept stocked, removes the “I can’t make this because I don’t have X” failure:

Carbs. Rice, pasta, bread, tortillas. Two of these, always.
Canned / jarred. Tomatoes, beans, coconut milk, soy sauce, stock cubes.
Frozen. Mixed vegetables, peas, fish fillets, chicken portions. Frozen is the cheapest “fresh” you can buy.
Aromatics. Onion, garlic, ginger. Most weeknight dinners start with these three.
Eggs. The single most useful ingredient in any kitchen. Breakfast, dinner fallback, baking, the binder in a meatball.
Oil, salt, pepper, a few dried herbs. The non-negotiable minimum.

When these are stocked, the meal plan can rely on fresh ingredients for the protein and produce, and everything else is already in the kitchen. The weekly shop becomes smaller, and the budget becomes predictable.

How does this fit with a budget?

Food is the largest “needs” line in most budgets, after rent. The 50/30/20 framing treats it as a single bucket, but inside the bucket, the right split is between groceries and dining out. The two are tracked as separate categories. The groceries line is funded to a real number; the dining-out line is a small allowance that exists for social meals, not for last-minute failures.

A meal plan keeps the dining-out line at the allowance. The plan’s flex night, the fallback meals, and the 3-list system are all working on the same problem: keeping the “I had no other option” excuse from being the most expensive line in the budget.

The plan is also a measurable goal in disguise. “Reduce the monthly grocery bill by 15%” is a wish. “Keep this week’s shop under USD 38” is a goal with a number, a deadline (Sunday), and a visible record in the receipt. The plan is the system; the goal is the metric.

Where Finanxy fits

Finanxy treats groceries and dining out as separate categories, each with its own weekly cap. The planned-payments view schedules the weekly shop as a single planned transaction; the actual receipt is then compared against the plan at the end of the week.

The reports that matter are the weekly trend (is the shop getting smaller or bigger, in real USD per week?) and the dining-out frequency (how many of the 21 evening meals this month were cooked vs ordered). The first time you see the dining-out frequency, it is usually higher than you expected. The plan, the fallback, and the cap are the response.