TrainingPeaks Complete Guide: TSS, CTL, ATL Explained

TrainingPeaks is the training analytics platform used by virtually every professional endurance coach, Olympic athletes, and serious age-groupers across cycling, running, triathlon, and swimming. The platform's Performance Management Chart (PMC)—displaying Chronic Training Load (CTL), Acute Training Load (ATL), and Training Stress Balance (TSB)—is the gold standard for quantifying fitness, fatigue, and form. Professional coaching plans from CTS, TrainerRoad, and Sufferfest all revolve around TrainingPeaks metrics.

But for athletes new to structured training, the TrainingPeaks interface is bewildering. What is TSS, and how does it differ from Training Load on my Garmin watch? Why does CTL increase slowly while ATL spikes wildly? What TSB range indicates I'm ready to race versus overtrained? And most importantly: how do I use this data to avoid injury, build fitness systematically, and peak for my goal race?

This is the complete beginner's guide to TrainingPeaks metrics—explaining the underlying mathematics, practical interpretation, and actionable training decisions based on TSS, CTL, ATL, and TSB. By the end, you'll understand how to read your Performance Management Chart like a professional coach and optimize your training load for sustainable fitness gains without overtraining.

The Foundation: Training Stress Score (TSS)

What TSS Measures

Training Stress Score (TSS) quantifies the physiological stress of a single workout by combining intensity and duration into one number. A harder, longer workout = higher TSS.

The Formula (Simplified):

TSS = (Duration in hours) × (Intensity Factor²) × 100

• Duration: How long you trained
• Intensity Factor (IF): How hard you trained relative to your threshold (FTP for cycling, threshold pace for running)

Example Calculation:

• 2-hour ride at 85% of FTP (Intensity Factor = 0.85)
• TSS = 2 × (0.85²) × 100 = 2 × 0.7225 × 100 = 144.5 TSS

TSS Benchmarks by Workout Type

Workout Type	Typical TSS	Description
Easy 1-hour Zone 2 run	40-50 TSS	Recovery/base building
Moderate 1-hour tempo run	65-75 TSS	Threshold development
Hard 1-hour interval session	85-100 TSS	VO2 max intervals, HIIT
3-hour Zone 2 long ride	150-180 TSS	Endurance base
2-hour threshold ride	120-140 TSS	Hard sustained effort
Marathon race (3.5 hours)	250-350 TSS	Maximum sustainable effort

Key Principle: TSS is sport-neutral and duration-independent. A 100 TSS workout produces the same physiological stress whether it's a 2-hour easy ride or a 1-hour hard run—both require ~1-2 days recovery.

How Devices Calculate TSS

Cycling (Power-Based TSS):

• Requires power meter (measures watts output)
• Requires FTP (Functional Threshold Power) set in device
• TSS calculated from actual power data (most accurate method)

Running (Heart Rate-Based TSS / rTSS):

• Requires threshold heart rate or threshold pace set in device
• Garmin/Polar estimate TSS from HR zones and duration
• Less precise than power-based but sufficiently accurate for training load management

Swimming (sTSS):

• Typically manual entry based on perceived exertion and duration
• Most coaches use 1 TSS per minute of threshold-intensity swimming as rough guide

Chronic Training Load (CTL): Your Fitness Baseline

What CTL Measures

Chronic Training Load (CTL) is the exponentially weighted 42-day rolling average of your daily TSS. It represents your aerobic fitness baseline—how much training stress your body has adapted to handle.

The Math:

• CTL today = (Yesterday's CTL × 41/42) + (Today's TSS × 1/42)
• This exponential weighting means recent training affects CTL more than distant training
• CTL changes slowly—it takes weeks of consistent training to move meaningfully

CTL Benchmarks by Athlete Level

CTL Range	Fitness Level	Typical Athlete
0-30	Beginner/Detrained	New to structured training, returning from injury
30-60	Recreational Athlete	Training 4-6 hours/week, local races
60-90	Competitive Age-Grouper	Training 8-12 hours/week, podium finisher
90-120	Advanced/Elite Amateur	Training 12-16 hours/week, national-level
120+	Professional/Olympic	Training 20+ hours/week, full-time athlete

