Your race is four months out. The plan exists, in theory: base, quality, peak, taper. Then life happens — work, family, bad sleep. Suddenly your long run lands on a Wednesday, intervals fall the day after a hard session, and the taper starts three days before the race because “it didn’t work out”.
This is not a story about lacking discipline. It’s a story about the fact that a plan on paper cannot see your body. A rigid plan has one mode: execute. Your body has more.
A plan is also what you DON’T do
Periodization in UltraFlow is not a spreadsheet of kilometres. It’s a system of constraints guarding the boring things that decide everything:
🛑 Three brakes that act before something breaks
And the thing almost nobody does: when data is missing, the system says “I don’t know”. An incomplete night from your watch is not a reason to guess readiness — it’s a reason not to compute it, and to say why.
The day the plan meets reality
Every morning the report confronts the plan with your physiology: HRV against your own baseline, resting heart rate against your personal alarm threshold, sleep, your morning check-in. And here is where a system differs from a spreadsheet:
- A regular session on a bad day? You do it easier. The week’s structure stays intact.
- A key session — the long run, a quality day — and your body says no? The system moves it by a day or two, swapping with an easy day. You see it in the app, with the reason.
- No room to move it? The session is dropped, never made up. A deliberate design decision: making up missed work is the easiest way for one weak week to ruin the next three.
- Several bad days in a row? The system proposes rebuilding the block into a gentler rhythm — and waits for your consent. No plan rebuild ever happens behind your back.
It also works the other way — and that’s the part rigid plans stay silent about.
Brakes aren’t everything — how the system knows you can do more
Most plans from the internet undershoot, because they must be safe “for everyone”. UltraFlow doesn’t plan for everyone — it plans for you, from two sources:
First: your real capacity, not a declaration. The engine calibrates block volume from your actual, healthy training weeks — ones with complete data, outside post-race recovery windows. If your history shows you carry more than a typical template would assume — your plan starts higher. If there isn’t enough data, the system says so openly and plans conservatively instead of faking confidence.
Second: an explicit green light. When the night is complete, HRV stable and resting heart rate normal — the report doesn’t mutter precautionary warnings. It says: ready for a stimulus. A key-session day with a green light is a day you can trust — because you know that if something were off, the system would say so, just as concretely.
And a third thing, minor at first glance: when you want to add your own route into a plan week, the system checks it before saving — does it land next to a heavy day, does it blow up the week, does it fall inside a recovery window:
Not a gram more, not a gram less
“It’s not about training more. Nor less. It’s about training, every single day, exactly as much as your body can turn into fitness.”
— the UltraFlow plan engine principleA rigid plan you either execute or you don’t. A plan that sees your data, you execute wisely — with brakes when needed, and with a clear conscience when you can push.
Every number in UltraFlow has a source: your watch, your history, your check-in. Zero guessing — including when the honest answer is “not enough data”.