Weekly TSS target for an amateur cyclist: the number to aim for and the number to ignore

What 'weekly TSS target' actually answers — and what it doesn't

TSS is a load proxy, not a load goal. Coggan and Allen built it to score what an athlete already did, so historical loads could be compared and chronic-load curves modeled [Allen et al. 2019]. The published category benchmarks — 300-450 TSS/week for a Cat 4, 500-700 for a Cat 2, 700-1000+ for an elite — are descriptive averages of what those riders happened to produce, not prescriptions of what an amateur should target on Monday.

The category-by-TSS charts circulating on TrainingPeaks and YouTube descend from observational ranges Coggan published alongside the original Performance Manager Chart [Allen et al. 2019]. They are useful as sanity checks — a Cat 3 averaging 200 TSS/week is undertrained for the category; one averaging 900 is probably riding too hard — but they describe the steady-state output of riders training appropriately, not the lever an athlete should pull to get there. Mujika's 2017 review of training-load quantification methods [Mujika 2017] is explicit that external load metrics like TSS are designed to estimate the biological stress an athlete experienced, not to prescribe the stress they should impose. Inverting the relationship is a category error.

The practical consequence is that targeting a TSS number directly invites the wrong fix. Below your target on Sunday? The fastest way to close the gap is to ride harder rather than longer — adding 30 minutes of zone 2 produces about 30 TSS, while replacing a 60-minute zone 2 ride with 60 minutes at sweet spot produces about 80. The TSS scoreboard rewards the second behavior even though the second behavior is precisely the intensity drift Seiler's polarized-distribution research [Seiler 2010] and Stöggl and Sperlich's descriptive analysis of well-trained athletes [Stöggl & Sperlich 2015] identify as the amateur's most common training error. This sits inside the broader self-coached cyclist playbook: when there is no coach holding the periodization line, the rider has to know which metrics to act on and which to read as feedback.

Why hours-per-week is the better primary target for amateurs

Weekly hours is the input variable an amateur actually controls. It is bounded by life, scales linearly with low-intensity volume, and is the single strongest correlate of long-term endurance progression in the descriptive literature [Seiler 2010, Stöggl & Sperlich 2015]. A defensible weekly hours target with a fixed 80/20 intensity ratio produces a TSS range automatically — and it produces the right one.

Run the math forward instead of backward. Six hours per week at 80% low intensity and 20% high intensity produces about 310 TSS — the bottom of the Cat 4 range. Eight hours produces about 415. Ten hours produces about 520, the bottom of the Cat 3/2 range. The TSS number is the output of the time budget and the distribution, not the input. A rider who fixes hours and distribution lands in a sustainable TSS band by construction; a rider who fixes TSS and lets distribution float hits the number by drifting upward in intensity.

Hours-as-target also handles the realities the TSS framing hides. A 90-minute group ride that averaged a normalized 0.85 IF scores roughly 110 TSS — the same as a structured 75-minute threshold session, even though the cardiovascular and recovery costs differ meaningfully. Counting the hour against a weekly-hours budget treats both honestly; counting the TSS against a weekly-TSS target lets the rider double-book the intensity bucket and call it a productive week. Mujika's quantification review [Mujika 2017] is direct on this point: external load proxies should be paired with internal-load monitoring (heart rate at power, RPE) for exactly this reason.

AdaptCycling builds plans against a weekly hours ceiling rather than a TSS target, and re-derives expected weekly TSS from the prescribed sessions. TrainingPeaks lets a coach do the same manually; Intervals.icu surfaces both but enforces neither; TrainerRoad's plan builder is closer to a session-count target. None of these tools are wrong — they optimize different variables. The self-coached rider has to pick which variable to be honest about, and weekly hours is the one life actually constrains.

How to set a defensible weekly TSS range from your own history

Forget the category charts. Pull your last 12 weeks from Strava, Intervals.icu, or TrainingPeaks, drop the highest and lowest weeks, and take the median of the remaining ten. That number — call it your sustainable baseline — is the floor of your weekly range. The ceiling is roughly 1.3-1.4x that baseline, capped by an acute:chronic workload ratio under ~1.5 [Hulin et al. 2016].

The reason to use your own data rather than a Cat 4 chart is that the chart describes a rider whose life, sleep, work stress, and training age are not yours. A 38-year-old parent with a full-time job who has been training consistently for three years has a different sustainable load than a 24-year-old with eight hours of free evenings, even if their FTPs are within 10 watts of each other. Foster's monotony framework [Foster 1998] is built on this directly — illness and overreaching across his 25-athlete sample correlated with the product of weekly load and daily-load variance, not with any absolute TSS number. The relevant baseline is yours, computed from weeks where your training actually went well.

Apply the floor and ceiling as guardrails, not targets. A week that climbs above the 1.5x acute:chronic ratio — the threshold for elevated injury risk in Hulin's rugby-league data and one Halson's monitoring review highlights as actionable [Halson 2014] — is the cue to hold the next week flat or pull a recovery week forward. The manual check is whether this week's TSS is more than 1.5x the trailing four-week average. The recovery-week mechanics that follow are covered in our spoke on recovery-week cadence for self-coached riders.

