ACWR Explained for Runners: The Training Load Metric That Predicts Injuries

If you have ever started a marathon training block feeling great, ramped up your mileage aggressively, and then found yourself nursing a sore knee six weeks before race day — you experienced the consequence of a poor Acute:Chronic Workload Ratio (ACWR).

The ACWR is a training load metric developed primarily by sports scientist Tim Gabbett, originally for team sports but now widely used in endurance coaching. It is arguably the most predictive single number for injury risk in recreational runners, and it is the metric that well-designed AI coaching platforms use to keep your training in the safe zone.

What the ACWR Measures

The ACWR compares two rolling averages of your training load:

• Acute load: Your training load over the past 7 days — what your body is currently experiencing.
• Chronic load: Your training load over the past 28 days — what your body is conditioned to handle.

The ratio is simply: ACWR = Acute Load ÷ Chronic Load

If your chronic load (28-day average) is 50 km/week and your acute load (last 7 days) was also 50 km, your ACWR is 1.0 — exactly what you are conditioned for. If your acute load jumps to 70 km while your chronic load is still 50 km, your ACWR is 1.4 — you are doing significantly more than your body is prepared for.

What the Research Says About Safe ACWR Values

The research consistently shows that an ACWR between 0.8 and 1.3 is the "sweet spot" — associated with peak fitness gains and low injury risk. Below 0.8, you are undertraining relative to your recent history. Above 1.3–1.5, injury risk begins rising sharply. Above 1.5, you are in high-risk territory.

Gabbett's original research (and subsequent replications across endurance sports) found that athletes training in the 0.8–1.3 range had significantly lower injury rates than those training outside it — regardless of absolute training volume. This means a runner doing 80 km/week at a stable ACWR of 1.0 is at lower injury risk than a runner doing 40 km/week at a spiking ACWR of 1.6.

Why Recreational Marathon Runners Are Especially Vulnerable

ACWR spikes are extremely common in marathon training for predictable reasons:

• Following a fixed plan without a running base: The first three weeks of a typical 16-week marathon plan involve a steep mileage increase for runners who have not been running much. Going from 20 km/week to 45 km/week in two weeks creates an ACWR of 2.0+ — the injury risk zone.
• Trying to make up for missed weeks: Life gets in the way during a 16-week training block. The temptation after a missed week is to run extra sessions to catch up, which produces exactly the kind of acute spike the ACWR is designed to flag.
• Pre-race anxiety mileage: In the final two to four weeks before a marathon, some runners add extra sessions or extend long runs because they feel underprepared. This is often the exact moment that produces an injury that forces a DNS.

How to Calculate Your ACWR

The simplest approach uses distance (km or miles) as your load unit, though more sophisticated systems use a training stress score (TSS) that accounts for intensity as well as volume.

Manual calculation:

1. Sum your total kilometres for the past 7 days → this is your acute load
2. Sum your total kilometres for the past 28 days, then divide by 4 → this is your chronic load (weekly average)
3. Divide acute load by chronic load → this is your ACWR

Example: You ran 55 km last week. Your total for the past 28 days was 160 km (weekly average: 40 km). Your ACWR is 55 ÷ 40 = 1.375 — approaching the upper boundary of the safe zone.

What to Do When Your ACWR Is Too High

If your ACWR exceeds 1.3 and you are not yet injured, the right response is to reduce this week's training load — not to push through. Specifically:

• Replace one quality session with an easy run or rest day
• Shorten your long run by 20–30%
• Keep the same number of sessions but reduce the total duration
• Do not try to make up the missed load next week — let your chronic load catch up to your acute load over time

The key insight is that the safest way to increase training volume is slowly. An ACWR of 1.1–1.2 consistently applied over 12–16 weeks will build more fitness than repeated cycles of 1.5 ACWR followed by injury-enforced rest.

How AI Coaches Use ACWR

One of the core advantages of an AI running coach over a static plan is continuous ACWR monitoring. A fixed 16-week marathon plan cannot adapt when you run extra sessions, miss a week, or have a race-like effort that dramatically elevates your acute load. It just continues on schedule.

PacecraftAI recalculates your ACWR after every logged session. When your ratio approaches 1.3, it automatically adjusts upcoming sessions — pulling back intensity, shortening long runs, or inserting recovery days — before the ratio reaches the injury-risk zone. When your ACWR is low (under 0.8), it knows you have capacity to absorb more training and may extend sessions or add volume.

This is the mechanism that makes adaptive coaching meaningfully different from a fixed plan — not just in theory, but in the specific ways it changes your schedule week by week.

ACWR Limitations

The ACWR is a useful tool but not a complete picture of injury risk. Factors it does not capture include:

• Running form and biomechanical inefficiency
• Sleep quality and total recovery (though HRV data partially addresses this)
• Footwear wear and surface changes
• Single traumatic events (ankle rolls, falls)
• Strength and muscle imbalances

Used alongside HRV monitoring, resting heart rate trends, and sleep data, ACWR becomes significantly more powerful. This is why the most effective AI coaching systems integrate wearable data alongside mileage tracking.

The Practical Takeaway

The ACWR is useful primarily as a number you should never let get above 1.5. For most recreational marathon runners, a simple rule applies: do not increase your weekly mileage by more than 10–15% in any given week, and do not try to make up for missed weeks by cramming extra mileage. Both of these rules are essentially ACWR management in disguise.

If you are using an AI coach that monitors ACWR, trust its recommendations when it suggests pulling back. If it is telling you to rest, your training load data is telling a story your legs have not fully told you yet.