The Hidden Flaws of TSB

The hidden flaws of training stress balance

Training stress balance (TSB) promises a simple answer to a complex question: how fresh am I? It’s tempting to steer your training and racing by that single number. But TSB has blind spots. If you treat it as truth rather than as one input among many, you’ll misread recovery, mis-time key sessions, and miss performance.

What TSB is — and why it feels useful

TSB is usually calculated as chronic training load (CTL) minus acute training load (ATL). In most platforms, CTL is a rolling, weighted average of your last ~42 days of training stress; ATL covers roughly the last 7 days. A positive TSB suggests freshness; a negative TSB suggests fatigue.

Because CTL and ATL are built from training stress score (TSS), TSB gives a compact view of how much stress you’ve applied recently versus what you’re adapted to handle. It’s helpful for spotting blocks of heavy training (TSB negative) and tapers (TSB trending toward zero or slightly positive).

Useful, yes — but TSB is a model of workload, not your physiology. It doesn’t directly measure recovery.

Where TSB falls short

TSB inherits every limitation of TSS and adds a few of its own. Here are the big ones that routinely trip riders up.

  • FTP errors distort the math. TSS depends on FTP. If FTP is set too high, workouts look easier on paper and TSB appears more positive than it should. If FTP is too low, TSB can scream fatigue when you’re fine.
  • Not all stress is captured. Strength training, hard standing climbs, sprints, skills sessions, and off-bike life stress (sleep loss, travel, work) don’t land properly in TSS, so TSB underestimates real fatigue.
  • Energy system bias. TSS is calibrated to threshold work. Anaerobic and neuromuscular efforts (think crit surges or short climbs) can leave you cooked with less TSS than a steady tempo ride.
  • Environment matters. Heat, altitude, dehydration, and illness degrade performance and increase recovery needs without changing TSS. Your TSB can look perfect while your body is not.
  • Individual time constants vary. The default 7-day (ATL) and 42-day (CTL) windows won’t fit every athlete. Some recover fast, others slow. One-size settings hide that variability.
  • It’s a trailing indicator. TSB reflects what already happened. Day-to-day readiness can swing with sleep, glycogen, or stress in ways TSB won’t catch.
Limitation Why it matters What to add
FTP drift or error TSB skews “freshness” up or down Update FTP/CP monthly via best-efforts or a power-duration curve
Missing non-bike stress Underestimates recovery needs Track sleep, soreness, mood, and strength sessions
High-intensity bias Short, hard work feels harder than TSS implies Note RPE and next-day legs after anaerobic sessions
Heat/altitude/illness Performance suppressed at the same TSB Adjust targets 2–8% and increase recovery
Generic time constants Mismatched to your recovery rate Tune ATL/CTL windows or rely more on subjective checks

Smarter ways to manage readiness

You don’t need to abandon TSB. You need to pair it with signals that reflect your physiology today.

1) Calibrate the inputs

  • Refresh FTP or CP every 4–8 weeks using recent best efforts across 3–20 minutes. Don’t rely on a single 20-minute test.
  • Verify power meter accuracy and zero-offset regularly. A 2–3% drift can move TSB meaningfully.
  • Log strength training and big life stress. A simple “+” note or estimated stress points is better than zero.

2) Add simple readiness checks

  • Morning snapshot: resting HR, a quick HRV reading if you use it, and a 1–10 readiness/RPE score. Look for trends, not single numbers.
  • Warm-up probe: ride 5 minutes at your endurance/tempo boundary (e.g., 70–75% of FTP). Compare heart rate and RPE to your normal. If HR is >5 bpm high or low for the same watts and RPE is off, adjust the plan.
  • In-ride sanity check: after the first interval, ask: can I repeat the target with similar quality? If not, cut the set or switch to endurance.

3) Plan with ranges, not absolutes

  • Load blocks: many riders tolerate TSB between -10 and -30 for 5–10 days if sleep and fueling are strong.
  • Key sessions/racing: aim for TSB around -5 to +10, but let feel and readiness checks overrule the number.
  • CTL ramp rates: target 3–5 CTL/week for newer riders and 5–8 for experienced riders, but cap hard‑minute accumulation (e.g., threshold+ minutes) to prevent hidden fatigue.

4) Respect context

  • Heat and humidity: reduce target watts by 2–8% or extend recoveries; increase fluid/sodium. Expect higher HR and RPE at the same TSB.
  • Altitude: reduce intensity for the first 5–10 days; use cadence and RPE to avoid overreaching.
  • Menstrual cycle: note phases that alter perceived effort and adjust key workouts accordingly.

Putting it together: practical examples

Scenario 1: TSB says +8, but legs feel heavy. You slept poorly and traveled. Swap the VO2 session for aerobic tempo with a few short opens, or move the key session 24 hours. Protect quality.

Scenario 2: TSB is -20 during a build, but you feel good. Keep the planned workout if warm-up probes and first interval quality are normal. Trim volume by 10–20% to stay ahead of fatigue.

Scenario 3: Race taper. In the final 5–7 days, let TSB drift toward -5 to +10 by cutting volume 30–50% while keeping a touch of intensity. Use readiness checks daily. If HRV and mood bounce back, you’re on track.

Key takeaways

  • Use TSB to visualize load, not to diagnose recovery.
  • Keep FTP/CP current and note off-bike stress so the model is closer to reality.
  • Let readiness checks (HR, HRV, RPE, warm-up response) overrule the number on the day.
  • Plan in ranges and adjust for heat, altitude, illness, and life.

TSB can guide the big picture. Your nervous system, muscles, and gut decide the small picture. Blend both to time your best rides when it counts.