Training Load and Periodization: Complete Guide for Runners

Master training stress score, periodization, and load management to optimize performance and prevent overtraining

Key Takeaways: Training Load for Runners

  • Training Stress Score (TSS) quantifies how hard each run stresses your body—combining intensity and duration into a single actionable number
  • CTL (Chronic Training Load) measures your fitness level built over 42 days of consistent training—your long-term aerobic capacity
  • ATL (Acute Training Load) tracks recent fatigue from the past 7 days—your short-term training stress and recovery needs
  • TSB (Training Stress Balance) reveals your form: fitness minus fatigue equals readiness to race or need to recover
  • Periodization structures training load progression across training cycles to peak for goal races while preventing overtraining
  • Understanding running training load prevents the #1 cause of runner injuries: doing too much too soon

Why do some runners build fitness rapidly while others plateau or get injured? The answer lies in training load management. This comprehensive guide reveals how Training Stress Score (TSS), Chronic Training Load (CTL), Acute Training Load (ATL), and Training Stress Balance (TSB) transform subjective training into quantified, data-driven performance optimization.

Whether you're training for your first marathon, chasing a Boston qualifier, or preparing for ultra-distance events, mastering training load and periodization is the difference between reaching peak fitness and burning out before race day. This guide provides the most complete resource on training stress management specifically for runners—not cyclists or triathletes, but runners who face unique challenges from impact stress, neuromuscular fatigue, and musculoskeletal demands.

You'll learn how to calculate TSS for every run, build CTL safely, interpret TSB signals, structure periodized training blocks, execute perfect tapers, and use Run Analytics to automate the entire process while keeping your data private. By the end, you'll have the knowledge to manage training load like elite coaches do—with precision, purpose, and proven results.

Understanding Training Load in Running

Training load quantifies the cumulative stress imposed on your body by training. Unlike simply counting miles or hours, training load accounts for both volume (how long you train) and intensity (how hard you train), combining these dimensions into metrics that predict adaptation, fatigue, and injury risk.

Defining Training Load

Every run creates two simultaneous effects: fitness stimulus and fatigue accumulation. Training load metrics quantify this duality. A 60-minute easy run generates moderate training load—enough stimulus to maintain fitness without excessive fatigue. A 90-minute long run with threshold intervals creates high training load—significant fitness stimulus but substantial fatigue requiring recovery.

The challenge of effective training lies in applying sufficient load to drive adaptation without accumulating so much fatigue that performance declines or injury occurs. Too little load produces no improvement. Too much load leads to overtraining syndrome. Optimal training load hovers in the narrow band that maximizes adaptation while managing fatigue—and that band differs for every runner based on training history, genetics, recovery capacity, and life stress.

Why Training Load Matters

Managing training load solves the three critical challenges facing competitive runners:

🎯 Optimize Adaptation

Quantified training load ensures every workout contributes to your training plan. Too easy? You won't adapt. Too hard? You'll accumulate fatigue without additional benefit. Precise load management keeps you in the adaptation zone where fitness improves steadily.

🛡️ Prevent Overtraining

80% of running injuries stem from training errors—primarily "too much too soon." Training load metrics provide early warning signals when fatigue accumulation exceeds recovery capacity, allowing proactive rest before injury forces it.

📈 Time Peak Performance

Peak race performance requires fresh legs AND maintained fitness—conflicting goals solved by training load periodization. Understanding CTL, ATL, and TSB relationships enables precise tapering that eliminates fatigue while preserving fitness.

Internal vs External Load

Exercise science distinguishes between two training load categories:

External Load measures the work you perform: distance covered, pace maintained, elevation gained, training duration. These metrics are objective and easily measured by GPS watches. A 10K run at 5:00/km pace with 200m elevation gain represents specific external load regardless of who performs it.

Internal Load measures your physiological response to external work: heart rate elevation, lactate production, glycogen depletion, hormonal disruption, neuromuscular fatigue. The same 10K run produces different internal load depending on your fitness—easy for an elite runner but exhausting for a beginner.

Effective training load metrics like TSS bridge external and internal load by calculating stress relative to your individual threshold (Critical Running Speed). This personalization ensures your training load reflects YOUR physiological response, not generic workload.

How to Measure Training Load

Runners have multiple options for quantifying training load, ranging from simple RPE-based scores to sophisticated physiological metrics:

  • Session RPE (sRPE): Rate perceived effort 1-10, multiply by minutes = training load. Simple but highly subjective and inconsistent.
  • TRIMP (TRaining IMPulse): Heart rate-based calculation weighted by time in zones. Better than RPE but requires HR monitor.
  • Training Stress Score (TSS): Intensity² × Duration × 100, where intensity is relative to threshold. Most accurate for runners with established CRS.

This guide focuses on TSS-based metrics (TSS, CTL, ATL, TSB) because they provide the most actionable and scientifically validated framework for training load management in endurance sports. TSS forms the foundation for all advanced running training load analysis.

Training Stress Score (TSS) for Runners

Training Stress Score (TSS) represents the ultimate single-number summary of workout stress. By combining intensity and duration, TSS quantifies "how hard was that run?" with precision that accounts for both cardiovascular and musculoskeletal demands specific to running.

What is TSS?

TSS was developed by Dr. Andrew Coggan for cycling but has been adapted for running as rTSS (running Training Stress Score). The fundamental principle: one hour at your threshold pace = 100 TSS. This standard allows comparing workouts of different durations and intensities on a common scale.

🎯 TSS Standardization

The 100 TSS baseline provides intuitive scaling:

  • 30 minutes at threshold = ~50 TSS
  • 60 minutes at threshold = 100 TSS (definition)
  • 120 minutes at threshold = 200 TSS
  • 60 minutes at 80% of threshold intensity = ~64 TSS
  • 60 minutes at 110% of threshold intensity = ~121 TSS

How TSS is Calculated

The TSS formula mathematically combines intensity and duration:

TSS = (IF²) × Duration (hours) × 100

Where Intensity Factor (IF) represents effort relative to threshold:

IF = Normalized Pace / CRS Pace

For runners using pace (inverted from speed): IF = CRS pace / Average pace

If your CRS pace is 4:00/km and you run at 4:20/km: IF = 240/260 = 0.923

Worked Example: Tempo Run TSS Calculation

Runner Profile:

  • CRS Pace: 4:00/km (threshold pace for 30 minutes)
  • CRS: 15 km/hr or 240 seconds/km

