Why this is hard to judge on your own
The advice everywhere is the same. Ask yourself what percentage of FTP you rode at. Look at whether your power dropped in the second half. Check how smooth it was. All correct, and all of it leaves you doing the interpretation while you are still tired and disappointed from the race.
The trap is that overbiking is easy to assert and hard to prove. A high intensity factor on its own does not mean you overcooked it. Neither does a rough run. The only honest way to call it is to compare what you rode against a level you have actually held before, and most tools stop at showing you the numbers.
What The Debrief actually checks
- Whether your bike power sat above a level you have demonstrably sustained, not an estimated ceiling you never touched.
- How your power held or faded across the second half, where overbiking usually shows first.
- Whether your run pace decayed in the pattern that follows a bike that was too hard, versus heat, fuelling or a pacing error on the run itself.
- How your heart rate tracked your power, since decoupling late in the bike is one of the clearer tells.
If the file cannot support the verdict, it will say so. Calling an overbike you did not commit is worse than leaving the question open. The read stays inside what your data can actually prove.
What you get back
A debrief written the way a coach would talk you through it. Not a wall of charts to interpret yourself, and not a confident verdict pulled out of thin air. Just what the file shows about how you executed, in plain language, on screen, right after you upload.