Training Fundamentals

Training Load Management: Knowing When to Push and When to Pull Back

A practical guide to monitoring training fatigue across three dimensions — impact, CNS, and metabolic — and the specific adjustments smart coaches make to keep runners healthy and progressing.

12 min read
1stMarathon Team
Level:beginnerintermediateadvanced
Phases:basebuildpeaktaper
#training load#recovery#overtraining#fatigue management#injury prevention#cross training

Every workout creates stress. Stress drives adaptation — stronger muscles, denser bones, a more efficient heart. But only if you can recover from it. Push too hard without enough recovery and the same stress that builds fitness starts breaking you down: overtraining, injury, burnout.

The difference between a runner who improves steadily and one who's always hurt isn't talent. It's load management — knowing when to push, when to pull back, and which specific adjustments to make based on where the fatigue is accumulating.

This article covers the three dimensions of training fatigue, how to recognize when each is getting too high, and the concrete workout modifications that keep you training consistently instead of cycling between overreaching and forced rest.


Three Dimensions of Training Fatigue

Not all fatigue is the same. A runner who did a long run on Sunday and heavy squats on Monday is fatigued in two completely different ways. Lumping it all together as "tired" misses the point — the adjustments you need are different depending on where the fatigue is.

Impact Load — Bones, Joints, and Connective Tissue

Every footstrike sends 2–3x your bodyweight through your legs. Over thousands of repetitions, this cumulative force stresses bones, tendons, ligaments, and cartilage. Plyometric exercises — depth jumps, bounding, box jumps — generate even higher forces per contact.

Impact fatigue is insidious because connective tissue adapts much slower than your cardiovascular system. Your heart and lungs might be ready for more miles while your shins, Achilles tendons, and knees are silently accumulating damage. Stress fractures, tendinopathy, and shin splints are all impact overload injuries.

What drives impact load up:

  • Running volume — more miles means more footstrikes
  • Running intensity — intervals and sprints generate higher ground reaction forces than easy running
  • Plyometric and power exercises — depth jumps, bounding, explosive jumps
  • Consecutive running days without rest

What does NOT contribute meaningfully:

  • Squats, deadlifts, lunges, and other pure strength work — heavy but low ground reaction forces
  • Bodyweight strength (push-ups, planks, core work)
  • Mobility and stability sessions
  • Cycling, swimming, or other non-impact cross-training

CNS Load — The Nervous System

High-intensity and explosive efforts tax the central nervous system. Unlike muscle soreness, CNS fatigue doesn't hurt — it shows up as feeling flat, being unable to hit paces you normally can, poor coordination, and sluggish reaction times. Runners often describe it as "the legs just aren't there today."

CNS fatigue accumulates from two distinct sources:

From running: Intervals, threshold sessions, and sprint work all demand high neural drive — your nervous system is working hard to recruit muscle fibers quickly and precisely.

From strength training: This is the one most runners miss. A heavy barbell squat session (RPE 8+) taxes the central nervous system significantly. The neural cost depends on the equipment and intent:

  • Heavy free weights (barbell, dumbbell) impose the highest CNS demand. Stabilizing heavy external loads under gravity requires maximal motor unit recruitment.
  • Kettlebells are moderate — ballistic but with lighter absolute loads than barbells.
  • Bodyweight strength is the lowest — the load is submaximal by definition.
  • Power and explosive work (cleans, snatches, plyometrics) is CNS-expensive regardless of equipment because it requires maximal-rate force development.

A runner who does heavy squats on Monday and then can't hit interval paces on Tuesday isn't unfit — they're CNS-fatigued. The nervous system hasn't recovered from the strength session, and now the intervals are asking for the same neural resources.

What does NOT contribute meaningfully:

  • Easy and recovery running (low neural demand)
  • Stability exercises
  • Light accessory work (bicep curls, calf raises)
  • Mobility sessions

Metabolic Load — The Whole Body

Metabolic load captures total physiological demand: how much your body is processing versus how much it can recover from. It combines training volume with recovery signals — sleep quality, energy levels, and soreness.

You can have moderate impact and CNS loads but still be running on empty because you're sleeping poorly, eating too little, or carrying stress from work. Metabolic load is the "whole body" check that catches what the other two dimensions miss.