Workout: 10km run in 43:20 (average pace 4:20/km = 260 sec/km)

Step 1: Calculate IF
IF = 240 sec/km ÷ 260 sec/km = 0.923

Step 2: Calculate Duration
43:20 = 43.33 minutes = 0.722 hours

Step 3: Calculate TSS
TSS = (0.923²) × 0.722 × 100
TSS = 0.852 × 0.722 × 100 = 61.5 TSS

Interpretation: This tempo run generated moderate training stimulus—typical of quality aerobic sessions.

Interpreting TSS Values

Understanding what different TSS ranges represent helps design effective workouts and manage weekly training load:

TSS Range Workout Type Recovery Needed Example Workouts
< 50 Easy Recovery < 24 hours 30-45min easy run, recovery jog, strides
50-100 Moderate Training 24-36 hours 60min steady run, easy long run
100-200 Hard Training 36-48 hours 90min with threshold work, quality long run
200-300 Very Hard 48-72 hours 2-3hr long runs, half marathon pace work
> 300 Extreme 72+ hours Marathon races, ultra-distance events

TSS Ranges by Workout Type

Different training sessions generate predictable TSS ranges based on duration and intensity:

  • Easy Runs (60-75% effort): 8-15 TSS per 10km, 40-75 TSS for 60-90 minutes
  • Long Runs (conversational pace): 100-200 TSS for 90-150 minutes of steady aerobic running
  • Tempo/Threshold Runs: 80-150 TSS for 20-40 minutes at threshold intensity with warmup/cooldown
  • Interval Sessions: 100-180 TSS depending on interval length, intensity, and recovery duration
  • VO2max Workouts: 90-140 TSS for high-intensity intervals (shorter than threshold but higher intensity)
  • Marathon Races: 250-350+ TSS (extreme stress requiring extended recovery)

💡 Running vs Cycling TSS

The same TSS value represents MORE physical stress in running than cycling due to impact forces and musculoskeletal loading. A runner accumulating 400 TSS/week experiences similar training adaptation to a cyclist with 600-700 TSS/week. Use running-specific TSS benchmarks, not cycling targets. Learn more about running TSS calculation.

Chronic Training Load (CTL): Your Fitness Level

Chronic Training Load (CTL) quantifies your long-term fitness by averaging daily TSS over the past 42 days with exponential weighting (recent days count slightly more than distant days). CTL represents the training load your body has adapted to—your aerobic fitness foundation built through consistent work.

What is CTL?

CTL answers the fundamental question: "How fit am I right now?" Unlike subjective feelings or single workout performances, CTL provides an objective fitness metric based on accumulated training stress your body has successfully processed and adapted to over six weeks.

Higher CTL indicates greater aerobic capacity, improved running economy, enhanced recovery systems, and increased resilience to training stress. A runner with CTL of 80 can handle weekly training loads that would devastate someone with CTL of 40—their cardiovascular, metabolic, and musculoskeletal systems have adapted to chronic stress exposure.

🔬 The Science: 42-Day Time Constant

CTL uses a 42-day exponentially weighted moving average (EWMA). This time constant reflects physiological adaptation timescales:

  • Capillary density changes occur over 4-6 weeks
  • Mitochondrial biogenesis requires 3-6 weeks
  • Aerobic enzyme adaptations develop across 4-8 weeks
  • Neuromuscular coordination improves over 4-12 weeks

The 42-day window captures these adaptations while remaining responsive enough to reflect recent training changes.

How CTL is Calculated

CTL updates daily based on yesterday's CTL and today's TSS:

CTLtoday = CTLyesterday + (TSStoday - CTLyesterday) × (1/42)

This exponential weighting means:

  • Today's workout influences CTL by 2.4% immediately
  • A workout from 14 days ago still contributes ~60% weight
  • A workout from 42 days ago contributes ~37% weight (1/e)
  • Workouts beyond 60 days have minimal influence (~25%)

CTL Build Example: 12-Week Marathon Block

Starting Point: CTL = 45 (intermediate runner, 4 runs/week, ~350 TSS/week)

Week 1-4: Build to 400 TSS/week → CTL rises to 52

Week 5-8: Build to 500 TSS/week → CTL rises to 62

Week 9-11: Peak at 550 TSS/week → CTL reaches 68

Week 12: Taper to 300 TSS → CTL holds at ~66

Result: +21 CTL points over 12 weeks = 47% fitness improvement

Building CTL Safely

The critical question for every runner: "How fast can I safely increase CTL?" Building too slowly wastes training time and limits progress. Building too fast accumulates fatigue faster than adaptation, leading to injury, illness, or overtraining syndrome.

⚠️ Safe CTL Ramp Rates for Runners
  • Beginners (CTL 15-35): +2-3 points per week maximum. Building base requires patience.
  • Intermediate (CTL 35-60): +3-5 points per week. Consistent progress without excessive injury risk.
  • Advanced (CTL 60-85): +5-7 points per week during build phases. Higher absolute load tolerance.
  • Elite (CTL 85-120+): +5-8 points per week. Years of training create robust adaptation systems.

These rates align with the "10% rule" for weekly mileage increases and reflect running's high impact stress on muscles, tendons, and bones. Exceeding these rates significantly increases injury risk.

CTL Targets by Goal

Appropriate CTL depends on your race distance goal, competitive level, and training history:

Goal Race Recreational Competitive Advanced Elite
5K/10K 30-45 50-70 70-90 90-110
Half Marathon 40-55 60-80 80-100 100-120
Marathon 50-65 70-90 90-110 110-130+
Ultra (50K+) 55-70 75-95 95-115 115-140+

These ranges represent peak CTL values after full training buildups. Begin training cycles 15-25 CTL points below target, allowing 12-20 weeks to build safely while maintaining consistency and managing fatigue.

Acute Training Load (ATL): Your Recent Fatigue

Acute Training Load (ATL) tracks short-term training stress by averaging daily TSS over the past 7 days. Unlike CTL (which changes slowly), ATL responds rapidly to training—jumping after hard weeks, dropping during recovery. ATL represents your current fatigue level and recovery state.

What is ATL?

ATL quantifies the training stress accumulated in recent days that hasn't yet been fully absorbed and adapted to. Think of ATL as your "training debt"—work performed that still requires recovery resources. High ATL indicates accumulated fatigue requiring rest before your next quality session.

