Yes. A running watch can flag cardio fatigue before a marathon, though it cannot diagnose it.
Cardio fatigue here means accumulated training tiredness where your heart works harder for the same pace. Watches combine overnight heart signals, sleep, and recent load into readiness or fatigue scores. Those trends help you choose hard training or rest in race weeks.
Medical information disclaimer: This article is for general educational purposes only and does not provide medical advice, diagnosis, or treatment. Always consult a physician or other qualified health professional about symptoms, medications, tests, or treatment decisions.
Table of Contents
- What your watch actually scores
- Which warning pattern matters most
- How should marathoners check it?
- When should you ignore a red score?
What your watch actually scores
Garmin gives Training Readiness as 1–100, from poor to prime, using recovery time, sleep history, training-load trends, HRV status and stress to advise hard training versus rest, according to Garmin's explanation of Training Readiness. Garmin says its HRV Status tracks overnight beat-to-beat variation against a personal baseline, then interprets it with sleep, load, recovery time and Body Battery.
COROS takes a load-based route. Its EvoLab compares 7-day Load Impact with 6-week Base Fitness to produce a 0–100 Fatigue score plus a post-workout recovery timer, and warns that training while too tired raises injury risk, according to COROS help on EvoLab fatigue. Apple Support says Apple Watch estimates VO2 max as Cardio Fitness during Outdoor Walk, Outdoor Run or Hiking workouts.
Which warning pattern matters most
Single mornings mislead. Coaches reviewing runner studies point to a 7-day HRV average below your normal for 4 or more days, with rising resting heart rate, failure to rebound, or high HRV while paces slip, according to RunnersConnect's review of HRV trends for runners. In one 9-week runner study they cite, single-morning HRV scored 0.17 out of 1 for usefulness versus 0.76 for the weekly average.
The same multi-signal idea worked under heavy overload. Triathlon Magazine, reporting a European Journal of Sport Science study, says 24 athletes did 3 weeks of normal training, 2 weeks of about 80% overload, and 1 week of recovery. Half developed functional overreaching with slower time trials, and nighttime heart rate plus an effort index and readiness score identified them with over 90% accuracy.
How should marathoners check it?
Build a baseline first. Wear the watch for sleep for several weeks, keep workout heart-rate data consistent, and note illness, alcohol, travel, and poor sleep.
Then scan for agreement across signals during peak training and taper: Treat one bad night or one red score as noise. Act when two or more signals point the same way for several days.
- 7-day HRV average stays low for 4+ days
- resting heart rate climbs while usual paces feel harder
- readiness or fatigue score stays poor after easy days
- soreness, heavy legs, or poor sleep match the data
When should you ignore a red score?
Wrist estimates need weeks of baseline and shift with short-term disruptors. Apple Support says illness, alcohol, poor sleep, and heart-rate-limiting drugs can affect estimates and can overestimate VO2 max. RunnersConnect advises the same caution about isolated HRV dips.
So marathoners should ease off only on multi-day flags plus felt fatigue or soreness, not one red score. If flags clear after sleep and easy days, resume the plan. If low HRV, high resting heart rate, poor readiness, and heavy legs persist into race week, cut intensity and protect the start line.