Cook Once, Eat All Week

The Cook-Once Mindset

It's 6:42 on a Tuesday evening. You've just walked in the door, or hung up the last work call, or finally got the smaller human to stop crying about a sock. You open the fridge. You look at the cold light and the half-bag of spinach going limp in the drawer, and a small, tired voice in your head asks the worst question of the day: what's for dinner?

I want to start this whole book right there, in front of that open fridge, because that is the moment we are going to fix. Not your cooking — your cooking is probably fine. The moment. That specific, daily, soul-flattening moment where you have to decide what to eat, find the will to begin, and somehow produce a meal out of nothing while running on empty. That moment is the real problem. And it is a much more solvable problem than you've been led to believe.

So before we talk about a single recipe, let's talk about how to think about all of this. Because the people who batch-cook happily for years — and stick with it long after the New Year's resolution energy wears off — aren't more disciplined than you. They're not better cooks. They've just quietly rearranged when the hard part happens.

The real enemy isn't cooking. It's deciding and starting.

Here's something worth sitting with: most of us don't actually mind cooking. Chopping an onion is fine. Stirring a pot is fine, even pleasant, on a good day. What we mind is being asked to invent, decide, and launch the whole operation from a standing start when we are at our most depleted.

Think about your own week honestly. The cooking itself — the twenty or thirty minutes of hands-on work — is rarely the thing that breaks you. What breaks you is the cascade of small decisions stacked in front of it. What do we even have? What goes with what? Do we have enough? Is the chicken still good? Can I be bothered to defrost something? Why is there no plan? By the time you've answered all that, you've spent your last drop of energy before you've turned on a single burner. So you order in. Again. Not because you're lazy — because you're out of decisions for the day.

Researchers have a friendly name for this feeling, and you already know it in your bones: decision fatigue. You only get so many good choices in a day, and "what's for dinner" arrives at the exact moment your tank is empty. That's not a character flaw. That's just bad scheduling.

So the whole trick of this book — the entire premise — is this: move the hard part to one chosen moment. Make the decisions once, when you have a bit of energy and headspace, instead of seven times when you don't. You're not adding cooking to your life. You're relocating it, away from the worst possible time and into a window you actually choose. The Tuesday-night version of you doesn't have to decide anything. She just has to assemble what the Sunday version of you already set up. And she will quietly thank you for it.

Meet the Cook-Once Loop

That relocation has a shape, and I want to name it now because we'll come back to it in every single chapter. I call it The Cook-Once Loop, and it has five steps:

Plan · Shop · Batch · Stash · Remix.

Plan — you decide, in one short sitting, the handful of flexible building blocks you'll make this week. Shop — you buy for all of them in one pass, one trip or one order, no daily top-ups. Batch — you cook those building blocks in a single relaxed session, with the radio on and nobody asking for dinner yet. Stash — you store everything safely and smartly so it's ready and so nothing dies in the back of the fridge. Remix — across the week, you combine and finish those building blocks into different meals, fast, with almost no decisions left to make.

Please notice the word Loop. This is not a heroic Sunday where you sweat for six hours, fill every container you own, and collapse. That's the version that burns people out by February. A loop is a gentle, repeatable cycle — something you spin up again next week, a little smoother each time, until it stops feeling like a project and starts feeling like just how you eat. Some weeks the loop is big. Some weeks it's tiny — two things and a shrug. Both count. The goal is a rhythm you can keep, not a performance you have to psych yourself up for.

You'll get a whole chapter on each part of the loop. For now, just hold the shape in your head: five steps, one cycle, round and round.

The engine: Base & Remix

Inside the loop is the idea that makes the whole thing actually work, the one that separates this from the sad, grey meal-prep you may have tried and quit. I call it Base & Remix.

