Plan and training
How the plan adapts to life
What happens to the plan after a missed session, an illness or an unexpectedly hard week.
16 min read
In this article
- What the platform knows about your training
- “Unknown” is not zero
- Missed work is not made up
- The week's terms and the receipt
- We propose rather than rewrite in silence
- If you move a session yourself
- What a recalculation keeps after your edit
- When the platform offers to rebuild the rest of the week
- If you say you are tired
- What the readiness traffic light does
- When recovery takes a long time
- Coming back after a break
- It can always be put right
A plan is written in advance, but you live in the present: a work trip, a sick child, three broken nights in a row — and the week goes nothing like it was meant to. This article covers what the platform does in those cases and, more importantly, what it never does without asking you.
What the platform knows about your training
Every completed workout is matched to the planned session of the same day — one to one, with no load smeared across neighbouring days. The result is one of five states:
- done as planned;
- easier than planned — under 85% of the planned duration or under 80% of the planned load;
- harder than planned — over 120% of the duration or over 130% of the load;
- not done;
- unknown.
The fifth state is the most important one, and the next section is entirely about it.
“Unknown” is not zero
No data does not mean a missed session. A workout only becomes a missed one when three conditions line up: six hours have passed since midnight of the following day (twelve if your time zone is unknown), the day is fully described by what actually happened, and every connected source has reported for that day.
A silent source never turns into a missed session, no matter how much time passes. Instead, the source is flagged as not having synced for a while, and the decision stays with you: confirm the miss or leave that source out of the calculation. Strength work is never marked “missed” automatically at all — it leaves no digital trace, so only you can confirm a miss.
The same rule works a level up. A week that contains unknown days is not used as the baseline for growing load, and detraining is counted only from a confirmed break. Silence in your sync is not proof that you did not train.
Missed work is not made up
If you miss a key session — a long one or a hard one — the platform looks for a slot for it within the next three days. The move never crosses the week boundary, never happens more than once a week, and never lands in a recovery week, a taper, race day or the window straight after a race: there, less load is the point, not a loss. It also never lands on a day that carries a limit after illness, and a session missed on such a day is not moved at all. The target day is checked against the same rules as ordinary week building: is it free, does it fit under the ceiling, is the gap between hard days respected. If no suitable day is found, the session stays in the plan as missed: the platform has no right to delete it, otherwise “how much of the plan was done” would be counted against a plan with the undone part quietly taken out. A missed easy session is neither moved nor removed — it gets a receipt.
Two hard days back to back to make up for a miss will never happen. And a shortfall never creates extra load: a week that fell short fell short — that is already reflected in your fitness and form.
Overshooting works the other way. Do noticeably more than planned and the platform will offer to shorten the nearest non-key session of the same discipline in the rest of the week, but by no more than a third of its load. Anything smaller than a tenth it leaves alone, and it does not touch next week at all: that budget is worked out from what you actually did anyway.
The week's terms and the receipt
A week is published together with its terms: for every aerobic session not yet done, the outcome of skipping it — and of overdoing it by half the working time — is worked out in advance. The answer is a fitness number at the start of the next key day — “projected fitness by Saturday 41.4 instead of 42.8” — plus the balance zone name when it changes. It is a load-model calculation assuming the other sessions go to plan, not a readiness forecast; while the series is calibrating or the week has a day without data, the numbers stay hidden and only the words remain. The snapshot is stored with the week's revision, and the current calculation is refreshed as facts arrive.
A miss is closed with one tap: the “Not today” button on the session card marks the session missed, asks no reason and moves nothing. What comes back is a receipt: “Miss recorded · so many planned load points not done · no need to add them to the next sessions”, with the same fitness calculation. A recording of the same session arriving later lifts the mark by itself. The plan and the week's denominator do not change — the written-off load is shown as a caption, not subtracted from the plan.
A receipt also comes where there is nothing to decide: an easy session missed, an overshoot with nothing left to shorten in the week, a proposal that expired unanswered (“The proposal was not applied; this proposal did not change the plan”). A proposal with buttons appears only when there is a concrete change to a future session and the choice is yours. The next session after a miss follows the current plan: nothing is added for the miss, and the receipt introduces no new limits.
We propose rather than rewrite in silence
This is the core principle of the whole adjustment layer. A change arrives as a proposal showing “before — after”, and you accept or reject it with one tap. A proposal lives until the end of the day it concerns, and it is checked again at the moment it is applied — your plan never changes on stale numbers. And it can never add load: only move, shorten, swap for something easier, or remove.
The only things that apply on their own are hard safety rules — the medical layer stopping the plan. You are always told about that directly, and it cannot be rejected.
Why asking matters so much. A plan rewritten in silence stops being yours: you no longer know what was intended or why the week looks the way it does. And the platform does not see everything — it knows nothing about a shift change at work, the drive to your holiday, or the fact that today you simply want to run. So the last word belongs to the human.
If you move a session yourself
Drag a session to another day in the calendar or ask the AI assistant to move it. Strength can also be moved within the same week. Usually the move happens immediately.
Sometimes a move carries a risk. Your muscles may not have recovered before a run, or two hard sessions may end up together. The risk appears while you drag. After you release, the plan waits for your choice: the assistant's option, Move as is or Do not move. The assistant usually suggests a lighter version, such as cycling instead of running, or another day in the same week without visible conflicts. With a red traffic light, it recommends against moving work to today.
After you move as is, the platform does not offer the same change again that day. If yellow turns red, a new offer arrives. When you ask the assistant to swap sessions, it assesses the whole exchange and offers up to two options, one recommended.
Strength has additional conditions. A session with a saved result cannot be moved, including a skipped session. A second strength session cannot be placed on a day that already has one. Moving preserves exercises, sets, repetitions and weight. A warning about the new day does not itself lighten the session. Near a race or key session, the platform warns you and you decide.
What a recalculation keeps after your edit
You can edit an endurance session in the editor, add one or move one. After that it is pinned to its day. A recalculation does not remove it or rewrite it. This holds for the Recalculate plan button, the automatic recalculation, the recalculation after a new threshold and a request to the AI assistant to drop a sport from the week.
The recalculation builds the other days around the pinned session. Its minutes and load points count towards the week's budget and the growth ceilings. No other endurance session is placed on that day. The numbers in it stay yours: after a threshold change the platform does not change its pace or power on its own. And the day you moved the session away from can get another one.
A strength session you added through the AI assistant or moved stays on the chosen day in an ordinary recalculation of the week. A strength session you cancelled yourself is not brought back by a recalculation.
The platform may still propose to make a pinned session easier, for example on a red traffic light. That is an ordinary proposal with buttons, and nothing changes until you tap.
When the platform offers to rebuild the rest of the week
An edit or a new session changes the load of the week. Right after you save, the platform shows the before and the after. If the shift is noticeable, it offers to rebuild the other days. Your edit stays.
The shift counts as noticeable in one of three cases.
- The week went over a ceiling. That is the ceiling on weekly load, on running minutes or on ride minutes. The ceilings are described in How the plan is built.
- The weekly load changed noticeably, up or down. In an ordinary week the offer is possible when the shift is no smaller than the larger of two numbers: 10 percent of the previous weekly load or 25 points. In a week with reduced load, for example a deload or a taper, the threshold is lower. The larger of two numbers is taken: 5 percent of the previous weekly load or 15 points.
- Your load growth is limited right now, and the edit raised the load. Then any increase is enough.
The offer appears only when there is something to rebuild. After the day of the edit the week must still have at least one endurance session that is not done and that you did not pin yourself. And the recalculation must change something. If it would build the same sessions, there is no offer.
The offer sits on the screen after saving and arrives in the AI assistant feed. It shows how many sessions will change, how many will go and how many will stay. Rebuild recalculates the current and the next week, and pinned sessions stay where they are. Keep as is changes nothing. The platform does not rebuild the week on its own after your edit. Only one such offer can be waiting for an answer for a week at a time. A new offer replaces the previous one if you have not answered yet.
Sometimes the pinned sessions alone add up to more than the weekly ceiling. Then a rebuild will not bring the week under the ceiling, and the offer says by how many points they are over.
A ceiling does not stop you from saving. The platform names the excess as a number, and the decision is yours. A refusal comes in other cases, for example a day that has passed, a session already done or the plan stopped by the medical layer. Put it back returns the previous version.
If you say you are tired
Tell the AI assistant you are tired or falling asleep. If there is a session today, the platform builds a What to do with today's session card. It offers to ease it, move it to another day in the same week or remove it. One option is recommended. Each shows the change in session and weekly load.
Sometimes removal is the only option: with a red traffic light, if you are falling asleep right now, report symptoms, or today's session is strength. Record symptoms with I feel unwell on the day card. A chat message does not change medical restrictions, check-in or the traffic light. The assistant can discuss how you feel and suggest easing the day, but the platform sets restrictions.
What the readiness traffic light does
The traffic light looks at today and changes today's sessions only; yesterday's unfinished ones are handled by the missed-session rules.
Yellow for general recovery. If the session contains work at moderate intensity or above, it is swapped for an easy session of the same duration. If the session is easy already, it is cut by 30%. One lever, not both at once, and exactly one session of the day: yellow is a signal of uncertainty, not a ban.
Yellow for muscles and joints. Here the impact comes out: the strength session is dropped, a run becomes a ride, and if there is no ride that day, a swim. The rule applies to every impact and strength session of the day, because leaving a second impact element in means it has not been applied at all.
Red. You are offered to drop every session of the day, strength work included. This is an ordinary proposal too — you can reject it.
Grey. Does nothing: no data means no reason to change the plan.
When recovery takes a long time
One yellow day changes only that day. If at least four of the last seven days were yellow or red, with at least five days of data, the next week becomes a deload earlier than planned. An early deload happens at most once in 28 days.
If things are no better after it, a load hold begins. The plan labels such a week Load hold. Volume stays at deload level, there is no growth and no work at threshold or above. The hold ends after two calm weeks in a row, each with at least five days of data. If you train without a watch and check in less often, there is still a way out: the hold ends after 14 days in a row without a single yellow or red day. The first week after a hold grows in a small step, at most 10% above the last hold week. This is a training rule, not a diagnosis.
Coming back after a break
Coming back is deliberately conservative. After 7–13 days without load, the week is built at roughly 85% of your usual volume and with no new intensity. After 14–27 days, about 65%, if there were ordinary training weeks before the break; without them the platform starts with calibration. The percentages are taken from the smaller of two numbers: your schedule and what you actually did before the break. A schedule alone is not a norm. After 28 days or more, the platform no longer treats your old norm as confirmed and starts from a clean slate: 50 to 70% and starts with calibration. Seven or more days in a row without data put you in the same cautious mode until the facts are confirmed.
Growth after a return is capped more tightly than usual — 5–10% of volume per week.
Sometimes the break is in one sport only. For example, you rode all month and did not run at all. If a sport was missing for 28 days, it comes back on its own. First two short easy sessions a week, with no long session and no intensity. This lasts at least two weeks, and each of them needs at least one completed session of that sport. After that its volume grows in small steps, no more than 10% a week. The other sports go as usual, and the time removed is not handed over to them.
The reason is simple: underestimating costs you a few extra easy days, overestimating costs you an injury in your very first week back. Coming back after illness or injury follows a separate, even more cautious path — see “Safety and where medicine begins”. After an illness the medical steps come first. Then comes the return week, and it is set by how long the illness itself lasted: 7 to 13 days of illness give about 85% of your usual volume, 14 to 27 days about 65%. If the steps end on a Thursday, the return week only starts on Monday, so Friday, Saturday and Sunday are lighter too: no intensity and the same reduction as the return week. Easy sessions during the steps do not cancel this return, and no early deload is put on the return week: one illness lowers the plan once.
It can always be put right
A session's state is not an entry in a logbook but the result of a calculation over the input data. A file arrived a week late, a duplicate turned up, you linked an activity to a session by hand — a wrong “miss” is undone no matter how much time has passed. The 14-day limit applies not to the truth about what happened, only to plan edits: repairing a week long gone makes no sense.
Your manual decision (link, unlink, mark as done or missed) beats the automatic one and survives any recalculation until you undo it yourself. Marking a session Done with no activity behind it counts the full planned load. If a watch recording arrives later, the load is recalculated from it.
Terms in this article
What to read next
- How the plan is builtSeason phases, load growth, recovery weeks and the taper into your main race.
- Readiness: your traffic lightHow the platform decides whether to push today or hold back — and why it sometimes stays honestly silent.
- The AI assistant: what to ask and what to requestWhat the assistant explains, which plan changes it prepares at your request, and how to phrase a message. With examples.