What a batch cooking session actually involves
Batch cooking means setting aside one longer stretch of time, usually a weekend afternoon, to cook several meals' worth of food in one go, then eating from that stock across the week ahead. Instead of cooking from scratch on a Tuesday when you're tired and the fridge looks unpromising, you're reheating something you already made when you had the time and the energy to do it properly.
The idea isn't to cook every meal for the next seven days in one sitting. Most households who make it stick pick two or three dishes that freeze or keep well, make a larger batch of each, and portion them out as they go. A big pot of chilli, a tray of roasted vegetables with a grain, and a batch of meatballs in sauce cover a surprising number of weeknights between them.
Why it changes what a Tuesday evening actually looks like
The problem batch cooking solves isn't really about time in the kitchen. It's about decision fatigue: after a full day, working out what to cook, checking whether you have the ingredients, and then actually cooking it are three separate jobs, and a takeaway removes all three at once. Batch cooking removes two of them in advance, so the only thing left on a Tuesday is heating something up.
Use our batch cooking session planner to work out how many meals a single session could realistically cover for your household, based on how many people you're feeding and how much freezer space you've actually got.
Where the real saving comes from
Cooking three portions of rice instead of one takes almost no extra time, and the same is true for most sauces, stews and roasted vegetables. The saving in a batch session comes from the fixed costs, chopping an onion, heating a pan, washing up, being spread across several meals rather than repeated for each one.
Common mistakes people make on their first attempt
Most people who try batch cooking once and don't come back to it fall into one of a small number of traps.
- Cooking too many different dishes at once. Three unfamiliar recipes in one session means three sets of ingredients, three sets of pans, and a much longer afternoon than expected. Two dishes done properly beat three done in a rush.
- Not checking freezer space first. A batch of six portions is only useful if there's somewhere flat to freeze it. Containers that stack matter more than containers that look nice.
- Freezing the whole batch as one block. A single large container of chilli takes a day to thaw and gives you one meal. Portioning before freezing, rather than after, is what makes a batch actually flexible.
- Choosing dishes that don't reheat well. Anything with cream that's likely to split, or salad leaves that will wilt, doesn't belong in a batch. Stews, curries, bakes, soups, and cooked grains all hold up.
- Skipping the shopping list step. Buying ingredients dish by dish means buying the same onion or tin of tomatoes three times over. Working out totals across all the dishes first usually cuts the bill.
Getting portions and freezer space right
The two numbers that decide whether a batch cooking session actually works are how many portions your household eats in a typical week and how much space you have to store them. Guess either one wrong and you either run out by Thursday or end up with three tubs of the same stew that nobody wants to eat again.
A reasonable starting point is to batch cook enough for four to six main meals, split across two dishes, and see how quickly they actually get eaten before increasing the quantity. Labelling containers with the dish and the date matters more than it sounds: a freezer full of unlabelled tubs is where good intentions quietly go to waste.
Freezer-friendly doesn't mean freezer-only
Most batch cooked dishes keep in the fridge for three or four days as well as the freezer, which is worth knowing if you're only planning a few days ahead. A dish described as freezer-friendly will normally keep in the freezer for up to three months, but the fridge is the better home for anything you'll eat within the week.
Building a session that fits your week
The mechanism that makes batch cooking work is fairly mechanical once you see it laid out: pick the dishes, work out the combined shopping list, cook in an order that uses the oven and hob at the same time, then portion and label as things cool. None of that needs to be worked out from scratch every time.
- Choose two or three dishes that freeze or keep well, ideally ones sharing a few ingredients.
- Work out how many portions each dish needs to make, based on how many meals you want covered.
- Build one shopping list across all the dishes.
- Cook the dish that takes longest first, and use the time it's in the oven or simmering to prepare the others.
- Portion into the containers you'll actually use, and label each one with the contents and the date.
Use our batch cooking session planner to lay this out for your own household: it works from the portions and freezer space you tell it, so the plan it gives back can be wrong for your particular kitchen, and it's worth treating as a starting point rather than a fixed plan, adjusting anything that doesn't fit once you're actually cooking.
Where batch cooking fits with the rest of your week
A batch cooking session covers the meals you can predict in advance, but it isn't meant to replace every dinner. Most households pair it with a couple of quicker meals built around whatever's actually in the fridge partway through the week. If you want help with that half of the plan, the fridge ingredient matcher works from what you've got left.
It's also worth looking at the cost side before deciding how much to batch. The takeaway vs home cooking cost comparison gives a sense of what a session like this is worth in pounds, and the weekly meal budget planner guide covers how batch cooking sits inside a broader weekly food budget.