What exactly is training monotony?

Monotony is the mean of daily training load divided by its standard deviation, computed over a window (usually 7 days). A value near 1 means high variance — clear hard and easy days. A value above 2 means low variance — every day looks similar. The metric was introduced by Carl Foster in 1998 as a workload distribution indicator and has been validated across multiple sports.

What is training strain?

Strain is weekly training load multiplied by monotony. It combines the total amount of training with the distribution pattern. A week with 4000 TRIMP and monotony of 1.2 has strain of 4800. A week with 3000 TRIMP and monotony of 2.0 has strain of 6000 — lower total load but higher strain, and usually the riskier week.

Why does monotony matter separately from volume?

Because the body adapts to variable stimuli better than to constant ones, and because hard days need easy days to compensate. A week of consistent medium-hard days fails to give any muscle or system a true recovery window, even if the total volume is moderate. Two weeks of such monotonous training is usually enough to produce measurable overreach markers in trained athletes.

What's a high-monotony threshold I should care about?

Foster's original thresholds: monotony above 2.0 is a warning sign, and strain above a personal baseline (varies by athlete) flags elevated overreach risk. These aren't absolute — competitive athletes in peaking blocks sometimes tolerate monotony of 1.8 to 2.2 for short periods. The principle is that sustained high monotony over multiple weeks is the risk.

Does ACWR replace monotony and strain?

No. ACWR measures whether recent load is climbing relative to chronic baseline. Monotony and strain measure whether the shape of the week has enough variance to be recoverable. They're complementary signals. A week can have acceptable ACWR and unsafe monotony, or vice versa. Good overtraining surveillance uses all three together.

Monotony and Strain: The Overtraining Signal Wearables Miss

You trained hard Monday. You trained hard Wednesday. You trained hard Friday. You took Saturday off. Your ACWR is sitting at 1.1, which is green. Your weekly volume is close to your normal. Everything looks fine.

Meanwhile, you’ve been training exactly this way for three weeks, and you’re starting to feel flat. Your sleep quality is gradually degrading. Your top sets are getting harder. Your HRV is trending down.

You’re overtraining. ACWR didn’t catch it. Weekly volume didn’t catch it. What’s missing is a signal that tracks the structure of the week, not just the total.

That signal is monotony, combined with strain. This post is about what they are, why they matter, why consumer wearables miss them, and how they fit into the broader adaptive training intelligence stack.

The Monotony Problem

Carl Foster introduced the concepts of training monotony and strain in a 1998 paper in the Journal of Strength and Conditioning Research. The starting observation: in athletes he was studying, overtraining syndromes didn’t correlate cleanly with weekly volume. Athletes with lower volumes sometimes overreached; athletes with higher volumes sometimes adapted without issue. What tracked better was the shape of the week — specifically, how much variance there was in daily load.

A week of consistent medium-hard training lacks recovery windows. The body never gets a chance to clear systemic fatigue, replenish glycogen reserves, or resolve low-grade inflammation. Any given session in isolation is unremarkable. The cumulative pattern across days and weeks is what produces overreach.

A week with deliberate variance — hard days, easy days, a true off day — gives the body the pulse of stress-and-recovery that drives adaptation. Same total volume, different distribution, different physiological outcome.

The insight was simple but load-bearing. Foster formalized it into two metrics.

Monotony. The mean of daily training load divided by its standard deviation across a 7-day window. If every day is identical, the standard deviation is zero and monotony is infinite (in practice, capped). If daily loads vary widely (hard, easy, off, hard, easy, off, easy), monotony is low — closer to 1.

Some numerical intuition:

Monday 6, Tuesday 0, Wednesday 6, Thursday 0, Friday 6, Saturday 0, Sunday 0. Mean 2.6, SD 2.9, monotony 0.9.
Monday 4, Tuesday 4, Wednesday 4, Thursday 4, Friday 4, Saturday 4, Sunday 0. Mean 3.4, SD 1.5, monotony 2.3.
Monday 3, Tuesday 3, Wednesday 3, Thursday 3, Friday 3, Saturday 3, Sunday 3. Mean 3.0, SD 0.0, monotony infinite (problematic).

The first pattern has clear hard/easy structure. The second is the “consistent medium-hard every day” pattern that’s risky. The third — perfectly consistent daily load — is either a very early block, a rehab protocol, or a sign of a program that needs variance injected.

Strain. Weekly training load multiplied by monotony. It combines the total dose with the distribution.

Volume 18 with monotony 1.0: strain 18. Low risk.
Volume 18 with monotony 2.5: strain 45. Higher risk.
Volume 30 with monotony 1.2: strain 36. Moderate risk.
Volume 30 with monotony 2.0: strain 60. High risk.

The insight strain captures: two weeks can have identical total volume but very different physiological cost, because the distribution matters. High strain — the combination of high volume and high monotony — is where overtraining syndromes actually appear in Foster’s data.

How Monotony Catches What ACWR Misses

