A week of dinners can be planned on a single sheet of paper, and the sheet does not need to be clever. The template that survives real kitchens is almost embarrassingly plain: seven slots, four of them assigned to a rotating cast of familiar meals, three left open for whatever the week throws at it. It works because it is boring enough to repeat and loose enough to bend.
Most meal plans fail in the same place. They are built for the cook someone wishes they were, the one with time to braise on a Tuesday and a pantry stocked like a restaurant walk-in. The template below assumes the opposite: a cook who is tired by six o'clock, a fridge with odds and ends in it, and a standing preference for food that tastes like something without requiring a shopping list of twenty ingredients.
The four fixed slots and why they repeat
The template assigns four dinners to categories rather than recipes. One night is a starch with a protein and a green thing. One night is a pot of something that yields leftovers. One night is a fast pan dish, cooked in under half an hour. One night is assembly: bread, cheese, whatever vegetables are in the drawer, a fried egg if the mood calls for it. The categories repeat weekly. The specific dishes inside them rotate, but only slowly, maybe one swap a month.
The repetition is the point, and it is also the part people resist. A cook who makes the same roast chicken on the same night for six weeks will hear complaints around week three, then something quieter and more useful happens: the complaints stop, the cooking gets faster, and the chicken gets better. By week five the cook knows exactly how the oven behaves, how much salt the bird needs, how long the pan takes to come to temperature. Skill accumulates inside repetition. A new recipe every night builds nothing but fatigue.
There is a second benefit that shows up in the shopping. Four fixed categories produce a grocery list that barely changes. The same vegetables get bought in roughly the same quantities, which means less waste at the end of the week, fewer half-used bunches of parsley turning to slime in the crisper drawer. The open slots absorb the variation instead.
What belongs in the three open slots
The three remaining nights are not blank in the sense of undecided. They are blank in the sense of unassigned, and the difference matters. Each one gets a label by Sunday night, even if the label is provisional. One slot is for whatever produced a glut: a pot of beans that needs finishing, a bag of spinach going soft, the second half of a cabbage. One slot is for something new, a single recipe pulled from a book or a website, tried once and judged. One slot is for the week's wild card, usually a night when energy is lowest and the correct answer is eggs on toast or a bowl of cereal eaten standing up.
The new-recipe slot deserves a rule: one per week, no more. Two new recipes in the same week is how a person ends up at the takeout counter on Thursday, defeated by two half-learned techniques and a sink full of pans. A single new dish, cooked once, costs an hour of attention and teaches something. The rest of the week runs on muscle memory and leaves room for it.
The glut slot has a quieter function. It is where the template pays for itself, converting leftovers and near-dead vegetables into a meal that feels deliberate. A pot of white beans made on Monday becomes beans on toast with garlic and olive oil on Thursday, and the transformation reads as generosity rather than thrift.
The pantry that makes the template work
A repeating template only functions if the staples underneath it never run out. The list is short and unglamorous: olive oil, a neutral oil, salt, pepper, garlic, onions, canned tomatoes, dried pasta, rice, a couple of tins of beans, stock cubes, soy sauce, vinegar, mustard, flour, eggs, butter. If those are present, every category on the template can be filled without a trip to the store.
The restock habit matters more than the list. A five-minute check on Sunday, before the week begins, catches the empty bean shelf and the garlic down to its last wrinkled clove. The check is dull and it saves the entire plan. A template with a hole in the pantry is a template that collapses on Wednesday.
There is a version of this advice that turns the pantry into a project, with decanted jars and labeled containers and a spreadsheet. That version is a hobby. The working version is a shelf, a pen, and a grocery list that gets written before the store, not during it.
How the template bends without breaking
Two adjustments do most of the work of making the template fit a real household. The first is portioning for the pot night. Whatever gets cooked on the pot night should be made in a quantity that leaves a full second meal, because that second meal is not a failure of planning, it is the plan. The pot night and the glut night are the same engine running twice.
The second adjustment is a swap rule: any fixed night can trade places with any open night, but the count stays the same. Four fixed, three open. When Tuesday's pan dish becomes Thursday's and the new recipe slides into Tuesday, nothing is lost. The structure holds because it is a shape, not a schedule.
What breaks the template is subtraction without replacement. Skip the pot night two weeks running and the glut night has nothing to draw from. Skip the new-recipe slot for a month and the cooking goes flat, all maintenance and no curiosity. The template tolerates a missed week. It does not tolerate a missed month, because the habits it depends on decay faster than most people expect.
A sample week written out in full
Monday, pot night: a large pot of lentil soup with canned tomatoes, onion, carrot, and a bay leaf, cooked in enough volume to fill four containers. Tuesday, pan night: sliced chicken thighs seared hard in a cast iron pan, finished with lemon and whatever green vegetable is closest to the front of the fridge. Wednesday, assembly night: bread, a wedge of cheese, sliced radishes, a boiled egg, olive oil. Thursday, glut night: the second half of the lentil soup, reheated with a spoonful of yogurt stirred in and a piece of toast alongside.
Friday, starch night: rice, a protein, a green thing, in this case a piece of salmon and a pile of broccoli roasted at high heat until the edges char. Saturday, new recipe: a single dish from a cookbook, tried once, with the leftovers going into Sunday's lunch. Sunday, wild card: eggs on toast, eaten early, because the week starts again in the morning and the pantry check is due.
Seven nights, four categories, three open slots, one shared shopping list. Nothing about the week is impressive. The lentil soup is the kind of thing anyone can make. The salmon needs salt and a hot oven and nothing else. That is the whole argument for the template, laid out in a row.
The week the template gets abandoned
Every household eventually hits a week when the template cannot be followed: a late meeting on pot night, a child with a stomach bug, a fridge that failed and took the week's groceries with it. The instinct in that week is to declare the whole system dead and order out until Monday. The better move is narrower. Fill one slot, any slot, with the cheapest possible version of itself. A can of soup counts as pot night. A bag of frozen dumplings counts as pan night. The template's job that week is to keep the shape alive, not to produce a good dinner.
Then comes the test that separates a template that lasts from one that gets abandoned in a drawer. On the following Sunday, the template gets written out again, unchanged. No new resolve, no upgraded version with more ambition and a color-coded spreadsheet. The same seven slots, the same four categories, the same pantry check. The households that keep a repeating meal template are not the ones with the most discipline. They are the ones who, after a bad week, sit down with the same plain sheet of paper and fill in Monday.