What this baseline does not do is grow on its own. Coggan and Allen's framework operationalizes 5-7 TSS/day per week as the upper-safe progression for a build phase, with a deload before resuming the ramp [Allen et al. 2019]. Stack three weeks of progression against a recovery week and the new sustainable baseline is roughly 5-15% above the old one. That is the actual rate at which an amateur's TSS ceiling moves. Anything faster is borrowed.

When the TSS number is lying to you

TSS is a power-meter metric scored against your FTP. Four common scenarios degrade its accuracy enough to mislead a self-coached rider: HR-only rides without a power meter, mountain-bike and gravel rides with prolonged coasting and surges, group rides with high variability index, and a stale FTP that has drifted from reality. In each case the number on the scoreboard is not the load on the body.

On HR-only rides, platforms estimate TSS from heart-rate-time-in-zone. The estimate is reasonable for steady-state aerobic work but systematically under-counts very short, very high efforts and over-counts extended hot or dehydrated rides. Halson's monitoring review [Halson 2014] is direct that internal-load methods like HR-derived load are best treated as complements to power-derived load, not equivalents. Treating an hrTSS of 90 and a power-TSS of 90 as the same training stimulus is a small lie that compounds over a season.

Off-road riding produces the opposite distortion. A mountain-bike ride with frequent coasting and hard surges produces a normalized power that under-represents the neuromuscular cost — short supra-threshold spikes are flattened by the 30-second rolling average, and TSS often runs 20-30% lower than the rider's perceived load. Group rides have a related problem: high variability index inflates normalized power, which inflates IF, which squares into TSS. The number is technically correct and practically misleading.

The fourth distortion is the one self-coached riders miss most often. TSS scales as IF squared, so a stale FTP that is 8% low inflates every TSS score by about 17%. A rider who has not retested in three months and has gained fitness will see weekly TSS climb on identical rides. Allen and Coggan recommend updating FTP whenever a 95%-of-20-minute or 60-minute power best is set [Allen et al. 2019]; AdaptCycling, Intervals.icu, and Xert auto-update FTP from the power curve to defend against this drift. If the TSS line is climbing and perceived effort is not, suspect the denominator before celebrating the numerator.

Quick answers

Sources cited in this guide

1. 01
   Allen et al. 2019. Training and Racing with a Power Meter (3rd ed.). VeloPress.
2. 02
   Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.
3. 03
   Stöggl & Sperlich 2015. The training intensity distribution among well-trained and elite endurance athletes. Frontiers in Physiology.
4. 04
   Mujika 2017. Quantification of training and competition loads in endurance sports: methods and applications. International Journal of Sports Physiology and Performance.
5. 05
   Foster 1998. Monitoring training in athletes with reference to overtraining syndrome. Medicine & Science in Sports & Exercise.
6. 06
   Hulin et al. 2016. The acute:chronic workload ratio predicts injury: high chronic workload may decrease injury risk in elite rugby league players. British Journal of Sports Medicine.
7. 07
   Halson 2014. Monitoring training load to understand fatigue in athletes. Sports Medicine.

More inside The self-coached cyclist

Other articles in this series

1. 01

   How to restart cycling training after two weeks off

   When you miss two weeks on the bike, the question isn't whether to resume — it's how to restart without overshooting the next two.

   →
2. 02

   How often to take a recovery week as a self-coached cyclist

   The 3-on/1-off recovery-week cadence is a guideline, not a law. When self-coached riders should hold it, push it, or deload sooner.

   →
3. 03

   Am I overtrained or just tired? A self-coached cyclist's guide

   Functional overreaching, non-functional overreaching, and OTS — what each looks like, and when fatigue crosses into something more serious.

   →
4. 04

   How to spot and fix junk intensity as a self-coached cyclist

   Most amateur rides drift into the medium-hard zone you can't recover from but don't adapt to. How to spot junk intensity — and three structural fixes.

   →
5. 05

   Why year two stalls: junk intensity and the amateur plateau

   Year-one gains came from any training. Year two stalls when intensity drift inverts the 80/20 rule. The mechanism — and the fix.

   →
6. 06

   Cycling training plan for an irregular schedule

   Shift work, a new baby, and weekly travel break the standard 7-day training week. How to plan around an unpredictable schedule.

   →
7. 07

   Safe CTL ramp rate for amateur cyclists: how fast is too fast

   How fast a self-coached cyclist can grow CTL without crossing into non-functional overreaching — the numbers, the signals, and the override rules.

   →
8. 08

   The cheapest way to self-coach cycling in 2026

   Free apps cover most of self-coaching. The one tool worth paying for, where the false economies hide, and the cheapest credible stack in 2026.

   →
9. 09

   When self-coached stops working: signals it's time for a coach

   Self-coaching works for most amateur cyclists — until it doesn't. The four honest signals you've outgrown DIY, and the cheaper fixes to try first.

   →
10. 10

    FTP test vs power curve: should self-coached riders test?

    When the self-coached cyclist actually needs an FTP test versus when the power curve is enough — a judgment-call framework with research backing.

    →
11. 11

    Self-coached 12-week training plan for a goal event

    How a self-coached cyclist builds a 12-week base/build/peak/taper block for a goal event — the math, the workouts, and the taper that holds the peak.

    →