How to meal plan for two: cooking for a couple without wasting half of everything

Cooking for two sits in an awkward position in the world of food content. The majority of recipes serve four, sometimes six. Cookbooks are rarely written with two people in mind as their primary audience. Meal planning advice almost universally assumes either a solo cook or a family. The couple cooking together, or the person cooking for themselves and a partner, is expected to do the mental arithmetic themselves: halve this, approximate that, guess what to do with the half-used tin.

The practical consequence is that cooking for two produces more food waste per person than cooking for four, not because couples are less careful but because the system isn't designed for them. A tin of coconut milk opened for a curry for two leaves half a tin with an uncertain future. A whole chicken bought for a roast produces leftovers that take four or five days to get through. A bunch of herbs purchased for one recipe goes off before a second recipe uses it up. These aren't failures of attention. They're the predictable results of cooking quantities and packaging sizes calibrated for a larger household.

A meal plan designed specifically for two addresses these problems from the start rather than treating them as inconveniences to manage. It thinks in quantities that work for two people, uses ingredient overlap to close the gap between what gets bought and what actually gets used, and builds a week that produces variety without producing the low-level food waste that comes from constantly being the wrong size household for the recipes you're cooking.

---

The core problem: almost everything is designed for four

Understanding why cooking for two is specifically harder than cooking for other household sizes is useful before building a system for it, because the solutions follow directly from the problems.

The four-serving default exists because recipe development has historically happened in test kitchens where yield matters, and four is the minimum quantity that allows for meaningful testing and easy scaling. It has nothing to do with the actual distribution of household sizes, which skews heavily toward one and two person households in most developed countries. The mismatch between the recipes available and the households using them is structural, and it produces consistent results: over-buying, over-cooking, and food waste concentrated in the gap between what a recipe makes and what two people can actually eat before it goes off.

Protein packaging compounds this. Most supermarket chicken, fish, and meat is packaged in quantities designed for families. A tray of chicken thighs typically contains four to six pieces. A fillet of salmon is often sized for two but surrounded by other identical fillets. Buying the minimum quantity available frequently means buying more than two people can eat at one meal, which is fine when the leftovers have a plan and a problem when they don't.

The answer isn't to find smaller packages, though that helps when available. The answer is to plan the week so that the quantities available in standard packaging are used across multiple meals, rather than buying exactly what one recipe needs and discarding the rest.

---

Planning around the full package, not the single recipe

The most useful shift in meal planning for two is thinking in packages rather than recipes. Instead of deciding to make a chicken curry and then buying the chicken you need for it, you decide to buy a tray of chicken thighs and plan two meals that use them.

This reframe sounds minor but it changes the shopping and planning logic considerably. When the starting point is the package, the week's meals are built to use it fully. Four chicken thighs become Monday's roast and Wednesday's noodle stir fry using the remaining two, shredded cold. The whole tin of coconut milk goes into Monday's curry and Tuesday's soup base. The bunch of coriander gets used across three meals because the planning started from the bunch, not from the individual recipe.

In practice this means the recipe selection process for a couple is slightly different from the process for other household sizes. Rather than choosing four meals that sound good and then working out what to buy, the efficient approach is choosing an anchor ingredient or two first, then selecting recipes that use those anchors in different ways. This produces a week where ingredients serve multiple meals rather than a week where each meal has its own entirely separate shopping list.

A useful exercise when starting this approach is to look at the standard packaging sizes available for the proteins and fresh produce you typically buy, and to make sure the week's meals account for the full quantity of anything perishable. A tray of four chicken thighs needs two chicken recipes in the same week. A bunch of parsley that goes into Monday's pasta should also appear in Wednesday's grain bowl or Thursday's fish dish. Thinking this way before the shopping happens rather than after is what closes the waste gap.

---

Portions and leftovers: the strategic use of both

Cooking for two has a specific advantage that solo cooking doesn't: you can cook a portion sized for three or four and eat the surplus as leftovers without it feeling like a significant sacrifice. A soup made for four feeds two for dinner and provides lunch for two the following day. A tray of roasted vegetables made in a larger quantity than needed for one dinner shows up in grain bowls and pasta later in the week without requiring a separate cooking session.

This makes leftovers a planning category rather than an accident. Planning that Tuesday's lunch comes from Monday's dinner surplus means that the Monday dinner was intentionally cooked in a larger quantity. The shopping reflects this: you're buying 600g of salmon because you're making dinner for two and lunch for two, not because you misjudged the quantity.