A base is a flexible, lightly seasoned building block. A pot of plain shredded chicken. A tray of roasted vegetables. A batch of grains. A simple tomato sauce. A pot of beans. Crucially, a base is deliberately under-seasoned and unfinished. It's not a meal. It's a meal's most useful ancestor. It leans neutral on purpose so it can go in many directions.

A remix is what you do at the last minute, when you're hungry: you take a base or two and finish it into an actual dinner with fast, fresh touches. The same shredded chicken becomes a taco on Monday, a noodle bowl on Wednesday, and a quick soup on Friday — because you change the finish, not the base. A squeeze of lime and some warm tortillas. A splash of soy and sesame over rice. A ladle of broth and a handful of greens. Five minutes of finishing turns one humble base into three meals that don't taste remotely alike.

This is the cure for the thing everyone fears about batch cooking — the boredom, the "same sad container of chicken and broccoli for the fifth day in a row." You never eat the identical plate twice, because you never finish a base the same way twice. The repetition lives in your prep, where repetition is a gift. The variety lives on your plate, where variety is the whole point. Every recipe chapter in this book is organised this way: bases that earn their place by remixing at least three different directions, so nothing you cook is a dead end.

Let's bust four myths, because they're keeping good people from a good thing

When I tell someone "I batch-cook," I can usually guess which objection is coming. There are four, and all four are wrong.

Myth one: batch cooking means bland, sad food. This one I understand, because the rigid version of meal prep genuinely is bland — five identical sealed boxes of the same beige dinner, eaten with diminishing joy until you'd rather chew the lid. But that's not what we're doing. Base & Remix is the opposite: the base is plain so the finish can be bright. You're not eating bland food; you're eating a different vivid meal each night, built fast on a calm foundation. Blandness isn't a feature of batch cooking. It's a feature of bad batch cooking, and we're skipping that.

Myth two: you need expensive gadgets. You do not. I'll be honest with you throughout: a big pot, a sheet pan, a sharp knife, a cutting board, and somewhere to store food will carry you through almost this entire book. If you own a slow cooker or a pressure cooker or a fancy multi-thing and you love it, wonderful, use it — but you will never need it here. Anyone telling you that you must buy a three-hundred-dollar machine to feed yourself is selling a machine, not a meal.

Myth three: it eats your whole day off. This is the big one, and it's the myth that makes people not even start. Here's the truth: a real cook-once session, once you've done it a couple of times, is closer to two hours than to a lost Sunday — and much of that is hands-off time while things roast and simmer and you sit down with a cup of tea. Two hours once, against the daily drip of decide-shop-cook-clean-repeat, is not more work. It is dramatically less work, just gathered into one place where you can see it.

Myth four: it's joyless and samey. We've half-answered this with Remix, but let me say it plainly. Done right, the cook-once habit gives you more joy, not less, because it gives you back the thing you actually crave on a weeknight: the feeling of having a choice, without the burden of making one from scratch. Opening a fridge full of ready building blocks and thinking "ooh, I could do the noodle thing tonight" is a genuinely nice feeling. It's the difference between a blank page and a box of paints.

Start small. Good enough beats perfect.

Now, the most important practical thing I'll say in this chapter, and I need you to actually believe me: start small.

Do not, this week, attempt a twelve-dish marathon. Do not fill your trolley with fourteen ingredients and a dream. The graveyard of batch cooking is full of ambitious first Sundays that were so exhausting nobody ever did a second one. That's the trap. Heroic effort, then collapse, then "I guess that's not for me."

Start with two or three bases. That's it. One protein, one vegetable, maybe one grain. Cook those, stash those, remix those. See how it feels. Notice how many dinners you just bought yourself. Then, next week, if you want, add a fourth. The loop gets easier and bigger on its own, at the pace your life allows, but only if you let the first round be small enough to survive.

And hold tight to this little motto, because we'll repeat it often: good enough beats perfect. A slightly over-roasted tray of vegetables that actually gets eaten is infinitely better than the flawless meal plan you were too intimidated to begin. Done and a bit wonky wins. Perfect-in-your-head loses every time.