What drives metabolic load up:

  • Total training minutes exceeding what's prescribed
  • Poor sleep quality
  • Low energy levels
  • High overall soreness
  • Life stress (indirectly, through its effect on recovery)

Why it matters separately: A runner might handle their scheduled workouts fine in isolation, but when combined with a bad week of sleep and high work stress, the same training load becomes too much. Metabolic load detects this mismatch.


Load Zones: From Productive to Dangerous

Each dimension produces a fatigue score from 0 to 100. These map to five zones:

ZoneScoreWhat It Means
Very Low0–14Well-recovered but potentially underloaded. Fine short-term; if sustained across weeks, you may be detraining.
Low15–29Light fatigue. Good recovery window. You can absorb more training stress.
Optimal30–54The productive zone. Training stress is driving adaptation without outpacing recovery. This is where you want to spend most of your time.
High55–74Elevated fatigue. Still manageable short-term, but you need to reduce the specific work that's driving this dimension up. A session or two of pushing through is fine; a full week here invites trouble.
Critical75+Overreaching territory. Continuing to load this dimension without intervention leads to injury, illness, or forced time off. Immediate adjustments required.

No adjustments are needed in the Very Low through Optimal zones — that's productive training. The workout modifications below apply only at High and Critical levels.


Workout Adjustments by Load Zone

The following adjustments are what an experienced coach would make when monitoring a runner's fatigue. They're specific and actionable — not "listen to your body" vague advice, but concrete changes to specific workout types.

When CNS Load Is High (55–74)

The nervous system is fatigued but not depleted. The goal: reduce the most CNS-expensive work while preserving training stimulus where possible.

Running:

  • Intervals: Reduce volume by 30%. If 6×800m is prescribed, do 4×800m. Keep the target pace — quality over quantity.
  • Threshold: Shorten the sustained threshold block by 30%. A 25-minute tempo becomes 18 minutes. Keep the pace.
  • Sprints: Cancel. Replace with 4–6 strides at the end of an easy run. Strides maintain neuromuscular connection at a fraction of the CNS cost.
  • Easy and recovery runs: No change. Low CNS demand.
  • Long run: No change. Duration is the stimulus, not intensity.

Strength:

  • Heavy free-weight sessions (fg-strength) → Downgrade to kettlebell strength (kb-strength). Same movement patterns, lower absolute load, less CNS cost.
  • Kettlebell strength (kb-strength) → Downgrade to bodyweight strength (bw-strength).
  • Bodyweight strength (bw-strength) → No change. Already minimal CNS cost.
  • Any power/explosive template (fg-power, kb-power, kb-complex) → Replace with a mobility session. Explosive work is CNS-expensive regardless of equipment.
  • Bodyweight power (bw-power) → Downgrade to bodyweight strength (bw-strength). Remove the explosive intent, keep the movement.
  • Stability work (bw-stability) → No change.

Drills and supplemental:

  • Strip any plyometric drills from the session. Keep technique drills.
  • Mobility is always fine.

When CNS Load Is Critical (75+)

The nervous system is depleted. Hard or explosive sessions will be poor quality — you'll grind through them slowly and delay recovery. The right move is to remove all high-CNS demands and let the system recover.

Running:

  • Intervals: Reduce volume by 40%. 6×800m becomes 4×800m. 5×1000m becomes 3×1000m. Keep target pace for the remaining reps — fewer reps done well beats more reps done poorly.
  • Threshold: Convert to an easy run at the same duration — or, if threshold adaptation is behind and impact load allows it, move the threshold effort to the bike (same duration, same RPE, zero CNS cost from ground impact). No sustained hard running effort.
  • Sprints: Cancel. Replace with an easy run.
  • Easy and recovery runs: No change.
  • Long run: Keep, but enforce easy effort only. No marathon-pace segments, no progression finish. Just easy, steady distance.

Strength:

  • Heavy free-weight and kettlebell sessions (fg-strength, kb-strength) → Replace with a mobility session. No heavy loading until CNS recovers.
  • Bodyweight strength (bw-strength) → Reduce to 50% volume (half the sets). Keep the movements.
  • All power and explosive templates (fg-power, kb-power, bw-power, kb-complex) → Replace with a mobility session.
  • Stability work (bw-stability) → No change.

Drills and supplemental:

  • Cancel all plyometric drills. Keep technique-only drills if present.
  • Mobility is actively encouraged.

When Impact Load Is High (55–74)