The 7-day time constant reflects acute recovery timescales. Most runners need 24-72 hours to recover from individual workouts depending on intensity. A week of training stress captures this acute window while remaining responsive to daily changes.

How ATL is Calculated

ATL uses the same exponential weighting formula as CTL but with a 7-day time constant instead of 42:

ATLtoday = ATLyesterday + (TSStoday - ATLyesterday) × (1/7)

The shorter time constant makes ATL more responsive:

  • Today's workout influences ATL by 14.3% immediately
  • A workout from 3 days ago still contributes ~65% weight
  • A workout from 7 days ago contributes ~37% weight (1/e)
  • Workouts beyond 10 days have minimal influence

Managing ATL

Effective training requires actively managing ATL to balance stimulus and recovery:

📊 ATL Patterns

Build Weeks: ATL rises as you accumulate training stress. Target ATL of 60-80 for competitive runners during hard training blocks.

Recovery Weeks: ATL drops when you reduce volume. Every 3-4 weeks, let ATL fall 25-40% to consolidate adaptations.

Taper: ATL crashes during pre-race tapers (drop 50%+), revealing fitness beneath fatigue.

⚠️ Warning Signs

ATL > 100: Very high fatigue. Appropriate for elite runners during peak weeks but unsustainable for most.

ATL rising 3+ weeks straight: Fatigue accumulation without recovery. Injury risk elevated. Schedule down week.

ATL spike > 50% above average: Single week of excessive load. Monitor closely for overtraining signals.

🎯 Optimal Ranges

Maintenance: ATL matches CTL (TSB near zero). Sustainable indefinitely.

Building: ATL exceeds CTL by 10-20 points. Productive overload stimulating adaptation.

Recovery: ATL below CTL by 10-20 points. Absorbing training stress, dissipating fatigue.

ATL Response Example: Hard Week + Recovery

Starting State: CTL = 60, ATL = 58, TSB = +2 (balanced)

Hard Week: 550 TSS over 7 days (daily average = 79 TSS)

  • ATL rises rapidly: 58 → 65 → 70 → 74 → 77
  • CTL rises slowly: 60 → 61 → 62 → 63 → 64
  • TSB becomes negative: +2 → -4 → -8 → -11 → -13

Recovery Week: 300 TSS over 7 days (daily average = 43 TSS)

  • ATL drops rapidly: 77 → 72 → 67 → 62 → 58
  • CTL continues rising slightly: 64 → 65 → 65 → 66 → 66
  • TSB becomes positive: -13 → -7 → -2 → +4 → +8

Result: Hard week created overload (TSB -13). Recovery week dissipated fatigue while retaining fitness gains (+6 CTL). This pattern defines effective periodization.

Training Stress Balance (TSB): Form and Freshness

Training Stress Balance (TSB) represents the difference between your fitness (CTL) and fatigue (ATL). This single number reveals whether you're fresh or fatigued, ready to race or need recovery. TSB is the most actionable metric for day-to-day training decisions.

What is TSB?

TSB quantifies the fitness-fatigue relationship discovered by exercise physiologists in the 1970s: your current performance potential equals fitness minus fatigue. When TSB is positive, you're fresh (low fatigue relative to fitness)—ideal for races. When TSB is negative, you're fatigued (recent training stress exceeds current fitness)—normal during training blocks but problematic if extreme or prolonged.

TSB Formula: CTL - ATL

The calculation is elegantly simple:

TSB = CTLyesterday - ATLyesterday

Using yesterday's values (not today's) prevents same-day workouts from affecting TSB:

  • Positive TSB: Fitness > Fatigue. You're fresh and ready to perform.
  • Zero TSB: Fitness = Fatigue. Balanced maintenance state.
  • Negative TSB: Fatigue > Fitness. You're accumulated training stress.

Interpreting TSB Values

Understanding TSB ranges enables precise training and racing decisions:

TSB Range Status Interpretation Recommended Action
< -30 Overtraining Risk Extreme fatigue. Very high injury risk. Performance declining. Immediate recovery required. Reduce volume 50%+ or take rest days. Consider medical consultation if symptoms persist.
-20 to -30 Optimal Training Block Productive overload. Maximizing fitness stimulus while manageable. Continue plan but monitor closely. Watch for excessive soreness, poor sleep, or elevated resting HR.
-10 to -20 Moderate Training Load Standard training accumulation. Appropriate for most training weeks. Normal training state. Can handle quality threshold or interval sessions with proper recovery between.
-10 to +15 Transition/Maintenance Balanced state with slight fatigue or freshness. Good equilibrium. Suitable for B/C priority races, testing workouts, or active recovery weeks. Maintenance mode.
+15 to +25 Peak Race Form Fresh and fit. Optimal performance window for key races. A-priority races. Expect personal bests or season-best performances. Don't waste this window on training.
+25 to +35 Very Fresh Highly rested. Good for shorter, speed-focused events. Best for 5K-10K races, time trials, track events where speed and power dominate over endurance.
> +35 Detraining Too fresh. Fitness declining from extended inactivity or over-tapering. Resume training. Fitness eroding from lack of stimulus. Don't extend taper beyond 2-3 weeks.

TSB for Race Day

Target TSB on race morning varies by distance. Shorter races requiring speed need higher TSB (more freshness). Longer races requiring endurance tolerate lower TSB (some fatigue acceptable):

🎯 Target TSB by Running Distance

  • 5K Races: TSB +25 to +35 (7-10 day taper emphasizing freshness and speed)
  • 10K Races: TSB +20 to +30 (10-12 day taper for power and speed)
  • Half Marathon: TSB +15 to +25 (10-14 day taper balancing freshness with endurance)
  • Marathon: TSB +10 to +20 (14-21 day taper with volume reduction but maintaining some load)
  • Ultra Marathon (50K+): TSB +5 to +15 (7-14 day taper, maintain volume but reduce intensity to preserve endurance)

These ranges reflect racing physiology: shorter races need neuromuscular freshness (higher TSB), while ultra distances require maintained aerobic systems (moderate TSB).

Periodization: Structured Training Progression

Periodization is the systematic organization of training into specific phases (periods) designed to produce peak performance at predetermined times while managing fatigue and preventing overtraining. Instead of random training or constant intensity, periodization structures load progression to maximize adaptation.

What is Periodization?

