Acute:chronic workload ratio explained

The acute:chronic workload ratio, almost always shortened to ACWR, is the most cited number in load management and one of the most argued over. It is a deceptively simple idea: compare the work an athlete has done recently against the work they have been doing over a longer period, and read the gap between the two. A large gap means the athlete is doing something this week their body is not yet prepared for. That is the moment soft-tissue injury risk climbs.

It is worth being precise about the ratio, because most of the trouble with it in practice comes from people treating one number as a verdict. This piece sets out what the ratio measures, how to calculate it, the reference range that made it famous, and the serious methodological critiques that mean it should inform a conversation, never replace one.

What the ratio actually measures

Two windows sit at the centre of the calculation. The acute load is the work done in a short, recent window, conventionally the most recent seven days. The chronic load is a longer baseline, the rolling average of the weeks before it, that stands in for the fitness the athlete has built and the load their tissues have adapted to carry.

The ratio is acute divided by chronic-weekly. A value near 1.0 means this week looks like a typical recent week: the athlete is loaded about as much as they are prepared for. A value climbing above the band means load is accumulating faster than adaptation. A value well below it means the athlete is detraining, which carries its own risk on return.

Load here can be external (GPS distance, high-speed running, accelerations from a unit like Catapult or Polar Team Pro) or internal (session RPE multiplied by duration, or a heart-rate-derived training-load figure). The ratio works on any consistent load measure. Which measure you choose matters, and the critiques below return to it.

The reference range, and where it came from

The range most teams quote, an ACWR of roughly 0.8 to 1.3 as the low-risk "sweet spot" and values above about 1.5 as a "danger zone", comes from Tim Gabbett's widely read 2016 paper on the training-injury prevention paradox. Its central, genuinely useful insight is counter-intuitive: high load is not the enemy. Athletes with a high, gradually built chronic workload were better protected than under-trained athletes, provided they avoided sharp acute spikes. The injury risk is in the rate of change, not the absolute volume.

Hulin and colleagues found the same pattern in elite rugby league: a very high ratio (around 2.0 and above) carried a markedly elevated injury risk in the current and following week, while a high chronic base with controlled spikes was protective. This is the case for building fitness deliberately rather than capping it, and it is the part of the ACWR story that has held up best.

How Strong calculates it: uncoupled, 7 over 21

There is a quiet but important choice buried in the chronic window. In the original coupled formulation, chronic load is the trailing 28 days divided by four, which means the most recent seven days sit inside the chronic window. The same load appears in both the numerator and the denominator. Strong does not calculate it this way, and the reason is the next section.

Strong uses the uncoupled ratio. The acute window is the most recent seven days. The chronic window is the 21 days immediately before that, divided by three to give a weekly baseline. The two windows are disjoint: no day of load is counted twice. A full uncoupled ratio therefore needs 28 days of history, and until an athlete has that, Strong shows a "building baseline" state rather than a noisy number. That is a deliberate honesty choice. A ratio computed on half a baseline is not a smaller signal; it is a misleading one.

The critiques, taken seriously

The ACWR became popular faster than the evidence justified, and the last several years of sports science have been a correction. Any team using the ratio should know these arguments, because they change how much weight the number can bear.

Mathematical coupling. Lolli and colleagues showed that the coupled calculation produces a spurious correlation: because the acute load is part of the chronic load, the two are mathematically linked regardless of any real physiological relationship. Coupling damps the ratio toward 1.0 and hides exactly the spikes the ratio exists to surface. The uncoupled calculation Strong uses avoids this by keeping the windows disjoint. The practical significance of coupling is itself debated, with some case studies finding it makes little difference to the associations, but uncoupling is the safer default and costs nothing.

Rolling average versus weighted. A simple rolling average treats a load from 21 days ago as exactly as relevant as yesterday's. Williams and colleagues argued that fitness and fatigue decay over time, and proposed an exponentially weighted moving average (EWMA) that gives recent load more weight. Their work in elite Australian football found EWMA a more sensitive indicator of injury likelihood at high ratios. The rolling 7:21 model is simpler and more transparent; EWMA is more responsive. Both are defensible, and neither is a finished answer.

The deeper objection. Impellizzeri and colleagues raised the most fundamental concerns: the acute and chronic time spans are essentially arbitrary, the load variables used are wildly heterogeneous across studies, training load is not the same as the mechanical tissue load that actually causes damage, and ratios as data carry statistical problems that undermine ACWR as a causal predictor. Some studies have found that randomised chronic loads predict injury about as well as the real ratio, which is a damning result for anyone treating it as a prediction engine. Systematic reviews have concluded the relationship is real but modest and inconsistent, not the clean threshold the early enthusiasm suggested.

How to use it without overfitting to one number

None of this means the ratio is worthless. It means the ratio is a monitoring tool, not an injury predictor, and that is how the most careful practitioners now treat it. Used well, it does one thing reliably: it flags the athlete whose load has changed sharply relative to their own recent baseline, which is precisely the person worth a conversation before training.

The disciplined way to read it:

• Treat it as a trigger for a question, not an answer. A spike says "look here," not "rest this athlete."
• Read the trend, not the snapshot. A single day's ratio is noise; a ratio climbing across a week is signal.
• Individualise. People vary enormously in the load they tolerate. A 1.4 for one athlete is a different reality than for another, and the ratio knows nothing about that.
• Never read it alone. The ratio is one input alongside recovery, sleep, wellness, prior injury history, and the eye of a coach who knows the player.
• Avoid hard cliffs. A 1.3 and a 1.31 are the same athlete. The reference range is a gradient, not a tripwire.

This is exactly the posture Strong takes. The ratio orders the squad so the athletes whose load has spiked relative to their own baseline rise to the top of the list, the people worth a Monday-morning conversation. It is never printed as a verdict and never acts alone: it sits beside recovery, availability, and the rest of the athlete record on training load management, so the number informs a decision a human still makes. A ratio that surfaces the right person to talk to has done its whole job. Asking it to predict an injury by itself is asking it to be something the evidence says it is not.