Every power meter file ends the same way. You stop recording, upload the ride, and a number appears alongside all the other numbers: duration, kilojoules, average power, Normalised Power, and then — TSS. Training Stress Score. It sits there at the bottom of every post-ride summary, and for most cyclists it stays there, unexamined, while they scroll straight to average watts.
That is a wasted opportunity. TSS is the single most useful number your power meter produces for planning training, because it answers the question every cyclist eventually needs answered: how much did that ride cost me, and how much can I do tomorrow?
Dr. Andrew Coggan and Hunter Allen developed TSS as part of the power-based training framework they introduced in the early 2000s. The concept was deliberately simple: take the duration and intensity of any ride, express both relative to the rider's functional threshold power, and produce a single number that represents the physiological cost. One hour at FTP — your hour-of-power pace — equals exactly 100 TSS. Everything else scales from there. Half an hour at FTP is roughly 50. Two hours at 75% of FTP is roughly 112. A five-hour sportive at moderate intensity might produce 250. The number anchors every ride to the same reference point, making sessions comparable across duration, intensity and terrain.
The framework was built for power data, but it has since been extended to heart rate, perceived effort and running. The core logic remains identical: quantify the cost of the session so you can manage the total load across a week, a block and a season.
The formula
TSS is calculated from two derived metrics: Normalised Power (NP) and Intensity Factor (IF).
Normalised Power is a weighted average that accounts for the variable nature of cycling power — the surges, the coasting, the intervals. It uses a 30-second rolling average raised to the fourth power, averaged across the ride, then brought back to the fourth root. The maths sounds arcane, but the purpose is simple: NP reflects the metabolic cost of the ride better than simple average power does, because hard surges cost disproportionately more energy than easy spinning saves.
Intensity Factor is your Normalised Power divided by your FTP:
IF = NP / FTP
An IF of 1.0 means you rode at your functional threshold. Below 1.0 means below threshold. Above 1.0 means you pushed beyond it — sustainable only for shorter efforts.
The TSS formula itself is:
TSS = IF² × Duration (hours) × 100
The squaring of IF is critical. It means that intensity has an exponential effect on training stress. A ride at IF 0.90 does not produce 90% of the stress of a ride at IF 1.0 — it produces 81%. A ride at IF 0.70 produces only 49% of the stress per hour. This exponential weighting reflects a physiological reality: the metabolic cost of exercise rises non-linearly with intensity. Riding at 90% of threshold is not 90% as hard as riding at threshold. It is considerably less stressful, and the formula captures that.
A few benchmark examples to anchor the numbers:
| Ride type | Typical IF | TSS per hour | |-----------|-----------|--------------| | Recovery spin | 0.55–0.65 | 30–42 | | Zone 2 endurance | 0.65–0.75 | 42–56 | | Tempo | 0.76–0.85 | 58–72 | | Sweet spot | 0.85–0.95 | 72–90 | | Threshold intervals | 0.95–1.05 | 90–110 | | VO2max session (with rests) | 0.80–0.95 | 64–90 | | Time trial / race | 0.95–1.10 | 90–121 |
You can run your own numbers through the TSS Calculator without needing to do the arithmetic by hand.
What a single TSS number tells you
The value of TSS sits in its relationship to recovery. Coggan originally proposed the following framework for interpreting individual session TSS, and it has held up well across two decades of coaching practice:
Under 150 TSS: Recoverable by the next day for a trained cyclist. This covers most weekday sessions — an hour of intervals, ninety minutes of tempo work, a brisk club run. You wake up the next morning with some residual fatigue but nothing that prevents quality training.
150–300 TSS: Residual fatigue lingers into the next day and sometimes into the day after. A hard three-hour group ride, a four-hour endurance ride with a solid tempo block in the middle, or a demanding criterium. You can still train the next day, but it should be easy — recovery or low-intensity endurance. Stacking back-to-back sessions in this range without a rest day catches up with most amateur riders within a week.
300–450 TSS: This is a big day. A long sportive, a hard road race, or a five-to-six-hour training ride with significant climbing. Recovery takes two to three days for most riders. Masters cyclists over 45 often need three to four. Planning a quality interval session within 48 hours of a 350+ TSS day is optimistic for nearly everyone outside the professional ranks.
Above 450 TSS: Stage-race territory, ultra-endurance events, or simply very long days in the saddle with sustained intensity. Recovery demands four to seven days depending on the rider, the conditions and the accumulated fatigue heading into the effort. An Etape du Tour or a 200-kilometre audax in the mountains can produce 500–700 TSS. These are the rides that leave a mark on the body for a week.
These brackets are guidelines, not rules. A rider with a CTL of 100 absorbs a 200 TSS day differently from a rider with a CTL of 40. Age, sleep, nutrition, life stress and training history all shift the recovery timeline. But the scale gives you a working framework for planning what comes after a hard session — which is where most training plans either succeed or fall apart.
TSS per hour: the intensity marker hiding in plain sight
Raw TSS tells you the total cost of a ride. TSS per hour tells you how hard you rode. The distinction matters enormously.
Consider two rides, both producing 200 TSS. The first is a two-hour threshold session: 100 TSS per hour, relentless, legs screaming by the end. The second is a five-hour sportive at a social pace: 40 TSS per hour, conversational throughout. The total stress is identical. The physiological demand is not remotely comparable. The threshold session hammered your anaerobic system, taxed glycogen stores heavily and probably left you unable to produce quality power the next day. The endurance ride stressed the aerobic system, burned mostly fat, and you could likely ride again tomorrow with minor fatigue.
TSS per hour is, in effect, another way of expressing IF — and it is often more intuitive. Most coaches I have spoken to on the podcast use TSS/hr as a quick sanity check:
- Below 40 TSS/hr: Recovery or very easy aerobic riding
- 40–60 TSS/hr: Endurance pace, the Zone 2 bread and butter
- 60–80 TSS/hr: Tempo to sweet spot, the productive middle ground
- 80–100 TSS/hr: Threshold work, demanding and time-limited
- Above 100 TSS/hr: Race pace or sustained supra-threshold, rarely maintainable beyond 60–90 minutes
When you review your training log at the end of a week, scanning TSS/hr across sessions gives you an immediate picture of intensity distribution. If every ride sits at 60–75 TSS/hr, you are living in the grey zone — too hard to be genuine endurance, too easy to force threshold adaptation. That is the pattern that produces slow improvement despite feeling like you are working hard. A well-structured week shows variation: a couple of sessions at 40–55, one or two at 85–100, and perhaps one longer ride at 50–65.
Weekly TSS budgets
Individual session TSS tells you what a single ride cost. Weekly TSS tells you whether your overall training load matches your goals, your available hours and your body's capacity.
The table below gives approximate weekly TSS ranges by training level and available hours. These are guidelines for riders who have built to these loads progressively over months — not targets to hit in your first week back from a break.
| Training level | Hours/week | Weekly TSS range | |---------------|-----------|-----------------| | Recreational / fitness | 4–6 | 200–350 | | Club rider | 6–8 | 300–500 | | Serious amateur | 8–12 | 450–700 | | Competitive amateur | 10–14 | 600–900 | | Elite amateur / Cat 1-2 | 14–18 | 800–1,100 | | Professional | 20–30 | 1,000–1,500+ |
Adjusting for age
Masters cyclists need to read these numbers with a correction. Recovery capacity declines with age — not catastrophically, but measurably. The hormonal environment shifts: testosterone declines gradually from the late 30s, growth hormone drops, and the inflammatory response to exercise takes longer to resolve. Sleep architecture changes. Connective tissue becomes less elastic. None of this means you cannot train hard. It means the ratio of stress to recovery needs to shift.
A practical adjustment for masters riders:
- Ages 35–44: Most riders can operate at the upper end of their category's range with disciplined recovery (sleep, nutrition, periodisation).
- Ages 45–54: Drop 10–15% from the upper bound. A serious amateur who might sustain 700 weekly TSS at 38 is better served by 550–620 at 50 unless recovery is exceptional.
- Ages 55–64: Drop 15–25%. Training quality — what you do with the hours — matters more than raw volume. A 55-year-old accumulating 400–500 weekly TSS with polarised intensity distribution will outperform one grinding out 600 in the grey zone.
- Above 65: Individual variation widens dramatically. Some riders hold robust training capacity into their late 60s. Others need to moderate more aggressively. The non-negotiable is monitoring recovery markers — sleep quality, resting heart rate, mood, appetite — and adjusting weekly TSS in response to what the body reports, not what the calendar prescribes.
These are not hard limits. They are starting points. If your FTP zones are set correctly and you are tracking consistently, the data will show you where your personal ceiling sits.
Why TSS lies — the known limitations
TSS is useful precisely because it is simple. But that simplicity comes at a cost, and understanding where the model breaks is as important as understanding how it works.
It treats all stress equally
One hundred TSS from Zone 2 endurance riding is metabolically, hormonally and neurologically different from 100 TSS earned through VO2max intervals. The endurance ride primarily stressed the aerobic system, utilised fat oxidation, demanded minimal glycogen, and produced relatively little muscle damage. The interval session taxed the anaerobic system, depleted glycogen stores, created significant metabolic acidosis and inflicted measurable muscle damage. Both produce the same number on the screen. The recovery demands are not the same.
This is not a flaw in the formula — it is a deliberate trade-off. TSS was designed to quantify load at a level of abstraction that makes weekly and monthly planning possible. It was never intended to replace a coach's understanding of what kind of stress was applied. Coaches who use TSS well pair it with workout descriptions and intensity distribution data. Coaches who use it badly treat 100 TSS as 100 TSS regardless of source.
It underestimates easy rides
Because IF is squared, the contribution of low-intensity riding to TSS is compressed. A four-hour Zone 2 ride at IF 0.65 produces only 169 TSS (0.65² × 4 × 100). That number does not fully reflect the cumulative fatigue of four hours in the saddle — the glycogen depletion, the connective tissue stress, the postural fatigue, the hydration and caloric cost. The metabolic models that TSS is built on weight intensity heavily, which is correct for short and moderate-duration efforts but less accurate for the very long, very easy rides that form the base of any endurance programme.
In practice, this means your training log will consistently show low TSS for long slow rides relative to how those rides actually feel the next day. A five-hour Zone 2 ride producing 210 TSS looks like "less stress" than a 90-minute threshold session producing 135 TSS. Your legs will disagree.
It overestimates short, hard efforts
The inverse problem. A 20-minute all-out effort at IF 1.10 produces 40 TSS (1.21 × 0.33 × 100). That number overstates the systemic recovery cost because the ride was too short to create meaningful glycogen depletion, significant muscle damage or the accumulated fatigue that makes a long ride hard to recover from. Forty TSS in 20 minutes sounds alarming compared to 40 TSS in a gentle one-hour spin, but the spin is actually harder to recover from in total-body terms.
For riders who do a lot of short, high-intensity work — criterium racers, track cyclists, anyone whose sessions are built around short intervals with long rests — weekly TSS can look surprisingly high despite the actual recovery demand being manageable. The opposite can happen for ultra-endurance athletes whose enormous volume at low intensity produces modest weekly TSS totals that understate how much rest they need.
It depends on an accurate FTP
Everything in the TSS calculation pivots on FTP. If your FTP is set too high, your IF will be artificially low and your TSS will be underestimated — you will think you are doing less work than you are. If your FTP is set too low, TSS will be inflated, and you will over-estimate your training load.
This is not an abstract problem. FTP drifts with fitness, fatigue, illness and the season. A rider whose FTP was 260W in March and is now 280W in July but has not updated the number is systematically under-counting their TSS. The fix is simple: test regularly, or at the very least update your FTP every six to eight weeks. The FTP Test Calculator on this site can help you estimate your threshold from various test protocols.
TSS from heart rate: hrTSS and rTSS
Not every rider has a power meter on every bike, and not every activity produces power data. TrainingPeaks developed heart-rate-based TSS (hrTSS, sometimes called rTSS) to fill the gap. The principle is the same: quantify the cost of the session relative to a threshold marker. Instead of FTP, the reference is Lactate Threshold Heart Rate (LTHR).
The calculation uses the heart rate data to estimate an equivalent Intensity Factor, which is then plugged into the same IF² × duration × 100 formula. The result is a TSS-equivalent number that can be plotted alongside power-based TSS on the Performance Management Chart.
It works. But it works less well, for two specific reasons.
Cardiac drift. On rides longer than about 90 minutes, heart rate rises even at constant effort — a phenomenon driven by dehydration, heat accumulation and sympathetic nervous system drift. A rider holding 200W for four hours will see their heart rate climb from perhaps 135 bpm at the start to 150 bpm by the finish. Power-based TSS correctly counts that as constant effort. Heart-rate-based TSS sees rising intensity and overestimates the session's cost. The longer the ride, the larger the error.
Response lag. Heart rate takes 30 to 90 seconds to respond to a change in effort. During short intervals — 30-second sprints, one-minute VO2max repeats, Tabata efforts — heart rate never catches up to the actual intensity. The result is that hrTSS underestimates the cost of highly variable, short-interval sessions. A set of 30/30 intervals might produce 100 TSS from power data but only 70–80 from heart rate.
The practical advice is simple: use power-based TSS whenever you have it. Use hrTSS for rides where no power data exists — a mountain bike ride on a bike without a power meter, a spin class, a gravel ride on the second bike. Do not mix the two without understanding that the numbers are approximate rather than equivalent.
If you want to set your heart rate zones correctly so that hrTSS at least starts from the right baseline, the HR Zone Calculator will do that from your LTHR or max heart rate.
Using TSS to plan a training week
The real power of TSS is not in post-ride analysis. It is in forward planning. Once you know your weekly TSS budget, your session-level recovery brackets and your available hours, you can design a week before you ride a single metre of it.
Here is a worked example for a 48-year-old masters cyclist with an FTP of 250W, training 9 hours per week and targeting a weekly TSS of 500–550.
| Day | Session | Duration | Target IF | Estimated TSS | |-----|---------|----------|-----------|---------------| | Monday | Rest | — | — | 0 | | Tuesday | VO2max intervals | 1h 15min | 0.88 | 97 | | Wednesday | Zone 2 endurance | 1h 30min | 0.68 | 69 | | Thursday | Sweet spot intervals | 1h 15min | 0.87 | 95 | | Friday | Recovery spin | 45min | 0.55 | 23 | | Saturday | Long endurance ride | 3h | 0.70 | 147 | | Sunday | Tempo with efforts | 1h 45min | 0.80 | 112 | | Total | | 9h 30min | | 543 |
The week has shape. Two intensity days (Tuesday, Thursday), two endurance days (Wednesday, Saturday), one mixed ride (Sunday), one recovery day (Friday) and a full rest day (Monday). No single session exceeds 150 TSS, so every day is recoverable overnight. The intensity distribution is roughly 60% easy, 20% moderate, 20% hard — close to the polarised model that most research supports for endurance development.
The beauty of planning with TSS is that you can adjust on the fly. If Tuesday's session leaves you more fatigued than expected — if the VO2max efforts produced 115 TSS instead of 97 because you went harder than planned — you can drop Wednesday's IF target from 0.68 to 0.60, accept a lower TSS, and protect Thursday's quality session. The week still hits the budget. The distribution still works. But the plan responded to the reality of how the body absorbed the stress.
You can model different scenarios using the TSS Calculator before the ride and the Training Load Calculator afterwards to see how each session affects your CTL, ATL and TSB.
How much TSS can your body absorb?
This is the question behind the question, and the answer is frustratingly individual. But there are useful markers.
The ramp rate ceiling. Your Chronic Training Load (CTL) represents the training stress your body has adapted to over the last six weeks. Increasing weekly TSS faster than your CTL can absorb leads to accumulated fatigue that the recovery between sessions cannot clear. The commonly cited safe ramp rate is five to seven CTL points per week — which translates to increasing weekly TSS by roughly 35–50 per week. For a detailed look at how CTL, ATL and TSB interact, the companion guide to the Performance Management Chart covers the model in depth.
The weekly ceiling. As a rough guide, your sustainable weekly TSS should not exceed your CTL multiplied by about 10–11 during a hard training block (because daily TSS averaged across seven days equals weekly TSS divided by seven, and you want daily averages near your CTL with room for one or two bigger days). During a recovery week, weekly TSS drops to roughly 50–60% of a normal training week.
The monthly pattern. The classic three-weeks-on, one-week-off mesocycle reflects a practical TSS absorption limit. Three weeks of progressive overload — each week slightly harder than the last — followed by a recovery week where volume drops 40–50% and TSS falls accordingly. Masters riders over 50 often respond better to a two-on, one-off pattern, absorbing two hard weeks before the body demands a lighter one. The right pattern depends on training age, recovery capacity and how honestly you assess your own fatigue.
The annual trajectory. Over a full season, CTL follows a planned arc: building through base and build phases, peaking before target events, then backing off during transition. Annual Training Stress — the sum of every day's TSS across 365 days — gives a macro view of total training volume. Year-on-year increases of 10–15% are sustainable for most developing riders. Larger jumps require either significantly more available hours or significantly better recovery practices, and usually both.
TSS and the Performance Management Chart
TSS feeds into the Performance Management Chart — the three-line graph of CTL, ATL and TSB that coaches use to manage fitness, fatigue and form across a season. Every daily TSS value is a data point in the exponential averages that produce those three lines.
This relationship is why an accurate FTP and consistent TSS tracking matter so much. Garbage TSS data — from an outdated FTP, from mixing power and heart rate carelessly, from sporadic uploads — produces a PMC that tells lies about your fitness and fatigue. The model is only as good as the data you feed it.
If you have not read the CTL, ATL and TSB guide yet, that is the natural next step from here. TSS is the raw material. The PMC is the tool that turns raw material into actionable training decisions.
Making TSS work for you
Five practical habits that separate riders who use TSS well from riders who collect numbers they never act on.
Set FTP correctly and update it regularly. Every TSS number downstream depends on this single input. An outdated FTP corrupts every metric that follows. Test every six to eight weeks during a training block, and re-set after any extended break. Use the FTP Test Calculator if you want to estimate from a shorter test protocol.
Track weekly TSS totals, not just session TSS. A single 180 TSS ride tells you about one day. The rolling weekly total tells you about the trend. Plot it in a spreadsheet, track it in TrainingPeaks, or use the Training Load Calculator — the method matters less than the consistency of doing it.
Build your week in advance using TSS targets. Before the week starts, sketch out each session with a target duration, target IF and target TSS. You will not hit them perfectly. You are not supposed to. The point is to have a plan that distributes stress intentionally rather than letting it accumulate randomly. Use the Interval Session Builder to structure the hard days.
Respect the recovery brackets. If a session produces more than 150 TSS, the next day should be easy or off. If it exceeds 300, budget two to three recovery days. These are not signs of weakness. They are the non-negotiable cost of the adaptation you are trying to create.
Pair TSS with subjective data. Rate your fatigue, your sleep quality and your motivation every day, even if it is just a 1-to-5 score in a notebook. When TSS says you should be fine but your body says you are not, the body wins. When TSS says you should be wrecked but you feel sharp, consider whether your FTP needs updating — you might be fitter than the number thinks.
Where TSS fits in the bigger picture
TSS is one metric in a framework, not the framework itself. It quantifies load. It does not measure fitness. It does not predict performance. It does not account for the specificity of what you did, the conditions you did it in, or the state of your body when you started.
What it does — and does well — is give you a common currency for comparing sessions, planning weeks and managing the balance between stress and recovery. That currency is only as good as the exchange rate (your FTP) and the accounting (consistent tracking), but when both are solid, TSS becomes the foundation that every other training decision rests on.
The number at the bottom of your ride summary is not decoration. It is the cost of the work you just did, expressed in terms your body will charge you for over the next 24 to 72 hours. Learn what that cost means, and you stop guessing at recovery. You start planning it.
If you want to connect with other riders who are building structured training around these principles, the Roadman Cycling community on Skool is where those conversations happen — real numbers, real experiences, no hype.