Periodization emerged from Eastern European sports science in the 1960s when researchers discovered that planned variation in training load produces superior results compared to constant training stress. The fundamental principle: you cannot maintain peak fitness indefinitely, but you can predictably build fitness and time peaks through structured load manipulation.

For runners, periodization solves three critical problems:

  • Adaptation Plateau: Constant training stress produces diminishing returns as your body adapts. Periodization varies stimuli to prevent adaptation plateaus.
  • Overtraining Risk: Continuous high-intensity training accumulates fatigue leading to injury or burnout. Periodization builds recovery phases into the plan.
  • Race Timing: You can't race at 100% year-round. Periodization peaks fitness for goal races while accepting lower performance at other times.

Macrocycles, Mesocycles, Microcycles

Periodization operates at three timescales, each serving specific purposes:

📅 Macrocycle

Duration: 16-52 weeks (season or annual plan)

Purpose: Complete training progression from base building to race peak to recovery

Example: 24-week marathon training plan or full year training two marathon peaks (spring + fall)

🗓️ Mesocycle

Duration: 3-6 weeks (training phase or block)

Purpose: Target specific physiological adaptations (base, build, peak, taper)

Example: 4-week base building mesocycle focusing on aerobic development

📆 Microcycle

Duration: 1 week (7 days)

Purpose: Balance training stress and recovery within weekly structure

Example: Weekly pattern: hard Tuesday, easy Wednesday, long Saturday, recovery Sunday

Linear vs Non-Linear Periodization

Two primary periodization models dominate endurance training, each with distinct characteristics and applications:

Aspect Linear Periodization Non-Linear (Undulating)
Structure Sequential phases (base → build → peak → race) Varied workouts within weeks (Monday threshold, Wednesday VO2max, Saturday long run)
Load Progression Gradually increasing volume then intensity across weeks Variable intensity day-to-day with overall volume control
Best For Single peak races (goal marathon, championship), beginners Multiple race peaks, experienced runners, maintaining fitness
Advantages Clear progression, excellent for building base, predictable peaks Prevents boredom, addresses multiple systems simultaneously, flexible
Disadvantages Risk of detraining specific systems during single-focus phases Requires more planning, harder to execute perfectly, easy to over-train
CTL Pattern Steady rise across training cycle with distinct taper Gradual rise with weekly undulations from varied intensity

Periodization for Different Goals

Optimal periodization structure depends on race distance, competitive level, and season structure:

  • Marathon Training: Linear periodization excels. 12-20 weeks: base phase (8-12 weeks building volume), build phase (4-6 weeks adding intensity), peak phase (2-3 weeks race simulation), taper (10-21 days). Target CTL progression: +25 to +35 points from start to peak.
  • 5K-10K Racing: Non-linear periodization maintains speed while building endurance. 8-12 week cycles alternating threshold, VO2max, and tempo work within weeks. Shorter tapers (7-10 days). Target CTL: +15 to +25 points per cycle.
  • Ultra Marathon: Modified linear with emphasis on volume over intensity. Extended base phases (12-16 weeks), moderate build intensity, longer peak phase (3-4 weeks), minimal taper (5-10 days). Target CTL progression: +30 to +45 points reflecting extreme volume.
  • Multiple Race Season: Non-linear base maintenance with 3-4 week mini-peaks before A-races. Maintain CTL year-round (fluctuating ±10 points), use 2-3 week focused builds before priorities, recover 1-2 weeks between race efforts.

Base Building Phase: The Foundation

Base building establishes the aerobic foundation supporting all subsequent training. This phase prioritizes volume over intensity, developing the physiological infrastructure (mitochondria, capillaries, aerobic enzymes, musculoskeletal resilience) required to absorb later high-intensity work without injury.

What is Base Building?

The base phase focuses on Zone 2 running—conversational pace aerobic training that builds endurance capacity without excessive fatigue. This "boring" training creates adaptations impossible to achieve with intensity-focused approaches:

  • Mitochondrial Density: More cellular powerhouses producing aerobic energy
  • Capillary Networks: Increased oxygen delivery to working muscles
  • Fat Oxidation: Enhanced ability to burn fat, sparing glycogen for harder efforts
  • Tendon Strength: Collagen remodeling strengthens connective tissue
  • Running Economy: Neuromuscular patterns become more efficient through repetition

How Long to Build Base?

Base phase duration depends on training history, starting fitness, and goal race distance:

📊 Base Building Duration Guidelines

  • Beginners (new to structured training): 12-16 weeks minimum. Build aerobic foundation before adding intensity.
  • Intermediate (1-3 years training): 8-12 weeks. Re-establish base after off-season or recovery breaks.
  • Advanced (3+ years training): 6-8 weeks. Shorter base phases since you maintain year-round aerobic fitness.
  • Post-Injury Return: 8-16 weeks depending on layoff duration. Rebuild gradually to prevent re-injury.

Marathons and ultras require longer base phases than 5K-10K training due to extreme endurance demands.

Training During Base Phase

Base building emphasizes volume and frequency over intensity. The goal: accumulate time at aerobic intensities that stimulate adaptation without creating fatigue requiring extended recovery.

Typical Base Week Structure:

  • Easy Runs: 4-5 per week at Zone 2 pace (conversational). 40-90 minutes each.
  • Long Run: 1 per week, gradually progressing from 60 minutes to 120-180+ minutes depending on goal race.
  • Strides: 4-6×100m at 5K pace after easy runs (2-3 times weekly) to maintain neuromuscular coordination.
  • Limited Intensity: One tempo run every 7-10 days (optional) or occasional progression runs (finish 10-15 seconds faster than start).
  • Rest Days: 1-2 per week for beginners, 0-1 for advanced runners with high training volume tolerance.

Weekly TSS Targets: 300-450 for recreational runners, 450-600 for competitive, 600-800+ for advanced/elite. Build TSS gradually (increase 5-10% weekly) while monitoring fatigue signals.

CTL Targets for Base Building

Base phase CTL progression should be gradual and sustainable. Rushing the base creates fatigue without proper aerobic adaptation:

Runner Level Starting CTL Target CTL (End of Base) Weekly Increase Duration
Beginner 15-25 35-45 +2-3 12-16 weeks
Intermediate 30-45 50-65 +3-4 8-12 weeks
Advanced 50-65 70-85 +4-5 6-10 weeks
Elite 70-90 95-115 +5-7 6-8 weeks

