CTL, ATL, TSB: What to Ride Tomorrow
9 min read
Photo by Zuzana Ruttkay on Unsplash
Fitness vs fatigue vs form, in one call: if you feel wrecked but the chart says go, skip the hero interval. How a time-crunched racer turns load into tomorrow's ride.
On this page
Photo by Munbaik Cycling Clothing on Unsplash.
CTL tracks long-term load, ATL tracks recent fatigue, and TSB estimates readiness. Use them to change one clear dial, not your whole plan.
Training load metrics turn your ride history into a control panel. They do not replace your legs, sleep, or judgment, but they help you see when fitness is building, fatigue is stacking, and freshness is returning.
Peak season often mixes heat, racing, travel, and outdoor intensity, so your plan can drift fast. CTL, ATL, and TSB help you spot that drift before you rewrite the whole week.
Think of the three numbers as one system, not three separate verdicts. CTL shows the load you have built, ATL shows the load you just took on, and TSB shows how fresh that leaves you today.
The best use is narrow and practical. When the system drifts, change one dial first: volume, recovery, or timing. For race-week tradeoffs, pair this article with form and fitness near race day.
Read CTL as built load, not proof of fitness.
Read ATL as recent strain, not a moral score.
Read TSB as readiness context, not a command.
Change one dial before changing the whole week.
That keeps the next move clear when the dashboard gets noisy.
In N+One terms: these three numbers are your training system’s dashboard.
Photo by Alexandre Daoust on Unsplash.
CTL, or chronic training load, is a long-window average of training stress. It moves slowly, so it is best read as a trend across weeks, not a verdict on one ride.
ATL, or acute training load, is the shorter-window view of recent stress. It can rise quickly after hard intervals, race blocks, camp weeks, or stacked long rides.
TSB, or training stress balance, is commonly shown as CTL minus ATL. A higher TSB usually means more freshness, while a lower TSB means more recent fatigue, within your own baseline.
These numbers come from a stress input such as TSS, normalized load, or a heart-rate based model. If you want to read workout stress with more care, use workout quality beyond total stress alongside these load trends.
CTL = longer-term load from repeated training stress.
ATL = recent load from the last run of sessions.
TSB = CTL minus ATL in many tools.
Positive TSB often means fresher, within your own history.
Negative TSB often means more fatigue, not failure.
CTL = long-term average training stress (fitness).
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Most load charts use smoothing, which weights recent days more than older days. That is why ATL can change fast while CTL often lags behind your current feel.
The exact setup differs across tools and stress models. Treat absolute numbers with care, then focus on the slope, the gap between lines, and your own past response.
A missed file, stale threshold, bad power data, or unlogged ride can bend the chart. Your model is only as useful as the data stream feeding it.
This is also why CTL is not the same as health, toughness, or worth. It is a model of recorded training stress, and the model needs your human checks.
Compare trends inside the same app.
Check power, threshold, and ride files often.
Do not compare your CTL to another rider’s CTL.
Ask whether the chart matches your legs.
In N+One terms: the math gives you a lagged, smoothed signal, so read direction before drama.
Use CTL to plan the build, ATL to guard recovery, and TSB to time sharper work. That simple split keeps the metrics tied to decisions.
For a build block, let CTL rise in small steps while keeping key intensity possible. If fatigue starts to blur your hard days, trim endurance volume before cutting every hard effort.
For a taper, reduce recent load so ATL falls while CTL stays mostly in place. Keep short, race-like efforts so freshness rises without making your legs feel flat.
Season goals matter here. A summer A-race build should not look like winter base work, so set fitness goals around your A-race before chasing a bigger number.
Build: let CTL rise in small, staged steps.
Key sessions: protect intensity before adding more volume.
Taper: lower recent load while keeping short race efforts.
Race week: compare TSB with your own best past races.
Use the three numbers to choose the next dial, not to chase every line.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- TSS, IF, and Variability Index: Reading Workout Quality Beyond Total Stress — Learn how to read TSS, IF, and Variability Index together so you can judge workout quality beyond total stress and make one clear training adjustment.
- Detraining for Cyclists: How Fast CTL Drops After Illness or Holiday — Direct evidence on CTL drops after illness or holiday is limited. Use this clear return plan to cut volume, keep some intensity, and rebuild safely.
- Acute-to-Chronic Workload Ratio for Cyclists: Injury Risk and Performance Sweet Spots — Learn how cyclists can use ACWR to spot sudden training load spikes, understand its limits, compare it with TSB, and plan one conservative week.
The first mistake is overreacting to one value. A single low TSB day may be fine inside a planned build, especially if power, mood, and sleep still look steady.
The second mistake is chasing weekly stress totals while ignoring the shape of the week. Two riders can reach the same load with very different strain, monotony, and recovery cost.
The third mistake is acting as if life stress does not count. Heat, poor sleep, work pressure, travel, and illness can lower your recovery room even when the chart looks tidy.
If ATL jumps after a camp week or race block, plan a soft landing instead of snapping back to normal. The same idea applies when ATL spikes after camp weeks and your legs need time to catch up.
Do not chase a universal TSB target.
Watch the shape of load, not only the total.
Lower volume when life stress rises.
Use sleep, mood, and session feel as checks.
If data and body disagree, trust the body first.
In N+One terms: the model is useful, but your biology writes the final score.
If your TSB falls below your usual low range, or your recovery feel drops, keep intensity and cut volume. Hold that change for seven days, then reassess.
This move protects the signal from hard sessions while taking load out of the system. It is simple enough to use when you are tired and busy.
If recovery returns, resume the build with smaller steps. If fatigue stays high, repeat the reduced-volume week and look for missing inputs such as sleep debt, heat strain, illness, or fueling gaps.
This rule is especially useful after a forced break, when the urge to catch up can distort the build. Use a slower path for rebuilding CTL after time off instead of forcing the chart upward.
Trigger: TSB is below your normal low, or recovery feels poor.
Action: keep intensity, reduce weekly volume for seven days.
Check: review morning feel, sleep, and session quality.
Next: resume only when recovery returns.
That single move turns a noisy chart into a next-session decision.
In N+One terms: one clear dial, keep intensity, trim volume, reassess in a week.
Day 0 — assessment: Confirm TSB is unusually low for you, or that recovery feels poor. Keep only easy riding unless you feel ready for one short race-intensity check.
Week 1 — reduce volume, keep intensity: Cut total weekly volume by a small but clear amount. Preserve one quality session, but shorten it if power or perceived effort is off.
Week 2 — monitor and nudge CTL: If recovery improves and TSB moves toward your normal range, resume with a gentler build. If not, repeat the reduced-volume week.
Week 3 — resume progression or extend recovery: If metrics and feel are back in range, return to planned progression. If fatigue persists, pause the build and seek qualified medical or coaching support.
CTL tracks long-term load, ATL tracks recent fatigue, and TSB estimates readiness. Use them together, then make one clear move: keep quality, trim volume when fatigue outruns recovery, and reassess after a week.