Free Tool · ACWR

Training Load Calculator

Enter your last 4 weeks of mileage to calculate your Acute:Chronic Workload Ratio (ACWR) — the sports-science metric that flags overtraining before it becomes an injury.

Weekly Distance (most recent first)
Your ACWR
1.14
Sweet Spot
This week (acute)
50.0
km
4-week average (chronic)
43.8
km

Sweet Spot (1.14) — Your acute training load is well matched to your recent baseline. This is the range associated with the lowest injury risk and steady, sustainable fitness gains.

What Is Training Load and Why It Matters

Every run adds stress to your body — and every rest day lets it adapt to that stress and get stronger. Injuries happen when the stress arrives faster than your body can adapt to it, not simply from running "too much" in absolute terms. Two runners can both run 60 km in a week; the one who jumped there from 30 km/week is at far higher risk than the one who has been running 55 km/week for months.

Training load metrics like ACWR exist to make this relationship visible, so you can catch a dangerous ramp-up before it becomes a stress fracture, tendinopathy, or muscle strain.

What Is ACWR (Acute:Chronic Workload Ratio)?

ACWR compares your acute load (your most recent training — typically the last 7 days) to your chronic load (your established baseline — typically the average of the last 4 weeks). The formula used by this calculator:

An ACWR of 1.0 means your recent training exactly matches your baseline — no ramp-up, no drop-off. The metric was developed by sports scientist Tim Gabbett and has since been validated across running, football, cricket, and rugby.

The Danger Zone: High ACWR and Injury Risk

Multiple studies have found that an ACWR above 1.5 is associated with a sharply elevated injury risk compared to the 0.8–1.3 "sweet spot" range — in some studies, 2–4x higher. The mechanism is straightforward: connective tissue (tendons, ligaments, bone) adapts far more slowly than your cardiovascular system. You can feel aerobically capable of running more well before your tissues are ready for it.

Common causes of a high-risk ACWR spike: returning from injury or illness too aggressively, a sudden jump in weekly mileage, adding a race or hard event without building up to it, or stacking multiple hard sessions in a single week.

The Undertrained Zone: Why Too Low Is Also Worth Watching

An ACWR below 0.8 isn't dangerous the way a spike is, but it signals detraining — you're losing fitness relative to your recent baseline. This is completely normal and expected during a taper. Outside of a planned taper, if your ACWR stays low for multiple weeks (after travel, illness, or a break), rebuild gradually rather than jumping straight back to your previous peak mileage — increasing by roughly 10% per week is a widely used, conservative rule of thumb.

How to Safely Increase Training Load

To build fitness while keeping your ACWR in the sweet spot:

Frequently Asked Questions

ACWR compares your recent training load (the "acute" load, typically your most recent 7 days) to your established baseline (the "chronic" load, typically your average over the past 4 weeks). It was developed by sports scientist Tim Gabbett and is one of the most widely used metrics for predicting injury risk in runners and other endurance athletes. An ACWR near 1.0 means your recent training matches what your body is used to; a high ACWR means you’ve ramped up faster than your body has adapted.
Most research places the lowest injury-risk range at 0.8–1.3 — often called the "sweet spot." Below 0.8 suggests you’re detraining (not dangerous, but you’ll lose fitness). Between 1.3 and 1.5 is a caution zone. Above 1.5 is consistently associated with a sharply elevated injury risk across multiple studies in runners, footballers, and cricketers.
The simplest version uses total distance: Acute load = this week’s distance. Chronic load = the average of your last 4 weeks’ distance (including this week). ACWR = Acute ÷ Chronic. For example, if you ran 60 km this week and your last 4 weeks averaged 45 km, your ACWR is 60 ÷ 45 = 1.33 (overloading). More advanced versions weight duration and intensity (using RPE or heart rate) rather than distance alone — this is what PacecraftAI’s in-app training load monitoring uses.
Don’t panic — a single high reading isn’t an injury, it’s a risk signal. Reduce your volume by 20–30% for the coming week, prioritise sleep and recovery, and avoid adding new intensity (hills, intervals, tempo) until your ACWR settles back toward 1.0–1.2. If you have any pain, not just fatigue, stop and assess before continuing to build load.
A low ACWR isn’t an injury risk in itself, but it usually means you’re losing the fitness you built. This is completely normal and expected during a taper before a race. Outside of a planned taper, a persistently low ACWR (after illness, travel, or a break) means you should rebuild volume gradually — increasing weekly mileage by no more than about 10% per week — rather than jumping straight back to your previous peak.
This free tool uses the classic rolling-average method (this week’s distance ÷ average of the last 4 weeks) for a quick, no-signup estimate. PacecraftAI’s in-app training load monitoring uses a more precise method — exponentially weighted daily training load (factoring duration and intensity, not just distance) — to calculate your ATL, CTL, and ACWR continuously and flag risk before you feel it.

Let AI monitor your training load automatically

PacecraftAI tracks your ATL, CTL, and ACWR continuously from your actual training — not a manual 4-week entry — and adjusts your plan before a risky ramp-up turns into an injury.

Start free — no credit card →