The hardest part of a weekday dinner is rarely the cooking. It is the deciding, the chopping and the sinking feeling at 7 p.m. that nothing has been started. Batch cooking attacks exactly that problem: a planned session on the weekend that leaves the week’s building blocks ready, so weekday meals become assembly rather than production. Done sensibly, it saves several hours a week, cuts food waste, reduces ordering-in, and lowers the daily mental load that makes evenings feel rushed.

Done badly, of course, it means eating the same tired sabzi four days running, which is why many people try it once and stop. The difference between the two outcomes is not effort; it is what you choose to cook ahead.

Prepare components, not complete meals

The most durable batch-cooking insight is to prepare components rather than finished dishes. A pot of dal tastes progressively duller reheated daily. But cooked chana, boiled and cubed potatoes, a base gravy of onion-tomato masala, washed and chopped greens, soaked and cooked rajma, a jar of roasted peanuts — these are neutral building blocks. The same base masala becomes chole on Monday, a quick paneer curry on Wednesday and pav bhaji on Friday. Nobody at the table experiences repetition, because the finishing — the tempering, the fresh herbs, the final spicing — happens in ten minutes on the day.

A useful weekend session for a typical household fits in about two hours and produces a predictable set of outputs.

  • One base gravy (onion-tomato masala) that anchors two or three different curries during the week.
  • Two cooked pulses or legumes — say rajma and chana — cooled and refrigerated in meal-sized boxes.
  • Prepped vegetables: chopped for curries, and a tray of washed salad vegetables stored with a paper towel to stay crisp.
  • One batch of grain — rice, millet or poha base — plus dough for rotis if your household eats them daily.
  • Something for breakfasts: idli-dosa batter, overnight-oat jars, or boiled eggs.

Storage is where batch cooking succeeds or fails

Food safety and freshness decide whether the system survives contact with reality. Cool cooked food quickly rather than leaving pots on the counter all afternoon, and refrigerate within two hours. Use shallow containers so contents chill fast, and label anything going to the freezer with a date — frozen mystery boxes are where good intentions go to die. Most cooked dals, gravies and legumes hold well for three days refrigerated; anything meant for later in the week is better frozen on day one than refrigerated hopefully. Rice deserves particular care: refrigerate it promptly and reheat it thoroughly, only once.

Glass or steel containers in a single consistent size make the whole system calmer — they stack, they move from fridge to table, and you can see what exists at a glance. A visible fridge is an underrated anti-waste device: food that can be seen gets eaten.

Making it stick

The habit fails when it is framed as a grand Sunday project requiring the whole afternoon and a spotless kitchen. It survives when it is boring and bounded: same two-hour slot each weekend, a rotating plan of two or three familiar menus rather than new recipes, and music or a podcast to keep company. Families who share the load report the best results — one person chops while another manages the stove, and the session halves in time.

It also helps to plan around your actual week, not an idealised one. If Thursdays always run late, that is the night for the freezer meal, not the assembly job. If weekends sometimes vanish, keep a fallback shelf — a stocked pantry meal like khichdi ingredients — so one missed session does not collapse the system into a week of ordering in.

Batch cooking will not turn anyone into a different person, and it should not try to. Its promise is narrower and more valuable: on an ordinary Tuesday, at the end of an ordinary working day, dinner is twenty minutes away and already half done. Repeated across a year, that small removal of friction changes how the whole week feels.