Musculoskeletal structures are accumulating stress. The priority: reduce ground reaction forces while preserving training stimulus from low-impact work.

Running:

  • Long run: Cap at 90% of prescribed distance. An 18 km long run becomes 16 km. The long run is the single biggest contributor to weekly impact.
  • Easy and recovery runs: No change individually, but if 4 or more consecutive run days are scheduled in the week, convert one mid-week easy run to an equivalent-duration cycling or elliptical session to break up the impact accumulation.
  • Intervals and threshold: No change. The total ground contact time is relatively short compared to easy mileage.
  • Sprints: No change. Very short duration, limited total impact.

Strength:

  • Power/explosive templates (fg-power, kb-power, bw-power) → Replace with the same-tier pure strength template. fg-power becomes fg-strength, kb-power becomes kb-strength, bw-power becomes bw-strength. This removes the plyometric/ballistic element while keeping the training stimulus.
  • Kettlebell complex (kb-complex) → Replace with kb-strength. Remove the explosive component.
  • Pure strength templates (fg-strength, kb-strength, bw-strength) → No change. Squats, deadlifts, and lunges don't generate the repetitive ground reaction forces that cause impact injuries.
  • Stability work → No change.

Drills and supplemental:

  • Strip plyometric drills (depth jumps, bounding). Keep technique drills — A-skips and high knees done for short durations are low-impact.
  • Mobility is always fine.

When Impact Load Is Critical (75+)

Musculoskeletal system is at injury risk. Aggressively reduce all sources of ground reaction forces.

Running:

  • Long run: Cap at 80% of prescribed distance. A 20 km long run becomes 16 km.
  • Intervals: Reduce reps by 30% and extend recovery between reps by 50%. 6×800m with 90-second jog recovery becomes 4×800m with 2:15 walk/jog recovery. Fewer ground contacts, more recovery between efforts.
  • Easy and recovery runs: Cap any session over 60 minutes at 60 minutes. If 3 or more consecutive run days are scheduled, convert one to cross-training (cycling, aqua jogging, or elliptical at the same easy effort) or insert a rest day.
  • Sprints: Cancel. Replace with strides — shorter efforts, fewer total ground contacts.
  • Threshold: Reduce the sustained block by 20%. If threshold adaptation is behind, consider moving the entire session to the bike — same effort, same duration, zero impact.

Strength:

  • All power and explosive templates (fg-power, kb-power, bw-power, kb-complex) → Replace with a mobility session. No plyometric or ballistic work.
  • Pure strength templates (fg-strength, kb-strength, bw-strength) → No change. Low-impact training is still fine — and actually beneficial for maintaining tissue resilience.
  • Stability work → No change.

Drills and supplemental:

  • Cancel all drills with any plyometric component.
  • Mobility is actively encouraged — it supports tissue recovery.

When Metabolic Load Is High (55–74)

Total physiological demand is outpacing recovery. Reduce overall training volume across the board.

Running:

  • Long run: Cap at 90% of prescribed distance.
  • Intervals: Reduce volume by 20% (fewer reps).
  • Threshold: Shorten work block by 20%.
  • Easy and recovery runs: No individual changes.
  • Total weekly running volume capped at 90% of what's prescribed.

Strength:

  • All templates: Reduce to 80% volume (fewer sets, same exercises and load).

Drills and supplemental:

  • Reduce total drill time by 20%.
  • Mobility is always fine — it's recovery-supporting.

When Metabolic Load Is Critical (75+)

Systemic overload. Your body cannot handle current training demand. Everything gets easier until recovery catches up.

Running:

  • All hard sessions (intervals, threshold, sprints) → Convert to easy runs at the same duration. No intensity whatsoever.
  • Long run: Cap at 70% of prescribed distance, easy effort only.
  • Easy and recovery runs: No change.
  • Total weekly running volume capped at 70% of prescription.

Strength:

  • Heavy free-weight sessions (fg-strength) → Downgrade to kettlebell strength (kb-strength).
  • Kettlebell strength (kb-strength) → Downgrade to bodyweight strength (bw-strength).
  • Bodyweight strength (bw-strength) → Reduce to 50% volume.
  • All power and explosive templates → Replace with mobility sessions.
  • Stability work → No change.

Drills and supplemental:

  • Cancel all drills. Replace with easy mobility or rest.
  • Mobility is always welcome.

