Three athletes train the same week: lifts on Monday and Wednesday, intervals on Tuesday, a long session on Saturday, nothing on Thursday. One cooks everything on Sunday and eats from boxes until Friday. One cooks dinner every night. One keeps tubs of cooked chicken and rice in the refrigerator and builds a plate in ten minutes. All three eat well on Monday. By Thursday their weeks look very different, and the cooking is rarely the reason.

Quick answer: batch prep, nightly cooking, or component prep

  • A full Sunday batch costs one afternoon and gives you every weeknight back. Its weak point is a session that moves after the lids are on.
  • Cooking every evening bends to any week, because nothing is decided until the day. The price is five evenings at the stove.
  • Component prep sits between them: proteins and grains cooked ahead, plates built each night, portions decided at the counter.
  • The refrigerator sets a limit on anything cooked ahead. One Sunday cook does not reach Friday without a freezer or a second cook.
  • The workflow matters less than the portions. Whichever one you pick, the food has to follow the training days.
Four tests for three ways of cooking a training weekA grid of four criteria against a full Sunday batch, cooking every evening, and component prep. The rows are portions sized to the training day, a midweek schedule change absorbed, weeknights kept free, and food eaten inside the refrigerator limit. Each cell shows whether that approach does the thing, does it in part, or is not built for it, as a count of filled dots, with a legend. A full Sunday batch is built for cooking once and keeping the weeknights free. Cooking every evening is built for deciding each dinner on the day you eat it. Component prep is built for cooking the slow parts ahead and assembling a plate each night. Across four criteria, a full Sunday batch does one of them and part of three, cooking every evening does three of them, and component prep does two of them and part of two. Where a column says a tool is not built for something, that is a statement of scope, not a fault. Each cell states the answer as a word and repeats it as a count of filled dots, so nothing depends on colour.
Across four criteria, a full Sunday batch does one of them and part of three, cooking every evening does three of them, and component prep does two of them and part of two. Where a column says a tool is not built for something, that is a statement of scope, not a fault. Put the rows to your own week as questions before you pick a column.

Three ways to cook for the same week

These are ways of working, not rival camps. Each one is built for something, and each one pays for it somewhere else. Plenty of athletes run two of them at once without giving either a name.

A full Sunday batch is built for cooking once and keeping the weeknights free. Cooking every evening is built for deciding each dinner on the day you eat it. Component prep is built for cooking the slow parts ahead and assembling a plate each night. Across four criteria, a full Sunday batch does one of them and part of three, cooking every evening does three of them, and component prep does two of them and part of two. Where a column says a tool is not built for something, that is a statement of scope, not a fault.

These columns describe ways of working, not specific apps. A given app may implement more than one of them, and several do, so treat the rows as descriptions of an approach rather than a verdict on any product.

The four rows are the places where a training week puts pressure on a kitchen: the size of the plate, a session that moves, the hours you have on a weeknight, and the age of the food by Friday. Read the grid as four questions to put to your own week. Adding up the dots tells you very little, because the four rows do not weigh the same for any two people.

The four tests, one at a time

On portions sized to the training day, a full Sunday batch does this in part, cooking every evening does this, and component prep does this. On a midweek schedule change absorbed, a full Sunday batch does this in part, cooking every evening does this, and component prep does this. On weeknights kept free, a full Sunday batch does this, cooking every evening is not what it is for, and component prep does this in part. On food eaten inside the refrigerator limit, a full Sunday batch does this in part, cooking every evening does this, and component prep does this in part.

1. Do the portions follow the training day?

Carbohydrate is the part of the diet that guidance scales to the demand of the training being done, not something held at one level all week1. So the first test for any way of cooking is whether Tuesday’s plate can differ from Thursday’s.

Cook every evening and it happens without effort: you know what today held before the rice goes in the pot. Component prep works the same way, because the scoop is decided at the counter. A full batch gets there only if you sized the boxes on Sunday and wrote the day on each lid. Five identical boxes hold the food at one level by construction. How to meal prep around training days covers sizing a batch that way.

How far apart the sizes sit is your call. A rest day is a rest day, not a restriction day, and the smallest plate of the week is still a full dinner.

2. What happens when a session moves?

Say Wednesday’s lift moves to Thursday. If you cook each night, nothing needs fixing, because Wednesday’s dinner was never made. With components, the bigger scoop goes on Thursday’s plate and that is the whole change. With a full batch you trade two boxes and fix the lids, which works as long as the box you need is thawed and still inside its dates.

That condition is why the full batch is the most fragile of the three on this row. The decision was made on Sunday and sealed. A swap handles one moved session. Move two in the same week and the boxes stop matching the days. What to do with your meal plan when your workout schedule changes walks through the swap, box by box.