Leftovers aren't an afterthought. They're the plan.

One more reframe, and it's a good one. Most of us treat leftovers as a kind of accident — sad, slightly shameful evidence that we made too much, shoved to the back of the fridge to be guiltily thrown out on bin day. I want to flip that completely.

In the cook-once world, there are no leftovers. There are planned-overs. You made extra on purpose, because extra is the entire point. That tub of chicken isn't last night's remains — it's Thursday's dinner, already half-built, waiting for its remix. When you cook a base, you are deliberately making future meals and parking them. The "extra" was never a mistake. It was an asset you designed in from the start. Once you see your fridge this way — as a bank of building blocks rather than a museum of regrets — the whole thing clicks.

One Sunday, two pots: a small, ordinary miracle

Let me leave you with a little story. It's made up — a stand-in for a hundred real evenings, yours possibly among them — but I think you'll recognise her.

Picture Priya. She works long days, comes home wrung out, and orders takeaway maybe three nights a week. Not because she can't cook — she cooks beautifully on holidays — but because at 7 p.m. on a Tuesday the decision is simply beyond her. The ordering isn't a treat anymore. It's a small white flag she runs up every night, and it's quietly bothering her: the cost, the waste, the feeling of feeding herself worse than she knows she could.

One Sunday, almost as an experiment, she tries the smallest possible version of this. Two bases. She puts a pot of chicken on to simmer until it shreds, and she tips a tray of chopped vegetables into the oven to roast. That's the whole ambition. Maybe ninety minutes, most of it spent reading on the sofa while the oven does the work.

And here's the moment I love. Standing in her kitchen afterwards, looking at one tub of chicken and one tub of roasted veg, Priya realises something that genuinely startles her: she hasn't just made food. She's made decisions. Monday's dinner is decided. So is Tuesday's, and Wednesday's, and Thursday's — four nights, each one different, each one already mostly built. She didn't cook four meals. She cooked two bases and disarmed four landmines. The dread that used to detonate at 6:42 every evening just... didn't go off. That's the shift. Not from "can't cook" to "can cook." From nightly dread to weekly calm.

Your turn

So here's what I'd like you to do before we go any further — and it takes about five minutes, no cooking required.

First, write down your weeknight default. Not your aspirational dinner — the real one. What actually happens on the nights you're too tired? Takeaway? Cereal standing at the counter? Toast and a vague sense of failure? No judgement here at all; we just need the honest baseline, because you can't redesign a habit you won't look at.

Then, circle the single hardest moment of your day to cook. Is it the walking-in-the-door slump? The witching hour with the kids? The 9 p.m. shift-work hunger when everything's shut? Find the exact pressure point. That's the moment we're building the whole system to protect.

And finally, your one real takeaway from this chapter — the thing that turns reading into doing: find a two-hour window this week, and pick it now. Not "sometime." A specific day, a specific slot. In that window, you're going to try one small cook-once session with just two bases. That's the entire assignment. The next chapter will show you exactly how to plan and shop for it without over-buying or building some rigid day-by-day timetable. You don't need to know the recipes yet. You just need to block the window and trust that future-you will be very, very glad you did.

A quick, honest word before we cook, and you'll hear me say versions of this throughout the book: everything here is general, evergreen cooking guidance — the friendly kind, not the official kind. When it comes to the specifics of food safety — how cold, how hot, how long things keep — I'll always point you to your own national or local food-safety authority and to the instructions that came with your appliances and ingredients, because those numbers vary by country and kitchen and they change over time. I make no health or nutrition claims, and if you've got allergies, a medical condition, a pregnancy, or any particular dietary need, please check with a qualified doctor or registered dietitian and the current official guidance for your situation. With that said: pick your window. Let's begin the loop.

Plan the Week, Shop Once