Recovery priority: When metabolic load is critical, the most important interventions are off the training plan: prioritize 8+ hours of sleep, eat enough calories and protein, and manage life stress. Training volume will naturally increase as these recovery signals improve.


Cross-Training as a Load Management Tool

Reducing or replacing a workout isn't the only option when fatigue is elevated. Cross-training lets you maintain the training stimulus — aerobic fitness, threshold development, active recovery — without loading the fatigued dimension. The key is matching the modality to the situation.

Why Cross-Training Works Here

Running generates impact and (at high intensities) CNS load simultaneously. Cross-training decouples these. You can do threshold-effort work on a bike without a single footstrike. You can log 60 minutes of aerobic volume in the pool with zero ground reaction forces. This means you don't have to choose between "push through and risk injury" and "rest and lose fitness." There's a third option: train the energy system through a different movement.

Choosing the Right Modality

Not all cross-training is interchangeable. Each modality has strengths that make it suited to specific load management scenarios:

Cycling — The default substitute when you need to maintain intensity without impact. Cycling allows sustained threshold and tempo efforts that closely mimic the metabolic demands of hard running. It's also easy to control effort precisely via power or heart rate. Best for replacing threshold runs, adding aerobic volume on high-impact weeks, or breaking up consecutive run days.

Aqua jogging — The closest movement pattern to running, performed in deep water with zero impact. The water provides resistance through the full range of motion, maintaining running-specific muscle recruitment. Best for replacing easy runs when impact is critical, long run substitution (at reduced duration — aqua jogging is harder to sustain mentally), or as active recovery after a heavy running block.

Swimming — Zero impact and excellent aerobic stimulus, but uses predominantly upper body and core. Less running-specific than cycling or aqua jogging, but uniquely useful for active recovery because it promotes blood flow without any eccentric muscle loading. Best for recovery days, light aerobic maintenance, or when a runner needs complete lower-body offloading.

Elliptical — Running-adjacent mechanics (similar hip extension pattern) with significantly reduced impact compared to actual running. Some impact remains — it's not zero like swimming or aqua jogging — but it's roughly 50–60% of running's ground reaction forces. Best for runners who want something that feels like running when impact is elevated but not critical.

Rowing — Full-body aerobic work with no impact. Moderate CNS demand when done at high intensity (heavier than cycling due to the strength component of each stroke). Best for general aerobic volume, but be aware that hard rowing sessions do carry some CNS cost — don't substitute rowing for a cancelled strength session if the reason was CNS fatigue.

When to Substitute Cross-Training for Running

Cross-training substitutions are most valuable in these specific scenarios:

Impact is High or Critical but aerobic adaptation is behind: Instead of just cutting running volume, replace some of the cut volume with cycling or aqua jogging. You lose the running specificity but maintain the aerobic training effect that you need.

Impact is High or Critical but threshold adaptation is behind: This is the single most powerful cross-training application. Instead of cutting a threshold run entirely, do the threshold effort on a bike. Same metabolic and cardiovascular stimulus, zero impact. A 25-minute cycling tempo is not as specific as a 25-minute running tempo, but it's far better than skipping it.

CNS is Critical but aerobic adaptation is behind: Replace cancelled hard runs with easy cross-training. Cycling or aqua jogging at conversational effort adds aerobic volume without CNS demand. Avoid rowing at high intensity in this scenario — it carries meaningful CNS cost.

Consecutive run days need to be broken up: Instead of inserting a full rest day (which may feel like lost training), substitute one of the mid-week easy runs with an equivalent-duration cycling or elliptical session. Same aerobic benefit, zero impact accumulation, and the runner keeps their training rhythm.

Metabolic load is Critical: Cross-training doesn't solve metabolic overload — the issue is total demand versus recovery, regardless of modality. A hard cycling session still adds metabolic load. In this scenario, the adjustment is to make everything easier or shorter, not to shift modalities.

When NOT to Substitute

  • Easy runs are already low-cost. Swapping an easy 30-minute run for 30 minutes on the bike saves minimal impact and loses running specificity. Only substitute easy runs when impact is genuinely Critical or consecutive run days are excessive.
  • Long runs are highly specific. The long run develops running-specific endurance (fat oxidation, connective tissue adaptation, mental toughness for sustained effort) that cross-training cannot replicate. Cap the distance rather than replacing the long run entirely — a shorter long run is better than a long bike ride for marathon preparation.
  • Race-specific phases (peak, taper). As the race approaches, running specificity matters more. Cross-training substitutions should be used more conservatively in peak and taper phases unless load is genuinely Critical.

