How to batch cook: a plan for cooking once and eating all week

The fastest way to build a batch cooking plan for the week is to work backwards from the last day you’ll eat it: pick three or four dishes that genuinely hold up that long, shop and prep them in one deliberate order, and leave room for one thing that’s cooked fresh so the week doesn’t taste like a single long meal on repeat. Most people do it the other way round — cook whatever looks appealing on a Sunday, then discover on Wednesday that half of it has gone grey and nobody wants it — and that’s the whole reason batch cooking gets a reputation it doesn’t deserve.

Here’s the method, and then the part where you stop starting from zero every week.

Choose dishes that actually survive four days

Not everything you love to eat survives a Tuesday reheat, and figuring that out before you cook is most of the battle. A few rules that hold up across almost any cuisine:

• Braises, stews and curries improve. Anything simmered low and slow tastes better on day two than day one — the flavours have had time to find each other. If you’re batch cooking for the first time, start here.
• Grains and legumes hold their shape. Rice, farro, lentils, chickpeas — cook a big batch once and they stay good as a base for four different bowls.
• Roasted vegetables go soft, not bad. They lose their crisp edge but they’re still worth eating, especially folded into a grain bowl or blitzed into a soup.
• Sauces are the real trick. One big batch of tomato sauce, a peanut sauce, or a simple vinaigrette turns four different proteins and grains into four different-feeling meals, which is what actually keeps you from getting sick of the plan by Wednesday.

The dishes to leave off the list: anything fried (it doesn’t recrisp), delicate fish (it overcooks the second time), and salads with a dressing already on them (they wilt). Those are worth cooking fresh, even on a batch-cooking week.

The shopping and prep order that keeps it to one afternoon

The difference between a batch cooking session that takes three hours and one that eats your whole Sunday is almost never the cooking — it’s the order you do things in.

1. Shop from what you already have first. Check the fridge and the freezer before you write a list, so you’re not buying a second bag of onions you already own. This is the step people skip, and it’s the one that turns a grocery run into a genuinely one-trip errand.
2. Prep everything raw before anything goes on the stove. Chop every onion, wash every green, portion every protein — all of it, up front — so you’re never stopping a simmer to go find a knife.
3. Start the slowest thing first. Get the braise or the stock going, then use that hands-off time to roast vegetables and cook grains in parallel. Batch cooking is really just running two or three burners and an oven at once, in the right sequence.
4. Cool everything before it goes away. Food that goes into a sealed container hot steams itself soft and grows bacteria faster in the fridge. Spread it out to cool for 20 minutes, then pack it.
5. Label what’s going in the freezer and what’s staying out. A batch that’s headed for the freezer needs a name and a date on it, or it becomes an anonymous block of something in three weeks. If you want somewhere to note what went in and what came back out again, that’s exactly the gap a pantry inventory closes — you cook once, but you still want to know what you’re actually working with a week later.

Done in that order, a real cook-once-eat-all-week session runs three to four hours for a full week of dinners, most of it hands-off simmering and roasting rather than active chopping.

What reheats well, and what collapses

Reheating is where a good batch-cooking plan is won or lost, and the fix is almost always the same: add moisture, use gentle heat.

Reheats beautifully: soups, stews, curries, chili, braised meat, cooked grains (splash of water, covered, in the microwave or on the stove), roasted root vegetables, most sauces.

Reheats fine with a little help: rice (always add a splash of water first, it dries out fast), pasta dishes with a sauce (never dry pasta on its own — it turns to glue).

Collapses: anything meant to be crisp — fried chicken, roasted potatoes you wanted crunchy, a salad that’s already dressed. Greens wilt into something sad if they sit dressed for four days; keep the dressing separate and add it the day you eat.

The trick that saves most of the “collapses” category: cook the crisp element fresh, in 10 minutes, and reheat only the part that was always going to be soft anyway. A batch of braised lentils plus a freshly fried egg is still a five-minute dinner.

The honest failure modes that make people quit after one try

If you’ve tried batch cooking once and never went back, it’s almost certainly one of these, and every one of them is fixable.

You cooked one enormous dish. A single giant pot of chili sounds efficient and turns into a chore by day three — nobody wants the same flavour five nights running. The fix is variety through sauces and bases, not through five separate elaborate recipes; see the sauce trick above.

You didn’t plan for a fresh night. A week that’s 100% reheated food feels like eating leftovers on purpose, which it technically is. Once a month cooking works the same way at a bigger scale — the people who stick with it always keep one or two nights genuinely fresh, so the freezer stash is a safety net, not the whole plan.

You underestimated the cleanup. Batch cooking concentrates a week’s worth of dishes into one afternoon, and if the sink fills up faster than you can keep clearing it, the whole session starts to feel punishing. Wash as you go, and put the big stockpot on to soak the second it’s empty.

You forgot what you’d already cooked. This is the quiet one. Three containers deep in the fridge, nothing labelled, and by Thursday you’re ordering takeout because finding the right meal felt harder than skipping it. A sticky note works. So does anything that keeps a running note of what’s already made and what’s already in the freezer, so day four is a decision, not an archaeology dig.

Start with one week, not a system

You don’t need a colour-coded plan or a dedicated Sunday ritual to get the benefit. Pick three dishes from the “survives four days” list above, shop from what you already have, prep in the order above, and see how Wednesday feels. If it holds up, do it again next week. If a particular dish flopped, drop it and try another — the method stays the same, only the dishes change. That’s the whole plan: cook once, eat well, and stop deciding what’s for dinner five nights in a row.