I have written about what CTL, ATL and TSB mean — the Banister model, the maths, the Performance Management Chart, the whole framework. If you want to know what the three numbers are and where they came from, start there. This piece is about something different: how to actually use them in the real world without losing your mind.
Because that is what happens. Cyclists buy a power meter, open TrainingPeaks, discover CTL, and within three months are checking their PMC more often than their bank balance. The chart becomes the coach. Rest days start feeling like failure because CTL drops. Hard days get added not because the body needs work, but because the number needs feeding. A tool that was supposed to serve training starts running it.
I have watched this happen with athletes I coach, with listeners of the podcast, and — if I am honest — with myself, years ago when I first got my head around the numbers. The model is seductive because it is clean. Three lines, three numbers, an apparently objective answer to the messiest question in sport: am I doing enough? Too much? Just right?
The problem is that the question is never that clean. And the answer is never fully contained in a chart.
The PMC is a compass, not a map
The Performance Management Chart describes the load your body has absorbed. That is useful information. But it says nothing about how well you absorbed it, what kind of stress it was, whether you slept through the adaptations, or whether the forty hours of work you did this week at your desk are sitting on top of the training stress like an invisible second load.
The analogy I keep coming back to: a compass tells you which direction is north. It does not tell you whether the terrain between here and north is a road or a cliff. The PMC tells you the direction of your training load. It does not tell you whether the load is producing adaptation or just producing fatigue.
This distinction matters because the default assumption — higher CTL equals fitter cyclist — is wrong often enough to be dangerous. And the corollary — negative TSB means I need rest — is wrong even more often.
CTL does not equal fitness
This is the single most important sentence in any conversation about training load management, and I will keep saying it until it stops needing to be said.
CTL measures the training stress you have absorbed over roughly six weeks. It does not measure the fitness you have gained. Those are different things. They are related, but they are not the same thing, and treating them as interchangeable is where most amateur training plans go wrong.
Here is a rider with a CTL of 90. Trained consistently for months, rarely missing a day. Eighty percent of their riding has been in the grey zone — too hard for Zone 2, too easy for threshold. They sleep six hours a night, skip meals, and feel permanently flat. Their twenty-minute power is the same as it was six months ago.
Here is another rider with a CTL of 65. Four days a week: two properly easy rides below their Zone 2 ceiling, one proper interval session at 105% of FTP, one longer weekend ride. They sleep eight hours, eat enough to fuel the work, and take a recovery week every third week. Their twenty-minute power has gone up twelve watts in three months.
The second rider is fitter. The chart says otherwise. The chart is wrong — not because the maths is broken, but because the maths measures load, not adaptation. Dr. Stephen Seiler's work on polarised training makes the mechanism clear: adaptation requires that easy sessions are actually easy and hard sessions are actually hard. Grey-zone riding satisfies neither requirement. It produces TSS, which produces CTL, which produces a number that looks like fitness and is not.
If you take one thing from this article: stop chasing CTL. Let it be a by-product of good training. The moment you start designing sessions to feed the number rather than to produce adaptation, you have handed the tool the coaching decisions.
When to trust TSB and when to ignore it
TSB — Training Stress Balance — is the gap between your fitness (CTL) and your fatigue (ATL). Negative means you are carrying fatigue. Positive means you are fresh. Simple.
Except that TSB is most useful at the extremes and nearly useless in the middle.
TSB below −30 for more than a week: pay attention. This is genuine overreaching territory. If it is planned — a three-day training camp, a deliberate overload block — and recovery follows, fine. If it is unplanned, or if it persists beyond ten days, the risk of non-functional overreaching, illness and injury rises sharply. The number is doing its job here. Listen to it.
TSB above +15 heading into a target event: also useful. This confirms that the taper is landing, fatigue is clearing, and the fitness you built over the preceding months should be available on race day. The number and the body should agree, and if they do not — if TSB is +18 but you still feel flat — that is a signal worth investigating (usually sleep or nutrition).
TSB between −15 and +5: this is where most training life happens, and this is where the number tells you the least. A TSB of −8 on a Tuesday morning during a build block is completely normal. It does not mean you need rest. It means you trained over the weekend, which is what you were supposed to do. If you slept well, your resting heart rate is normal, and you want to ride, then ride. The number is not the deciding vote. Your body is.
The danger zone is when a rider sees TSB at −12 and cancels an interval session because the chart says they are fatigued. Maybe they are. Maybe they are not. The chart cannot know because it cannot measure sleep quality, work stress, whether they ate properly yesterday, or whether the weekend volume was Zone 2 or Zone 4. In the middle range of TSB, the subjective check wins every time.
The Monday morning check
I use a simple five-minute routine with every athlete I coach. Before looking at any numbers, before opening TrainingPeaks, before checking TSB — answer four questions honestly.
Resting heart rate. Taken before getting out of bed, ideally at the same time each morning. The absolute number matters less than the deviation from your baseline. If your normal resting HR is 52 and this morning it is 58, that is a signal. If it is 53, that is noise.
Sleep quality. Not duration — quality. Rate it 1 to 5. Did you wake up rested or did you drag yourself out of bed? Did you wake up in the night? Were you still wired at midnight? A 1-5 score is more actionable than eight hours of tracked data, because it captures how you actually feel rather than how long you were horizontal.
Appetite. Normal or suppressed? Genuine fatigue — the kind that means the body is struggling to recover — almost always suppresses appetite. It is one of the earliest warning signs and one of the most ignored. If you do not want breakfast on a training day, something is off.
Training motivation. Do you want to ride today, or are you dreading it? There is a difference between "I don't feel like doing intervals" (which is normal — nobody feels like doing intervals) and "I cannot face getting on the bike at all." The first is laziness, which you override. The second is a warning, which you respect.
The decision rule: if three of the four are good, train as planned. If two or more are off, adjust. Adjustment does not mean cancelling. It might mean turning today's interval session into Zone 2. It might mean cutting the session from ninety minutes to sixty. It might mean swapping today's hard ride for tomorrow's easy one. The point is that the decision comes from you, not from a line on a chart.
After you have made the call, then look at the numbers. Use them to confirm or challenge your subjective read. If your Monday check says you are fine and TSB says you are at −22, you might choose to train but keep an eye on things across the week. If your Monday check says you feel awful and TSB says you should be fresh at +10, you need to investigate what the model is missing. The interplay between subjective feel and objective data is where real training intelligence lives.
The gap the PMC cannot see
The model was built to quantify physical training stress. It does this well. What it cannot do — what it was never designed to do — is account for the rest of your life.
Work stress. A toddler who does not sleep through the night. A house renovation. Financial pressure. All of these impose genuine physiological stress — cortisol, sympathetic nervous activation, impaired sleep — that competes directly with training stress for the same recovery resources. The PMC treats a 200-TSS week during a relaxing holiday and a 200-TSS week during a divorce as identical loads. They are not. Same numbers, different outcomes.
This is why subjective markers matter more than the data for daily decision-making. The HRV-monitoring approach Dr. Dan Plews advocates — using the 7-day rolling average — catches some of this external load because HRV reflects total stress, not just training stress. But the simplest stress detector remains the four-question Monday morning check. If appetite and motivation are both suppressed on a day when your training load is moderate, look at what else is happening in your life before adding more stress on the bike.
Why masters riders need a different lens
If you are over 40 — and most of the Roadman audience is — the standard PMC time constants do not quite fit you. The model uses a 42-day constant for fitness and a 7-day constant for fatigue. Those constants were derived from research on younger athletic populations, and while they work well enough as defaults, they miss something that every masters cyclist eventually discovers: fatigue lingers longer than it used to.
At 25, a hard Saturday group ride clears by Tuesday. At 45, that same ride might still be sitting in your legs on Wednesday. The session was the same. The recovery demand grew. The PMC does not know this because the 7-day ATL constant does not change with age. Your actual fatigue profile has stretched to nine, maybe twelve days, but the model still assumes seven. The result is that ATL declines on the chart faster than fatigue declines in your body. TSB climbs to zero and the chart says you are fresh. Your legs say otherwise.
The practical response is not to hack the time constants in TrainingPeaks — that creates more confusion than it solves. The practical response is to build a longer recovery buffer into your weekly and monthly structure. Hard sessions spaced 72 hours apart instead of 48. Recovery weeks every third week instead of every fourth. And — this is the important one — permission to call an audible when the body is still carrying last week's load, regardless of what the chart says today.
Andrea Morelli, who has been coaching masters cyclists for over twenty years, told me something I have never forgotten: the biggest gains for riders over 40 come not from training harder but from recovering better. Every masters cyclist I work with who makes a breakthrough does so by protecting their recovery, not by adding volume. The CTL might sit lower than a younger rider's. The adaptation rate is often higher, because the work that does get done is absorbed properly.
The Masters Recovery Score tool on this site is designed for exactly this — giving masters riders a way to cross-reference their training load with age-adjusted recovery expectations.
The difference between tired and overtrained
This is where numbers actually help, if you know what to look for.
Normal training fatigue looks like this: legs feel heavy, first ten minutes of a ride are harder than usual, but once you warm up the power is there. Intervals within 3-5% of target. Sleep fine. Appetite normal. Motivation wavers but comes back once you start pedalling. TSB mildly negative. This resolves within two to three days of easier riding.
Non-functional overreaching looks like this: the fatigue does not clear after a rest day. Intervals drop more than 5% below target across multiple sessions. Sleep is disrupted — difficulty falling asleep or waking at 3am. Appetite suppressed. Motivation replaced by dread. Resting heart rate elevated by 5-8 beats above baseline. You catch every cold going around. TSB has been below −20 for three or more weeks, or — and this is the sneaky one — TSB has climbed back toward zero but you still feel wrecked, which means the external load the chart cannot see is the problem.
Where the numbers help: the PMC is most useful for spotting the trajectory toward overreaching before it arrives. A CTL ramp rate above 7 points per week sustained for three or more weeks is a warning. TSB below −30 for more than ten days is a warning. ATL spiking without a corresponding planned overload block is a warning. These are patterns visible on the chart weeks before the body breaks, and this is where training load tracking earns its place — as an early warning system, not as a daily decision-maker.
Where the numbers do not help: once you are properly overtrained, the PMC will not tell you how long recovery takes. That depends on how deep the hole is, how much external stress is involved, and individual physiology. Some riders bounce back in two weeks. Others need two months. The chart will show CTL declining and TSB rising, and at some point the numbers will look normal, but the body might still not be ready. This is where a coach who knows you, or at minimum the honest four-question morning check, matters more than any dashboard.
What a well-managed training week looks like
Not in sessions — I have written about weekly structure in the time-crunched cyclist guide and the interval session builder handles the specifics. This is about what a well-managed week looks like through the lens of load.
Monday: rest day or very easy spin (under 40 TSS). Run the morning check. Review last week's actual load against planned load.
Tuesday: first hard session. Threshold or VO2max intervals, 80-120 TSS in 60-90 minutes. Arrive rested from Monday. If the power is more than 5% below target after a proper warm-up, cut the session short. A failed interval set is worse than a shortened one because it adds fatigue without the stimulus that justifies it.
Wednesday: easy ride or rest. Genuine Zone 1, under 65% of FTP, or off the bike entirely. This is the day most amateurs wreck by riding too hard. If Wednesday becomes a tempo ride, Friday's intervals suffer.
Thursday: easy ride. Same rules as Wednesday. Two rest days before a hard session is not laziness for a masters rider — it is strategy.
Friday: second hard session. Shorter intervals or race-specific work, 70-100 TSS. If Tuesday's session went well and today's power numbers are on target, the week is tracking.
Weekend: one longer endurance ride (2.5-4 hours, mostly Zone 2, 120-180 TSS) and one easy day or rest day. The long ride is where CTL gets its weekly feeding, but only if it is actually aerobic. A "Zone 2 ride" that drifts into tempo for every climb is grey-zone work — it adds TSS without the intended aerobic adaptation.
The weekly TSS total for this structure typically lands between 400 and 550 for an amateur riding 8-10 hours. More important than the total is the distribution: two sessions carry most of the intensity stress, the long ride carries the volume stress, and the remaining days carry almost nothing. That polarisation — not the total number — is what produces adaptation.
When tracking helps and when it becomes noise
Training load tracking earns its keep in three specific contexts.
Seasonal planning. Watching CTL build across a 16-week progression gives you a visual check on whether the plan is working. The staircase pattern — three weeks up, one week back, next block starting higher — should be visible. If CTL is flat despite consistent training, intensity distribution or recovery is the problem. If CTL is rising but race results are not, training quality is the problem.
Taper timing. The two-week window before a target event is where TSB earns its place. Watching ATL drop while CTL holds steady, watching TSB climb toward the +5 to +15 window — that is the model doing exactly what Banister designed it to do. You can time your sharpening sessions, your last hard day, and your final rest day with real precision using the PMC as a guide. The broader race peaking guide covers the nutrition, openers, and race-week structure that sit around these numbers. This is the model's best use case by a wide margin.
Post-illness or post-injury return. After a forced break, CTL tells you where your fitness baseline has dropped to. That number sets the starting point for rebuilding — and it prevents the common mistake of jumping back to pre-illness volume because "I was doing that three weeks ago." You were. Your body is not there anymore. The chart keeps you honest about where you actually are.
Training load tracking becomes noise — or worse, actively harmful — in other contexts.
Daily decision-making. Checking TSB every morning to decide whether to ride is like checking the weather forecast every five minutes during a ride. The information changes too little across that timescale to be actionable, and the habit of checking creates anxiety where none is needed. Check twice a week. Monday for the weekly picture. Friday to confirm the week is tracking. That is enough.
Rest day guilt. If a rest day triggers the thought "but my CTL will drop," the tracking has become a problem. CTL drops roughly one point per rest day. A single rest day might cost you half a point of CTL and save you from a blown session later in the week that would cost you far more in missed adaptation. The maths favours rest. The psychology of number-chasing does not.
Comparing your numbers to other riders. Your CTL reflects your training history, your hours, your recovery, your age, your genetics, and a hundred factors that have nothing to do with anyone else's chart. A CTL of 60 for a forty-five-year-old parent training eight hours a week is a completely different achievement from a CTL of 120 for a twenty-five-year-old training twenty hours. Stop comparing.
Putting it together
The riders I coach who manage training load well share a few habits that have nothing to do with software.
They train by feel first and check the numbers second. They use the Monday morning check — resting heart rate, sleep quality, appetite, motivation — as the primary input, and let the PMC confirm or challenge that read. They have learned to distinguish between the mental resistance to hard work (normal, override it) and the physical signals of accumulated fatigue (real, respect it).
They do not chase CTL. They understand that a dip during a recovery week or a period of life stress is not lost fitness but managed load. They let CTL be the result of good training rather than the target of it.
They protect their recovery with the same discipline they bring to their intervals. The session creates the stimulus. Sleep, food and rest create the adaptation. Miss the second part and the first part was just fatigue for nothing.
They use the PMC for what it is good at — seasonal trajectory, taper timing, post-break recalibration — and ignore it for daily decision-making during a normal training block.
And they treat subjective markers as data, not as weakness. "My appetite is off" is information. "I slept badly for three nights running" is information. The rider who logs these alongside their TSS has a richer picture of their training state than the rider who logs TSS alone.
The PMC is a good tool. It might be the best single tool we have for tracking training load across a season. But it is a tool, not a coach. The moment you hand it the coaching decisions — the moment you stop listening to your body because the chart says something different — is the moment it stops working for you and starts working against you.
If you want to talk through how this applies to your own training, the Roadman community on Skool is where that conversation happens. Coaches, athletes, and riders working through the same questions — when to push, when to back off, and how to tell the difference.
If you want the theory behind the numbers this article puts into practice, the full CTL, ATL and TSB explainer covers the model, the maths, and where it came from.
And if you want to run your own numbers, the Training Load Calculator, the TSS Calculator, and the FTP Zone Calculator are on the site — free, no signup, no spreadsheet required.