⚠️ Base Building Mistakes to Avoid

  • Running Too Hard: Most runners make base runs too fast. Zone 2 should feel EASY. If you can't hold conversation, slow down.
  • Adding Intensity Too Soon: Resist urge to add intervals or tempo runs. Focus on volume. Intensity comes in build phase.
  • Increasing Volume Too Fast: Follow the 10% rule. Jumping from 40km to 60km weekly invites injury.
  • Skipping Rest Days: Adaptation occurs during recovery, not training. Rest is productive training time.
  • Ignoring Fatigue Signals: Persistent soreness, elevated resting HR, poor sleep = take extra rest day before injury forces it.

Build and Peak Phases

After establishing aerobic base, build and peak phases layer intensity onto your aerobic foundation. Build phase adds threshold and tempo work to raise your lactate threshold. Peak phase incorporates race-specific training to prepare your body for goal event demands.

Build Phase: Adding Intensity

The build phase transitions from pure volume focus to intensity plus volume. Goal: raise your lactate threshold and improve your body's ability to buffer and clear lactate while maintaining the aerobic base built in previous phase.

Build Phase Characteristics (4-6 weeks):

  • Volume: Maintain or slightly reduce from base phase (5-10% reduction acceptable)
  • Intensity: Add 1-2 quality sessions per week (threshold runs, tempo intervals, progressive runs)
  • Workouts: Lactate threshold focus at 96-100% of CRS pace for 20-40 minutes total work
  • TSS Distribution: 70% Zone 2 easy running, 20% threshold work (Zone 4), 10% recovery/strides
  • Weekly TSS: Increase 5-8% weekly. Typical: 500-650 for competitive runners, 650-800+ for advanced

Sample Build Week:

  • Monday: 60 min Zone 2 easy (65 TSS)
  • Tuesday: 4×1 mile at threshold + warmup/cooldown (110 TSS)
  • Wednesday: 45 min Zone 2 recovery (40 TSS)
  • Thursday: 75 min Zone 2 steady (85 TSS)
  • Friday: Rest or 30 min easy with strides (25 TSS)
  • Saturday: 25min tempo run + warmup/cooldown (90 TSS)
  • Sunday: 120 min long run Zone 2 (135 TSS)
  • Total: 550 TSS, TSB likely -15 to -25 (productive overload)

Peak Phase: Race-Specific Training

Peak phase fine-tunes race readiness by incorporating race-pace work and race-specific demands (long runs at marathon pace, VO2max intervals for 5K racing, terrain-specific training for trail races).

Peak Phase Characteristics (2-4 weeks):

  • Specificity: Workouts mimic race demands (pace, distance, terrain, conditions)
  • Volume: Maintain or slightly reduce to manage accumulating fatigue
  • Intensity: Mix of threshold work AND race-pace efforts
  • Quality Over Quantity: Every workout has clear purpose. Eliminate "junk miles."
  • Mental Preparation: Practice race day nutrition, pacing, gear in peak workouts

Peak Phase Examples by Race Distance:

  • Marathon: 20-mile long runs with 10-15 miles at marathon pace, mid-week threshold runs 8-12 miles
  • Half Marathon: 15-16 mile long runs with 8-10 miles at half marathon pace, tempo runs 6-8 miles
  • 10K: 8-12 mile long runs with 4-6 miles at 10K pace, threshold intervals (6×1 mile)
  • 5K: VO2max intervals (5×1000m at 5K pace), tempo runs with surges simulating race rhythm

Managing Load in Build/Peak

Build and peak phases create highest injury risk because you're combining high volume AND high intensity. Managing training load becomes critical:

⚠️ Build/Peak Load Management
  • Monitor TSB: Target TSB of -15 to -25 during peak weeks. Below -30 = high injury/overtraining risk.
  • Schedule Recovery Weeks: Every 3-4 weeks, reduce TSS by 30-40% for one week. Let TSB rise to -5 to +10.
  • Watch Resting HR: Elevated resting HR (5+ bpm above baseline) suggests inadequate recovery. Add rest day.
  • Quality Over Quantity: Better to skip workout than force it while overly fatigued. One missed session won't hurt; injury from over-training derails entire training cycle.
  • Respect the 48-Hour Rule: Allow 48 hours between high-intensity sessions. Monday threshold + Wednesday intervals + Friday tempo = recipe for injury.

CTL/ATL/TSB Targets for Build/Peak Phases:

Phase CTL Target ATL Range TSB Range Status
Build Phase Rising 4-6/week 65-85 -15 to -25 Productive overload
Recovery Week Stable or +1-2 50-65 -5 to +10 Consolidating adaptations
Peak Phase Stable (highest of cycle) 70-90 -20 to -30 Maximum stimulus
Pre-Taper Week Begins slight decline 65-80 -15 to -20 Transitioning to freshness

Taper and Recovery Strategies

The taper reduces training volume and intensity before goal races to eliminate accumulated fatigue while preserving fitness. Proper tapering is the difference between good performances and personal bests—research shows well-executed tapers improve performance 2-4% on race day.

Tapering for Peak Performance

Taper physiology exploits the different time constants of CTL (42 days) and ATL (7 days). By dramatically reducing training load, ATL drops rapidly (fatigue dissipates quickly), while CTL drops slowly (fitness persists). The result: high fitness with low fatigue = optimal TSB for racing.

Taper Principles:

  • Reduce Volume, Maintain Intensity: Cut mileage 50-70% but keep some intensity (short threshold efforts, race-pace bursts) to maintain neuromuscular sharpness
  • Frequency Maintenance: Keep running most days (reduce duration, not frequency) to avoid feeling "rusty"
  • Progressive Reduction: Gradual taper over 10-21 days works better than sudden "crash taper"
  • Individual Variation: Some runners need longer tapers (masters, high-mileage trainers), others shorter (younger runners, lower weekly volume)

Taper Duration by Race Distance

Optimal taper length correlates with race distance and training volume:

Race Distance Taper Duration Volume Reduction Target TSB Notes
5K 7-10 days 50-60% +25 to +35 Emphasis on freshness and speed
10K 10-12 days 55-65% +20 to +30 Balance speed with short endurance
Half Marathon 10-14 days 60-70% +15 to +25 Moderate freshness, retain endurance
Marathon 14-21 days 60-70% +10 to +20 Longer taper, maintain some volume
Ultra (50K+) 7-14 days 50-60% +5 to +15 Shorter taper, preserve endurance systems

