Most first attempts at meal prep fail for the same three reasons
People rarely give up on batch cooking because it does not work. They give up because the first session was designed badly.
The three usual causes: it took four hours instead of the two that were available; every container held the same meal, so by Wednesday nobody wanted it; and half of what was cooked did not survive four days in the fridge. All three are planning problems, and all three are fixable before you turn on the oven.
This guide describes one realistic session — roughly two hours, four meals, food you will still want to eat on day four.
Prep components, not finished dinners
The single most useful change for a beginner is to stop cooking five identical portions of one dish and start cooking a small number of components that combine in different ways.
A component is one finished element: a pot of grains, a tray of roasted vegetables, a cooked protein, a sauce, a jar of dressing, a batch of caramelised onions. Four components can produce a bowl on Monday, a wrap on Tuesday, and a grain salad on Thursday. Four finished dinners produce exactly four dinners, and by the third you are eating out of obligation.
Components also fail more gracefully. If the sauce is dull, you have lost the sauce, not the week.
A reasonable first set:
- One grain or starch — rice, pasta, potatoes, couscous, or barley.
- One or two proteins — roasted chicken, a pot of lentils, baked tofu, hard-boiled eggs, or a pan of spiced mince.
- One tray of vegetables — roasted, because roasting is unattended time.
- One sauce or dressing — the element that makes the same components taste different on different days.
Plan the session backwards from the time you actually have
Write down the finish time first, then work backwards. A two-hour session is not two hours of cooking; it is roughly fifteen minutes of setup, ninety minutes of overlapping work, and fifteen minutes of packing and cleaning.
The skill in batch cooking is overlap. Anything that cooks unattended should start first, and anything that needs your hands should happen while it does.
A workable two-hour shape:
- 0:00 Oven on. Vegetables cut and into the oven first, because they are the longest unattended block.
- 0:15 Grain on the stove. Protein prepped while it cooks.
- 0:35 Protein into the oven or a pan. Sauce and dressing made now, while both are cooking.
- 1:10 Everything comes out. Grains and vegetables spread out to cool.
- 1:30 Pack, label, and clean while the last items cool.
If the plan needs three things on the stove at once and you have two burners, it is not a plan. Check the hardware, not just the timings.
When you want the timeline generated rather than sketched, the CookFeed batch cooking planner takes your available minutes, meal count, servings, dietary needs, and whether the meals are for the fridge or freezer, then produces a prep order and storage guidance you can adjust.
Cool food properly, then store it properly
This is where a good session gets undone, and it is the part worth being conservative about.
Hot food should be cooled quickly rather than left on the counter to reach room temperature over several hours, and it should not be sealed while still steaming. Spread it out to increase the surface area, use shallow containers rather than deep ones, and get it into the fridge once it has stopped steaming. Follow your local food-safety guidance on cooling and storage times; the specifics vary by country and are worth knowing accurately.
Then label everything. Not with the dish name — with the date. A container of rice with no date is a container you will eventually throw away, because nobody remembers whether it was Sunday or the Sunday before.
Rough planning guidance, not a safety rule: cooked grains, roasted vegetables, and cooked proteins are typically planned for a few days in the fridge, while most cooked dishes freeze well for a month or more. Use your own judgment, follow local advice, and discard anything you are unsure about. Do not taste food to test whether it is safe.
Freeze the surplus on day one, not day four
The most common waste pattern in meal prep is optimism: you cook five portions, eat three, and discover the last two on Friday when it is too late to do anything with them.
Decide at packing time which portions are for this week and which are going straight into the freezer. Freeze them immediately, while they are at their best. Two meals in the freezer on Sunday is a good outcome. Two meals discovered on Friday is a loss you paid for twice — once at the shop and once in the bin.
Sauces, soups, stews, cooked grains, and most braised dishes freeze well. Dressed salads, fried food meant to be crisp, and most dairy-heavy sauces do not.
Make reheating part of the plan
Food that reheats badly does not get eaten. Think about the last five minutes before each meal while you are still cooking.
- Undercook vegetables slightly if they will be reheated, so the second cooking finishes them.
- Store sauce separately from grains and vegetables where you can — it keeps textures distinct and lets one component taste like three meals.
- Keep anything crisp or fresh out of the container entirely. Herbs, citrus, yoghurt, nuts, and raw vegetables are worth adding at the last moment, and they do more for a fourth-day meal than anything you can do on the first day.
- Reheat thoroughly and evenly, and follow local guidance on reheating.
Start smaller than you think you should
For a first session, cook two components and two meals rather than four. A short session that finishes on time teaches you the timings; an ambitious one that runs to four hours teaches you that you hate meal prep.
Once one session works, scale it. Once two work, connect it to the week: a batch session is most useful when it fills specific gaps in a plan you already have, which is why it pairs naturally with a weekly plan built from your pantry and with a single consolidated shopping trip rather than three.
The measure of a good session is not how much food is in the fridge on Sunday evening. It is how much of it you actually ate by Thursday.