It writes your plan toward your race. It reads your vitals every morning. It rewrites today's session when your life spills over. And when you try to force the wrong day, it refuses.
A PDF plan has no idea you slept badly.
The meeting that runs long. The bad night. The knee that talks. You force the wrong day, you skip the right one, and by week 6 you're not following anything. You know this. You've done it. So have I. Two of us believed a PDF would survive twelve weeks.
The worst part is that nothing warned you. Nothing flagged that the week was too heavy, nobody moved Thursday's session. The plan noticed nothing. The plan never notices anything.
You know Dave from the club run. Forty-five minutes at lunch, so he buries himself. Every lunch. Tuesday he wrecks himself for a Strava segment, Sunday he blows up on the first climb, and the excuse is ready before he even clips in: the heat, the wind, the derailleur. His power curve falls off a cliff at ten minutes and he refuses to look at it.
What he's missing fits in one sentence: someone to tell him no on Tuesday.
“Performance isn't sexy. It's a pile of thankless tasks executed with rigour and violence.”
Your feeling is lying to you. HRV, TSB, watts, paces: we measure, we decide, we check.
One-click JSON export, .zwo/.fit/.mrc for your devices. If you leave, you leave with everything.
Hard on the days you can, easy on the days you must. Pain is information, not an emotion: you read it, you don't run from it. A missed session is dead. We absorb it, we don't stack it.
“The AI never computes a threshold or a load. The numbers come from the engine, the decisions from the rules, the words from the coach. Everyone in their own corner.”
Dated goal, thresholds, history, availability. No thresholds? It estimates them from your sessions, and never in silence.
Full periodisation to your race, deloads already placed. A block contract, not a to-do list.
“Kill Thursday.” It rewrites, compensates on Sunday, and shows you the diff before touching anything.
Target against actual, lap by lap: EF, decoupling, tonnage. Nothing gets lost.
Not a log that fills up. A season arc, with its phase chapters, the deloads already placed, the race at the end. The coach lives in the right-hand column.
Base, build, peak, taper: every phase owns a focus and a skeleton.
Volume ramp, deloads, 5K test: the plan commits, and it answers for it.
.zwo, .fit, .mrc, intervals.icu: every session lands on your device.
The phone in the morning to decide, the big screen on Sunday night to understand. Same numbers, same decision, no watered-down version.
Threshold recalculated at every test, paces per block, cardiac drift read split by split.
FTP, CP and W′ fitted over 90 days. Above threshold, your margin before you blow up is drawn.
CSS from your 400/200 test, zones derived, SWOLF tracked. Two sessions a week, never stacked behind strength.
A strength cycle built into the plan: tonnage, RIR, progressions. Never glued to a quality day.
“Several sports. One single fatigue.”
Triathlon, or any hybrid mix (bike + lifting, run + bike), is not trained by stacking two plans on top of each other. Every load you produce falls into the same engine. The Architect balances your week: Saturday's long ride weighs on Sunday's run, and cardio intensity never lands behind a heavy strength session. The Protocol arbitrates for you.
Why Z2 today, why the squat stays, why we don't stack a camp onto an already heavy week: every decision is justified, quantified, and linked back to an article. HRV, sleep, resting HR and load cross into a single score out of 100, never handed to you alone, always placed on your form curve.
Grey zone. The quality work happened Tuesday, today we protect: endurance stays, tonight's strength gets lighter.
Seven days, no card, on The Protocol and on The Season alike. The tools on cornermanprotocol.com are included in both. On their own they cost €20 a year. With a plain free account they stay usable, capped at two GPX a month.