Picture the most chaotic version of grocery shopping you know. It's Tuesday. You're standing in the bright aisle holding a basket with a single bell pepper and a vague sense of dread, because you can't remember what you bought on Sunday, you don't know what's for dinner tonight, and you're fairly sure there's a half bag of spinach turning to soup in the crisper at home. You buy the pepper anyway. You buy a few other things you might use. You'll be back on Thursday, and probably Saturday, because no single trip ever quite covers the week.

That loop — shop, forget, wing it, shop again — is exhausting, and it's expensive, and it's the thing we're going to dismantle in this chapter. By the end of it you'll be able to look at your actual upcoming week, choose a small handful of bases that work together, and turn them into one tidy shopping list sorted the way the store is actually laid out. One plan. One trip. A week that holds together even when the week, as weeks do, refuses to cooperate.

Here's the reassuring part before we start: this is not about becoming the kind of person who has color-coded dinners assigned to each night of the week. That version of planning is fragile — one late meeting or one cranky toddler and the whole chart falls apart, and you're back to the bell pepper. We're going to plan in a way that bends instead of breaks. Let's build it.

Start with the week you actually have

Most meal planning goes wrong because it starts in the wrong place. People open a cookbook, get inspired by seven gorgeous recipes, write them onto seven days, and then collide with reality somewhere around Wednesday. The trick is to plan backwards from your week — to look hard at the real shape of the next seven days before you let a single recipe into your head.

So, before you think about food at all, ask yourself three plain questions.

First: how many nights will I actually be home and cooking? Not how many nights there are — how many you'll truly be at the stove. Be honest, even pessimistic. If Thursday is always a write-off because someone has a class and you get home late, Thursday is not a cooking night. If Friday tends to dissolve into takeaway no matter your good intentions, let it. A plan built for the cook you actually are beats a plan built for the cook you wish you were.

Second: who's eating, and how many of them? Two adults all week is a very different shop from two adults plus two kids on weekdays and a friend on Sunday. Note the bodies at the table. You're sizing your batches to feed real mouths, with maybe a little cushion.

Third: where do lunches need to travel? This is the question almost everyone forgets, and it's the one that quietly causes the most waste. If you or your partner or your kids need lunches that go out the door — to a desk, a job site, a school bag — those meals need to exist too, and they need to survive a few hours in a bag. A week's worth of dinners with no thought for lunch is a week where you'll still be buying sad sandwiches at noon.

Write the answers down. Three lines is enough. Nights home: four. Eating: two adults, plus the kids three of those nights. Lunches to pack: two of us, most weekdays. That's it — that's the skeleton your whole plan hangs on, and it took thirty seconds.

Choose a Base Menu, not seven dinners

Now the part that changes everything. Instead of planning seven separate meals, you're going to plan three to five bases — and let them do the work of feeding you all week through remixing.

This is the heart of the Cook-Once Loop, and it's worth slowing down for. A base, remember, is a flexible, lightly-seasoned building block: a pot of grains, a tray of roasted vegetables, a batch of cooked protein, a good sauce, a soup. On its own a base is not dinner. Combined with one or two others and a quick finishing touch, it becomes dinner — and a different dinner each time you recombine. That's the magic. You are not cooking seven things. You are cooking four or five things that rearrange into far more than seven meals.

So you choose a small Base Menu for the week, and you choose it with one rule front of mind: the bases should share ingredients and remix widely. This is the difference between a smart plan and a cluttered one. If your protein, your grain, your veg tray, and your sauce all pull from an overlapping pool of ingredients, your shopping list shrinks, your fridge stays coherent, and nothing strands you with a lone specialty item you'll use once and forget.

A solid starter Base Menu is almost boringly simple, and that's the point:

