How Many Meals Should Be in a Dinner Rotation? (And How to Build One)

How many meals should be in a dinner rotation? For most households, somewhere between 10 and 20 dinners you already know everyone will eat is enough to plan a fortnight without anyone noticing the repeats. Fewer than that and boredom creeps in. Many more and you're back to scrolling for ideas, which is the thing a rotation is meant to stop.

It's a question that keeps coming up. In one r/workingmoms thread, someone with 13 recipes in rotation says their family is getting bored of them, and the replies range from seven to well over forty. In r/foodquestions, a person cycling about five meals says even their favourites have started to feel meh. And in r/Mommit, parents swap the rotations they use to cut down the mental load of dinner.

I've spent a lot of time thinking about this while building Foodedo, because a rotation is really just a way of deciding dinner less often. Here's how I'd size one, build one, and keep it from going stale.

What a dinner rotation actually is

A dinner rotation is a fixed list of meals your household likes, which you cycle through instead of inventing dinner from scratch each week. Some people run the same seven dinners every week. Others run a two-week or four-week cycle. Some use themes, such as pasta on Monday and something with rice on Wednesday, and swap the specific dish inside each theme.

The point isn't variety or efficiency for its own sake. It's that you stop facing an open-ended question every evening. I've written about why deciding what's for dinner is harder than cooking it, and a rotation is one of the most direct fixes for that: the decision has already been made, by you, on a better day.

How many meals you need

There's no perfect number, but the people who seem happiest with their rotation tend to fall into one of three sizes.

• Around 7 meals. One for each night, repeated weekly. This is the lowest-effort version and the shopping is almost identical every week. It works best when the meals are loose, like "a stir-fry" or "tacos", so you can change the protein or veg without changing the plan.
• Around 10 to 15 meals. Enough for two weeks without a repeat if you cook five or six nights. This is the size I'd suggest for most families, because nobody gets the same dinner twice in seven days, but the list is still short enough to remember.
• Around 20 to 30 meals. A four or five-week cycle. Good if you get bored easily or have a bigger household with more tastes to cover, but it takes more upkeep and more ingredients you don't buy often.

A quick way to work out your number: count how many nights a week you actually cook, then decide how often you're happy to see the same dinner. If you cook five nights and don't mind a repeat every fortnight, you need about ten meals. If you'd rather go three weeks, you need fifteen.

Don't count every night. Most rotations work better with one or two nights left for leftovers, a takeaway or something from the freezer. Planning seven cooked dinners and managing four is how a rotation starts to feel like a failure.

How to build your first rotation

You don't need to sit down and invent a list. You almost certainly have one already. It's just scattered across your head, your bookmarks and your camera roll.

• Write down every dinner you've made in the last month that went down well. Don't filter yet.
• Cross off anything that took far longer than it was worth, or that one person always pushes around the plate.
• Check the mix. If half the list is pasta, swap a couple for something with rice, potatoes or bread, so the week doesn't feel the same every night.
• Mark two or three as your easy fallbacks: meals you can make from things you usually have in, for the nights the plan falls over.
• Put the recipes in one place, so planning doesn't start with hunting for them.

That last step matters more than it sounds. If your favourite chilli lives in a screenshot and your go-to curry is on a website you can never find again, every planning session costs you ten minutes before it starts. I've covered how to save and organise recipes from websites if you want a fuller walkthrough.

Why rotations go stale, and how to keep yours fresh

Most rotations fail in one of two ways. Either they're too small and everyone gets sick of them, or someone tries to fix that by adding lots of new recipes at once, which means more planning, more unfamiliar shopping and more meals that don't land.

The approach that seems to work for a lot of people is slow, steady swapping:

• Try one new dinner every week or two, not every night.
• If it goes down well, it joins the rotation. If it doesn't, drop it without guilt.
• Every month or so, retire the meal everyone's most tired of. It can come back later.
• Vary inside a meal rather than replacing it. The same taco night can be beef one week, chicken the next and beans the week after.

Seasons help too. Soups and stews in winter, more salads and grilled things in summer. Swapping a few meals as the weather changes gives you variety without adding anything to remember.

Turning the rotation into a weekly plan and shopping list

A rotation on its own still leaves you choosing which meals go into this week. The easiest way to handle that is to do it once, at the weekend, and write the shopping list at the same time. If you do it by hand, it helps to group the list by aisle and to keep a set of staples you add back every week. There's more on that in how to build a shopping list from your meal plan.

This is also the bit I built Foodedo to take off your hands. When you generate a plan, Foodedo picks the dinners for you, based on simple behaviour: the meals you've saved, liked, used before or turned down. In practice that means your saved meals become your rotation, and the plan gets shaped by what your household actually eats rather than by a fixed list you have to keep updating. You can still pick meals yourself if you want to, but you don't have to.

The shopping list is linked to the plan, so if you swap a dinner, the list changes with it. You can add recipes by pasting a link or the recipe text, which is the quickest way to get your existing favourites in. To be straight about the limits: some recipe sites won't import cleanly, in which case pasting the text is the workaround, and Foodedo doesn't track what's in your cupboards, so checking the list against what you already have is still down to you.

Does eating the same meals every week matter?

Not really, as long as the meals themselves are reasonably varied. A rotation of ten dinners that covers a mix of vegetables, proteins and carbs gives you more variety across a fortnight than a lot of improvised weeks do, because improvising under pressure tends to fall back on the same two or three meals anyway.

If you're worried about it, look at the rotation as a whole rather than night by night. Is there fish or beans somewhere? A couple of meals heavy on veg? Something that isn't pasta? If so, you're probably fine.

A simple way to start this week

If you want to try it without overthinking it:

• Write down ten dinners your household already likes.
• Pick five for this week and leave the other nights loose.
• Make the shopping list while you're picking.
• Next week, pick the other five, and add one new dinner to try.

After a fortnight you'll know whether ten is the right number for you, or whether you need a few more. Either way, you'll have spent two weeks not asking what's for dinner, which is really the whole point.