Skip to content

By · Published: 2026-11-03

Running a household week: meals, chores and a Friday movie

The questions that wear a household down are small ones. What’s for dinner, whose turn it is to do the dishes, what we’re watching on Friday. Each takes thirty seconds to answer and five minutes to argue about. This guide sets up a family’s week in one sitting on Sunday afternoon, using three tools: the meal picker for seven dinners, the chore roster for four daily jobs shared by four people, and the movie picker for Friday night. The family in the example has two adults and two kids, aged 9 and 13. The setup takes about twenty minutes, and most of what follows is about the few places where each tool behaves differently from what you’d assume.

Sunday, 4 p.m.: the plan for the week

JobToolSettingsOutput
Weeknight dinners (Mon–Thu)Meal pickerInclude tag quick, Avoid last N days 84 meals
Weekend dinners (Fri–Sun)Meal pickerExclude tag quick, Avoid last N days 83 meals
Daily choresChore rosterDays / periods 1, then rotate by handOne starting assignment
Friday filmMovie pickerInclude tag family, Remove on pick ticked1 title

All three tools keep their lists in your browser, so you type the meals, the people, the chores and the watchlist once, and they’re there next Sunday. The options are kept too: the tag filters, the avoid window and the tick boxes are saved in your browser as you set them. That’s convenient on a Sunday, and it means a filter you set for one odd night is still set the next week. Check them before you press anything.

Dinners: seven meals, picked in one sitting

The meal list is one meal per line with optional hashtags, such as Chicken stir-fry #quick or Slow-cooked chilli #batch. Our example family has 20 meals: 10 tagged #quick (under 30 minutes) and 10 without the tag.

The picker filters before it draws. Include tag keeps only meals that carry every tag you list, separated by commas. Exclude tag removes any meal carrying any tag you list. Avoid last N days removes every meal the picker has chosen in the last N days. Then it picks one of whatever’s left, uniformly at random, and shows you the name without its tags.

The avoid window counts from the moment you press the button

That last option is where the Sunday planning trick comes from, and where its one trap is. The picker records each meal at the moment it picks it, not on the day you eat it. So when you pick seven dinners in one sitting on Sunday, the window already excludes the meals picked earlier in that sitting. Seven presses give you seven different meals, without any need to check for repeats.

Next Sunday is where the timing matters. Saturday’s dinner was “picked” last Sunday at 4 p.m., and next Sunday at 4 p.m. is exactly seven days later. With the window set to 7, last week’s meals become available again more or less on the hour, depending on whether you sit down a little earlier or later. Set it to 8 and the whole of last week’s plan is reliably excluded. Set it to 6 if you don’t mind repeating a favourite from last week.

A rejected suggestion still counts as picked

Every press is recorded, including the ones you turn down. If the picker suggests fish tacos and the 9-year-old objects, pressing again gives you something else, but fish tacos is now in the avoid window too, for the next eight days. That’s mostly what you want, since it won’t come back this week. But it uses up the pool, and that’s where the size of the list matters.

Here are the numbers for the example family. Weeknights draw 4 meals from the 10 quick ones. Next Sunday, with the window at 8, those 4 are still excluded, plus any you turned down. Next week’s four weeknight dinners need four quick meals left over, so:

  • 10 quick meals, minus 4 eaten, minus up to 2 rejections, leaves the 4 you need.
  • A third rejection, and next Sunday’s fourth weeknight press finds nothing left. The picker says no meals match those filters, and you either drop the window to 6 or add quick meals to the list.

The weekend picks use Exclude tag quick for the same reason. If the weekend drew from all 20 meals, it would often take quick meals out of next week’s pool. Three weekend draws from the 14 meals left after the weeknights take at least one quick meal 67% of the time. Excluding the tag keeps the two pools separate.

If you want to start over, Clear history on the meal picker also clears the avoid window.

Chores: randomness for the start, rotation for the week

The chore roster takes two lists, People and Chores, and a number, Days / periods. Our family has four people and four daily jobs: dishes, wiping down the kitchen, feeding the dog, and bins and recycling.