• A grain or starchy base — a big pot of something neutral that reheats well.
• A protein base — cooked plainly enough to go in several directions. (Plant-based eaters, your protein base might be a pot of beans or lentils, or a tray of seasoned tofu — the principle is identical.)
• A tray of roasted vegetables — whatever's good and abundant right now.
• A sauce or two — because the sauce is what makes Monday taste different from Wednesday. A bright sauce and a rich sauce will carry you a long way.

Four bases. From those four you can build a grain bowl, a wrap, a tray of something baked, a quick stir-together, a soup with the grain stirred in, a packed lunch that's just last night reassembled cold. Each remix feels like a real meal because the finishing — fresh herbs, a squeeze of citrus, a handful of cheese or toasted seeds, a different sauce — changes the character entirely, even though the bones are the same.

Notice what you did not do: you didn't decide that Tuesday is bowl night and Thursday is wrap night. You chose ingredients, not appointments. Which brings us to the rule that keeps the whole thing from collapsing.

Anchor roles, not fixed days

Here's where planning usually turns rigid and then snaps. The moment you write "Wednesday: chicken and rice" you've made a promise to a future version of yourself who may be stuck in traffic, or out of energy, or suddenly hosting a friend. Break the promise once and the guilt creeps in; break it twice and you've abandoned the plan entirely.

So don't make day-by-day promises. Give your bases anchor roles instead.

Think of each base as having a job, not a date. The grain is your "fills it out" anchor. The protein is your "makes it a meal" anchor. The veg tray is your "freshness and bulk" anchor. The sauce is your "makes it taste like something" anchor. On any given night you reach for the anchors you feel like and assemble. Home early with energy? Build something a little composed. Home late and flattened? Grain, protein, sauce, done, eaten standing up if need be. Plans change; anchors don't care. The week flexes around your life instead of demanding your life flex around it.

This is what flexible-not-fragile means in practice. A rigid plan has a single point of failure — miss one night and the dominoes fall. An anchor-based plan has no single failure point, because nothing was ever pinned to a specific evening. A blown Tuesday just means those bases get eaten Wednesday instead. Nothing is wasted; nothing is wrong.

Shop your kitchen before you shop the store

You're almost ready to write a list — but not quite, because the cheapest, fastest groceries are the ones you already own. Before you add a single item, shop your kitchen first.

Take five minutes and actually look. Open the fridge and note what's in there, especially anything teetering on the edge — that half bag of spinach, the yogurt with a few days left, the lonely peppers. Open the freezer and see what past-you stashed: there may be a protein base or a portion of soup already waiting, which could knock a whole item off your plan. Open the cupboards and check your pantry staples — the oil, the grains, the tins, the spices — so you don't come home with your fourth jar of cumin and no rice.

This inventory does two jobs at once. It stops you double-buying things you already have, and it lets you rescue food that's about to turn — by building this week's plan partly around it. That wilting spinach isn't a failure waiting to happen; it's the green in this week's grain bowls, claimed on purpose. Shopping your kitchen first is the single habit that does the most to cut both your bill and your bin.

Build the list by section

Now, the list. And the way you write it matters more than you'd think, because a list written in the order ideas occur to you — pasta, then apples, then milk, then more pasta — sends you crisscrossing the store three times and tempting yourself past every end-cap on the way.

Instead, build the list by section, grouped the way the store is laid out:

• Produce — the vegetables and fruit, including whatever you're rescuing and building around.
• Proteins — the meat, fish, eggs, tofu, or the beans and lentils if they live elsewhere in your store.
• Pantry — grains, tins, oils, the dry and shelf-stable things.
• Freezer — anything frozen you're topping up.
• Dairy and alternatives — milk, yogurt, cheese, and their plant-based stand-ins.

Walk your bases through each section and jot what they need as you go. The grain base lands in pantry. The protein in proteins. The veg tray in produce. The sauces scatter across produce, pantry, and dairy. Because your bases share ingredients, you'll find the same item serving two or three of them — one bunch of herbs finishing several meals, one onion feeding the lot — and you simply note it once. A section-sorted list turns shopping into a single clean sweep through the store, no backtracking, far less impulse-buying.

