The two-week rotation: reuse a week you already planned
You already have a rotation; it is just not written down
Most households eat about fourteen dinners over and over. Not because they lack ambition, but because fourteen is roughly how many meals a family can cook well, shop for reliably and agree on. The weekly planning session still starts from a blank grid every Sunday, as though the question were what could we possibly eat rather than which of ours is it this week.
A two-week meal plan rotation closes that gap. You work out what you actually cook, pick two weeks' worth that cover the effort you have on each night and the allergens in your house, and write them down as Week A and Week B. From then on, planning is selection rather than invention: you look at the shortlist, not the whole library, and a week takes five minutes instead of forty.
Our Table Tonight is the record-keeper for this. Be clear about what it does today: it holds the history that tells you what your rotation really is, and it holds each week's plan. There is no saved template and no copy-a-week-to-next-week button, so a new week is re-assigned from your shortlist by hand. The method below is built around that, and it works because re-assigning from fourteen known meals is a small job.
Step one: find out what you actually cook
Start with evidence, not memory. Everyone believes they cook a wider range than they do, and a rotation built from what you think you make will contain three meals you have not cooked since last winter.
The app collects that evidence if you mark meals at the end of each week. Each slot gets Made, Didn't Make, and optionally a rating out of five, and they submit together. Only Made writes to your cook history, which is what makes the number worth reading — it is a record of what happened, not of what was planned.
Every recipe then shows how many times you have prepared it, and, if you plan in a household, how many times the household has. Sort your impressions against those two numbers and three groups appear:
- The keepers — cooked repeatedly, rated well, no argument at the table. These are your rotation whether you meant them to be or not.
- The perennial intentions — planned several times, made once. Something about them does not survive a real Tuesday. They are usually too long, or they need an ingredient you never have in.
- The unknowns — never planned at all. Some are worth a trial; most are there because you saved them once.
Give it two or three weeks of marking meals before you trust the counts.
Step two: pick fourteen that fit the week you really have
Now choose. The temptation is to pick fourteen meals you like; the useful move is to pick fourteen that fit the nights they will land on.
Every recipe carries an effort level worked out from its prep and cook times — express, easy, involved or project — and you can filter on it, or on a maximum total time, when you search. A rotation with five involved dinners in it is a rotation that gets abandoned by Wednesday. Count your actual cooking nights first: if two of the seven are takeaway or leftovers and one is someone else's turn, you need four dinners a week, not seven.
Two other filters are worth running the shortlist through before you commit to it:
- Allergens. Recipe search can exclude recipes tagged with a given allergen, so you can build a shortlist that is safe from the start rather than being flagged every time you assign it. The planner will still check each assignment against your household's recorded allergens and flag conflicts — it flags, it never blocks — but a rotation that never triggers a warning is less work than one that always does.
- Overlap. Meals that share ingredients shop better. If four of the fourteen use the same base — a stock, a jar, a bag of rice — a fortnight's shopping stops being fourteen separate lists of components.
Writing down Week A and Week B
Split the fourteen into two weeks with the same shape: the same number of quick nights, one longer cook on the night you have time for it, the same slots left for eating out. Two weeks rather than one, because a single week repeated is noticeable by the third pass and a fortnight is not.
Keep the two lists somewhere you will look. What matters is that on Sunday you are choosing from fourteen rather than from everything.
Example
Step three: plan the new week by selecting
With the shortlist in hand, filling a week is assignment work: pick the day, pick the meal, pick the recipe. A few things in the planner make that faster, and one thing it does not do yet is worth stating plainly rather than leaving you to discover it.
- You can look back while you plan. The single arrow moves a day and the double arrow moves a week, and the date picker jumps to the week containing any date. Week A as you actually cooked it three weeks ago is a few clicks away, and reading it beats reconstructing it.
- You choose how much is on screen. Show between one and seven days at a time; the choice is remembered in your browser, so a phone can sit on one day while a laptop shows the whole week.
- Copying works within the week on screen. The copy button on a filled slot offers the other days shown, lets you send the meal to a different meal type, warns before overwriting anything already there, and brings the servings override with it. It can also mark the copy as leftovers, which is the honest way to plan Wednesday when Tuesday made too much.
- Copying to another week is not available, and neither are saved templates. You cannot press a button that turns Week A into next week. Re-assigning fourteen known meals takes a few minutes; do not wait for a feature to start the rotation.
Step four: shop the rotation, weekly or fortnightly
Generate the shopping list from the plan for the date range you are actually shopping for. The app collects ingredients from every cooked slot in that range, scales them by any servings overrides, merges duplicates so two meals wanting onions produce one line, and groups the result by category. Eat-out and leftovers slots are skipped.
The range is yours to choose, which is what makes a fortnightly rotation practical: one list for fourteen days of storecupboard and freezer items, and a shorter one mid-fortnight for the fresh things. Once the same fourteen meals come round regularly, you learn what that shop weighs and it stops being a surprise.
Keeping a rotation from going stale
A rotation dies in one of two ways: nobody changes it and everyone is bored, or it is rewritten every month and stops being a rotation. The fix is a rate. Swap one meal per fortnight — a single new dish tried on a night you have time, and one of the fourteen retired if it earns its place.
Let the same evidence make the call. Keep marking meals; check the counts and ratings every month or so. A meal in your rotation that is repeatedly planned and not made has already left it, and the list should say so.
- Mark meals for two or three weeks so the cook counts mean something.
- Pick fourteen that match your real cooking nights, effort budget and allergens.
- Split them into Week A and Week B with the same shape.
- Plan each new week by re-assigning from those fourteen.
- Generate the list for the week or the fortnight you are shopping.
- Swap one meal per fortnight, chosen from the counts rather than from mood.
Related guides
Match the meal to the night: plan by effort, not just recipe
Quick weeknight dinner planning starts with effort, not the recipe box. Sort your library by prep time so a busy Tuesday never lands a project-length meal.
Updated ...
How to plan a week of meals with your whole household
A shared meal planning app for families: build one weekly plan together, assign meals to the right night, and keep everyone working from the same list.
Updated ...
Try this in your own week
Our Table Tonight is a free beta. Sign in if you already have an account, or join the waitlist and we'll email you when a spot opens.
Sign in