3. What does a weeknight cost?

Here the order reverses. A full batch takes one block of about two hours on Sunday, then three minutes at the microwave each night. Cooking every evening takes 30 to 45 minutes a night, five nights running, plus the washing up. Component prep takes about an hour on Sunday and ten minutes a night to put a plate together.

Those figures are rough and your kitchen will differ, so time one week of your own. The shape holds either way. Nightly cooking spends its time on the evenings you train, and those are the evenings with the least to spare. An 8 p.m. finish on Tuesday followed by 40 minutes at the stove is the night that way of working is hardest to keep.

4. Is Friday’s food still inside the limit?

Cooked leftovers keep in the refrigerator for three to four days2. Count from the day you cooked, and do not round up. A Sunday cook covers Monday through Wednesday, with Thursday at the outside. Friday is past it.

Cooking every evening stays inside that by default, because nothing waits more than a day. The other two both run into it. A full batch needs the Thursday and Friday boxes frozen on Sunday and moved to the refrigerator the night before each one is eaten. Component prep needs the same freezer pass, or a second short cook on Wednesday. The handling is the same for all of it. Divide hot food into shallow containers so it cools quickly, and get it into the refrigerator within two hours of cooking2.

One week, cooked three ways

Take the week from the top: lifts on Monday and Wednesday, intervals on Tuesday, a rest day on Thursday, a long session on Saturday. Dinner is chicken thighs, roasted vegetables and rice in all three kitchens.

The full batch. Sunday afternoon: two trays in the oven, one big pot of rice, five boxes. Tuesday’s box gets the biggest scoop of rice and Thursday’s the smallest, and each lid gets its day. Thursday’s and Friday’s boxes go in the freezer. Every weeknight is free. Then Wednesday’s lift moves to Thursday. You trade the two boxes, and one of them is frozen solid at 6 p.m.

Every evening. No Sunday cook. Each night the rice goes on, the chicken goes in the pan and the vegetables go in the oven. After Tuesday’s intervals you make a bigger pot. When the lift moves, the only sign of it is a fuller pot on Thursday. You also cook on Tuesday at 8 p.m., tired and hungry, with a pan to wash afterwards.

Components. Sunday: the same trays and the same pot, stored in three tubs instead of five boxes. Each night you build a plate, and the rice scoop follows the day. When the lift moves, the scoop moves with it. On Wednesday evening you cook a second pot of rice and one more tray, about twenty minutes of attention, so Thursday’s and Friday’s food is fresh.

Same food, same shop, same oven. What differs is when the decision gets made and how many evenings it takes.

The part that is the same in all three

Look at what did not change between those kitchens. The grocery list was identical in this example: the same chicken, the same rice and the same vegetables, in the same amounts. The amounts came from the training days, not from the way of cooking. Four sessions and a rest day decide how much rice the week needs before anyone decides when to cook it.

The prep order is the same problem too. Whether you cook once or five times, the long job starts first, the short jobs fit into the gaps, and assembly comes last. The Sunday meal prep checklist for athletes lays that order out for one big cook, and it shrinks to fit a Wednesday top-up or a single dinner.

So the choice of workflow is the smaller decision. The larger one is whether the portions follow the training days at all. A flawless Sunday batch of five identical boxes misses the week. So does a fresh dinner every night cooked to the same size. Get the week’s amounts right first, and any of the three will carry them.

How to choose

  • Your sessions rarely move and your evenings are full. Run the full batch. Size the boxes by day, label the lids, and freeze the late ones.
  • Your sessions move every week and you like to cook. Cook every evening. Protect the nights after your hardest sessions with one fast dinner you can make tired.
  • Your work hours are fixed and your sessions shift around them. Run component prep: one cook on Sunday, a short one midweek, plates built at the counter.

You can mix them. Lunch at a desk cannot be assembled, so box the lunches and keep components for dinner. A week with travel in it might be a batch week, and a quiet week at home might be a nightly one.

Give whichever you pick one full week before you judge it, and judge it on Friday. Monday flatters every method. The useful questions come at the end of the week: was Friday’s food still good, did the plates match the sessions, and how many evenings did it take?

Where Mero fits

All three ways of cooking start from the same inputs: an amount for each day, one list to shop from, and an order to cook in. Working those out by hand is the slow part, whichever column you are in.

Mero sizes each day's portions for the day type you planned. It also produces one grocery list for the week and a batch-prep plan with step-by-step Kitchen Mode. The app also keeps your accepted meals, targets, grocery list and prep fixed when a session moves, and points you to a small carb top-up already in your weekly shop when it lands on a new day. Mero is on the App Store and Google Play in 16 countries.

The meal prep for athletes page covers how the batch is put together.