Match the meal to the night: plan by effort, not just recipe

Tuesday did not fail because of the recipe

The dinner you abandoned on Tuesday was probably a perfectly good recipe. It failed because it needed forty minutes of your attention on a night that had fifteen. That is a scheduling mismatch, not a cooking problem, and no amount of searching for better recipes fixes it.

Quick weeknight dinner planning starts one step earlier than most people start it. Before you choose what to eat, work out how much attention each night of the week actually has. Then organise your recipes by prep time — specifically by hands-on prep time, which is not the same as the total time printed at the top of the page — and match the two. Short nights get short meals. The long cook goes on the night you are at home anyway.

Our Table Tonight does that sorting for you: every recipe carries an effort level computed from its prep and cook minutes, and you can filter the library by it. This guide covers the method first, then how each step works in the app.

Step one: write down each night's attention budget

Take the seven days and give each one a number in minutes — not how long you are willing to wait for dinner, but how many minutes you can stand at a counter chopping and stirring before someone needs collecting, a call starts, or the children need to be in the bath.

A typical week comes out lopsided, and that is the useful part:

• Monday — 25 minutes. Tuesday — 15, back from swimming at six.
• Wednesday — nobody cooks, it is leftovers. Thursday — 30.
• Friday — 60 minutes, and nobody is going anywhere afterwards.
• Saturday — as long as you like. Sunday — 45.

Write it once. The shape of a week changes a few times a year, not weekly, so you revisit this when term dates or shifts change rather than every Sunday.

Step two: rate recipes by hands-on time, not total time

Total time is the wrong measure, and it is the one every recipe site leads with. A three-hour braise with fifteen minutes of chopping is an easy meal: you cut things up, put the lid on, and the oven does the rest. A thirty-minute stir fry where all thirty minutes are you at the hob is the harder ask on a Tuesday.

So weight prep more heavily than cooking. The app uses a fixed 80/20 split — prep minutes count four times as much as unattended cook minutes:

1. Take the prep minutes and multiply by 0.8.
2. Take the cook minutes and multiply by 0.2.
3. Add them. That number, not the total, is what the effort level is set from.

The braise above — 15 minutes prep, 165 minutes cooking — scores 45. The stir fry, at 25 minutes prep and 5 minutes cooking, scores 21. They land one band apart, in the direction your Tuesday self would agree with.

The four bands

• Express — 20 or under. Assembly and reheating, for the night you got home late.
• Easy — 21 to 45. An ordinary weeknight dinner.
• Involved — 46 to 90. Worth doing when you are not also doing three other things.
• Project — over 90. A weekend cook.

In the app this is computed, not chosen. You fill in prep minutes and cook minutes on the recipe; the level follows, and there is no field to set it by hand. That matters, because a level you can set by hand drifts — everything ends up marked easy once you have made it twice and stopped noticing how long it takes. Entering honest times is the only work here.

Step three: put the effort on the right night

Now match the two lists. Express and easy go on the weeknights. Involved goes on Friday, or whichever evening is your first with nothing after it. Project goes on the weekend, where it can be the afternoon's activity rather than an obstacle before dinner.

A week planned this way is deliberately uneven, and it should look uneven on the grid. Two express nights in a row is not a failure of ambition; it is what a week with two late finishes honestly contains. The plan that collapses is the one with four involved dinners stacked Monday to Thursday.

The planner shows each assigned meal with its effort level on the card, so an imbalance is visible while you are still filling the week rather than discovered on the night. If Tuesday is carrying something involved, move it before you shop, not after.

Step four: choose from a filtered library, not the whole one

The other half of this happens at the point of choosing. Scrolling your entire collection looking for something quick is how you pick the wrong thing — everything looks manageable in a photograph.

Search in the app filters on the things that decide whether a meal fits the night:

• Effort — express, easy, involved and project, as chips you can combine. For a Tuesday, tick express and easy and stop looking at anything else.
• Max total time — 30, 45, 60 or 90 minutes, for when the constraint is genuinely the clock, such as a meal that has to be on the table before a fixed departure.
• Dietary tags and allergens — include the tags you need, exclude the allergens you cannot have.
• Free text— searches recipe names and descriptions, so you can combine “chicken” with an effort filter rather than choosing between them.

Filter first, choose second. It turns picking a Tuesday dinner into a short list of things that were always going to work.

Step five: set a serve time and let the app do the arithmetic

Knowing a meal is easy still leaves the question that ruins weeknights: when do you start? Set the time you want to eat on the slot as you assign the meal, and the app works backwards through the recipe's prep and cook minutes to show the start time on the card — “Start cooking at 5:15pm”.

Set a default serve time per meal in your profile — breakfast, lunch, dinner and snack — and slots arrive pre-filled, so you correct a time rather than enter one. Leave a default blank if your household eats when it eats; no default is a real answer, and a better one than a fictional time you fix every week.

A serve time also unlocks the alert. Switch prep alerts on for the slot and you get a notification at the start time — in the app, and by email or on your phone depending on what you have set up. It only fires if there is a serve time to compute from, which is why you set one at assignment rather than promising to add it later.

Step six: treat assembly as a real answer

Some nights the right meal involves no cooking at all: bread, cheese, cut vegetables, hummus, fruit. A plate of things is a legitimate dinner, and planning it on purpose beats the same food arriving at eight o'clock as a defeat.

The app calls these packs. A pack is a saved list of components with no instructions and no times — build it once, name it, and assign it to a slot the way you assign a recipe. It goes through shopping list generation like anything else, so the crackers and the hummus reach the list.

Because a pack has no prep or cook minutes, effort is not a meaningful sort for one: the arithmetic gives every pack the same answer. Find packs with the kind filter in search, which narrows to recipes, packs, or both.

What this looks like once it is set up

1. Your attention budget for the week is written down and rarely changes.
2. Every recipe has honest prep and cook minutes, so its effort level is honest too.
3. You filter by effort before you browse, and the long cooks sit on the two days that can hold them.
4. Each slot carries a serve time, so the start time is a fact rather than a guess.

None of that makes anyone a faster cook. It stops the week asking for time it never had.