A modeled estimate from recent training load, not a direct measurement of how tired or recovered you feel.
Physiological Background
Training fatigue accumulates over time and dissipates through recovery. This follows the fitness-fatigue model (Banister, 1975), where each workout adds to both fitness and fatigue, but fatigue decays faster than fitness gains. [1]
The Fatigue metric represents accumulated fatigue from recent training, with more recent workouts contributing more heavily. This helps identify:
- Overreaching risk - when fatigue climbs too high
- Taper effectiveness - fatigue should drop before races
- Training consistency - stable fatigue indicates regular training
- Recovery status - how much fatigue remains from recent work
Formula
Fatigue is calculated as the weighted sum of training load over the past 21 days, with exponentially decaying weights: [2]
Where:
- di
- Distance in meters on day i
- Ei
- Effort value on day i
- si
- Secondary distance (strength work) on day i
- Di
- Decay factor for day i
Decay Factors
The decay factors model how fatigue dissipates over time. As in the fitness-fatigue model, fatigue fades exponentially: every day a workout keeps the same share (87%) of the weight it had the day before. Today's workout has full impact (1.0), while a workout from 20 days ago contributes only about 7% of its original load: [1]
Where:
- i
- Days ago (0 = today, up to 20)
- 0.135
- Decay rate per day: a time constant of about 7.4 days, so a workout's weight halves roughly every 5 days
The decay curve follows research on glycogen replenishment, muscle repair, and neuromuscular recovery. Most acute fatigue clears within 7 days, but residual effects persist for 2-3 weeks.
A rule of thumb
If every day were the same, Fatigue would settle at one day's load times the sum of the 21 decay factors, 7.46. A day's load is its kilometres times its Effort, so with the week spread evenly:
| Weekly km | E = 1.2 | E = 1.4 | E = 1.6 |
|---|---|---|---|
| 30 | 38 | 45 | 51 |
| 50 | 64 | 75 | 85 |
| 70 | 89 | 104 | 119 |
| 90 | 115 | 134 | 153 |
Real weeks are not even: a long run yesterday weighs more than one six days ago, so daily Fatigue swings around this level (figure 3.2). Still, it says what a week of training settles into.
How fast Fatigue responds
After a lasting change in training, Fatigue covers about 65% of the way to its new level in one week, 90% in two and all of it in three, when the oldest days leave the window. The other way round, a week off takes away about 65% of it. That is why a taper of two or three weeks lowers Fatigue clearly, while fitness, built over months, holds.
What counts
- Runs: distance in metres times Effort.
- Strength and other training: its secondary distance in metres, added as it is, so 1,000 m of secondary distance weighs like a kilometre at Effort 1.0.
- Planned runs: at their planned pace, or the default Z2 pace without one, so you see where a plan takes your Fatigue before you run it.
- Several workouts on one day: all of them.
When Fatigue is shown
Fatigue needs an entry on each of the last 15 days: a run, other training or a rest day. With gaps the app shows nothing rather than a number that would read too low, since a missing day may be a run that was never logged. Log rest days as workouts in the Rest category; plan templates do it for you. Fatigue is rounded to whole numbers.
Interpreting Fatigue Values
| F | Load | Meaning |
|---|---|---|
| < 30 | Low Load | Recovery phase, detraining risk if prolonged |
| 30–50 | Moderate Load | Maintenance training, good for base building |
| 50–70 | High Load | Peak training, monitor for overreaching |
| > 70 | Very High Load | Risk of overtraining, consider recovery |
Note: These ranges are individual. Athletes with years of training may handle higher fatigue, while beginners should stay conservative. Track your personal patterns over time.
Using Fatigue for Race Preparation
These metrics help you plan training load during peak phases leading up to a race. The key principle: avoid exceeding fatigue levels significantly higher than your previous training peaks.
When building toward a goal race:
- Review your fatigue values from previous successful training blocks
- Use those peaks as a ceiling - don't exceed them by more than 10-15%
- Build gradually toward that ceiling over several weeks
- Allow fatigue to drop during taper (typically 30-50% reduction)
Pushing fatigue far beyond what your body has previously handled increases injury risk and often leads to arriving at race day fatigued rather than fresh. Progressive overload means small, sustainable increases - not dramatic jumps that overwhelm your recovery capacity.
Sources & further reading
Scientific References
These sources provide the scientific background discussed in this article. The formulas and coefficients used by Running Browser are described above, including their assumptions and limits.
- Modeling elite athletic performance
Physiological Testing of the High-Performance Athlete · Library record
- A new approach to monitoring exercise training
Journal of Strength and Conditioning Research