ACWR measures whether this week’s load is elevated relative to recent weeks. It’s a trend signal. But a week can be in the normal trend band (ACWR ≈ 1.0 to 1.2) while being internally overtrained-prone, because the shape of the week has drifted.

Imagine an athlete running a block with a “hard Monday/Wednesday/Friday, easy Tuesday/Thursday, off Saturday/Sunday” structure for four weeks. Monotony during those weeks is around 1.0 to 1.2 — good variance. ACWR is stable around 1.0.

In week five, the athlete gets a schedule change at work that pushes them to training every evening. Now it’s “moderate every day, no off days.” Weekly volume is about the same because the athlete dropped the intensity to accommodate the frequency. ACWR stays at 1.0 — no volume change, no ratio change. But monotony has jumped from 1.0 to 2.5. Strain has doubled.

ACWR would not flag this. The shape change — loss of variance — is invisible to a ratio-of-sums metric. Monotony catches it immediately. By week six or seven, the athlete is likely to show up in HRV, RHR, and subjective fatigue data. By week eight, they’re overreached. A monotony flag in week five could have prevented it.

The reverse also matters. An athlete might run a week with deliberately heavy volume — a peak week before a meet or a shock microcycle — that puts ACWR at 1.4 or 1.5. The volume is real, and the ACWR flag is appropriate to notice. But if monotony is at 0.9 — lots of hard/easy structure within the week — the strain value might be lower than in a seemingly-quiet week of constant medium training. A nuanced reading of all three metrics distinguishes the intentional peak from the slow accumulation.

Why Consumer Wearables Miss This

Monotony and strain require daily training load data. Most consumer wearables either:

Don’t ingest detailed session-level data from a lift tracker or training log, so they can’t compute daily load accurately.
Compute a proxy for daily training load from HR or activity minutes, but don’t expose monotony/strain.
Have the data but don’t surface the metrics, either because the product decision was to simplify or because monotony/strain didn’t make the feature cut.

The result: most dashboards show weekly volume, maybe ACWR, maybe a readiness score. Monotony is absent. Strain is absent. The athlete has to compute these mentally or with a spreadsheet, which almost no one does.

This is a gap that matters. Monotony and strain are more predictive of overtraining than most of the signals consumer dashboards do surface. An athlete with access to the metric sees overtraining patterns two to three weeks before they’d notice them from HRV or readiness alone.

What Counts as Daily Training Load

To compute monotony and strain, you need a daily training load number. Several conventions exist:

Session RPE × duration. Foster’s original method. Multiply the RPE of the session by its duration in minutes. A 60-minute session at RPE 7 = 420 load units. This is easy to log and widely used. The unit is arbitrary but internally consistent.

TRIMP (Training Impulse). Banister’s method. Integrates heart rate over the session, weighted by intensity. Requires a heart-rate-tracking wearable. More granular than session RPE but more data-intensive.

Hard-set equivalents. For strength training, counting hard sets (at RPE 7 or higher) per muscle group and summing or weighting across muscles produces a strength-specific load number. Different scale from cardio-oriented metrics, but consistent.

Hybrid. Some systems combine cardio load (TRIMP or HR-based) with strength load (set-count-based) using a conversion factor. This is appropriate for lifters who do both.

For monotony and strain calculations, what matters is consistency. The same unit across all days, so that the standard deviation calculation is meaningful. An athlete who mixes units across sessions or days gets spurious monotony spikes from unit mismatch rather than real variance changes.

The Variance-Over-Time Question

Monotony is usually computed on a 7-day window, but the principle applies on longer timescales too. An athlete can have good within-week variance but monotonous training over months — same three-workout pattern every week for six months, same loads, same exercises.

Within-week monotony is the standard metric. But thinking about over-time monotony — whether your weeks themselves vary in structure — is worth doing on a longer horizon. Block periodization, which deliberately varies intensity and volume across blocks, is partly about reducing over-time monotony.

Some modern approaches extend monotony computations:

Rolling 14-day or 21-day monotony for catching slower-developing variance collapses.
Per-modality monotony — cardio load monotony separate from strength load monotony — for athletes doing both.
Per-intensity-zone monotony — variance within zone 2, zone 4, zone 5 training — for endurance athletes whose overall load might be varied but whose high-intensity load might be monotonous.

These refinements are niche but useful for athletes with specific concerns. For most lifters, 7-day monotony on total load is the right default.

Strain as the Combined Signal

Monotony on its own is incomplete. A monotony of 2.0 at very low volume is usually fine — you’re doing a little bit every day and it’s not taxing. A monotony of 2.0 at high volume is the risk pattern.

Strain combines the two. Higher weekly volume multiplied by higher monotony produces higher strain, and strain is the single number that best summarizes overtraining risk in Foster’s framework.

In practice, strain is most useful as a personal baseline signal. Population strain thresholds exist but vary widely across sports. What’s more actionable: your own strain trend.

Week-over-week strain climbing steadily for 4+ weeks is a warning.
Strain spiking 50 percent above baseline for a single week is a flag (unless intentional peak).
Strain consistently in your normal band but with creeping monotony is an early warning that variance is collapsing.

