Running Training Load Explained: How to Measure, Manage, and Use It

Training load is the total physiological stress your running places on your body over a given period — calculated by combining how hard you run (intensity) with how long you run (volume). Understanding running training load explained in practical terms means knowing not just how much you're doing, but whether the dose is appropriate for where you are in your training cycle, and whether your body is absorbing it.

What Training Load Actually Measures

Most runners think of load as weekly mileage. That's a start, but it misses half the equation. A 10-mile easy run and a 10-mile tempo run are not the same stress on your body. Training load tries to quantify the difference.

There are two main approaches:

External load — what you actually did: distance, duration, elevation gain, number of strides. These are objective measurements your watch records.

Internal load — how hard your body worked to do it: heart rate, perceived effort, lactate accumulation. This is the physiological response.

The most common training load metric combines both into a single score. Garmin calls it "Training Load." TrainingPeaks uses TSS (Training Stress Score). The underlying math varies, but the concept is identical: stress = intensity × duration.

For example, TrainingPeaks' TSS formula is based on the relationship between your normalized power (or pace) and your functional threshold. A 60-minute run at threshold pace = 100 TSS. A 60-minute easy run at 65% of threshold = roughly 42 TSS. Same duration, very different stress.

Acute vs. Chronic Load: The Ratio That Predicts Injury Risk

This is where training load gets genuinely useful for injury prevention.

Acute load is your training stress over the past 7 days. Chronic load is your rolling average over the past 28 days. The ratio between them — Acute:Chronic Workload Ratio (ACWR) — is one of the most researched metrics in sports science for predicting soft-tissue injury risk.

The original research by Tim Gabbett (2016) established a "sweet spot" ACWR of roughly 0.8–1.3. Stay in that range and you're building fitness without outpacing your body's ability to absorb the stress. Spike above 1.5 and injury risk climbs significantly — hamstrings, Achilles, stress fractures, IT band.

A concrete example: if your chronic load averages 400 TSS per week and you suddenly jump to a 620 TSS week (ratio = 1.55), you're in the danger zone. The fix isn't to never push — it's to build chronic load gradually so you can tolerate higher acute loads without the ratio spiking.

The practical implication: don't just track weekly mileage. Track the ratio of this week's load to your average load over the past month. That number tells you more than raw miles ever can.

How Intensity Distribution Shapes Your Load

Two runners can have identical total training loads and wildly different fitness trajectories based purely on how that load is distributed across intensities.

Most elite distance running programs follow an 80/20 polarized model: roughly 80% of sessions at low intensity (conversational pace, below the first ventilatory threshold) and 20% at moderate-to-high intensity. Research by Stephen Seiler consistently shows this produces better aerobic adaptations than moderate-intensity-heavy programs, primarily by allowing full recovery between hard sessions.

In Jack Daniels' VDOT system, this maps roughly to spending the bulk of your running in E (Easy) and L (Long) zones, with targeted work at M (Marathon), T (Threshold), I (Interval), and R (Repetition) paces — the harder zones — accounting for a minority of weekly volume.

Where most recreational runners go wrong is the moderate-intensity trap: too hard to be truly aerobic, too easy to generate a training stimulus. The result is accumulated fatigue with limited fitness return. You're loading without adapting.

Tracking load by zone, not just total load, reveals this immediately. If 60% of your load is sitting in zone 3 (moderate), that's a warning sign — not because zone 3 is bad, but because it's unsustainable at high volume and tends to crowd out the quality sessions that actually drive improvement.

Progressive Overload: How to Increase Load Without Getting Hurt

The 10% rule — don't increase weekly mileage by more than 10% — is a reasonable heuristic but a blunt instrument. It doesn't account for intensity changes, and it applies the same ceiling to a 20-mile week and a 70-mile week.

A more accurate framework uses the ACWR model above combined with planned recovery weeks. A standard periodization structure might look like:

• Week 1: Chronic load baseline (say, 300 TSS)
• Week 2: +8–12% (330 TSS)
• Week 3: +8–12% (365 TSS)
• Week 4: Recovery week, drop back to ~70% of week 3 (255 TSS)

The recovery week isn't wasted time. It's when adaptation actually occurs — when your body remodels tendons, replenishes glycogen, and consolidates the neural patterns from speed work. Skipping it doesn't make you fitter; it makes you chronically fatigued.

One thing worth noting: adaptation timelines differ by tissue. Cardiovascular fitness responds to load within days to weeks. Tendons and bones take 6–12 weeks to structurally adapt to new stress levels. This mismatch is why fit runners get stress fractures — their cardiovascular system can handle the volume before their skeletal tissue has caught up.

Reading Your Load Data: What the Numbers Are Telling You

Raw load numbers are meaningless without context. Here's how to interpret what you're seeing:

Consistently low acute load relative to chronic load (ACWR < 0.8): You're undertraining. Fitness will slowly erode. This is fine during a taper, problematic if it persists for weeks.

ACWR between 1.0–1.3: Optimal building zone. You're adding stress faster than you're recovering it, which is exactly what creates a training stimulus.

ACWR > 1.5: Danger zone. Back off. This is the number that predicts injury more reliably than any single session metric.

High load, low HRV, elevated resting heart rate: Your chronic load is possibly too high even if the ratio looks fine. Internal load metrics like heart rate variability are the body's vote on whether it's absorbing the external load you're applying.

Stagnant fitness despite adequate load: Look at intensity distribution first. If most of your load is in zone 3, restructuring toward 80/20 often produces more fitness from the same total volume.

One pattern I see often: runners who hit their mileage targets but ignore the quality of that mileage. 50 miles of zone 2 running will produce a different athlete than 50 miles split between zone 1-2 and targeted threshold work. The total looks identical; the adaptation is not.

The Honest Limits of Load Metrics

Training load models are useful approximations, not physiological truth. TSS doesn't know if you're sick, sleep-deprived, stressed at work, or running in 32°C heat. Internal load metrics like heart rate help, but they're still proxies.

Use load data as one signal among several. Combine it with how you actually feel, how your easy-pace heart rate is trending, and whether your workout performances are improving. When the numbers and your body disagree, trust your body.

Load management doesn't replace good coaching judgment. It sharpens it.

If you want your training load calculated automatically alongside pace zones and weekly adaptations, Pacenotes tracks all of this from your GPS data and adjusts your plan week by week based on how your load is trending.