Training
Tired or overtrained? Reading fatigue before it wrecks your season
Normal training fatigue, functional overreaching, and overtraining syndrome are three different problems with three different fixes. Here is how to tell which one you have.
Three different things get called overtraining, and only one of them is overtraining. Normal training fatigue is heavy legs that come good after an easy day or two — the fatigue you signed up for. Functional overreaching is a deeper hole, dug on purpose or by accident, that takes one to two genuinely easy weeks to climb out of. Overtraining syndrome is rare, serious, measured in months, and not something anyone diagnoses from one bad week. And most age-group athletes who think they are overtrained are simply under-recovered: not enough sleep, too much life, not enough food for the load they are carrying. Telling these apart is most of the skill.
Three states, one word
| State | Usual cause | Time to clear | What performance does |
|---|---|---|---|
| Normal training fatigue | The last hard session or a big weekend | 1–3 easy days | Back to normal after rest |
| Functional overreaching | A deliberate overload block, or a ramp that got away from you | 1–2 genuinely easy weeks | Down during the block, then back, sometimes better |
| Non-functional overreaching | Overreaching that never got resolved | Several weeks to a few months | Flat or down, and rest does not produce a bounce |
| Overtraining syndrome | Months of unresolved overload, usually with poor sleep, life stress, or under-fueling stacked on top | Months, sometimes a full season | Down and stays down despite extended rest |
The uncomfortable part: these boundaries are drawn after the fact. There is no test that tells you on Tuesday which one you are in. You find out by how long it takes you to come back. That is not a failure of your monitoring — it is how the condition is defined, in the sports science literature as much as in your training log.
Which is why the practical question is never "am I overtrained?" It is "have I responded to this yet, and how long has it been?" An athlete who takes three easy days and comes back sharp was tired. An athlete who takes ten easy days and is still flat is somewhere further down the table, and the response is more rest, not more diagnosis.
Before you call it overtraining, check the three boring things
Genuine overtraining syndrome is uncommon, and it is disproportionately reported in athletes training a lot more than most age-groupers manage. Under-recovery, on the other hand, is everywhere. Three causes account for the large majority of "I think I'm overtrained" weeks.
Sleep. Chronic short sleep produces almost the entire symptom list on its own: heavy legs, elevated morning heart rate, poor mood, low motivation, worse session quality, more frequent illness. If you have been sleeping six hours a night for a month, you have not discovered a training problem.
Life stress. Your body does not keep separate ledgers for a hard interval session and a difficult quarter at work. A new baby, a house move, a bad stretch mentally — all of it competes for the same recovery capacity. The week that worked in March can be too much in September with nothing about the training having changed.
Fueling. Persistently eating less than the training demands produces fatigue that looks exactly like overtraining, plus effects that are more serious than tiredness — disrupted hormones, weakened bones, suppressed immune function. This is the pattern described as relative energy deficiency in sport (RED-S), and it deserves to be ruled out early rather than late, particularly if training volume went up and body mass went down at the same time.
If any of those three is obviously off, fix it before you rearrange your training. It is the cheaper experiment and it is more often the answer.
The signals, ranked by how much they deserve your trust
Not all fatigue signals are equally informative. Ranked roughly from most to least trustworthy:
1. Performance at a fixed effort. The most reliable signal by a distance. Not "how fast did I run" — a bad race has a hundred causes — but a repeatable, moderate reference effort you can execute in almost any state. A 20-minute steady run at a fixed heart rate, or a standard tempo bike segment. Compare pace or power at the same internal effort over weeks. Real, persistent decline here is the signal that carries the most weight.
2. How hard easy pace feels. Closely related and almost as good. When your usual easy pace requires noticeably more heart rate or more concentration than it did two weeks ago, and stays that way, something has accumulated. This is also the earliest thing most athletes notice, well before any device tells them.
3. Sleep quality. Not hours in bed but whether you are sleeping through. Waking at 3am with a racing heart during a heavy block is a genuine flag, and it is a nasty one because it removes the very thing that would fix the problem.
4. Motivation and mood. Losing interest in sessions you normally enjoy is a real physiological signal, not a character defect. Persistent irritability, flatness, and dreading the start of easy sessions all belong on the list. Mood tends to fall before performance does.
5. Morning resting heart rate and HRV, as a trend. Useful only as direction over weeks, and useful mostly for confirming what the four signals above already told you. Never as the first alarm, and never from a single morning.
Notice that four of the five are things you can feel. The measured ones sit at the bottom, and that ordering is deliberate.
Signal, benign explanation, and when to worry
Almost every symptom on the overtraining list has a boring explanation that is more likely than the alarming one. What separates them is duration and company: how long has it lasted, and how many other signals is it traveling with?
| Signal | Usually just means | Worth acting on when |
|---|---|---|
| Morning resting HR up several beats | You raced or went long yesterday, drank alcohol, slept badly, or the room was warm | It stays 5 or more beats above your own normal for a week or more, with no obvious cause |
| HRV down | Yesterday was hard, or you woke up at a different time, or you took the reading standing up | The multi-week average trends down while training load is flat or rising |
| Heavy legs | Normal, especially 24–48 hours after a big session | They do not clear after three genuinely easy days |
| Easy pace feels hard | Heat, humidity, altitude, a poor night, the start of a cold | It persists for two weeks at cooler temperatures and normal sleep |
| Broken sleep | Life, caffeine, screens, a late hard session | Repeated 3am waking during a heavy block, especially with elevated morning HR |
| Low motivation | The boring part of a build block; a long stretch without a race | It persists into a rest week, and covers things you normally enjoy |
| Irritability, low mood | An ordinary bad week | Weeks long, noticed by other people, not lifted by an easy week |
| Frequent minor illness | Winter, or small children | Three or more infections in a couple of months during heavy training |
| Appetite loss after hard sessions | Common, transient | Persistent, with unintended weight loss |
| Higher HR at a given pace | Heat, dehydration, caffeine, fatigue | Persists in cool conditions across several weeks |
| Lower max HR in intervals, cannot reach normal numbers | You backed off; the session was poorly paced | Repeatedly cannot get heart rate up while feeling wrecked — a classic deep-fatigue pattern |
The last row deserves a note, because it surprises people. Deeply fatigued athletes often cannot drive their heart rate to normal peak values in a hard session. Feeling terrible while your watch says you are barely working is a more meaningful pattern than a single high resting reading.
HRV, honestly
Heart rate variability is a real physiological measurement and a genuinely noisy one. Two things are true at once, and the marketing tends to acknowledge only the first.
It carries real information about the balance between the stress and recovery branches of your nervous system, and its multi-week direction correlates loosely with how well you are absorbing training. Used as a trend, alongside everything else, it adds something.
And a single day's reading tells you close to nothing. HRV moves with measurement position, time since waking, breathing rate, alcohol, a heavy dinner, hydration, room temperature, and where you are in your menstrual cycle. Day-to-day swings of a size that would look alarming on a chart happen in athletes who are perfectly fine. Compare a seven-day average against your own rolling baseline, ignore individual mornings, and be aware that the baseline itself shifts across a season.
There is a third problem worth naming, because it does real damage: checking a readiness score every morning and letting it decide the day is its own pathology. It teaches you to distrust how you actually feel, it makes a good session feel unauthorized and a bad number feel like permission to skip, and the anxiety it generates is itself the kind of stress that lowers the number you are anxious about. Plenty of athletes have improved their sleep and their training simply by not looking. If a daily score is making you worse, the tool is not worth its cost.
The load side, in plain English
The numbers cannot see your sleep or your job, but they are good at one specific thing: telling you whether what you have been doing lately is far out of line with what you are adapted to.
That is the comparison behind acute versus chronic load — recent training over roughly the last week set against your accumulated training over roughly the last six weeks, usually labeled ATL and CTL. The ratio between them, the acute:chronic workload ratio, is popular in injury-risk discussions and its research base has drawn serious criticism, so treat it as a rough gauge of "how unusual is this week for me" rather than a risk score with real predictive power. The full picture of what those numbers measure and where they mislead is in training load explained.
The more useful number is ramp rate: how fast your accumulated load has been climbing. Roughly 3–5 points of CTL a week is a build most athletes absorb. Sustained ramps above about 8 are where injury and illness cluster in practice. Neither figure comes from a controlled trial — they are accumulated coaching convention — but they are consistent enough to plan around, and a three-week ramp above 8 is a solid explanation for fatigue that arrived without any obvious single cause.
This is the part software should carry for you, because it is arithmetic and it is easy to miss in the moment. PaceBeats tracks the ramp against what you are actually adapted to and re-plans the week when the gap opens up, which is a lot cheaper than noticing three weeks later that the build got away from you.
Two blind spots are worth knowing. A stale threshold makes the chart look calm while every session quietly costs more than it is priced at. And a week that hits its planned total by cramming four sessions into three days is harder than the same total spread across five, which no load model sees.
What to actually do about it
Three responses, matched to three different depths.
Two to three genuinely easy days. For ordinary training fatigue: heavy legs, one flat session, a high morning heart rate the day after a long ride. Keep moving — 30 to 45 minutes of properly easy work maintains rhythm without adding a debt — and drop all intensity. Most fatigue that gets called overtraining resolves here. Note that "easy" means easy: if the recovery days are only slightly softer than normal days, they do not count, and this is where most athletes get it wrong.
A full week down. For fatigue that has lasted one to two weeks, or shows up as multiple signals at once, or follows a three-week block you know was too steep. Cut volume to roughly half, remove intensity entirely, keep frequency so you do not lose the habit, and eat normally rather than matching food to the reduced load. Recovering costs energy. If a week down does not produce a clear bounce, take a second one. Two easy weeks on a good base cost you almost no fitness, and they cost a great deal less than a ruined September.
See a doctor. Not a coaching problem. Warranted when a resting heart rate stays clearly elevated for weeks, sleep is persistently disrupted, you have picked up infection after infection, mood has genuinely collapsed, or you have taken a proper break and still feel wrong. The reason is important: several conditions look exactly like overtraining and need treatment, not rest. Iron deficiency and anemia, thyroid problems, post-viral fatigue, sleep apnea, and low energy availability all present as an endurance athlete who is inexplicably slow and tired. Blood work is a faster route to the answer than another month of guessing, and if the answer is under-fueling, a doctor and a dietitian are the right people.
The prompt for all three is the same: not a bad day, but a pattern that persists after you have given it the obvious fix.
Getting back
Coming out of a hole is quieter than falling into one, and the order is fairly predictable. Sleep and mood usually recover first, then how easy pace feels, then top-end sharpness last. Do not judge whether the rest worked by how a hard session goes on day one back — being flat in the first hard effort after an easy week is completely normal and reverses in a few days.
When you restart, restart lower than where you stopped. Returning to the exact week that dug the hole is a reliable way to dig it again. Take 20 to 30 percent off, hold that for a week, and build from there. If you are rebuilding after missed sessions, how to handle a training plan after missed workouts covers the rebuild itself in more detail.
And keep the record. The single most useful thing for next season is a note of what the week looked like before the fatigue arrived: the ramp, the sleep, what else was happening in your life. Overtraining research is comparatively thin and highly individual, which means your own history is genuinely better evidence about you than any general guideline — but only if you wrote it down.
Questions athletes ask
How do I know if I'm overtrained or just tired?
Time is the test. Normal training fatigue clears after one to three genuinely easy days. Functional overreaching takes one to two easy weeks. True overtraining syndrome is measured in months and is rare, especially at age-group training volumes. So take two or three properly easy days first: if you come back sharp, you were tired. If two weeks of real rest leave you flat, with an elevated resting heart rate, disturbed sleep, and low mood, that is worth a doctor's appointment rather than a training tweak — several medical causes, including iron deficiency and thyroid problems, look identical to overtraining.
How long does overreaching take to recover from?
Functional overreaching — the deliberate or accidental deep-fatigue state after a hard block — typically clears with one to two weeks of genuinely easy training. Cut volume to roughly half, remove intensity entirely, keep the sessions short and easy rather than stopping altogether, and eat normally rather than matching food to the smaller training load. If a single easy week does not produce a clear bounce, take a second one. Two easy weeks on a solid base cost very little fitness. Fatigue that persists past several weeks of real rest has moved beyond overreaching and should be investigated medically.
Is a high resting heart rate a sign of overtraining?
Only as a sustained trend, not as a single reading. Morning resting heart rate rises for many ordinary reasons: a hard session the day before, alcohol, poor sleep, a warm bedroom, dehydration, the start of a cold. One elevated morning means very little. What is worth acting on is a resting heart rate that sits about 5 or more beats above your own normal for a week or longer with no obvious explanation, especially alongside other signals such as easy pace feeling harder or broken sleep. Compare against your own baseline, since normal resting heart rate varies enormously between people.
Should I train through fatigue?
Sometimes, and the distinction is specific. Ordinary heavy legs during a build block are expected and training through them is normal and often necessary — that is how overload works. What you should not train through is a pattern: easy pace feeling hard for two weeks, a resting heart rate that stays elevated, broken sleep, repeated illness, or motivation that does not return during a rest week. A useful rule is to start the warm-up and reassess honestly after 15 minutes. If it comes good, do the session. If it does not, convert it to easy work rather than grinding out a poor version of the planned one.
Can you get overtrained on 8 hours a week?
True overtraining syndrome is unlikely at that volume, but being genuinely under-recovered is very possible and produces the same symptoms. Recovery capacity is not set by training hours alone — sleep, work stress, family demands, and whether you are eating enough for the load all determine how much training you can absorb. Eight hours a week on six hours of sleep, a stressful job, and an under-fueled diet can be more than your body can handle, while the same eight hours in a calm month is easy. If you feel wrecked on moderate volume, examine sleep, life stress, and fueling before restructuring the training.
Next step