Planning dinner one night at a time is exhausting mostly because it's the wrong unit of time. A week is the right one: it's short enough to plan accurately (you know what's actually happening Tuesday), and long enough that doing it once covers seven decisions instead of one.
Here's a concrete way to run that weekly session, whether you're using a shared calendar app or just a notebook on the counter.
Start from what's already planned
Open the week and look at what's already there before adding anything new: repeating meals like Taco Tuesday, a restaurant night already on the calendar, anything from last week that got pushed forward. Planning around fixed points first is faster than starting from a blank week.
Fill the easy nights first
Some nights plan themselves — quick pasta after a late practice, leftovers the day after a big cook. Assign those first. It's a small thing, but clearing the easy decisions early means the nights that actually need thought (a birthday, a night with guests) get real attention instead of leftover energy at the end of the session.
Let a rating-weighted suggestion do the boring picks
For a night where nobody has a strong opinion, a random pick beats staring at the recipe box. In Fam to Table, each day on the calendar has a suggest button that pulls from your own recipe library, weighted so five-star recipes come up roughly three times more often than three-star ones, skips anything already on the week, and automatically avoids a match that conflicts with a household member's serious allergy. Hit it again if the first pick's wrong for the week; it cycles to another option instead of repeating the same one.
There's also a single button that fills every remaining open dinner slot at once, for the week where you genuinely don't want to think about it night by night. It respects the same rules: no repeats, nothing that conflicts with anyone's allergies, weighted toward what your household actually rates well.
Track coverage, not just intentions
A plan that says "we'll figure out Thursday" isn't a plan. Whatever you're using, make it show at a glance how many nights are actually covered: 3 of 7, 5 of 7, all 7 done. That single number is what turns "I think we're mostly set" into "we're actually done," and it's the difference between a real weekly system and a good intention that quietly falls apart by Wednesday.
Leave room for input after the plan is set
Once the week's assigned, give the household a low-effort way to react: a vote, a comment, a thumbs down on the one meal nobody actually wants. This is meant to happen once, right after the plan goes out, not as an ongoing negotiation every night. In Fam to Table this happens right on each planned meal, including a way to vote on behalf of kids who don't have their own account, so a five-year-old's opinion about broccoli casserole is on record before Thursday, not discovered at the table.
Ten minutes on a Sunday, structured this way, replaces seven separate moments of "what are we even doing tonight." That's the actual value of planning by the week instead of by the day: not less thinking, just thinking at one better time.