Critical Insight: CTL is the single most important number in your training life. Every decision about volume, intensity, and recovery should be made with the goal of systematically building CTL without exceeding your body's adaptation capacity.

How Fast Should CTL Increase?

Conservative guideline: +3-5 CTL points per week during base building phases.

• Too slow (<3 CTL/week): Undertraining, fitness gains plateaued
• Optimal (3-5 CTL/week): Sustainable fitness building, low injury risk
• Aggressive (5-8 CTL/week): Rapid gains but higher injury/overtraining risk, only sustainable 4-6 weeks
• Too fast (>8 CTL/week): Overreaching, injury likely, unsustainable

Example: Building from CTL 50 → 80 over 12 weeks = +2.5 CTL/week (conservative, safe). Building from 50 → 80 over 6 weeks = +5 CTL/week (aggressive, requires careful fatigue monitoring).

Acute Training Load (ATL): Your Current Fatigue

What ATL Measures

Acute Training Load (ATL) is the exponentially weighted 7-day rolling average of your daily TSS. It represents how tired you are right now—recent training stress that hasn't yet been absorbed into CTL.

The Math:

• ATL today = (Yesterday's ATL × 6/7) + (Today's TSS × 1/7)
• 7-day window means ATL responds quickly to training changes
• A hard week spikes ATL immediately; a rest week drops ATL within 3-4 days

ATL vs CTL: The Relationship

Under normal training conditions:

• ATL ≈ CTL: Training at steady-state maintenance (not building fitness, not tapering)
• ATL > CTL: Overload phase (building fitness, accumulating fatigue)
• ATL < CTL: Recovery week or taper (absorbing previous training, reducing fatigue)

Training Stress Balance (TSB): Your Form/Freshness

What TSB Measures

Training Stress Balance (TSB) is the difference between CTL and ATL:

TSB = CTL - ATL

• Positive TSB: Fresh, rested, ready to perform (but fitness may be declining if positive too long)
• Negative TSB: Fatigued, building fitness (productive training stress)
• Zero TSB: Balanced state (neither building nor resting)

TSB Ranges and Training Implications

TSB Range	Status	Action
+20 to +30	Over-rested	Fitness declining, resume training
+5 to +20	Race Ready (Form Window)	Peak performance, race this weekend
-5 to +5	Neutral/Transition	Maintenance or start taper
-10 to -30	Productive Training (Sweet Spot)	Building fitness, sustainable
-30 to -50	Heavy Overload	Max 2-3 weeks, then recovery week
Below -50	Overtraining Risk	Mandatory rest, injury imminent

The Sweet Spot: Most productive training occurs at TSB between -10 and -30. You're accumulating enough fatigue to drive adaptation (fitness building) without exceeding recovery capacity (overtraining).

How to Use the Performance Management Chart (PMC)

Building a Base: 8-12 Week Block

Goal: Increase CTL from 50 → 75 (+25 points over 10 weeks = +2.5/week)

Weekly Structure:

• Weeks 1-3: Build weekly TSS from 350 → 450 (TSB drops from -5 → -20)
• Week 4: Recovery week, drop TSS to 250 (TSB rises to -5)
• Weeks 5-7: Build weekly TSS from 400 → 500 (TSB drops to -25)
• Week 8: Recovery week, TSS = 280 (TSB rises to -8)
• Weeks 9-10: Final build, TSS = 525 (TSB = -22)

Result: CTL increases steadily from 50 → 75. TSB oscillates between -5 (recovery weeks) and -25 (build weeks), preventing overtraining while accumulating fitness.

Tapering for a Race: 2-3 Week Protocol

Goal: Reduce fatigue (ATL) while preserving fitness (CTL) to achieve positive TSB on race day.

Example Taper (CTL = 80, 3 weeks out from race):