Keep one more thing alongside it: a running staples list. This is a little permanent note — on the fridge, in your phone, wherever you'll see it — where you jot a staple the moment it runs low, not when it's already gone. Oil's getting down? Add it. Last tin of tomatoes used? Add it. Then each week your list half-writes itself, and you stop discovering mid-recipe that the thing you needed ran out days ago.

A word on budget — in general terms

You don't need me to quote you prices to shop more cheaply, and I won't, because prices differ everywhere and change constantly. But the structure you've just built is already a budget structure, almost by accident.

Choosing bases that share ingredients means buying versatile staples that pull their weight across many meals rather than single-use oddments that sit in the cupboard reproaching you. Building around what's in season and abundant — letting the produce that's plentiful and well-priced this week steer your veg tray — costs less and usually tastes better. And scaling your batch size to your storage keeps you honest: cook only as much as you can actually stash and eat before it turns, because food cooked and then thrown out is the most expensive food there is. Bigger isn't automatically thriftier. The right-sized batch is.

Sam and Devi stop winging it

Let me show you the whole thing in motion with a hypothetical couple — entirely made up, but the shape will feel familiar.

Sam and Devi used to wing it completely. No plan, no list, just whoever-got-home-first standing in front of the fridge at seven o'clock. They shopped four times most weeks — a "big" trip that somehow missed half of dinner, then three top-up dashes for the things it missed, each one a small detour past the snacks. They spent more than they meant to, threw out more than they'd admit, and still ended a lot of evenings ordering in.

One Sunday they tried planning backwards. Four nights home, they reckoned, being honest about Devi's late Thursday. Two of them, plus Sam's brother on the weekend. Lunches to pack for both, most days. Then a Base Menu: one big pot of a grain, one protein cooked plain, one tray of roasted veg, and two sauces — one bright, one rich. They shopped the kitchen first and found a tub of beans in the freezer and a bag of greens to rescue, which they folded straight into the plan.

The list, written by section, was startlingly short — because the same handful of vegetables, the same herbs, the same staples kept showing up across all four bases. One trip covered it. The trolley was lighter and so was the receipt. And across the week those four bases became grain bowls, stuffed wraps for the packed lunches, a quick baked tray on the busy night, and a soup on Friday when neither of them could face anything fancy. They never ate the same plate twice, and they didn't go back to the store once. The week, for the first time in ages, felt calm.

Nothing about Sam and Devi is special. They just stopped planning meals and started planning bases.

Your turn: the fifteen-minute plan

Here's your exercise, and it's a real one — do it before you read on if you can.

Take one page. At the top, write your week's skeleton: nights you'll truly be home, how many people are eating, which lunches need to travel. Three lines.

Underneath, choose three bases to start — don't overreach; three is plenty for your first loop. Pick ones that share ingredients. Jot the anchor role each one plays.

Then, shop your kitchen — a quick look in fridge, freezer, and cupboards — and note anything to use up or top up.

Finally, draft your shopping list sorted by section: produce, proteins, pantry, freezer, dairy and alternatives. Walk your three bases through each section and write down what they need, claiming any rescued ingredients as you go.

And here is the takeaway I most want you to keep: aim to do the whole thing — plan and list — in under fifteen minutes. Set a timer if it helps. The goal is not a perfect, beautiful, optimized plan. The goal is a good-enough plan you'll actually use, written fast enough that you'll be willing to do it again next week, and the week after, until it's just a thing you do on a Sunday without thinking about it. Speed beats perfection here, every single time. A rough plan you repeat will transform your weeks; a flawless plan you only make once will not.

You've got the shape of your week and a list that covers it in one pass. Next, we'll get your kitchen ready to turn that list into food — the small, sane bit of kit you actually need, and the safe-handling habits that let you cook ahead and store with real confidence.