Using TSB for Taper

TSB provides objective feedback during taper, removing guesswork about whether you're fresh enough or rested too long:

Marathon Taper: TSB Progression Example

3 Weeks Before Race: CTL = 68, ATL = 85, TSB = -17 (coming off peak training)

Week -3: Reduce to 450 TSS (from 550)
→ CTL = 67, ATL = 72, TSB = -5 (fatigue dropping)

Week -2: Reduce to 300 TSS
→ CTL = 65, ATL = 55, TSB = +10 (becoming fresh)

Week -1: Reduce to 200 TSS (race week)
→ CTL = 63, ATL = 45, TSB = +18 (race ready)

Race Day: TSB = +18 = optimal marathon form (fresh but not detrained)

Taper Troubleshooting:

  • TSB rising too slowly? Reduce volume more aggressively. Cut additional 10-15% from current week.
  • TSB exceeding +30? You've tapered too long or too hard. Add short tempo run or race-pace intervals to maintain sharpness.
  • Feeling "flat" during taper? Common psychological response to lower training volume. Trust the process. Legs feel heavy 3-5 days out but sharp on race day.
  • Resting HR dropping? Good sign. HR typically drops 5-10 bpm during successful taper as recovery completes.

Post-Race Recovery

Recovery after goal races is non-negotiable. Racing creates extreme acute stress (300-400+ TSS for marathons) requiring extended recovery before resuming normal training:

⚠️ Post-Race Recovery Guidelines

  • 5K/10K: 3-7 days easy running or rest before quality training resumes
  • Half Marathon: 7-10 days easy running before threshold work, 10-14 days before high intensity
  • Marathon: 14-21 days easy running minimum. Some coaches recommend 1 day recovery per race mile (26 days for marathon)
  • Ultra (50K+): 21-30+ days depending on distance and terrain. Musculoskeletal recovery takes longer than cardiovascular

During recovery, target TSS of 200-350/week (50-60% of normal training load) until TSB rises to +15 to +25, then gradually rebuild CTL.

Avoiding Training Load Pitfalls

Understanding training load concepts intellectually differs from applying them successfully. These common mistakes derail progress for runners at all levels:

Overtraining Signals

Overtraining syndrome develops when training stress chronically exceeds recovery capacity. Early detection prevents progression to full-blown overtraining requiring months of recovery:

  • Performance Decline: Workouts that were manageable become difficult. Paces feel harder at same HR. Race times stagnate or worsen.
  • Elevated Resting HR: Morning HR 5-10+ bpm above baseline for 3+ consecutive days.
  • Sleep Disruption: Difficulty falling asleep, frequent waking, or unrefreshing sleep despite adequate opportunity.
  • Mood Changes: Increased irritability, anxiety, depression, or loss of motivation to train.
  • Persistent Soreness: Muscles remain sore 48+ hours after workouts. Legs feel "dead" on easy runs.
  • Illness Frequency: Catching colds frequently or symptoms lasting longer than usual (immune suppression).
  • TSB Warning: TSB below -30 for 7+ consecutive days with performance declining.

Action: Take 3-7 complete rest days. Resume training at 50% of previous volume for 1-2 weeks. Rebuild gradually while monitoring symptoms.

Ramping Too Fast

The most common training error: increasing training load faster than your body can adapt. This manifests as:

  • CTL Jumps: Increasing CTL by 8+ points per week consistently. Tissues can't adapt fast enough to stress.
  • Mileage Spikes: Jumping from 50km to 70km weekly (40% increase vs 10% rule maximum).
  • Skipping Base: Adding intensity before establishing aerobic foundation. Running intervals when CTL is still low.
  • No Recovery Weeks: Building load for 5-6 weeks straight without scheduled down weeks.

Prevention: Respect CTL ramp rate limits (+2-5 points/week depending on level). Schedule recovery weeks every 3-4 weeks. Build base fully before adding significant intensity.

Ignoring Recovery

Training stimulus occurs during workouts, but adaptation occurs during recovery. Common recovery mistakes:

  • No Easy Days: Running all sessions at moderate-hard intensity. The "grey zone" training that builds fatigue without quality stimulus.
  • Insufficient Sleep: Consistently getting <7 hours. Sleep is when growth hormone peaks and tissue repair occurs.
  • Ignoring Nutrition: Under-fueling training. Inadequate protein or carbohydrate prevents glycogen replenishment and muscle repair.
  • Life Stress Neglect: Failing to account for work stress, family stress, travel, or illness when planning training load.
  • No Off Days: Running 7 days weekly when body needs 1-2 complete rest days for adaptation.

Solution: Make easy days TRULY easy (Zone 2 only). Prioritize sleep (8+ hours for hard training). Take 1-2 complete rest days weekly. Reduce training load during high-stress life periods.

Tracking Training Load with Run Analytics

Run Analytics automates every aspect of training load management while maintaining complete privacy. Unlike cloud-based platforms that upload your data to external servers, Run Analytics processes everything locally on your iPhone—giving you the power of elite coaching analytics without compromising data ownership.

Privacy-First Tracking

Your training data reveals sensitive information: where you live (GPS tracks), when you're away from home (workout timing), your fitness level (performance metrics), and health status (heart rate, fatigue). Run Analytics architecture ensures this data never leaves your device:

🔒 Run Analytics Privacy Features

  • Local Processing: All TSS, CTL, ATL, TSB calculations happen on-device using iPhone processing power
  • No Cloud Uploads: App never transmits workout data, GPS tracks, or metrics to external servers
  • No Accounts: No registration, login, email, or personal information required to use the app
  • Apple Health Integration: Reads workouts from Health app (which Apple stores locally with optional end-to-end encrypted iCloud backup)
  • Complete Control: Export data in JSON, CSV, HTML, or PDF formats when YOU decide to share with coaches or backup

Automated Calculations

Run Analytics eliminates manual TSS calculation and spreadsheet tracking. The app automatically:

  • Calculates TSS: Every run processed using your Critical Running Speed as threshold reference. Accounts for pace variability and terrain.
  • Updates CTL Daily: 42-day exponentially weighted moving average updated after each workout. Visual charts show fitness trends.
  • Tracks ATL: 7-day exponentially weighted moving average reveals recent fatigue accumulation and recovery state.
  • Computes TSB: Form metric calculated daily showing whether you're fresh (positive TSB) or fatigued (negative TSB).
  • Monitors Trends: Long-term CTL progression, weekly TSS totals, and monthly load patterns visualized with intuitive charts.

