Training Monotony
Also known as: Foster Monotony, Daily-Load Monotony, Monotony Index
A scalar measure of how uniform your daily training loads are within a week — high when every day is similar, low when the week mixes hard and easy days. Monotony was introduced by Carl Foster (1998) as part of his training-monitoring framework alongside sRPE and AU, where it acts as a multiplier on weekly load to produce 'strain'. The idea is straightforward: the same weekly volume distributed as 7 medium days is harder to recover from than the same volume distributed as 3 hard days + 3 easy days + 1 off day.
Formula
monotony = mean(dailyAU over 7 days) ÷ standardDeviation(dailyAU over 7 days)
Where dailyAU is the daily Arbitrary Units load (sRPE × duration in minutes, summed across sessions in the day). Days with zero load count as zero, not omitted. Useful interpretive bands:
monotony < 1.5 — varied week (clear hard/easy contrast)
monotony 1.5-2.0 — moderate uniformity (typical productive training)
monotony > 2.0 — flat distribution (Foster's original threshold for elevated risk)
A full rest day in the week pushes the standard deviation up and the monotony down — which is part of why rest days work as more than just recovery.Example
Athlete A trains 7 days at 350 AU each: mean 350, SD 0 → monotony undefined (or infinity). In practice the system clamps SD to a small floor to keep the number finite, and the verdict is the same: every day looks identical, monotony is maximal. Athlete B trains 6 days at varied loads (600, 200, 400, 500, 100, 650) plus 1 rest day at 0: mean = 350, SD ≈ 245, monotony ≈ 1.43. Identical weekly load (2,450 AU), very different physiological week — Athlete B's hard/easy contrast lets recovery actually happen between hard days.
How Afitpilot Uses This
Afitpilot doesn't currently compute or display monotony on the session card or weekly view. The chronic/acute load chart and the ACWR metric capture the volume-and-rate-of-change story; monotony captures the within-week distribution story, which is complementary but not yet surfaced. It's a strong candidate for the load-trend chart's next iteration, especially because it explicitly answers a question athletes ask coaches all the time: 'why am I more tired this week when the volume is the same as last week?' Practical translation that monotony gives now: if your weeks are blurring together with no clear hard / easy / off pattern, the same load is costing more recovery than it should — break the week up.
Monotony in practice
| Who / Context | Value | Note |
|---|---|---|
| Foster's elevated-risk threshold | monotony > 2.0 | Derived from soccer/basketball; treat as a starting reference, not a verdict |
| Typical productive training week | monotony 1.4-1.9 | Clear hard/easy contrast with at least one rest day |
| Endurance base block | monotony 1.8-2.4 | Aerobic uniformity is the point; pair with low absolute load |
| Cost of a single rest day | Drops monotony by 0.2-0.4 in most weeks | The cheapest way to break a flat week |
| Polarized-training cadence | monotony 1.0-1.3 by design | 80/20 easy/hard creates strong day-to-day variance |
| What two athletes with equal load can differ by | 2-3x in monotony given different scheduling | Same volume, very different recovery cost |
Known Limitations
- •Monotony is mathematically undefined when load variance is zero (every day identical), and explodes when one day dominates. Real-world implementations clamp the SD floor or cap the metric to keep it interpretable.
- •The 7-day rolling window is convention. A 5- or 10-day window can produce more or less noisy values depending on the athlete's training rhythm. Foster's original work used calendar weeks because that's what athletes plan around.
- •Monotony treats all training days as interchangeable AU. A week with 5 strength days at 300 AU and 2 cardio days at 600 AU may compute identical monotony to a week with 7 mixed-modality days of comparable load — but the recovery cost is very different. The metric is modality-blind.
- •High monotony is not always bad. Endurance athletes in base-building blocks deliberately run 5-7 days of similar Zone 2 work, accepting elevated monotony in exchange for aerobic adaptation; the strain metric (monotony × weekly load) is the more honest read in those phases.
- •The Foster thresholds (monotony > 2.0, strain > 6,000) are derived from team-sport athletes and have not been replicated for strength sports or recreational training. Trends within an athlete are more reliable than crossing a textbook threshold.
Science Context
Carl Foster's 1998 paper 'Monitoring training in athletes with reference to overtraining syndrome' introduced monotony and strain together as a packaged framework for tracking overreaching risk via the same sRPE inputs already collected for AU. Subsequent work (Foster et al. 2001 on competitive cyclists; Halson 2014 systematic review on training-monitoring tools) confirmed that monotony × weekly load (strain) tracks subjective complaints and short-term illness in team-sport contexts; the strength-sport evidence is much thinner. The framework's value is the cheapness: same daily sRPE inputs, two extra scalar metrics, no additional athlete burden. The standard caveat applies — monotony is descriptive, not predictive of individual injury or illness, and the published thresholds are sport- and population-specific. Afitpilot's roadmap candidate for surfacing monotony fits this honest framing: show the metric and its trend; do not auto-modify a plan from a single high week.