Athlete fatigue monitoring

Two kinds of tired

Acute fatigue is the day or two after a hard session. It is the intended consequence of training, it shows up clearly in the data, and it resolves on its own. It is not what monitoring is for.

Accumulated fatigue is different. It builds across a block of sessions that all felt manageable at the time, and the first obvious sign is often a benchmark or a race going badly rather than a bad Tuesday.

The second kind is hard to catch by feel — including for the athlete, who adapts to feeling slightly worse and recalibrates what normal is. That recalibration is exactly why a recorded baseline beats memory.

What to track across a block

Direction, over weeks

Is this athlete's baseline itself drifting? A rolling average moving steadily down across a build is more informative than any single day within it.

Rebound after easier days

Healthy accumulation still bounces back on a lighter week. A failure to rebound is the more meaningful observation.

Motivation drift

Often one of the earliest things to move, and invisible to every sensor. This is the strongest argument for collecting self-report alongside device data.

Engagement

An athlete who quietly stops checking in is frequently an athlete who is struggling. Missing data is data.

What this is not

The roster problem

Catching slow accumulation requires looking at the same athlete repeatedly over weeks. That is straightforward for one athlete and does not scale by hand: reviewing thirty athletes' four-week trends every week is not a habit anybody sustains.

This is the practical case for prioritisation. Something reads the whole roster continuously and surfaces the handful whose baseline has actually drifted, so your attention goes to them rather than being spread thinly across everyone.

Frequently asked

How can I tell normal training fatigue from something more?

Duration and rebound are the practical discriminators. Expected fatigue resolves with easier days; the kind worth investigating persists through them. That distinction is a prompt to ask questions and, where it continues, to involve a medical professional — not something a coach or an app determines.

Which signal moves first?

It varies by athlete and by cause. Self-reported motivation and mood often move first for non-training stress, while sleep and resting heart rate tend to lead for physical accumulation. This is why several signals read together beat any single one.

Can software detect overtraining?

No, and be wary of anything claiming otherwise. Software can show that an athlete's signals have moved away from their own normal. Interpreting why is coaching judgement, and anything health-related is a medical question.