Personalized Recommendations

Run Analytics doesn't just display numbers—it provides actionable guidance based on your current training state:

  • CTL Ramp Warnings: Alerts when CTL increases exceed safe rates for your fitness level, preventing "too much too soon" injuries.
  • Recovery Suggestions: Recommends rest or easy days when TSB drops below optimal ranges or resting HR elevates.
  • Taper Guidance: Suggests when to begin taper based on race date and current CTL/TSB values for optimal race day freshness.
  • Zone Updates: Prompts for CRS retesting when sufficient time has passed or fitness changes suggest outdated zones.
  • Weekly Planning: Proposes target weekly TSS ranges based on current CTL and your selected training phase (base, build, peak, recovery).

All recommendations adapt to YOUR physiology, training history, and goals—not generic cookie-cutter advice. Download Run Analytics and experience the power of personalized training load management with complete data privacy.

Putting It All Together

Theory becomes valuable only when applied consistently. These practical examples show how to integrate TSS, CTL, ATL, and TSB into daily training decisions:

Sample Training Week

Runner Profile: Competitive marathoner, CTL = 65, building toward spring marathon 8 weeks away

Week 6 Before Marathon (Build Phase)

Day Workout TSS Daily Total
Monday 60 min Zone 2 easy + 6×100m strides 70 70
Tuesday 15min warmup + 5×1600m at threshold (2min recovery) + 10min cooldown 125 195
Wednesday 45 min Zone 2 recovery run 42 237
Thursday 80 min Zone 2 steady run 90 327
Friday Rest day (mobility work only) 0 327
Saturday 10min warmup + 8 miles at marathon pace + 10min cooldown 115 442
Sunday 2 hours Zone 2 long run 140 582

