Watch data and recovery: read trends, not one score

What a watch can record

Running watches and bands record pace, heart rate, cadence, elevation, sleep duration and heart-rate variability (HRV); some also produce “recovery”, “readiness” or “training load” scores. These numbers are useful for spotting trends and planning training, not for deciding on their own whether the body is healthy.

Optical heart rate can be distorted by cold, a loose strap, darker skin, arm movement or sweat. GPS drifts in urban canyons, forests and tunnels. Sleep staging is not the same as laboratory polysomnography. Algorithms and baselines differ between brands, so two readiness scores are not directly comparable.

One abnormal reading is not a conclusion

HRV is affected by sleep, alcohol, caffeine, infection, stress and training; one low day does not mean overtraining. Resting heart rate can rise with heat, dehydration, a late night or nerves. Treating a single reading as a body score encourages overreaction to normal variation.

A better approach is to build your own baseline over several weeks, measured at the same time under similar conditions. A sustained fall in HRV, a sustained rise in resting heart rate, worse sleep, fatigue, heavy legs or declining performance may justify adjusting load. Even then, a watch cannot diagnose overtraining.

Recovery is more than a number

There is no single biomarker for overtraining. Assessment combines training history, performance decline, fatigue, sleep and mood, and excludes other causes such as anaemia, thyroid disease, infection or depression. A device score cannot replace that assessment.

Sleep deserves attention, but the goal is not a perfect sleep score; it is regular, sufficient sleep and feeling awake during the day. Persistent insomnia, snoring with gasping, severe daytime sleepiness or weeks of fatigue warrant medical assessment.

Using the data well

Review trends once a week rather than refreshing all day. Put training logs, perceived fatigue, pain, sleep and races together. When data and felt experience disagree, start with the body and then look for an explanation. Do not change a tested race plan because of one readiness score, and do not use data to justify running through pain.

Mind privacy when sharing. Routes, heart rate and sleep are personal data; remove location, names and device identifiers from screenshots. Do not hand a complete training history to an unfamiliar third-party app without a reason.

Scope and limits

This page does not provide individual training-load advice, HRV interpretation or medical diagnosis. People with arrhythmia, chest pain, fainting, persistent insomnia, severe fatigue or known cardiovascular disease should consult a clinician; a device alert is not a substitute for emergency care.

Sources and scope

The concepts around overtraining, the absence of a single diagnostic marker and the need to exclude other causes follow a practical review in Current Sports Medicine Reports; advice on persistent insomnia follows the NHS insomnia page. Consumer-device data is a trend aid, not a clinical diagnosis. Checked 2026-10-28.