ACWR Monitoring in Football: A Practical Guide for S&C Coaches

A player who did nothing for two weeks then came back and trained at full intensity. A player whose weekly load jumped 40% because the team had three matches in eight days and nobody adjusted the match-day minus structure to compensate. A player who was gradually underloaded all season because nobody noticed the volume creeping down.

Every one of these scenarios is a setup for injury. And every one of them is maybe preventable if you're tracking the Acute:Chronic Workload Ratio. I said maybe because it's not a magic bullet, but it's a damn good tool to have in your arsenal.

What Is ACWR?

The Acute:Chronic Workload Ratio compares a player's recent training load (typically the last 7 days) against their longer-term average load (typically the last 28 days).

The formula:

ACWR = Acute Load (7-day) / Chronic Load (28-day rolling average)

That's it. One number that tells you whether a player is doing significantly more, significantly less, or roughly the same amount of work as their body is conditioned to handle.

• ACWR = 1.0 means this week's load matches the 4-week average. Business as usual.
• ACWR = 1.5 means this week's load is 50% higher than the 4-week average. The player is doing more than their body is accustomed to. Risk goes up.
• ACWR = 0.6 means this week's load is 40% below average. The player is undertrained relative to their recent history. They're losing fitness, and a sudden spike back to normal load becomes risky.

The Sweet Spot: 0.8 to 1.3

Research by Tim Gabbett and others has consistently shown that the lowest injury risk occurs when ACWR sits between 0.8 and 1.3. This range is sometimes called the "training sweet spot."

Here's how the zones break down:

Worth noting: the ACWR model has been debated in recent literature, with some researchers questioning the mathematical properties of the ratio itself (Impellizzeri et al., 2020). Despite this, monitoring acute vs chronic load trends remains valuable in practice -- the specific thresholds should be applied flexibly rather than as rigid cut-offs.

How to Calculate Training Load

ACWR needs a training load number to work with. For most independent S&C coaches working outside of professional setups with GPS systems and force plates, the most practical method is session RPE (sRPE):

Session Load = RPE (1-10) x Duration (minutes)

A player rates the session a 7 out of 10 and it lasted 60 minutes: the load is 420 arbitrary units (AU).

Do this for every session the player does — gym sessions, pitch sessions, matches, everything. Sum the week to get the acute load.

Example Calculation

Let's say a midfielder's weekly loads for the past 4 weeks are:

• Week 1: 2,100 AU
• Week 2: 2,400 AU
• Week 3: 2,200 AU
• Week 4 (current): 2,800 AU

Chronic load (28-day average): (2,100 + 2,400 + 2,200 + 2,800) / 4 = 2,375 AU

Acute load (current week): 2,800 AU

ACWR = 2,800 / 2,375 = 1.18

This player is in the sweet spot. Load is slightly above average but well within safe range. No red flags.

Now imagine the same player missed Week 3 due to illness (load: 400 AU) and came straight back to full training in Week 4:

• Chronic load: (2,100 + 2,400 + 400 + 2,800) / 4 = 1,925 AU
• ACWR = 2,800 / 1,925 = 1.45

Same training week, completely different risk profile. That missed week dropped their chronic load, which means a normal training week now registers as a spike. This is the kind of scenario ACWR catches that your gut feeling might miss.

Why Club Training Load Matters

Here's where most independent S&C coaches get ACWR wrong: they only track what happens in their own sessions.

If you see a player twice a week for gym sessions, you're capturing maybe 15-20% of their total weekly load. The other 80% — club training, matches, extra sessions — is invisible to you.

An ACWR based on 20% of the picture is misleading at best and dangerous at worst. A player could be massively overloaded from club training and you'd never see it if you're only tracking gym sessions.

How to capture external load:

• Ask the player to log their club sessions and matches with a simple RPE x duration entry
• A 2-minute daily check-in is all it takes
• Make it frictionless — if it takes more than 30 seconds, compliance drops to zero

The players who log their external training consistently give you the full picture. The ones who don't are flying blind — and you should make that clear to them.

Exponentially Weighted Moving Average (EWMA)

The simple rolling average method above works, but it has a flaw: it treats a session from 28 days ago the same as a session from yesterday. The EWMA model gives more weight to recent sessions, which better reflects how the body actually adapts and fatigues.

Most practitioners now recommend EWMA over the simple rolling average. The math is more involved, but any decent monitoring tool handles it automatically. The key insight is the same: compare recent load to established load and flag when the ratio moves outside the safe range.

If you're calculating ACWR by hand in a spreadsheet, the rolling average is fine to start. The important thing is that you're tracking at all.

Common ACWR Mistakes

1. Only tracking gym sessions

Covered above, but worth repeating. If you don't have the full training picture, your ACWR is fiction. So make sure you track all the training sessions, not just the ones you're responsible for. That's why i included the session LOGGER in the PLAYER VIEW, so you can track ALL the training sessions, not just the ones you're responsible for.

2. Ignoring low ACWR

Coaches tend to worry about high ACWR (spikes) but ignore low ACWR (undertraining). A player with a chronic ACWR below 0.8 is losing the protective effect of training. Their tissues are deconditioned. When they inevitably return to normal load, the relative spike is larger.

3. Treating ACWR as a hard threshold

An ACWR of 1.31 is not meaningfully different from 1.29. The ranges are guidelines, not cliff edges. Context matters — a well-conditioned player with a high chronic load can tolerate higher ACWR spikes than a player coming back from injury with a low chronic base.

4. Not accounting for match load

A 90-minute match at RPE 8 is a load of 720 AU in a single session. That's often the single largest load event of the week. If you don't include match load, your weekly total is massively underestimated.

5. Weekly totals without daily resolution

A weekly load of 2,400 AU could mean four sessions of 600 AU (well distributed) or one session of 1,800 AU and three sessions of 200 AU (terrible distribution). Same ACWR, very different injury risk. Look at daily load distribution, not just weekly totals.

Practical Implementation: Making It Work

Here's what ACWR monitoring actually looks like for an independent S&C coach with 5-10 players:

Daily:

• Player logs each session with RPE (1-10) and duration (minutes)
• Takes 15 seconds per session
• Include all training: your sessions, club sessions, matches, extra work

Weekly:

• Calculate ACWR for each player
• Flag anyone below 0.8 or above 1.3
• Review flagged players: is the spike/dip planned (deload, pre-season ramp) or unplanned (illness, extra matches)?

Case Example: Return from International Break

A defender goes on international duty for 12 days. He plays two matches and trains with the national team. You have no data on those sessions.

He returns and you need to program his next week. Without ACWR data from the international break, you're guessing.

What I do: Estimate the international training load using match minutes (RPE 7-8 x match duration) plus estimated training sessions (RPE 6 x 75 min for team training). It's imperfect, but better than leaving a two-week gap in the data.

If his estimated ACWR is above 1.3 upon return (heavy international schedule), I reduce his first week back. If it's below 0.8 (he was an unused substitute and barely trained), I ramp him gradually rather than throwing him straight into full sessions.

---

Tracking ACWR by hand is doable with a spreadsheet, but it gets tedious fast once you have more than a few players. PlayerPlan calculates ACWR automatically from session RPE data — including external training loads your players log themselves through their share link. No app download required, and you can see every player's load trend at a glance. Try it free for 30 days at player-plan.com.