Week Summary:

  • Total Weekly TSS: 582 (8% increase from previous week's 540)
  • Starting CTL: 65 → Ending CTL: 68 (+3 points = safe progression)
  • Starting TSB: -18 → Ending TSB: -22 (productive training load)
  • Next Week Plan: Reduce to 420 TSS (recovery week) to let TSB rise to -10 before final 3-week build

Monthly Load Planning

12-Week Marathon Training Block: CTL Progression Strategy

  • Weeks 1-4 (Base Extension):
    • Weekly TSS: 450, 480, 500, 380 (recovery week)
    • CTL Progression: 58 → 60 → 62 → 63 → 63
    • Focus: Volume at Zone 2, one threshold session weekly
  • Weeks 5-8 (Build Phase 1):
    • Weekly TSS: 520, 550, 570, 420 (recovery week)
    • CTL Progression: 63 → 66 → 68 → 70 → 70
    • Focus: Two quality sessions weekly (threshold + marathon pace work)
  • Weeks 9-11 (Peak Phase):
    • Weekly TSS: 580, 600, 580
    • CTL Progression: 70 → 73 → 75 → 75 (peak)
    • Focus: Race simulation long runs, threshold maintenance, high volume
  • Week 12 (Pre-Taper):
    • Weekly TSS: 450
    • CTL Progression: 75 → 73
    • Focus: Begin reducing volume, maintain intensity briefly
  • Weeks 13-14 (Taper + Race):
    • Weekly TSS: Week 13 = 300, Week 14 = 150 + race (~320 total)
    • CTL Progression: 73 → 70 → 68
    • TSB Progression: -20 → -10 → +5 → +15 (race day)
    • Focus: Freshness without detraining, short race-pace efforts, confidence building

Result: +17 CTL points over 14 weeks (29% fitness increase), arriving at marathon with TSB +15 (optimal form), ready for personal best performance.

💡 Key Training Load Principles

  • Build CTL gradually (3-5 points weekly for most runners) through consistent training
  • Accept negative TSB (-15 to -25) during build phases as productive fatigue
  • Schedule recovery weeks every 3-4 weeks to prevent cumulative fatigue
  • Use TSB to guide taper timing and race readiness (target +10 to +25 depending on distance)
  • Monitor trends over single data points—one bad workout doesn't indicate overtraining
  • Combine objective metrics (CTL/ATL/TSB) with subjective feedback (soreness, motivation, sleep quality)
  • Track training stress systematically using Run Analytics for automated calculations and insights

Frequently Asked Questions: Training Load and Periodization

What is Training Stress Score (TSS) in running?

Training Stress Score (TSS) quantifies workout intensity and duration into a single number representing total training stress. Calculated as (Intensity Factor²) × Duration (hours) × 100, where intensity is relative to your Critical Running Speed (CRS). One hour at threshold pace = 100 TSS by definition. A 60-minute easy run generates ~60-70 TSS, while a marathon race creates 300-400+ TSS. TSS enables objective comparison of different workouts and forms the foundation for CTL/ATL/TSB calculations.

How do you calculate TSS for a run?

Calculate running TSS using the formula: TSS = (IF²) × Duration (hours) × 100, where Intensity Factor (IF) = your threshold pace divided by average pace for the run. Example: If your CRS pace is 4:00/km and you run 10km at 4:20/km in 43:20 minutes (0.722 hours), then IF = 240/260 = 0.923, so TSS = (0.923²) × 0.722 × 100 = 61.5 TSS. Run Analytics automates this calculation for every run using your personalized CRS. Learn the complete TSS calculation methodology.

What is a good CTL for a marathoner?

Target CTL for marathon racing depends on your competitive level: Recreational marathoners: CTL 50-65; Competitive (sub-3:30 goal): CTL 70-90; Advanced (sub-3:00 goal): CTL 90-110; Elite runners: CTL 110-130+. These represent peak CTL values after 12-20 week buildups. Begin training 15-25 points below target, building +3-5 CTL points weekly. Higher CTL indicates greater aerobic fitness and ability to handle marathon-specific training volume (80-120 km/week for competitive runners).

What does TSB mean in training?

TSB (Training Stress Balance) equals fitness (CTL) minus fatigue (ATL), revealing whether you're fresh or fatigued. Positive TSB means low fatigue relative to fitness—ideal for racing. Negative TSB indicates accumulated training stress—normal during build phases. TSB ranges: Below -30 = overtraining risk; -20 to -30 = optimal training block; -10 to +15 = maintenance; +15 to +25 = peak race form; Above +35 = detraining from excessive rest. Use TSB to guide training intensity and taper timing. Target TSB +10 to +20 for marathon race day.

How fast should I build my CTL?

Safe CTL ramp rates depend on your current fitness level: Beginners (CTL 15-35): +2-3 points/week; Intermediate (CTL 35-60): +3-5 points/week; Advanced (CTL 60-85): +5-7 points/week; Elite (CTL 85+): +5-8 points/week during build phases. These rates align with the "10% rule" for weekly mileage increases and reflect running's high impact stress. Exceeding these rates significantly increases injury risk. Schedule recovery weeks (reduce TSS 30-40%) every 3-4 weeks to consolidate adaptations. Monitor TSB—if consistently below -30, you're building too fast.

What TSB should I have on race day?

Optimal race day TSB varies by distance: 5K races: TSB +25 to +35 (need maximum freshness for speed); 10K: TSB +20 to +30; Half Marathon: TSB +15 to +25; Marathon: TSB +10 to +20 (need some endurance retention); Ultra (50K+): TSB +5 to +15 (minimal taper preserves aerobic systems). Shorter races require higher TSB because performance depends on neuromuscular power. Longer races tolerate lower TSB because aerobic endurance matters more. Begin taper 7-21 days before race (longer for marathons) to achieve target TSB range.

Is TSS accurate for running?

Yes, TSS accurately quantifies running training stress when properly calculated using your individual Critical Running Speed as the threshold reference. Research shows strong correlation (r > 0.85) between TSS-based training load and performance outcomes. However, running TSS represents MORE total physical stress than cycling TSS at the same value due to impact forces and musculoskeletal loading. A runner accumulating 400 TSS/week experiences similar training adaptation to a cyclist with 600-700 TSS/week. Use running-specific TSS benchmarks and account for impact stress when interpreting values. Run Analytics provides running-specific TSS calculations and recommendations.

How long does it take to build fitness (CTL)?

Building meaningful CTL requires 8-20 weeks depending on starting fitness and goals. Beginners: 12-16 weeks to build from CTL 20 to 40 (establishing base fitness). Intermediate: 12-16 weeks to build from CTL 45 to 65 (marathon-ready fitness). Advanced: 12-14 weeks to build from CTL 65 to 85 (competitive racing fitness). CTL responds to consistent training with safe weekly increases (+3-5 points/week). Trying to rush CTL gains leads to injury or overtraining. Plan training cycles allowing adequate time for gradual CTL progression. After breaks (injury, off-season), allow 8-12 weeks to rebuild previous CTL safely.

What's the difference between CTL and ATL?

CTL (Chronic Training Load) measures long-term fitness—42-day exponentially weighted average of daily TSS representing adaptations your body has made to training stress. ATL (Acute Training Load) measures short-term fatigue—7-day exponentially weighted average representing recent training stress requiring recovery. CTL changes slowly (weeks to build), while ATL changes quickly (spikes after hard weeks, drops during recovery). The relationship between them (TSB = CTL - ATL) reveals your current training state. High CTL with low ATL = fit and fresh (good for racing). Rising ATL faster than CTL = productive training overload. Both metrics together provide complete picture of fitness and fatigue.

Can you over-train with TSS tracking?

Yes, tracking TSS/CTL/ATL/TSB doesn't prevent overtraining—it provides early warning signals so you can intervene before reaching overtraining syndrome. Key warning signs: TSB below -30 for 7+ consecutive days, CTL increasing faster than safe ramp rates, elevated resting heart rate, declining performance despite good metrics, or persistent fatigue. TSS metrics are tools, not rules—combine them with subjective feedback (sleep quality, motivation, soreness) and physiological markers (resting HR, HRV). If metrics suggest rest but you feel great, you might be fine. If metrics look good but you feel terrible, prioritize subjective feedback. Learn more about managing training load with zones.

Does Run Analytics calculate TSS automatically?

Yes, Run Analytics automatically calculates TSS, CTL, ATL, and TSB for every run without manual input. The app reads workout data from Apple Health, calculates Intensity Factor using your personalized CRS, computes TSS for each run, updates CTL (42-day average) and ATL (7-day average) daily, and displays TSB showing your current form. All processing happens locally on your iPhone—no cloud uploads, complete privacy. Visual charts show fitness trends over weeks and months. The app also provides recommendations for recovery timing, taper guidance, and CTL ramp rate warnings based on your current training state. Download Run Analytics for automated training load management with privacy-first architecture.

How is running TSS different from cycling TSS?

Running and cycling TSS use the same IF² formula, but running TSS represents more total physical stress per TSS point: Impact Stress: Running generates 2-3× body weight ground reaction forces each stride, creating musculoskeletal stress absent in cycling. Recovery Needs: Runners need more recovery for same TSS—400 TSS/week in running ≈ 600-700 TSS/week in cycling for equivalent training adaptation. Weekly Targets: Runners typically accumulate 300-500 TSS/week (recreational), 500-700 (competitive), 700-900+ (elite), while cyclists may exceed 800-1000+ at similar levels. Input Metric: Running uses pace/speed, cycling uses power meters. Use running-specific benchmarks, not cycling targets when planning training load.

Master Your Training Load and Periodization

You now understand the complete framework for training load management: TSS quantifies every workout's stress, CTL represents your long-term fitness, ATL tracks recent fatigue, and TSB reveals your readiness to race or need to recover. Periodization structures these metrics into training phases that systematically build fitness while managing fatigue.

The difference between runners who achieve their goals and those who plateau or get injured often comes down to training load management. By mastering TSS, CTL, ATL, and TSB, you gain the same data-driven insights elite coaches use to optimize training—precise load quantification, objective fatigue monitoring, and scientific taper timing.

🎯 Next Steps: Apply Training Load Management

  • Calculate Your CRS: Establish your threshold pace using our free CRS calculator—the foundation for accurate TSS calculation
  • Learn Training Zones: Understand how training zones relate to TSS and intensity-based training
  • Explore Performance Metrics: Discover how training load connects to VO2max, lactate threshold, and running economy
  • Download Run Analytics: Automate TSS/CTL/ATL/TSB tracking with our privacy-first iOS app (7-day free trial)
  • Plan Your Season: Structure your next training cycle using periodization principles from base building through race-day taper

Train smarter. Race faster. Recover better. Master training load management with Run Analytics—where elite coaching analytics meet complete data privacy.