Training Management

CTL, ATL, TSB Explained — Fitness, Fatigue and Form

April 10, 2026 Updated: June 4, 2026 11 min read Run · Bike · Triathlon

If you use a training app like TrainingPeaks, Strava or Yama, you've certainly run into these three acronyms: CTL, ATL and TSB. They sit at the heart of nearly every serious training system — and yet hardly anyone really understands what they mean.

The good news: the concept behind them is surprisingly simple. It comes down to three questions every athlete knows: How fit am I? How tired am I? And am I in form right now? In this article I'll explain all three metrics from the ground up — no sports science degree required, but with the real math behind them.

In short

CTL = your fitness (long-term, accumulated capacity). ATL = your fatigue (short-term tiredness from the last few days). TSB = your form (CTL minus ATL — fresh or tired?).

The foundation: what is TSS?

Before we get to the three metrics, we need a unit for training load. That unit is called TSS (Training Stress Score). It captures how demanding a single session was — from duration and intensity.

The idea: one hour at your threshold (FTP on the bike, threshold pace running) is defined as 100 TSS. An easy one-hour run might give 50 TSS. A hard two-hour interval session can produce 150 TSS or more.

TSS = (duration in sec × NP × IF) / (FTP × 3600) × 100

Don't worry, you don't need to compute this by hand — every training app does it automatically. What matters is the principle: TSS is the currency of training load. Everything else builds on it. If you want to go deeper into how intensity is measured, our article on the FTP test helps.

CTL — your fitness

CTL stands for Chronic Training Load. In plain terms it simply means: your fitness.

CTL is a rolling average of your daily TSS over the last 42 days (6 weeks). The reasoning: fitness builds slowly and fades slowly. A single hard week doesn't make you permanently fit — but six weeks of consistent training do.

CTLtoday = CTLyesterday + (TSStoday − CTLyesterday) / 42

This is an exponentially weighted moving average. In practice the number 42 means: training from six weeks ago still counts, but far less than what you did yesterday. The higher your CTL, the more training load you can handle.

Rule of thumb

A well-trained recreational endurance athlete often has a CTL between 50 and 90. Pros reach over 150. More important than the absolute value, though, is the trend: if your CTL rises over weeks, you're getting fitter.

ATL — your fatigue

ATL stands for Acute Training Load — that is, your fatigue. It works exactly like CTL, just over a much shorter window: 7 days.

ATLtoday = ATLyesterday + (TSStoday − ATLyesterday) / 7

Because the window is so short, ATL reacts quickly. A hard training week drives your ATL up immediately. Two rest days bring it back down. So ATL reflects how much fatigue is currently sitting in your legs.

On its own, ATL says little. It only becomes meaningful in combination with CTL — and that's exactly what TSB is.

TSB — your form

TSB stands for Training Stress Balance and is the most important of the three numbers for race planning. It's defined as simply as can be:

TSBtoday = CTLyesterday − ATLyesterday
Fitness minus fatigue = form

TSB answers the question: Am I fresh or tired? If your fatigue (ATL) is higher than your fitness (CTL), your TSB is negative — you're tired. If the fatigue has cleared while the fitness remains, TSB turns positive — you're fresh and in form.

What the TSB numbers mean

TSB rangeStateMeaning
+25 and aboveVery freshFitness may be decaying — rested too long
+5 to +25Race formIdeal for racing — fresh and fit
−10 to +5NeutralNormal training day-to-day
−30 to −10Productively tiredTraining block — fitness being built
−30 and belowOverreachedElevated injury and overtraining risk
The key trick

Good form doesn't come from rest alone — otherwise every couch potato would be in peak shape. It comes from high fitness (CTL) plus cleared fatigue (ATL). You build fitness over weeks, then reduce load just before the race so the fatigue disappears. That's called tapering.

Performance Management Chart across 11 weeks of marathon preparation. CTL (green line) rises from 45 to about 57 TSS per day across Build and Peak phases, ATL (red, more variable) follows with bigger swings. TSB (orange filled area) shifts between negative values during build and clearly positive values during taper and recovery weeks. Race-Day TSB is around plus 13, with a pre-race peak near plus 20.
Example trajectory of CTL, ATL and TSB across 11 weeks of marathon prep. Build, recovery, peak block and taper combine to produce a positive form on race day.

A real-world example over 12 weeks

Let's say you're preparing for a half marathon. Here's how the three values might develop over a typical training cycle:

