ACWR Explained: Using Acute:Chronic Workload Ratio Without the Math Errors

The acute:chronic workload ratio (ACWR) is one of the most used — and most misused — metrics in athlete monitoring. It promises something every coach wants: a simple number that tells you whether an athlete's training load is in a safe range or spiking toward injury risk.

Used correctly, ACWR is a genuinely useful flag. Used carelessly, it produces false alarms, false reassurance, and decisions that quietly harm athletes. This guide explains what ACWR actually is, the most common calculation mistakes, and how to use it in a way that survives contact with a real season.

What ACWR actually measures

ACWR compares an athlete's acute load (typically the last 7 days) with their chronic load (typically the last 28 days):

ACWR = acute load ÷ chronic load

The idea is simple: if your most recent week is much heavier than what your body is accustomed to (ACWR well above 1.0), you are loading into unfamiliar territory. If it is much lighter (well below 1.0), you may be detraining. The commonly cited "sweet spot" is roughly 0.8 to 1.3.

For the foundations — what counts as load, session RPE versus GPS-derived metrics, and how to collect the data — start with our complete guide to athlete load monitoring.

The four most common math errors

1. Mixing absolute and relative load

The classic mistake: comparing an athlete's current week against a chronic average that includes their off-season. A rugby player returning from a six-week break will always show an alarming ACWR — not because the program is dangerous, but because their baseline collapsed. ACWR is only meaningful against a chronic window that reflects comparable training conditions.

Fix: interpret ACWR alongside the raw chronic load, and re-baseline after breaks, injuries or major program changes.

2. Trusting the ratio while ignoring the numerator and denominator

An ACWR of 1.0 means nothing on its own. A squad member with an acute load of 400 AU and chronic load of 400 AU is in a very different situation from one at 4,000 AU and 4,000 AU. The ratio hides the magnitude.

Fix: always read ACWR as a ratio on top of absolute load, never instead of it.

3. Using rolling averages on volatile, small samples

The traditional 7:28-day rolling average treats all days equally and reacts slowly, while the EWMA (exponentially weighted moving average) method reacts faster to recent spikes. With small or patchy data — athletes who miss sessions, missed wellness entries, rest days logged as zero — both methods produce noisy, unstable values.

Fix: ensure load data is complete and consistent before trusting the ratio. A missing session is not a zero-load day; it is missing data, and treating it as such will distort the window.

4. Treating the sweet spot as a law

The 0.8–1.3 range came from cohort studies in specific sports with specific data quality. Later research — notably work led by Impellizzeri and colleagues — has criticised ACWR's statistical foundations and shown the ratio can add little beyond looking at absolute load change itself. Athletes get injured outside the range for reasons ACWR cannot see, and stay healthy inside it while chronically overloaded.

Fix: treat ACWR as one flag among several, not a decision rule.

How to actually use ACWR well

1. Collect consistent load data. Session RPE × duration every session, plus GPS where available. Consistency beats sophistication.
2. Pair it with wellness. A spike plus poor wellness scores is far more meaningful than either alone. See our guide to wellness questionnaires athletes actually answer.
3. Watch trends, not single days. One high reading is noise; three weeks of drift above 1.3 is a conversation with the coaching staff.
4. Individualise thresholds. A 19-year-old academy athlete and a 30-year-old with 200 professional matches do not share a safe range.
5. Act on the conversation, not the number. The metric's job is to prompt the right question at the right time — "why has Jordan's load jumped 40% this week?" — not to auto-regulate the program.

Where software earns its keep

The maths of ACWR is trivial; the discipline around it is not. Doing it well means load data captured every session, chronic windows that re-baseline after breaks, wellness scores sitting next to the number, and flags that reach the right staff member before the next session is delivered.

That is a data pipeline, not a spreadsheet. Platforms like Prospect calculate load and ACWR automatically from your sessions and check-ins, flag at-risk athletes squad-wide, and give every staff member the same view — so the ratio gets used the way the research intended: as an early-warning conversation starter.

Want to see it on your own squad? Start for free and have ACWR working before your next training block.

---

Related reading: Athlete Load Monitoring Guide · Wellness Questionnaires That Athletes Actually Answer · Periodisation for Strength & Conditioning