The lift was on the plan for six o’clock. At ten in the morning a work deadline lands at half five, and by lunchtime it is clear the session is not happening today and will not fit anywhere else this week. The food, meanwhile, is already made. There is a larger lunch in your bag, a bigger scoop of rice set aside for dinner after training, and a nagging question about whether eating any of it now is a mistake.
Quick answer: what to do with prepped food after a missed session
- Drop the day by one step. A missed hard session usually turns that day into an easy day, not a rest day. You have already eaten part of it, and one session is a small share of the week.
- Take the session’s add-on off, and nothing else. The base meals stay: breakfast, protein at each meal, the vegetables, the dinner you would eat anyway.
- If the larger lunch is already made, eating it is usually fine. One meal barely moves a training week.
- Count storage days from when the food was cooked. Cooked leftovers keep three to four days in the fridge. Anything you want after that goes in the freezer tonight.
- Do not rebuild the week. One day changes. In this example the shopping does not.
Why the day drops to easy, not to rest
The instinct after a missed session is to reclassify the whole day as a rest day and eat accordingly from that moment on. That usually overshoots, for two reasons.
You have already eaten part of it. A day planned around an evening session is loaded toward the afternoon: a larger lunch and a snack before training are common, a bigger breakfast less so. By the time the session falls through, some of that food is already inside you. Treating the whole day as a rest day tends to push dinner smaller than it needs to be, to offset a lunch that is already eaten.
One session is a small share of the week. A week with two or three hard sessions, a long run and a couple of shorter ones carries most of its demand in the sessions that still happen. Carbohydrate is the part of the diet that tracks training demand most closely, so it is the part that comes down when a session does not happen1. Coming down is not the same as going to zero.
So the approach here is one step down: a hard day that loses its session becomes an easy day. An easy day that loses a short session can usually stay as it is, because the difference is small enough that moving food around costs more attention than it saves.
Split the day into what stays and what comes off
Most planned days are two layers stacked together. The base is the food that would be there with or without training: breakfast, protein at every meal, vegetables, the lunch you eat most days. The add-on is the extra carbohydrate that exists because of the session, often a larger rice or potato portion around training and something like fruit, oats or bread nearby.
When a session is missed for scheduling reasons, the add-on is the part that can come off. The base stays. The mistake is cutting both, so that a lost session turns into an under-eaten day as well.
Consensus guidance on athlete nutrition treats adequate total energy as the foundation the rest of the plan sits on1. A missed session is not a reason to make up the difference with less food, and a week you are frustrated with is the week that most needs its meals to stay where they were. Skipping dinner to square the books with a session you did not do is punishment, not planning.
What to do with the food that is already cooked
The practical question is not what the day should look like on paper. It is what to do with the containers in the fridge.
The larger lunch is already made
Eat it. If you find out before lunch and the bigger container is already in your bag, that is the useful answer for most people. One larger lunch across a week of planned meals barely registers, and splitting a container at your desk to save half for later creates a storage question you do not need. If it bothers you, drop the afternoon snack instead. What you do not need to do is shrink dinner to compensate for lunch: dinner goes back to its base portion, and that is already the adjustment.
The meal after training has not been eaten
This is the portion that actually comes off. Leave the extra scoop of rice in the pot, or leave the second container in the fridge, and eat the base dinner. The food is not wasted. It is unassigned, and it goes to the next meal that can use it while it is still safe to eat.
Carrying cooked food forward
Here the limit is set by the food, not by the plan. Cooked leftovers keep in the refrigerator for three to four days, and freezing is the option for anything you want later than that2. Count from the day the food was cooked, not from the day it was planned for. Rice cooked on Sunday reaches its fourth day on Thursday, whatever the plan said it was for.
Treat the top of that range as a ceiling, not a target, and do not round it up. If the spare portion would be most useful later in the week than that, freeze it the evening you decide not to eat it and thaw it in the fridge the day before you want it. Food that has been out of the fridge is a separate case: cooked food belongs in the refrigerator within two hours, and perishable food left at room temperature for longer than that should be thrown away rather than carried forward2. A container that rode around in a warm bag all afternoon is not a candidate for tomorrow.
A worked example: the lift that does not happen
Here is the week as planned on Sunday. Monday easy, an evening run. Tuesday hard, a lower-body lift at six in the evening. Wednesday rest. Thursday easy. Friday hard. Saturday a long easy run. Sunday rest, and prep.
On Sunday the rice, chicken thighs, potatoes and a tray of vegetables were cooked and portioned, with the Tuesday lunch and dinner containers packed larger for the session. At ten on Tuesday morning a deadline lands at half five and the lift is off. There is no other slot for it this week, so it is lost rather than moved.
One tag changes: Tuesday goes from hard to easy. What happens to the food on that day:
- Breakfast. Already eaten, at its usual size. Nothing to do.
- Lunch. The larger container is already in the bag, and it gets eaten. In this example that is the sensible call: one bigger lunch is a small share of the week, and dividing it at a desk creates a storage problem.
- Afternoon snack. The snack that was there to go in front of the lift comes off, because there is no session for it to sit in front of.
- Dinner. Back to the base portion. The extra rice and potatoes packed for after the lift stay in their container.
- The spare portion. It was cooked on Sunday, so it has a day or two left in the fridge at most. In this example it goes into the freezer that evening and comes out for the meal after Friday’s session, thawed in the fridge the day before.
The other six days are untouched. Nothing about Wednesday, Thursday or the weekend moved, the next shop is the same shop, and the only real work was moving one container from the fridge to the freezer.
When it is fine to just eat it
Plenty of the time the right move is to ignore most of the above and eat what was planned. If the missed session is a one-off in an otherwise normal week, if the add-on was modest to begin with, or if the spare food will not keep, eating it as planned is a reasonable choice. How much it matters depends on the session you missed and how much was built around it, and for many athletes a single evening of extra rice is not worth a second thought.
The adjustment matters more when sessions go missing often, or when the portions built around a session are large. If a session falls through most weeks, the fix is in the plan rather than the fridge: schedule it where it tends to happen, or plan one fewer demanding session and stop cooking for the one that keeps disappearing.
When the reason is illness
Everything above is about sessions lost to a calendar: a meeting, travel, a closed gym, a child who needed collecting. A session missed because you are ill is a different case, and the add-on logic does not apply to it. If you are unwell, do not cut food because a session did not happen; prioritise fluids, foods you can tolerate and recovery, and seek medical guidance if it drags on or gets worse.
The same caution applies to a session skipped because you are simply too wrecked to do it. That is worth treating as information about the week, not as a reason to eat less on top of it.
Leave the rest of the week alone
The risk after a missed session is rarely the spare rice. It is the urge to rebuild: rearranging the remaining sessions, reshuffling every meal that follows, or redoing the shopping to account for one evening. Do none of it. One day changed.
If you would rather move the session than lose it, that is a different adjustment, and re-tagging a week when a session moves covers it: two days change instead of one. If you decide to treat the day as a full rest day instead, how a rest day is put together is the same base-first logic applied on purpose.
Most of this flexibility is bought on Sunday. Food prepped as components, a pot of rice, a tray of protein, a tub of vegetables, can be re-portioned in a minute, while five sealed containers labelled by date are harder to resize. Shopping against the week’s overall demand rather than a fixed daily grid means a missed session usually leaves the list as it was.
Where Mero fits
All of this runs fine from a notebook and a fridge. What it costs is a decision at an awkward moment: standing in the kitchen at eight in the evening, working out which container is spare, how old it is and where it should go instead. The framework above keeps that decision short.
Mero 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. It also sizes each day's portions for the day type you planned. The app also produces one grocery list for the week and a batch-prep plan with step-by-step Kitchen Mode. Mero is on the App Store for iPhone in the U.S.
The training meal plan page sets out the hard, easy and rest structure, and the meal prep page covers the Sunday side.
