You finish a ride, upload it to Strava, and see a handful of numbers. Maybe you glance at average power, notice the kilojoules, nod at the duration, and close the app. But how do you know if that ride actually made you fitter? Or whether you're just accumulating fatigue and digging yourself into a hole? Three numbers answer that question — CTL, ATL, and TSB. They sit at the heart of the Performance Management Chart, and once you understand what they mean, you'll never look at your training the same way.
These aren't abstract academic concepts. They're the same metrics professional cycling teams use to peak their riders for Grand Tours, the same framework time-crunched amateurs use to get the most out of limited training hours, and the same numbers that tell you whether you're genuinely ready to race or just hoping for the best. Let's break them down.
The Performance Management Chart
The Performance Management Chart — PMC for short — is the single most useful visual tool in cycling training. Developed by Dr Andrew Coggan as part of his pioneering work on power-based training, it plots three lines over time: your fitness, your fatigue, and the balance between them. The idea is deceptively simple. Training makes you fitter, but it also makes you tired. Performance is what happens when fitness exceeds fatigue. The PMC turns that concept into something you can track, measure, and act on.
If you've ever looked at a PMC and felt overwhelmed, that's understandable — three overlapping lines with acronyms don't exactly scream clarity. But each line tells a straightforward story, and once you understand all three, the chart reads like a training diary that never lies. It's not about the chart being complicated. It's about understanding the three ingredients that make it up.
CTL: Chronic Training Load — your fitness
CTL stands for Chronic Training Load, and it represents your fitness. Specifically, it's an exponentially weighted rolling average of your daily Training Stress Score (TSS) over the past 42 days. That sounds technical, but the concept is intuitive: it's a measure of how much training load your body has absorbed over roughly the past six weeks. The "exponentially weighted" part means recent days count more than older ones, so your CTL is always tilting toward what you've been doing lately, while still reflecting your longer-term consistency.
Think of CTL as your fitness bank account. Every ride you do is a deposit. The bigger and harder the ride, the larger the deposit. Miss a few days, and the balance starts to drift down. Take two weeks off the bike, and you'll see it drop noticeably. But here's the encouraging part — CTL is slow to build and slow to lose. A single bad week won't destroy months of consistent training, just as a single epic ride won't transform your fitness overnight. It rewards patience and consistency above everything else.
To put some real numbers on it: a recreational rider who trains three or four times a week might sit at a CTL of 40 to 60. A serious amateur who's training with structure — five or six rides a week with purposeful intensity — might be in the 80 to 100 range. Professional cyclists often carry a CTL of 120 or higher during the competitive season. These are rough benchmarks, not targets. Your CTL is personal to you, and comparing it to someone else's is about as useful as comparing your resting heart rate to theirs. What matters is your own trajectory — is it going up, holding steady, or declining?
The practical takeaway is that CTL tells you what you're capable of. A higher CTL means your body can handle more training stress and produce higher sustained efforts. But capability and readiness aren't the same thing. That's where the next number comes in.
ATL: Acute Training Load — your fatigue
ATL stands for Acute Training Load, and it captures your fatigue — how tired you are right now from recent training. It works the same way as CTL mathematically, but over a much shorter window: a 7-day exponentially weighted average of your daily TSS. Because it looks at just the past week, ATL responds quickly. A brutal weekend of back-to-back long rides will spike your ATL. Three easy days will bring it back down. It's volatile by design, because fatigue is volatile.
ATL is the number that tells you the cost of your recent training. High ATL isn't inherently bad — it's expected during a hard training block. The problem comes when ATL stays elevated for weeks without relief. That's the kind of sustained fatigue that leads to staleness, illness, and the dreaded overtraining syndrome. Your body adapts to training during rest, not during the training itself. If you never bring ATL down, you never give your body the chance to absorb the work you've done.
The relationship between CTL and ATL is where the real insight lives. When ATL is higher than CTL, you're accumulating fatigue faster than you're building fitness — which is exactly what should happen during a focused training block. When ATL drops below CTL, you're fresher than your fitness level would suggest — which is the setup for peak performance. That relationship has its own name: TSB.
TSB: Training Stress Balance — your form
TSB is the simplest calculation of the three, and arguably the most powerful. It's just CTL minus ATL. That's it. Your fitness level minus your current fatigue equals your form — your readiness to perform.
When TSB is positive, your fitness exceeds your fatigue. You're fresh. You've absorbed recent training and your body is ready to deliver. When TSB is negative, fatigue exceeds fitness — you're in the hole, carrying more tiredness than your current fitness can comfortably support. Neither state is inherently good or bad. What matters is when you're in each state and how deep you go.
The sweet spot for race day is a TSB somewhere between +5 and +25. That means you've rested enough to shed fatigue, but not so much that your fitness has started to erode. Elite cyclists and their coaches spend weeks orchestrating the taper — the deliberate reduction in training volume — to land TSB in exactly this range on the day that matters. It's not guesswork. It's arithmetic, informed by experience.
During a hard training block, you might see TSB drop to -10, -20, or even -30. That's fine, and it's necessary — you can't build fitness without going into fatigue debt. The critical thing is that you come back out of it. A planned recovery week brings ATL down, TSB climbs back toward zero or positive, and your body supercompensates. You emerge fitter than when you started the block. That cycle of stress and recovery is the engine of all endurance training. TSB is simply the gauge that tells you where you are in the cycle.
TSS: the building block
CTL, ATL, and TSB are all derived from a single daily number: your Training Stress Score, or TSS. Understanding TSS helps the whole system make sense. TSS quantifies how much stress a ride placed on your body, accounting for both intensity and duration, normalised against your Functional Threshold Power (FTP). If you're not familiar with FTP and power zones, think of FTP as the hardest effort you can sustain for about an hour — it's your personal yardstick for intensity.
The key reference point is this: riding for exactly one hour at exactly your FTP produces a TSS of 100. From there, everything scales. An easy two-hour endurance spin at 65% of FTP might generate 80 to 100 TSS. A hard three-hour group ride with surges and climbs could land at 200 to 250 TSS. A short 45-minute recovery spin might be just 25 to 35 TSS. The beauty of TSS is that it lets you compare wildly different rides on a single scale. A two-hour tempo session and a four-hour easy ride might produce similar TSS, and from your body's perspective, they impose a roughly similar total training load.
Every day, your TSS feeds into the CTL and ATL calculations. Days you don't ride count as zero TSS, which gradually pulls both averages down. This is why consistency matters so much — a week of zeroes drags your CTL down in a way that one big ride can't easily recover.
Practical examples
Numbers become meaningful when you see them in context. Here are three scenarios that illustrate how CTL, ATL, and TSB interact in real training.
Building for a target event. Imagine you're twelve weeks out from a sportive. Your CTL is at 55 — a solid base, but you want to be at 75 or higher on race day. You increase your weekly training load progressively: four rides a week, including one longer endurance ride and one interval session. Over the build phase, your CTL climbs steadily — perhaps 1.5 to 2 points per week. Your ATL runs higher than your CTL, so TSB is negative, typically sitting around -10 to -15. You feel tired, but you're getting fitter. Two weeks before the event, you start tapering. You cut volume by 40 to 50 percent, keeping some intensity to maintain sharpness. ATL drops fast. TSB swings from -12 to +10 over those two weeks. Your CTL barely moves because it's so slow to respond. On race day, your CTL is 73, your ATL is 60, and your TSB is +13. You're fit, fresh, and ready.
The overtraining warning. Another rider has been hammering every session for six weeks straight, chasing a higher CTL. They're riding hard six days a week, never taking a true rest day. Initially, CTL climbs nicely. But after week four, something stalls. CTL plateaus around 90 even though training hasn't changed. ATL is persistently high — 110, 115, 120. TSB is stuck at -25 or worse. Performances are getting worse, not better. Sleep is poor. Motivation is gone. The PMC is waving a red flag: fatigue is so high that the body can't absorb any more training. The fix isn't more training — it's a genuine recovery block. Five to seven days of dramatically reduced load, letting ATL crash and TSB return to positive territory.
Coming back from a break. You took three weeks off the bike — holiday, illness, life. Your CTL dropped from 65 to about 40. It feels like starting over, but it isn't. The research on detraining suggests that fitness comes back faster than it was originally built, thanks to retained physiological adaptations. Rebuilding sustainably means adding roughly 1 to 2 CTL points per week. Trying to rush it — jumping back to the training load you were doing before the break — is the fastest way to get injured or burnt out. Patience here literally pays off in fewer setbacks.
Common mistakes
The PMC is a powerful tool, but it comes with traps that catch even experienced riders.
-
Chasing CTL as a vanity metric. A higher number feels like proof you're training hard, and it's tempting to treat CTL like a leaderboard score. But CTL only reflects training load — not training quality. A CTL of 90 built on purposeful, structured training is worth far more than a CTL of 90 built on junk miles. And there's a ceiling that's personal to you. Pushing CTL beyond what your body, schedule, and recovery habits can support leads to illness and burnout, not speed.
-
Ignoring TSB for weeks at a time. If your TSB has been below -15 for three weeks straight, you're not in a training block — you're in a fatigue spiral. Hard training only works when paired with recovery. The adaptation happens during rest, not during the intervals.
-
Not tapering before events. You've done the work. You've built the fitness. And then you keep training hard right up to race day because you're afraid of losing fitness. CTL barely moves in two weeks. But TSB absolutely does. Skipping the taper means showing up with a high CTL and an equally high ATL — fit but exhausted. The taper is where you cash in on the training you've done.
-
Comparing your CTL to other riders. Your CTL reflects your FTP, your training volume, your recovery capacity, and your life circumstances. Someone with a higher CTL isn't necessarily fitter than you in any meaningful sense — they might have a lower FTP and ride longer hours, or they might be a full-time athlete. Track your own trend. That's the only comparison that matters.
How an AI coach tracks this for you
All of this — CTL, ATL, TSB, TSS, trend analysis, taper timing — is exactly the kind of work that an AI cycling coach excels at. These calculations aren't difficult, but doing them consistently and interpreting them in context is where most self-coached riders fall down. You can calculate your own CTL in a spreadsheet, but will you update it after every ride? Will you notice when your TSB has been negative for 18 days straight? Will you adjust your plan when the numbers suggest you need recovery instead of more intensity?
An AI cycling coach does this automatically. Every ride that syncs from Strava feeds into your PMC. Your CTL, ATL, and TSB are recalculated in real time. You can ask your coach "What's my form like right now?" and get an answer that considers your full training history, not just yesterday's ride. You can ask "Am I ready for my race on Saturday?" and get guidance grounded in actual numbers rather than feelings. When your TSB has been dangerously negative for too long, your coach flags it — before you notice the symptoms yourself.
The real power isn't in the calculations. It's in having something that connects the dots between your power zones, your training load trends, your upcoming goals, and your day-to-day readiness. That's coaching — turning data into decisions. And it's available every time you open the conversation.
Ready to try it?
If you've been training by feel and wondering why your results are inconsistent, your PMC is the missing piece. Connect your Strava account to Veloi, let your ride history sync, and your Performance Management Chart builds itself. You'll see your CTL, ATL, and TSB plotted over time — no spreadsheets, no manual calculations.
Then ask your coach what the numbers mean. Ask whether you should train hard tomorrow or take it easy. Ask when to start tapering for your next event. The data is already there in your rides. Now it's time to actually use it.
