TSS, CTL, ATL and TSB Explained
You see them everywhere: TSS, CTL, ATL, TSB. But what do these acronyms actually mean? And more importantly: how do you use them to train smarter?
🎯 TSB Calculator
Enter your current CTL and ATL to see your form status
TSB Reference
The Problem with Training by Feel
You just finished a brutal 3-hour ride. You’re wrecked. But how hard was that ride, really? And are you now “fit” or just “fatigued”?
Without objective metrics, you’re training by feel. And feel lies. Sometimes you feel tired when your body has fully recovered. Other times you feel great while you’re actually on the edge of overtraining.
🎯 TSS, CTL, ATL and TSB Solve This
They give you an objective picture of:
- How hard each training session was (TSS)
- Your long-term fitness level (CTL)
- Your short-term fatigue (ATL)
- Whether you’re ready for a peak performance (TSB)
TSS: Training Stress Score
What it is: A number that indicates how hard a specific workout was.
The simple explanation: TSS combines two factors: how long you trained and how hard you trained. One hour at 50% FTP is far less taxing than one hour at 95% FTP.
How TSS is Calculated
The formula:
TSS = (Duration × NP × IF) / (FTP × 3600) × 100
Where:
- NP = Normalized Power (your “effective” average wattage)
- IF = Intensity Factor (NP / FTP)
- FTP = Your Functional Threshold Power
Don’t worry—you don’t need to calculate this yourself. Apps like Polarized.cc, TrainingPeaks, or Intervals.icu do this automatically.
TSS Reference Values
| TSS | How Hard? | Example |
|---|---|---|
| < 50 | Light | Short recovery ride, 45 min zone 1 |
| 50-100 | Moderate | Standard training ride, 1.5 hour endurance |
| 100-150 | Hard | Long ride or intense intervals |
| 150-200 | Very Hard | Long mountain ride, race |
| > 200 | Extreme | Multi-day event, long race |
⚡ TSS Calculator
Estimate your workout’s Training Stress Score
Weekly TSS Guidelines
| Cyclist Type | TSS per Week | Increase Rate |
|---|---|---|
| Beginner | 200-300 | Max +10% per week |
| Recreational | 300-450 | Max +10% per week |
| Serious | 450-600 | Max +10% per week |
| Competitive | 600-900 | Max +5-10% per week |
⚠️ Rule of Thumb
Never increase your weekly TSS by more than 10% per week. Building too fast leads to overtraining.
CTL: Chronic Training Load (Fitness)
What it is: Your fitness level based on the past 6 weeks of training.
The simple explanation: CTL is the 42-day exponentially weighted average of your daily TSS. The higher your CTL, the more training load your body is accustomed to handling.
Why 42 Days?
Your body builds fitness slowly. A single hard week doesn’t suddenly make you fit. CTL captures this by looking at a long period, with recent training weighted more heavily than older sessions.
CTL Reference Values
| CTL | Level | Meaning |
|---|---|---|
| < 30 | Low | Beginning cyclist or long break |
| 30-50 | Base | Recreational cyclist, 3-4 hrs/week |
| 50-70 | Moderate | Regular cyclist, 5-7 hrs/week |
| 70-90 | Well-trained | Serious amateur, 8-12 hrs/week |
| 90-110 | Strong | Competitive amateur |
| > 110 | Elite | Semi-pro or professional level |
💡 Golden Rule: Build CTL by 3-5 Points per Week, Maximum
CTL 60 = average trained cyclist (~400-500 TSS/week). Building faster than 3-5 points/week significantly increases your injury and overtraining risk.
ATL: Acute Training Load (Fatigue)
What it is: Your fatigue level based on the past week of training.
The simple explanation: ATL is the 7-day exponentially weighted average of your daily TSS. It reacts quickly to what you’ve done in recent days.
ATL vs CTL
| Metric | Period | Responds to | Represents |
|---|---|---|---|
| CTL | 42 days | Weeks of training | Fitness |
| ATL | 7 days | Recent days | Fatigue |
How ATL Behaves
- After a hard training day: ATL spikes up
- After a rest day: ATL drops
- After a recovery week: ATL drops significantly
ATL fluctuates significantly throughout the week. That’s exactly as intended—it captures your short-term fatigue state.
TSB: Training Stress Balance (Form)
What it is: The difference between your fitness and your fatigue.
The formula: TSB = CTL - ATL
The simple explanation: TSB tells you whether you’re “fresh” (positive number) or “fatigued” (negative number). It’s the most important metric for timing races and FTP tests.
TSB Interpretation
| TSB | Status | What It Means | Action |
|---|---|---|---|
| > 25 | Very Fresh | Risk of fitness loss | Perfect for FTP test or A race |
| 10 to 25 | Fresh | Well recovered, ready to perform | Ideal for race or hard workout |
| -10 to 10 | Optimal | Balanced loading/recovery | Continue normal training |
| -25 to -10 | Tired | Accumulating fatigue | Schedule extra recovery |
| < -25 | Very Tired | Overtraining risk | Rest immediately |
The Art of TSB Management
During a build phase: TSB can be negative (-5 to -15). You’re deliberately loading.
Before an important race: TSB should be positive (+10 to +25). You achieve this by tapering.
Positive too long: If TSB stays above +20 for weeks, you’re losing fitness. You’re training too little.
Practical Example: Tapering for a Race
| Week | Focus | Average TSB |
|---|---|---|
| 4 weeks out | Normal training | -10 |
| 3 weeks out | Normal training | -8 |
| 2 weeks out | Volume -20% | -2 |
| 1 week out | Volume -40% | +8 |
| Race day | Rest/activation | +15 |
The Performance Management Chart (PMC)
All these metrics come together in the Performance Management Chart. This is a graph with three lines:
- Blue line (CTL): Your fitness, rises slowly
- Pink line (ATL): Your fatigue, fluctuates daily
- Yellow line/area (TSB): Your form, difference between the two
Reading the PMC
Build phase: Pink line (ATL) above blue line (CTL) = negative TSB = you’re loading your body.
Recovery week: Pink line drops below blue line = positive TSB = you’re recovering.
Race week: Pink line far below blue line = high positive TSB = you’re fresh and ready.
Common Mistakes
Mistake 1: Wanting TSB to Always Be Positive
“I don’t want to be tired” is a common thought. But training doesn’t work that way. You need to deliberately build fatigue (negative TSB) to get stronger.
Solution: Accept TSB of -5 to -15 during build weeks. Schedule a recovery week with positive TSB every 3-4 weeks.
Mistake 2: Building CTL Too Fast
Piling on 400 TSS extra every week to rapidly increase CTL leads to injuries and overtraining.
Solution: Maximum 3-5 CTL points per week. That’s roughly +10% weekly TSS, maximum.
Mistake 3: Only Looking at TSS
A high TSS week feels productive, but says nothing about the quality of your training.
Solution: Combine TSS with the 80/20 distribution. 400 TSS with good polarization (80% easy, 20% hard) is better than 500 TSS in the grey zone.
Mistake 4: Tapering Too Short or Too Long
Too short: you’re still fatigued on race day. Too long: you lose fitness.
Solution: 7-14 day taper for important races. Reduce volume, maintain intensity.
How Polarized Training Affects TSS/CTL/ATL/TSB
With polarized training, you see a specific pattern:
- Easy days (80%): Low TSS (30-60), keeps ATL low
- Hard days (20%): High TSS (80-120), brief ATL spike
- Recovery weeks: Very low TSS, TSB becomes positive
This Results In:
- Stable CTL growth (fitness increases)
- Controlled ATL spikes (fatigue recovers quickly)
- TSB that oscillates between -15 and +15 (optimal training zone)
Compare this to “grey zone” training where you do TSS 60-80 every day: your ATL stays constantly elevated, recovery is incomplete, and CTL grows slower.
Quick Reference: TSS, CTL, ATL, TSB
| Metric | Full Name | Measures | Period | Target |
|---|---|---|---|---|
| TSS | Training Stress Score | Load per workout | 1 session | 50-150 per workout |
| CTL | Chronic Training Load | Fitness | 42 days | Build slowly |
| ATL | Acute Training Load | Fatigue | 7 days | Let it fluctuate |
| TSB | Training Stress Balance | Form | CTL – ATL | -15 to +15 normal |
Frequently Asked Questions
It depends on your goals and the day. Easy rides: 30-60 TSS. Hard interval sessions: 70-100 TSS. Long endurance rides: 100-150 TSS.
Don’t focus on TSS targets per workout, but on weekly TSS and proper distribution (80/20).
Safely: 3-5 points per week. That means roughly 10% more weekly TSS. Building faster significantly increases your injury and overtraining risk.
Not necessarily. TSB of -20 is acceptable during a build block. Watch for signals from your body: sleep problems, persistent fatigue, declining performance.
If those occur, take extra rest. Otherwise, continue to your planned recovery week.
For an A race (most important of the season): TSB +10 to +25.
For a B race (important but not crucial): TSB +5 to +15.
For a training race: TSB 0 to +10 is fine.
Yes, with heart rate-based TSS (hrTSS). It’s less accurate but usable. Most apps calculate this automatically if you don’t have a power meter but do have a heart rate monitor.
IF (Intensity Factor) only measures how hard you rode, not how long. TSS combines duration and intensity.
An IF of 0.85 for 30 minutes gives low TSS; the same IF for 3 hours gives high TSS.
Every 3-4 weeks. During a recovery week, reduce volume by 40-50% and let TSB become positive (+5 to +15). This gives your body time to adapt to the training load.
For most amateurs, CTL above 100-110 is difficult to sustain alongside work and personal life. It’s not about achieving the highest CTL, but about the right CTL for your available training time and recovery capacity.
Start Tracking Your Fitness
Polarized.cc automatically calculates your TSS, CTL, ATL and TSB based on your Strava activities. See instantly whether you’re fresh enough for that FTP test or should take another rest day.
View Your Performance Chart →