PhaseCTLATLTSBFeeling
Week 1 (start)45450Neutral
Week 4 (build)5870−12Tired, productive
Week 8 (peak block)7288−16Really cooked
Week 11 (taper)7055+15Coming fresh
Week 12 (race day)6848+20Peak form

Note race week: CTL has only dropped slightly (from 72 to 68 — you've barely lost fitness), but ATL has fallen sharply (from 88 to 48 — the fatigue is gone). Exactly this combination produces the positive TSB of +20 and therefore race form.

The most common misconceptions

"High TSB is always good"

Wrong. A permanently high TSB means you're training too little — your fitness (CTL) is falling. TSB should only be high around races. In normal training a slightly negative value is completely right and even desirable.

"I need to keep raising my CTL"

Also risky. Too rapid a CTL increase (more than about 5–7 points per week) is considered a warning sign of overload. Pushing CTL up too fast earns you an injury sooner than a fitness gain — the body needs time to adapt to higher load.

"The numbers are directly comparable"

No. A CTL of 70 means something different for a runner than for a cyclist, because TSS accumulates differently per sport. Always compare your values only with yourself over time, never with other athletes.

Important: data quality

CTL, ATL and TSB are only as good as your TSS — and TSS is only as good as your threshold values (FTP, threshold pace, threshold heart rate). If your FTP is outdated, all three metrics are skewed. Keep your thresholds current: you can calculate your FTP here, and how to determine the lactate threshold without a lab is covered in our article on the lactate threshold.

Why these metrics aren't everything

CTL/ATL/TSB are powerful, but they have one weakness: they're distance-agnostic. A positive TSB tells you you're fresh — but not whether you have the specific endurance for your target distance. For a marathon, what counts isn't just freshness but also whether you have enough long runs in your legs.

That's exactly the gap Race Shape fills — a metric that additionally accounts for volume and distance specificity. How that works is explained in our article on Race Shape.

Yama shows all three live

Connect Strava with Yama — CTL, ATL and TSB are computed automatically from your activities and displayed as a performance management chart. See at a glance when you're coming into form and when you need rest.

Try Yama

Conclusion

Three acronyms, one simple principle: CTL is your fitness (slow, 42 days), ATL is your fatigue (fast, 7 days), and TSB is the difference — your form.

Anyone who understands these three can steer their training deliberately: ramp up fitness during build, shed fatigue before the race, and spot overload in time. The concept is simple — the discipline to stick to the plan even in the tired phase of a training block is the harder part.

One last bit of perspective: CTL, ATL and TSB are a model, not a law of nature. They reflect how much you've trained — not how well you've slept, eaten or recovered. Take the numbers seriously, but not as the whole truth.

Frequently asked
What does a negative TSB value mean?
A negative TSB means your short-term fatigue (ATL) is higher than your long-term fitness (CTL). You are more tired than usual. This is completely normal — and even necessary — during productive training phases. Values between −10 and −30 are typical for build phases. Only at around −30 does the load become critical, and at −45 overtraining risk increases significantly. Before a race, TSB should be positive again.
What TSB value is ideal before a race?
For key races, a TSB between +5 and +15 is considered ideal: you are rested enough but not so detrained that fitness suffers. Above +25, fitness drops faster than form improves. These values are typically reached through a taper over 1 to 3 weeks, where training volume is reduced while some intensity is kept to preserve power.
How fast can I increase my CTL per week?
A weekly CTL increase of 3 to 7 points is sustainably healthy for most athletes. Above 8 points per week, injury and overtraining risk rises noticeably. Experienced athletes with years of training history can tolerate more short-term, while beginners should stay closer to 3 to 4 points. Important: build phases should alternate with recovery weeks — e.g. 3 weeks build, 1 week recovery.
Why does CTL use 42 days and ATL use 7 days?
The time constants are empirically calibrated. 42 days (6 weeks) roughly matches the timeframe in which physiological adaptations — like mitochondrial density and capillary network — manifest. 7 days reflects the short-term fatigue that builds up and dissipates within a week. These values come from Andrew Coggan's Performance Management Chart and are now standard in TrainingPeaks and similar platforms.
Can CTL values be compared between athletes?
Not directly. CTL is based on TSS, and TSS depends on the individual threshold (FTP or threshold pace). If someone sets their FTP too low, all TSS values — and therefore CTL — will be artificially inflated. It makes more sense to compare your own CTL over time, or the ratio between CTL and race performance. Absolute numbers are only meaningful within a consistently maintained training history.