A good training platform tracks personal strain baseline and surfaces deviations. It doesn’t just report a single strain value for the current week — it reports the current value in the context of the last 12 weeks of strain, flagging excursions.

When High Monotony Is Intentional

Monotony isn’t always bad. Some training contexts genuinely require monotonous patterns:

Early-block familiarization. New programs need a few weeks of consistent execution to produce stable progression data. Monotony is naturally higher during this period.

Rehab and return-to-training. After injury, monotonous light training is often the prescription. Building tolerance requires repeated exposure, not variance.

Rehearsal blocks. Before a competition, athletes often simulate competition demands with repeated exposure to specific patterns. Monotony climbs intentionally.

Base-building phases. Aerobic base building often uses consistent zone 2 training every day. Monotony is high by design, and the load is low enough that the risk is managed.

Peaking. The final 2 to 3 weeks before a competition often involve reduced volume at high intensity. Monotony can climb as the variety narrows.

In all these cases, a monotony alarm would be a false positive. A good system lets the user flag the context (rehab, peak, base) and adjusts thresholds accordingly.

How an Adaptive System Uses Monotony and Strain

An adaptive training platform that takes overtraining surveillance seriously:

Computes monotony and strain daily from the rolling 7-day window of training load.
Maintains a personal strain baseline over a longer window (6 to 12 weeks).
Surfaces the trend, not just the current value. A week’s strain in isolation is less informative than its position in the personal trend.
Triggers warning flags at specific thresholds: sustained monotony above 2.0 for multiple weeks, strain excursions above personal baseline, or combined flags with HRV/RHR trends.
Accepts user context for high-monotony periods (rehab, peak, base) to prevent false alarms.
Feeds monotony and strain into deload timing. When multiple overtraining signals cluster, advance the deload rather than waiting for the calendar.
Integrates with ACWR and readiness signals for the composite overtraining picture. No single signal prescribes; the cluster of signals is what drives decisions.

This is what “overtraining surveillance” looks like in a modern adaptive system. It’s not one alarm; it’s a constellation of alarms that together catch patterns that any single metric misses.

What to Do With Your Own Data

If your platform doesn’t compute monotony and strain, the metrics are approachable with manual tracking.

Minimum tracking. Log session RPE and duration for every session. At week’s end, compute daily load (RPE × minutes), mean and standard deviation across 7 days, and monotony (mean / SD). Multiply by total weekly load for strain.

Trend watching. Track monotony and strain weekly for 8 to 12 weeks. Your personal baseline emerges. Excursions from that baseline — monotony climbing above your normal, strain spiking — are the actionable signals.

Response. When monotony climbs into the 2+ zone for more than a week, inject variance. A true off day. A deliberately easy session where hard was scheduled. An intensity contrast that breaks the uniform pattern. Often this is enough to reset without needing a formal deload.

Strain response. When strain excursions happen, look at which component is driving them. Is it volume (real ramp) or monotony (shape collapse)? They need different responses. A volume-driven excursion might warrant a deload. A monotony-driven excursion often responds to a single injected easy day.

What This Isn’t

A few boundaries:

Not a prescription. Like ACWR, monotony and strain are context signals. They flag. The prescription comes from MAV and the program structure.
Not specific to one muscle group. Monotony and strain are whole-athlete metrics. If you want per-muscle overtraining signals, you need different tools (per-muscle MAV utilization, per-muscle recovery markers).
Not infallible. Some athletes tolerate high monotony for sustained periods without overreach. Population signals are population signals; individual variance exists.
Not useful without consistent daily logging. The calculations depend on accurate daily load. A week with two missed logs has spuriously inflated monotony. Consistent logging is the price of admission.

The Broader Point

Monotony and strain are the oldest overtraining metrics in the modern sports science toolbox. They predate ACWR, they’re simpler mathematically, and they’re arguably more predictive of actual overreach syndromes. Their absence from most consumer dashboards is a historical artifact, not a reflection of their value.

An adaptive training system that combines monotony, strain, and ACWR with per-muscle prescription logic and composite readiness signals produces a more complete picture than any single metric. The stack is the point. No individual signal is the whole answer; their combination is what catches the patterns worth catching.

For Omnio’s implementation, see /features/adaptive-training.

In Summary

Monotony = mean of daily load / standard deviation of daily load (7-day window).
Strain = weekly load × monotony.
Introduced by Foster (1998); validated across multiple sports.
Catches overtraining patterns that ACWR and weekly volume miss.
High monotony means low variance; sustained high monotony is the risk.
High strain = high volume × high monotony; strongest single overtraining predictor.
Consumer wearables mostly don’t compute or surface these metrics — a gap worth knowing about.
In an adaptive system, monotony and strain join ACWR as context signals. Prescription comes from MAV and program structure.

If your training platform shows you one overtraining number, ask what it’s actually measuring. If the answer is just weekly volume or just ACWR, you’re missing the signal that actually catches the slow-creep overtraining patterns. Monotony and strain are the fix.