The distinction between planned leftovers and accidental leftovers matters more than it might seem. Planned leftovers feel like efficiency. Accidental leftovers feel like something that needs to be dealt with. When the surplus from Monday's cooking is part of the plan for Tuesday, it shows up in the fridge with a purpose rather than as an obligation.

Some foods lend themselves to planned leftovers better than others. Soups, stews, curries, and grain dishes improve with time and reheat well. Roasted vegetables stay good for three to four days and integrate into many different meal formats. Cooked grains can be repurposed in grain bowls, fried rice, and salads. These are the foods worth making in larger quantities for a household of two. Dishes that only work fresh, like a simple salad or a quickly cooked fish fillet, are better made in accurate two-person portions.

---

Scaling recipes without losing quality

The alternative to planning around packaging quantities is scaling recipes down to two servings, which is sometimes the right approach and sometimes produces results that don't match the original dish.

Most savoury recipes scale down reasonably well to two servings. A stew, a curry, a pasta sauce, a stir fry: halving the ingredients for a four-serving recipe produces approximately two generous servings with few complications. The main adjustments needed are in seasoning, which should be added conservatively and tasted rather than halved precisely, and in cooking time, which may shorten slightly for smaller quantities but less than proportionally.

Baking is where scaling to two becomes genuinely complicated. A cake recipe halved doesn't behave identically to the original, because baking chemistry is sensitive to quantity in ways that savoury cooking isn't. For baked goods, the more reliable approach is to use recipes specifically designed for small batches, or to make the full recipe and share or freeze the surplus, rather than trying to scale a standard recipe to two servings and expecting identical results.

For couples with different dietary preferences or restrictions, the component-based approach to meal planning is particularly useful. Planning meals that are partly shared and partly adaptable, rather than identical plates, reduces the complexity of catering to different needs without requiring entirely separate cooking. A grain bowl with shared grains and vegetables but different proteins is one cooking session that produces two genuinely different meals.

---

A concrete week for two

A week planned specifically for two people, built around the principles above, might look like this.

The anchor ingredients chosen before the week are: one tray of four chicken thighs, one tin of coconut milk, one bunch of coriander, one bag of spinach, and one quantity of tinned chickpeas. These are bought in standard available quantities. The week is built to use all of them.

Monday is a chicken and coconut milk curry with rice and coriander stirred through at the end. Two chicken thighs are cooked, along with a larger quantity of rice that will be used later in the week. The coconut milk tin is opened; half is used in the curry, half reserved.

Tuesday's lunch is leftover curry from Monday. The surplus rice is a practical foundation.

Wednesday is a chickpea soup using the remaining coconut milk as the liquid base, with spinach wilted in at the end and coriander as a garnish. The chickpeas provide protein without requiring additional protein shopping.

Thursday is the remaining two chicken thighs, shredded and used in a simple noodle bowl with the spinach remaining from the bag. The leftover rice from Monday provides the base.

Friday is flexible, either leftover soup from Wednesday or something fresh from the pantry.

The week used all four chicken thighs, the full tin of coconut milk, most of the coriander, and most of the spinach. The shopping for this week was a single targeted list rather than four separate recipe lists, and the end-of-week fridge contains far less unused produce than a week planned recipe by recipe for two people.

---

The shopping list as the connective tissue

The planning described above only works if the shopping list accurately reflects the week's combined requirements. For a couple, this is particularly important because the quantities involved are small enough that small errors, buying one extra courgette, forgetting that coriander is appearing in three recipes, not realising the spinach for Wednesday is the same spinach planned for Thursday, have an outsized effect on waste.

A shopping list for two built from all the week's recipes simultaneously, with quantities combined across all meals, is the practical tool that makes this approach work. It shows at a glance that the chicken being bought needs to cover two recipes, that the coriander appears three times and one bunch is enough, and that the spinach for Wednesday's soup and Thursday's noodle bowl can be bought as a single bag.

When your recipes are stored in one place with consistent ingredient names and complete ingredient lists, building this kind of combined list becomes a quick task rather than a mental exercise. Zavora is built around that workflow: recipes organized so you can plan a week for two and generate the shopping list that reflects it accurately, rather than approximating from four-person recipes and hoping for the best.

---

Related: Cooking for one: recipes and planning that actually work · How to reuse ingredients across multiple recipes · How to build a weekly meal plan with a shopping list · How to reduce food waste with smarter recipe planning