Mazir
Search "meal prep" and you'll find the same photo everywhere: ten identical containers of chicken, rice, and broccoli, lined up like a barracks inspection. It photographs beautifully and fails predictably — by Thursday the food is boring, by the second Sunday the four-hour cooking marathon feels like a part-time job, and by week three the whole project is abandoned. Batch cooking is genuinely one of the highest-leverage kitchen habits there is. It just doesn't look like the photo. Sustainable meal prep means prepping components and doubling batches, not pre-plating a week of identical lunches.
Why the Sunday marathon fails
- It front-loads too much effort. Four hours of cooking after a busy week is a chore you'll eventually skip — and the system has no answer for a skipped Sunday.
- It locks in decisions too early. Committing on Sunday to exactly what you'll want to eat Thursday ignores how appetites work. Rigid prep produces uneaten containers, which is waste with extra steps.
- Quality degrades. Most fully-assembled meals are noticeably worse on day four. Components, by contrast, keep well — and assemble into fresh-tasting food in minutes.
The three tiers of batching
Think of batch cooking as three separate techniques, deployed in combination:
| Tier | What it is | Effort |
|---|---|---|
| Component prep | Cook building blocks, not meals: a pot of grains, roasted vegetables, a protein, a sauce, washed greens | 60–90 min, once a week |
| Double-batching | Whenever you cook anyway, cook 2× and bank the surplus — near-zero marginal effort | +10 min per meal |
| Freezer stocking | Freeze portioned, labeled meals from your doubles for zero-effort nights weeks later | Free (byproduct of doubling) |
Tier 1: components, not containers
A 60–90 minute session — with the oven, hob, and cutting board working in parallel — produces something far more useful than ten identical lunches: a fridge full of almost-meals. A typical session: one grain (rice, quinoa, or roast potatoes), one or two proteins (a tray of chicken thighs, a pot of lentils), two trays of roasted vegetables, one sauce or dressing, plus washed salad greens. All week, dinner is assembly: grain bowl tonight, wraps tomorrow, fried rice from the same components on Thursday. Ten-minute meals, and no two feel alike — which is exactly what the identical-containers method can't offer.
Tier 2: the double-batch reflex
The cheapest cooking you will ever do is the second batch of something already on the stove. Chili, bolognese, curry, soup, stew — doubling them adds about ten minutes and one bigger pot, and yields a full extra meal. Make it a standing rule: every batchable dish gets doubled, always. The surplus either becomes a scheduled dinner later in the week or goes straight to the freezer.
Tier 3: run the freezer like a pantry
The freezer is where double-batches become a safety net — if you manage it, and merely a graveyard if you don't:
- Portion before freezing. Single- or family-meal-sized containers, frozen flat where possible. A frozen four-liter block of chili helps no one on a Tuesday.
- Label with name and date. Unlabeled containers become mystery objects nobody risks. Most cooked dishes keep well for two to three months.
- Plan withdrawals. When building the week's plan, pull one freezer meal into a slot deliberately. First in, first out — the freezer is a rotation, not an archive.
What batches well (and what doesn't)
Some dishes improve with a day's rest; others collapse. Save yourself the sad discoveries:
| Batch with confidence | Cook fresh |
|---|---|
| Stews, chili, curries, bolognese (better on day two) | Anything fried or crispy — coatings go soggy |
| Soups, cooked grains, legumes | Delicate fish fillets |
| Roasted root vegetables, casseroles, bakes | Dressed salads (prep components, dress at serving) |
| Sauces, marinated raw proteins | Pasta cooked to doneness (it keeps softening) — undercook if you must |
The food safety basics, briefly
Batch cooking concentrates food-safety decisions, so get four rules right: cool cooked food quickly (shallow containers, into the fridge within two hours — not on the counter overnight); reheat leftovers thoroughly until piping hot, once, not repeatedly; keep cooked food three to four days in the fridge and treat the freezer as the option beyond that; and thaw in the fridge or microwave, never on the counter.
Batching only works attached to a plan
Here's the step most meal-prep guides skip: surplus food without an assigned future is just slow-motion waste. The double-batch on Tuesday needs a named slot on Thursday; the freezer meal needs to be pulled into next week's plan. Batch cooking and meal planning aren't two habits — they're one loop: the plan decides what to batch, and the batches fill next week's plan.
Tip: in Mazir, planned dishes scale to any number of servings and the shopping list follows automatically — so doubling Tuesday's curry is one tap, and the extra portions sit in the plan where they'll actually get eaten.
Frequently asked questions
How much time does this actually save?
A 90-minute component session plus the double-batch reflex typically turns five weeknight dinners into 10–20 minute assemblies — saving three to four hours of weeknight cooking, on the nights when time is scarcest.
I live alone. Is batch cooking worth it for one person?
Arguably most of all — single-portion cooking has the worst effort-to-meal ratio there is, and recipes rarely scale down. Cook the full recipe, eat one portion, and bank three: instant variety across the week from a single cooking session.
Do I need special containers or equipment?
No. A stack of same-sized containers (they tessellate in the fridge and freezer), tape and a marker for labels, and ideally one big pot. Everything else is optional.
Make the batches part of the plan
Mazir lets you scale any dish's servings, drop the extra portions into future slots, and generates the week's shopping list to match. Free to start.
Try Mazir