• Week -3: Maintain training volume, TSS = 550 (TSB = -25, still building)
• Week -2: Reduce volume 30%, TSS = 380 (TSB rises to -10)
• Week -1: Reduce volume 50%, TSS = 270 (TSB rises to +8)
• Race Day: TSB = +10 to +15 (form window, optimal performance)

Critical Taper Principles:

• Reduce volume (duration), not intensity (maintain some high-intensity work to preserve sharpness)
• CTL will decline slightly during taper (~3-5 points over 3 weeks)—this is acceptable and unavoidable
• TSB should reach +5 to +20 by race morning (too high = over-rested, too low = still fatigued)

Recovery Weeks: When and How Often

Rule of Thumb: Every 3-4 weeks of progressive overload, insert 1 recovery week.

Recovery Week Structure:

• Reduce weekly TSS by 30-50% (if normal week = 500 TSS, recovery = 250-350 TSS)
• Maintain some intensity (don't eliminate hard sessions completely, but reduce volume)
• TSB will rise toward neutral or slightly positive (-5 to +5)
• Use recovery week to absorb accumulated fatigue and consolidate fitness gains

Signs You Need an Unscheduled Recovery Week:

• TSB below -40 for 10+ consecutive days
• Elevated resting heart rate (+5-8 bpm above baseline)
• Decreased HRV (>10% below baseline for 3+ days)
• Persistent fatigue, irritability, sleep disruption
• Performance regression (can't hit target power/pace despite adequate effort)

Integrating Garmin, Polar, and COROS Data

Automatic TSS Calculation

Garmin (Fenix 8, Epix 2, Forerunner 965):

• Calculates Training Load (Garmin's proprietary metric similar to TSS)
• Syncs workouts to TrainingPeaks automatically via Garmin Connect → TrainingPeaks integration
• TSS calculated from heart rate zones (requires threshold HR set correctly)
• For cycling: pair power meter for power-based TSS (most accurate)

Polar (Vantage V3, Grit X2 Pro):

• Calculates Training Load Pro (similar to TSS)
• Syncs to TrainingPeaks via Polar Flow → TrainingPeaks integration
• Requires Sport Profiles configured with correct HR zones

COROS (Pace 3, Apex 2 Pro, Vertix 2):

• Calculates Training Load based on heart rate and pace
• TrainingPeaks sync available via COROS app
• Less refined algorithm than Garmin/Polar but sufficient for TSS estimation

Setting Up Threshold Values for Accurate TSS

TSS accuracy depends entirely on correct threshold settings:

For Running:

• Threshold Heart Rate: HR you can sustain for ~60 minutes all-out (typically 88-92% max HR)
• Threshold Pace: Pace you can sustain for ~60 minutes (roughly 10K race pace for trained runners)
• Testing Protocol: 30-minute time trial after 10-minute warm-up, average HR of final 20 minutes = threshold

For Cycling (with Power Meter):

• FTP (Functional Threshold Power): Maximum power you can sustain for ~60 minutes
• Testing Protocol: 20-minute time trial after warm-up, multiply average power by 0.95 = FTP estimate
• Update Frequency: Retest FTP every 6-8 weeks as fitness improves

Common Mistakes and How to Avoid Them

Mistake #1: Chasing CTL Too Aggressively

Error: Increasing weekly TSS by 100+ points per week to rapidly build CTL (e.g., 400 → 500 → 600 TSS weekly progression).

Consequence: TSB plummets below -50, injury or illness results, forced time off destroys accumulated CTL.

Fix: Limit CTL increases to +3-5 per week. Insert recovery weeks every 3-4 weeks. Slow and steady wins.

Mistake #2: Never Taking Recovery Weeks

Error: Training at TSB -20 to -35 continuously for 8-12 weeks without recovery, believing "I feel fine."

Consequence: Chronic fatigue accumulates silently. Performance plateaus. Illness or injury eventually forces rest.

Fix: Schedule recovery weeks proactively, not reactively. Every 3-4 weeks, drop volume 30-50% regardless of how you feel.

Mistake #3: Tapering Too Much or Too Little

Error (Too Much): 3-week taper reducing TSS by 70%, arriving at race with TSB = +35 (over-rested, fitness lost).

Error (Too Little): 1-week taper reducing TSS by 20%, arriving at race with TSB = -15 (still fatigued).

Fix: Target TSB +5 to +20 on race morning. For most athletes, this requires 2-3 week taper with 30-50% volume reduction.

Mistake #4: Ignoring TSB Warnings

Error: Pushing through planned hard sessions despite TSB = -48 and elevated resting HR.

Consequence: Injury, illness, or chronic overtraining requiring 4-8 weeks complete rest (destroying months of CTL building).

Fix: If TSB drops below -40, take an unscheduled recovery week immediately. Your training plan is not gospel—your body's fatigue signals override the plan.

Advanced Concepts: Ramp Rate and CTL Planning

The Ramp Rate Metric

Ramp Rate = CTL change over past week (yesterday's CTL - CTL 7 days ago).

• Safe Ramp Rate: +3 to +8 CTL/week
• Red Flag Ramp Rate: >10 CTL/week (injury risk spikes)
• Detraining Ramp Rate: -5 or lower (fitness declining rapidly)

TrainingPeaks Premium displays Ramp Rate as a color-coded warning system. Green = safe progression, Yellow = aggressive but manageable, Red = overreaching.

Planning Annual CTL Periodization

Example: Marathon Runner (Current CTL = 40, Goal Marathon in 16 weeks)

• Weeks 1-4 (Base 1): CTL 40 → 55 (+3.75/week), TSB oscillates -10 to -25
• Week 5: Recovery, CTL maintains ~55, TSB rises to -5
• Weeks 6-9 (Base 2): CTL 55 → 70 (+3.75/week), TSB = -15 to -30
• Week 10: Recovery, CTL maintains ~70, TSB rises to -8
• Weeks 11-13 (Build): CTL 70 → 80 (+3.3/week), TSB = -20 to -30
• Week 14: Pre-taper recovery, TSB rises to -10
• Weeks 15-16: Taper, CTL 80 → 76, TSB rises to +10 (race-ready)

Result: Systematic fitness building from CTL 40 → 80 without exceeding safe ramp rates or accumulating chronic fatigue.

The Verdict: CTL Is Your North Star

After coaching hundreds of athletes and analyzing thousands of Performance Management Charts, the pattern is clear: CTL is the most predictive metric of race performance. An athlete with CTL 90 will outperform an athlete with CTL 60 in endurance events, all else equal. TSB determines day-to-day freshness, but CTL determines your ceiling.

The TrainingPeaks PMC transforms training from guesswork ("Am I training enough? Too much?") into quantified load management. By monitoring TSS, CTL, ATL, and TSB, you can:

• Build fitness systematically (+3-5 CTL/week) without overtraining
• Time recovery weeks proactively (every 3-4 weeks, when TSB drops below -35)
• Taper intelligently for peak races (achieve TSB +10 to +15 on race morning)
• Avoid injury by respecting ramp rate limits (<8 CTL/week increase)

For beginners, the metrics seem abstract. But after 12 weeks of tracking, the patterns become intuitive. You learn your personal TSB sweet spot (-15 to -25 for productive training), your sustainable weekly TSS (maybe 450-550), and your ideal taper duration (2-3 weeks to reach positive TSB).

TrainingPeaks doesn't make you faster by itself—it provides the dashboard to drive intelligently. Used correctly, it's the difference between random training and systematic progression. Every professional coach uses PMC analysis for a reason: it works.

Start tracking today. Set your threshold values correctly. Build CTL gradually. Respect TSB warnings. The math doesn't lie.

Related Reading: Sync your training data with our device guides: Garmin Fenix 8 + TrainingPeaks for automatic TSS calculation, and Polar Vantage V3 + TrainingPeaks for seamless PMC integration.