When Multiple Dimensions Are Elevated

In practice, fatigue dimensions often rise together. Heavy interval weeks spike both CNS and impact. Poor sleep combined with high mileage drives up metabolic load alongside impact. When multiple dimensions are in High or Critical zones simultaneously, the adjustment logic is simple:

Apply the most restrictive rule for each workout.

Some examples:

  • CNS High + Impact Critical → scheduled power session: CNS High says downgrade to mobility. Impact Critical also says replace with mobility. Same outcome either way — mobility.
  • CNS High + Impact High → scheduled intervals: CNS High says reduce 30%. Impact High says no change to intervals. Apply the CNS reduction.
  • CNS High + Metabolic High → scheduled fg-strength: CNS High says downgrade to kb-strength. Metabolic High says reduce to 80% volume. Both apply: kb-strength at 80% volume.
  • CNS Critical + Metabolic Critical → scheduled threshold: CNS Critical says convert to easy run. Metabolic Critical also says convert to easy run. Same outcome.

When two adjustments target different aspects of the same workout (one changes the type, another reduces volume), both apply. When they target the same aspect (both want to change the type), the more restrictive one wins.


Consecutive Run Days

Independent of the three load dimensions, consecutive running days deserve special attention. Connective tissue fatigue is cumulative and may not show up in load calculations until it's too late.

  • 4 consecutive run days: Consider scheduling a rest or cross-training day soon.
  • 5+ consecutive run days: Insert a rest day or convert one running session to non-impact cross-training (cycling, swimming, elliptical).

This guideline applies even when all three load dimensions are in the optimal range. The body's impact tolerance has limits that aren't fully captured by a 7-day rolling average.


Early Training Considerations

During the first four weeks of a new training plan, impact load calculations are capped — you can't reach Critical from impact alone. This prevents false alarms while the system builds a reliable baseline of what your body is accustomed to.

CNS and metabolic loads can still reach Critical during this period if recovery signals are poor or hard sessions are genuinely excessive. The impact cap is just a recognition that the acute-to-chronic workload ratio needs several weeks of data before it's trustworthy.


Common Misconceptions

"If I feel fine, my load must be fine"

Feeling fine doesn't mean tissues aren't accumulating damage. Impact overload injuries (stress fractures, tendinopathy) typically have no warning symptoms until they're already established. CNS fatigue often masks itself as "just a bad day" until you've had three bad days in a row.

"More rest days is always the answer"

Not necessarily. If CNS load is high but impact is low, you don't need a rest day — you need to swap the high-intensity work for something less neurally demanding. If impact is critical but your aerobic base needs work, you don't need to stop training — you need to move some of that volume to the bike or pool. Blanket rest when the issue is dimension-specific means you lose training stimulus you could have kept. Cross-training exists precisely for these situations.

"I should never train when a load dimension is high"

High is elevated, not emergency. You can train — you just need targeted adjustments. Critical is the emergency level. Many productive training weeks happen with one dimension in the High zone while the others are optimal. The adjustments keep it from tipping over.

"Strength training doesn't affect running fatigue"

A heavy squat session taxes the same CNS that your intervals need. Plyometric work generates impact forces comparable to or exceeding running. Ignoring strength work in fatigue calculations is like budgeting your finances but ignoring rent.


Summary

Training load management isn't about training less — it's about training smarter. By tracking fatigue across three independent dimensions (impact, CNS, and metabolic) and making targeted adjustments when specific dimensions are elevated, you can maintain higher overall training volume while staying healthy.

The adjustments follow a consistent logic: the more fatigued a system is, the more aggressively you reduce the work that taxes it. CNS fatigue calls for less intensity and lighter strength work. Impact fatigue calls for fewer ground contacts and less running volume. Metabolic fatigue calls for everything to get easier until recovery catches up.

The goal isn't to avoid hard training — it's to ensure that when you do hard work, your body is in a state to benefit from it.

Help Improve This Article

Found an error or have a suggestion? This knowledge base is open-source. Contribute on GitHub to help the community.

Edit on GitHub