A race report and a morning brief, exactly as the athletes received them. The race report is shortened and lightly edited to fit this page, with names removed.
You weren't tired on race morning: your form was +31, the freshest you'd been all build. What went wrong showed up in the first hour of the bike, when your heart rate sat around 150 for about 137 watts, 15–20 beats higher than your training rides at more power. A heart working that much harder for less output, from the start, usually points to heat, hydration, or something coming on, not to fitness. The data can narrow it down; you'll know which it was.
From the first hour your heart rate was about 17 beats above your long training ride while you were putting out less power. Over six hours your power faded by about a quarter, but your heart rate barely came down. That pattern points to something making every watt more expensive, not to a pacing mistake late in the ride.
On the run, your heart wasn't the limit. You averaged 133 bpm, lower than the 148 you held on the bike, and usually it's the other way round. Your heart rate drifted down, not up, through the marathon. Something other than your cardiovascular system held the pace back: fuel, stomach, heat, or legs. The swim was fine: 49 minutes at an average of 130 bpm.
If heat or fluid was the cause, it matters even more for your next race, because late November there is usually hot and humid. Your fitness isn't the problem. The gains will come from preparing for the heat and practicing a drinking plan, not from more training.
Our conclusion: humid heat, which a dry sauna doesn't prepare you for, plus travel across three time zones. He can now talk the report through with Training Intel in Ask.
Sent after the athlete's goal race. Every number is worked out from the race file and the weeks of training before it; the writing only explains what the numbers show, and asks what the data can't know.
The 44-minute session got done yesterday, but the 30-minute test inside it came in lighter than the plan called for: intensity factor 0.79 against 0.95 planned, and 50 stress points against 73. Your best 20 minutes averaged 144 bpm, and the 150 on file is 6 beats higher. A gap that size usually means the effort wasn't even, so keep 150 where it is. I'd redo the test in about two weeks at a steady, hard effort from the start.
Today is the Speed Endurance swim, 58 minutes and about 2,187 yards. The efforts at or above race pace are the point of it. Your recovery is 66%, a point short of green. Resting HR is 49 against your usual 51, and HRV is 27.7 against 28.8, so nothing is off by much. Your 7-day recovery average is 78%. I'd do the swim as written, but hold the fast efforts at a pace you can repeat on every rep. If the pace per 100 starts sliding well off the zone, stop the fast work there and swim the rest easy.
Did you hold an even effort through the 30-minute test, or build into it?
— Training Intel
The verdict on yesterday and the threshold check are worked out in code before a word is written; the brief only explains them. It asks at most one question, and only one whose answer changes the advice. The answer reaches tomorrow's brief.