How many TSS per week do you actually need?

TSS — Training Stress Score — compresses a whole ride into one number. It multiplies how long you rode by how hard you rode, with the hard part squared: an hour flat out at your FTP scores 100, an hour of easy Z2 maybe 40–50, and two easy hours roughly what one hard hour costs. Add up a week and you get a single figure for how much training you did. The obvious next question — and one of the most-asked in structured training — is how big that figure should be.

What the number actually measures

TSS is built from your ride's duration and its intensity relative to your FTP — and intensity is squared, which is the whole personality of the metric. Hard minutes cost disproportionately more than easy ones. That squaring is why a 45-minute VO2 session can out-score a two-hour café ride, and why the number tracks physiological stress far better than hours or distance do.

It also means TSS inherits every flaw in your FTP. If your FTP is set 10% too low, every ride scores too high and your whole week reads harder than it was. Keep the anchor fresh — a stale FTP quietly corrupts every number downstream. (Our FTP guide covers keeping it honest.)

Typical weekly TSS by rider level

There's no magic weekly number — the right load is the one you can absorb and repeat. But the ranges below describe where riders at each level typically land. They're approximate, they overlap, and hours matter as much as the score: the same 400 TSS is a very different week at 6 hours of intensity versus 10 hours of endurance.

Ballpark bands, not targets. A rider recovering well at 350 TSS is training better than one falling apart at 500.

The ramp rate is the real answer

Here's the reframe that makes the question tractable: the right weekly TSS isn't an absolute number, it's a bit more than you've been doing. Your body adapts to your rolling average load — the metric usually called CTL, or Fitness — and what it punishes is not high load but sudden load. A rider adapted to 600 TSS/week shrugs off a week that would hospitalise a rider adapted to 250.

So the useful rule of thumb is about the slope, not the height:

In practice a +3–5 CTL ramp means adding very roughly 30–50 TSS to your weekly total each week during a build — then taking an easier week every third or fourth to let the adaptations land. Slow and repeatable beats fast and fragile, every time.

How chasing TSS corrupts training

TSS is a measurement, and like every measurement, it degrades the moment it becomes the goal. The failure mode is well known: a rider starts riding for the score — a bit harder on the recovery spin, a bit of tempo on the endurance ride — because it makes the weekly number bigger. The result is a diet of junk tempo: everything comfortably hard, nothing easy enough to recover from, nothing hard enough to force adaptation. The score rises while the training quality falls.

Two identical 400-TSS weeks can be a well-polarised block or a grey-zone slog. The number can't tell the difference — you have to. Set the week's structure first (which sessions, which zones), and let TSS fall out of it as an audit, not a target.

Let Fitness, Fatigue and Form read it for you

The honest answer to "how many TSS do I need" is that you shouldn't have to do this arithmetic at all. The maths that turns daily TSS into a rolling picture — Fitness (your long-term average load), Fatigue (the short-term average) and Form (the gap between them) — is mechanical, and software does it better than a spreadsheet habit ever will. Moveee's fitness page computes all three from every ride automatically, shows you your current ramp rate, and makes it obvious when you're building sustainably versus digging a hole. (New to those three numbers? Our Fitness, Fatigue and Form guide explains them properly.)

So: land in the range for your level, ramp by a few CTL points a week, keep the easy days easy — and let the software do the counting.