Here’s what the tool does for each day: it shuffles the people and deals the chores across that shuffle. With four chores and four people, everyone gets exactly one job a day. If you had five chores and four people, one person would get two jobs that day.

The thing to know is that each day is a fresh, independent shuffle. The roster doesn’t track what you did yesterday, so over a week the jobs don’t even out. With four people and seven days, each person can expect the dishes 1.75 times, but:

  • Someone ends up with the dishes on four or more nights 28% of the time.
  • Everyone does the dishes at least once in only 51% of weeks.
  • Someone does the same job three or more times in 99.7% of weeks.

That’s fair in the sense that matters for a draw (nobody’s odds are better than anyone else’s), and it reads as unfair to a 13-year-old who has had the bins three nights running. Run Days / periods at 7 and you’ll be dealing with that by Wednesday.

The approach that works for a family is to let the tool pick the starting point and to rotate from there:

  1. Set Days / periods to 1 and press Build roster. You get one random assignment: say Ruby on dishes, Leo on the dog, Maya on the kitchen, Tom on the bins.
  2. Write it on the fridge as Monday, then shift every person one job along each day, in the order dishes, kitchen, dog, bins. On Tuesday Ruby moves to the kitchen, Maya to the dog, Leo to the bins, and Tom wraps round to the dishes.
  3. Every person does every job once every four days. Over seven days nobody does any job more than twice.

The random part settles the argument about who starts with the worst job. The rotation settles the arguments over the rest of the week. If one job is unsuitable for one person, such as the 9-year-old on the kitchen knives, swap that cell with whoever is on the dog that day and leave the rest of the rotation alone. The roster has no way to know that, and it doesn’t need to.

If you’d rather have a fresh draw each week than a rotation that never changes, press Build roster again next Sunday. Export CSV puts the result in a spreadsheet if the fridge isn’t your style. The chore roster post covers what to do when there are more chores than people.

Friday: one film, picked before anyone sits down

The watchlist works like the meal list: one title per line, with optional hashtags for service or genre, such as Paddington 2 #family #netflix or Heat #crime #adults. Our family has 24 titles, 6 of them tagged #family.

Set Include tag to family and press What should we watch? The tool draws from the matching titles only.

Then there’s Remove on pick. With it ticked, the chosen title is deleted from the watchlist and the shortened list is saved. Over four Fridays that guarantees four different films. Without it, four picks from 6 family titles repeat a film somewhere in the month 72% of the time.

Two things to know before you tick it:

  • A vetoed film is removed as well. The removal happens the moment the tool picks a title, so if the room vetoes the first suggestion and you press again, both titles are gone from the list. Either agree that the first pick stands, or keep a short “vetoed” line in your notes and paste them back in later.
  • Duplicate lines are removed together. Putting a title on the list twice gives it double the chance, which is a fair way to let a birthday child weight their favourite. With Remove on pick on, both copies go when it’s drawn.

Our family’s rule: each person gets one veto a month, the second pick stands, and vetoed titles go back on the list on the first of the month. The movie picker post has more on tagging by service.

The Sunday checklist

  • Meal picker: Avoid last N days set to 8. Include quick for four weeknight picks; then clear Include, set Exclude to quick for three weekend picks. Turn down at most two suggestions, or add more quick meals to the list.
  • Chore roster: Days / periods 1, Build roster, write it up as Monday, move everyone one job along each day.
  • Movie picker: Include family, Remove on pick ticked, one press on Friday, second pick stands.

What the tools don’t do

None of these tools knows about your household. The meal picker doesn’t know Thursday is swimming night, the roster doesn’t know the dog bites the youngest, and the movie picker doesn’t know what’s suitable for a 9-year-old beyond the tags you give it. They’re good at the single thing they do: making one decision fairly, so nobody has to argue about it. The post on decision fatigue at home makes the broader case for letting a tool handle that kind of question. The week above is that case put on a schedule, with the numbers checked so it still holds up by Thursday.

← Back to all posts

Send feedback

Found a bug, want a feature, or just say hi? Send it our way.