Batch Cooking 101: Cook Once on Sunday, Eat All Week
Batch cooking has a branding problem: people picture fourteen identical sad containers. Real batch cooking is the opposite — you cook components, not meals, and recombine them all week so Tuesday tastes nothing like Thursday.
The two-hour Sunday block
0:00–0:15 — protein in. A tray of seasoned chicken thighs in the oven, a pot of shredded-chicken braise on the stove. 0:15–0:45 — starches. A big pot of rice, a tray of roasted potatoes. 0:45–1:15 — vegetables and sauce. Roast two trays; blitz one sauce (garlic-yogurt or chipotle crema — a great sauce is the difference between components and cafeteria food). 1:15–2:00 — cool, box, label. Shallow containers, dates on lids.
Five components, five dinners
Chicken + rice + corn + sauce = a street corn chicken bowl Monday and a chipotle burrito bowl Wednesday. The braised chicken becomes pulled chicken tacos Tuesday and a butter chicken wrap Thursday. Friday, whatever remains meets a fried egg and calls itself a rice bowl. Same fridge, zero repeats.
Storage math
Cooked components hold 3–4 days in the fridge (the full chart is in the storage guide), so Sunday cooking covers through Thursday honestly. Anything aimed at Friday goes straight to the freezer on Sunday night, not Thursday as an afterthought.
The hidden payoff is decision fatigue: the 6 PM question shrinks from "what do we cook" to "which three boxes," and that difference is why this system survives when meal plans collapse.
