Stop Obsessing Over Yesterday's Session. Your Weekly Load Is What Matters.

Athletes check their training load after every single session. Did I go too hard? Was that enough? Should I have backed off?

Wrong question. The session doesn’t matter nearly as much as the week.

The research on training load and injury risk has been consistent for over a decade now. Individual sessions rarely cause injuries. Load spikes over 7 day blocks, relative to what you’ve been doing over the previous 28 days, are what break people. One hard day in the context of a sensible week is fine. One hard week in the context of a sensible month is fine. But ramp your weekly load 50% above your 4 week average and your injury risk doubles.

Your wearable shows you yesterday’s session. It rarely shows you the weekly pattern that actually matters.

The Acute to Chronic Workload Ratio

Tim Gabbett’s research on training load and injury risk changed how professional sport thinks about programming. The core concept is the acute to chronic workload ratio, or ACWR.

Acute load is your current week. Chronic load is the rolling average of the past 4 weeks. Divide acute by chronic and you get a ratio that predicts injury risk better than almost any other single metric in sport science.

The sweet spot is between 0.8 and 1.3. That means your current week’s load is between 80% and 130% of your recent average. Within this range, injury rates are at their lowest. You’re doing enough to stimulate adaptation without overwhelming your body’s capacity to absorb the load.

Below 0.8, you’re undertraining relative to your recent history. Paradoxically, this also increases injury risk. Detraining weakens the structures that protect against injury. Tendons lose stiffness. Muscles lose the fatigue resistance that comes from consistent loading. When you eventually ramp back up, those weakened structures are more vulnerable.

Above 1.5, injury risk climbs sharply. This is the “danger zone” that Gabbett’s data identifies consistently across multiple sports. Cricket, rugby, Australian rules football, running, cycling. The number varies slightly by sport and population, but the pattern is universal. Big spikes in weekly load relative to recent history break athletes.

Why Wearables Miss This

Garmin shows you a 7 day training load bar and a 4 week load chart. It’s there if you dig into the training status screens. Whoop gives you a weekly strain total. Apple Watch shows your Exercise Ring trends.

But none of them calculate the actual ratio and tell you where you stand on the risk curve.

Think about what a useful implementation would look like. You open your training app on Monday morning. It shows you: “Your current weekly load is tracking at 1.4x your 4 week average. You have a hard session planned for Wednesday. If you complete it as programmed, you’ll be at 1.6x by Thursday. Consider reducing Wednesday’s volume by 20% to stay in the optimal range.”

That’s what the data supports. That’s what a coach with access to your training log would tell you. No consumer wearable does this.

Instead, they show you yesterday’s session metrics in isolation. Strain 14.2. Training Effect 3.8. Those numbers are meaningless without the weekly and monthly context that determines whether they’re appropriate or dangerous.

The Monday Problem

Here’s a pattern that shows up constantly in recreational athletes who train seriously.

You take Saturday and Sunday lighter, maybe a rest day and a recovery session. Monday arrives. You feel great. Fresh legs, good sleep, high motivation. So you hammer Monday’s session. Tuesday you do the same. By Wednesday you’ve accumulated more load in 3 days than you did in the previous 5. Your acute load is spiking within the week itself.

This intra week load distribution matters too. Front loading your weekly volume into Monday through Wednesday and coasting Thursday through Sunday creates a different stress profile than spreading the same total volume evenly across the week. Your connective tissue doesn’t care that your weekly total was reasonable. It cares that you did 60% of it in 3 consecutive days.

Wearables track daily load. They don’t flag distribution imbalances within the week. A training platform that understood ACWR would recognise this pattern and warn you on Wednesday morning: “You’ve completed 58% of your projected weekly load in 3 days. Consider a lighter session today to distribute load more evenly.”

Progressive Overload Is a Weekly Concept

Every decent training program follows progressive overload. Gradually increase the stimulus over time. But “gradually” is defined in weeks, not sessions.

A well structured training block might increase weekly volume by 5 to 10% per week for 3 weeks, then pull back to 70% for a recovery week. That 3:1 build to recovery ratio keeps the ACWR in the sweet spot throughout the block. Each individual week is slightly harder than the last, but the increase is controlled and the body has time to absorb it.

Problems happen when athletes go by feel instead of plan. A great week of training tempts you to push harder the following week. You felt strong, so why not add 20%? Because a 20% weekly jump puts your ACWR at 1.2, which is fine. But if you had a lighter week before that great week, the chronic load denominator is lower. That same 20% increase might actually represent a 1.4 ratio. Getting close to the danger zone.

This math is not intuitive. It’s not something you can eyeball from a Garmin connect screen. It requires tracking your weekly totals, calculating the 4 week rolling average, and dividing. A calculator could do it. A smartwatch costing $500 should definitely do it. Almost none of them do.

External Load vs Internal Load

There’s another layer that complicates things. ACWR can be calculated using external load (distance, duration, weight moved) or internal load (heart rate based, RPE based). They don’t always agree.

External load stays the same when you repeat a workout. A 10km run at 5:00/km pace is 10km at 5:00/km whether you’re fresh or fatigued. But the internal load changes. Run that 10km on fresh legs after a recovery day and your average heart rate might be 145. Run it after three hard training days and the same pace might require an average of 158. Same external load. Different internal load. Different recovery cost.

For managing injury risk, internal load is more sensitive. It captures how hard the session actually was for your body, not just how far or how heavy. Most wearable training load calculations use some version of heart rate based internal load (TRIMP, EPOC, or proprietary variants), which is good.

But they still present it as a session metric, not as a weekly ratio.

What a Coach Does That Your Watch Doesn’t

A good coach looks at your training log and sees patterns. They see that your load jumped 30% this week. They see that you front loaded the volume into three consecutive days. They see that your RPE has been creeping up on sessions that used to feel moderate, which suggests accumulated fatigue even if the load numbers look stable.

Then they adjust. Not your next session. Your next week. They pull Wednesday’s session back, move Thursday’s interval work to Friday to create an extra recovery day, and cap the weekly total at 110% of last week instead of the 125% you were heading toward.

This is weekly load management. It’s the most impactful thing a coach does for injury prevention. And it’s almost completely absent from consumer wearable platforms.

The data to do this exists in every Garmin, Whoop, Polar, and Apple Watch. Daily training load is recorded. Weekly totals can be calculated. The 4 week rolling average is trivial math. The ACWR ratio is one division operation. The risk thresholds are published in peer reviewed research.

What’s missing is the intelligence to connect these numbers, present the ratio, and tell the athlete what it means for their next decision. Not their next session. Their next week.

Start Tracking It Yourself

Until your wearable does this for you, here’s the manual version.

Every Sunday evening, write down your total training load for the week. Use whatever metric your platform provides: Whoop Strain total, Garmin weekly training load, or just total training minutes if that’s all you have.

Keep a rolling 4 week list. Each Sunday, divide this week’s total by the average of the previous 4 weeks. That’s your ACWR.

If it’s between 0.8 and 1.3, you’re in the sweet spot. Keep going.

If it’s above 1.3, you ramped too fast. Next week should be a consolidation week, hold steady or pull back slightly.

If it’s above 1.5, you’re in the danger zone regardless of how good you feel. Feelings lie. The ratio doesn’t.

If it’s below 0.8, you’ve dropped off too much. Ramp back up gradually. Don’t jump back to your previous load in one week.

It takes 30 seconds. It requires a phone calculator and a notes app. And it captures more useful injury prevention information than any single metric your wearable shows you after a workout.

The session summary on your wrist is interesting. The weekly ratio in your notes app is what keeps you healthy.