Leftovers, takeaway and nights out: plan the whole week

The week you actually have

A plan that pretends every night is a cooking night gets abandoned by Wednesday. Seven dinners go in on Sunday, then Tuesday runs late, Thursday is someone's birthday, and by Friday the plan describes a week that did not happen. Once that is true, the shopping list built from it is wrong too, and the whole thing stops being worth opening.

A realistic weekly meal plan is not a plan with fewer meals in it. It is a plan that records the nights you will not cook as deliberately as the nights you will. Takeaway on Wednesday is a decision. Monday's chilli eaten again on Tuesday is a decision — and a good one, because it is a meal you get for the cost of cooking a bit more once. Written down, both are planned nights. Left blank, they are holes that make the plan look wrong and the list buy food for meals nobody is cooking.

Our Table Tonight has two kinds of entry for this, sitting in the planner alongside recipes: an eat-out entry and a leftovers entry. It is a free beta. Here is how to use them, and what each one changes about the rest of the week.

Step one: decide the non-cooking nights first

Before you pick a single recipe, go through the seven days and mark the ones that are already spoken for. Late meeting, football, a night out, dinner at someone else's house, the night after the roast when there is obviously going to be food left. Do it first, not last: if you fill the recipes in first, you will fit them to a week that has more capacity than the real one, and then the nights out arrive as disruptions rather than as part of the plan.

Most households find this leaves four or five cooking nights, not seven. That is the number to plan around.

Step two: put the night in the slot

Open the day and meal you are filling. As well as choosing a recipe, the slot offers an eat out and a leftovers option, and the difference between them is what the app can know about the food.

Eating out or ordering in

An eat-out entry is a single free-text line: where you are eating. “Pizza place”, “the Thai by the station”, “Mum's”, “curry after football”. There is no recipe behind it and no ingredients, which is exactly the point. The slot shows on the grid with a fork-and-knife marker so it reads as a different kind of night at a glance, and it counts as a filled slot in the week's progress — “18 of 25 slots filled” means eighteen decisions made, not eighteen dinners cooked.

Leftovers

A leftovers entry points at the recipe the leftovers came from, and you set how many servings you expect to get out of it. Marked that way, the night carries a leftovers badge on the grid and stays linked to the dish, so the plan says “Tuesday: the chilli again” rather than “Tuesday: something”. A month later, when you are trying to work out which recipes actually stretch to two nights, that link is the whole record.

Either way the slot is filled, and a filled slot is what stops the week looking like a failure. A planner with three empty rows reads as three unsolved problems. The same week with those rows marked out reads as done.

Step three: cook double on purpose

A leftovers night only works if there are leftovers, and that is a shopping decision made two days earlier. The step people miss is raising the servings on the night they cook, not on the night they eat again.

1. Assign the recipe to the cooking night — Monday's chilli, say — and set the servings on that slot to what you actually want to make: eight rather than four.
2. Assign Tuesday as leftovers of the same recipe, with the servings you expect to eat.
3. Generate the shopping list for the range. It scales Monday's ingredients to eight servings and buys for them; Tuesday adds nothing, because that food is already in Monday's line.

The quick way to set this up is the copy button on the filled slot. It offers the other days in the same week — copying is within the current week only — and a toggle to mark the copies as leftovers. Pick Tuesday, tick the toggle, done. The copy can land on a different meal from the one it came from, so Sunday's dinner becoming Monday's lunch is one action: the roast at midday on Monday, marked as leftovers, no extra shopping.

What these nights do not do

Both kinds of entry are deliberately left out of parts of the app, and it is worth knowing which.

• Neither reaches the shopping list. Eat-out nights have no ingredients; leftovers nights were bought for when you cooked the dish. Generation skips both, which is what keeps a week with three non-cooking nights from producing a list for seven dinners.
• An eat-out night gets no allergen check. The check that runs when you assign a recipe compares its ingredients and allergens against the dietary profiles of everyone in the household. A restaurant name has no ingredients, so there is nothing to compare and no warning will ever appear on that slot.
• An eat-out night records no cook history. Nothing was cooked, so nothing is added to the record of what you make. A leftovers night is linked to a real recipe, so marking it made does count towards that recipe's history.

The allergen one matters most if someone in the house has an allergy. The absence of a warning on an eat-out slot is not a statement that the meal is safe — it is the app saying it has no idea, because you have told it a place rather than a dish. Eating out is the moment the checking goes back to being yours: ring ahead, ask at the table, and read the menu with the person's allergens in front of you. The profiles you have recorded in the app are a useful thing to have on your phone for that conversation, even though nothing automatic is happening.

Step four: mark the week at the end of it

When the week is over — or when you navigate into the next one with slots still open — mark the meals. Every slot, including the eat-out ones, gets Made or Didn't Make, and they all submit together. Eat-out slots take no star rating; there is nothing in your recipe library to rate.

Marking a takeaway night Made feels pointless for about two weeks, and then it is the most useful thing in the plan. What accumulates is an honest count of how many nights you really cook. If you plan five and mark three, you are planning for a week you do not have — plan four next time and put a leftovers night where the fifth was. If Wednesday is eat-out three weeks running, stop assigning a recipe to Wednesday.

That is the loop. The nights out and the leftovers are not gaps in the plan; they are the part of it that makes the rest survive contact with the week.