Intensity Factor tells you how hard a cycling session was relative to your FTP. Training Stress Score combines that relative intensity with duration to estimate the session's total training load. Together they make power files easier to compare—but only when FTP and the underlying data are accurate.
One hour at FTP is defined as 100 TSS. Two hours at 70% IF also produces approximately 98 TSS. The scores are similar, but the workouts are not physiologically identical: one is short and hard, the other long and aerobic.
TSS measures estimated load, not training quality, adaptation or readiness. Use it to organise context—not to replace workout purpose, heart rate, perceived effort, sleep, soreness or performance.
Both metrics sit on top of FTP and Normalized Power. Review what FTP means in cycling if the threshold reference is unfamiliar, use the Cycling Power Zones Guide for the complete intensity system and use the Cycling Power Zone Calculator to convert a current FTP into workout targets.
TSS, IF, NP and FTP at a glance
| Metric | What it describes | Basic calculation | Best use |
|---|---|---|---|
| FTP | Your threshold reference in watts | Estimated from an appropriate test or performance | Set zones and scale relative intensity |
| Normalized Power | Estimated cost of a variable power file | Weighted calculation from rolling power | Interpret stochastic rides |
| Intensity Factor | NP relative to your FTP | NP ÷ FTP | Describe session intensity |
| Training Stress Score | Estimated load from intensity and duration | Hours × IF² × 100 | Compare and trend cycling workload |
If the distinction between mechanical mean and weighted power is unclear, read Normalized Power vs Average Power before using IF or TSS.
What is Intensity Factor in cycling?
Intensity Factor® expresses the Normalized Power of a ride or selected segment as a fraction of the rider's Functional Threshold Power.
If a cyclist records 210 watts NP with an FTP of 250 watts, IF is 210 ÷ 250 = 0.84.
IF is individualised. The same 210-watt NP produces an IF of 0.70 for a rider with a 300-watt FTP and 0.93 for a rider with a 225-watt FTP. It therefore describes relative intensity more usefully than watts alone when comparing sessions or riders.
How to interpret IF
| IF | Broad interpretation | Possible session context |
|---|---|---|
| Below 0.55 | Very light | Recovery spin or the easy portions of a ride |
| 0.55–0.75 | Endurance-oriented | Steady aerobic ride or long easy session |
| 0.76–0.90 | Moderate to hard | Tempo, sweet spot or a demanding mixed ride |
| 0.91–1.05 | Very hard | Threshold-focused workout, time trial or short race |
| Above 1.05 | Severe | Short race, hard intervals or an FTP/data problem |
An IF of 0.90 for 30 minutes is not equivalent to 0.90 for three hours. IF describes relative intensity over the selected time range; it does not contain duration. That is why TSS adds time.
What is Training Stress Score?
Training Stress Score® is a composite estimate of cycling workload derived from session duration and relative intensity. The model defines one hour at FTP as 100 TSS. Because intensity is squared, increasing IF raises TSS much faster than simply adding the same percentage of time.
Normalized Power, Intensity Factor and Training Stress Score are trademarks of Peaksware. This guide focuses on power-based cycling TSS. Heart-rate, running and swimming stress scores use different inputs and should not be assumed to have identical accuracy or physiological meaning.
How is cycling TSS calculated?
The full formula is:
Because IF equals NP ÷ FTP, this can be simplified to: duration in hours × IF² × 100.
-
Use the correct ride duration
The selected file or segment determines the time included. Warm-up, cool-down and stopped time can change the result depending on platform behaviour.
-
Calculate Normalized Power
The variable power file is converted into an estimate of equivalent steady physiological cost.
-
Relate NP to FTP
Dividing NP by the current FTP produces IF. A stale threshold distorts both IF and TSS.
-
Combine time and squared intensity
The final score increases linearly with duration but approximately with the square of IF.
TSS calculation examples
| Session | Duration | IF | Calculation | TSS |
|---|---|---|---|---|
| Recovery ride | 45 min | 0.50 | 0.75 × 0.50² × 100 | 19 |
| Endurance ride | 2 hr | 0.70 | 2 × 0.70² × 100 | 98 |
| Sweet spot workout | 75 min | 0.85 | 1.25 × 0.85² × 100 | 90 |
| Threshold hour | 1 hr | 1.00 | 1 × 1.00² × 100 | 100 |
| Long aerobic ride | 4 hr | 0.65 | 4 × 0.65² × 100 | 169 |
| Short hard race | 45 min | 1.05 | 0.75 × 1.05² × 100 | 83 |
The numbers are rounded. Real software calculates NP from the complete power file before applying IF and TSS, so a headline average wattage is not enough to reproduce the score reliably.
Why the same TSS does not mean the same workout
One hour near threshold
At approximately 1.00 IF, the ride scores 100 TSS. The dominant challenge is sustained high aerobic intensity and substantial acute fatigue.
Two hours of endurance
At 0.70 IF, the ride scores about 98 TSS. The dominant challenge is duration, energy availability and aerobic endurance.
The model intentionally creates a common load scale, but it compresses different stimuli into one number. A score cannot tell you whether the session developed threshold power, endurance, VO2 max, race specificity or technical skill. For example, an over-under cycling workout should be judged by the quality of its changes and the ability to settle—not only by its final TSS.
How to use IF correctly
- Confirm whether the IF covers the whole ride, one interval set or one race segment.
- Compare it with the planned intensity and actual duration.
- Use lap average power—not whole-ride IF—to assess steady interval execution.
- Review heart rate and RPE when IF looks unusual.
- Recheck FTP when ordinary sessions repeatedly produce implausible IF values.
An IF above 1.00 can be reasonable for a short race or interval selection. Sustaining it for a long event may point to an underestimated FTP, a calibration issue, a highly anaerobic effort or the limitations of Normalized Power.
How to use TSS correctly
-
Use it to compare cycling workload
TSS can reveal that a long easy ride and a shorter hard ride both created meaningful load even when their duration and watts look very different.
-
Track weekly trends, not isolated trophies
Look for sustainable changes across several weeks. A record weekly score is not automatically productive if consistency collapses afterwards.
-
Keep the workout purpose visible
Label endurance, sweet spot, threshold, VO2 max and race-specific work. Two weeks with the same TSS can contain completely different training.
-
Compare load with response
Add RPE, heart rate, sleep, mood, soreness and performance. External work and internal response are related but not interchangeable.
-
Adjust before fatigue compounds
If power quality, motivation and recovery deteriorate together, reduce training rather than chasing the planned score.
IF and TSS across common cycling workouts
| Workout | What IF helps show | What TSS helps show | What neither shows |
|---|---|---|---|
| Zone 2 ride | Whether the full ride stayed broadly aerobic | How duration accumulated load | Cardiac drift, fueling quality and late-ride durability |
| Sweet spot | Overall session intensity | Workload including recoveries | Whether each interval was even and repeatable |
| VO2 max intervals | A rough whole-session summary | A potentially incomplete estimate of severe work | Time near VO2 max and anaerobic contribution |
| Long group ride | Relative cost of the variable file | Total power-based load | Tactics, technical stress and individual fueling response |
| Triathlon bike rehearsal | Whether intensity matched the race plan | How much bike load preceded the run | Aerodynamics, comfort and actual run readiness |
The main limitations of TSS and IF
They depend on accurate FTP
If FTP is too low, IF and TSS are inflated. If FTP is too high, they are suppressed. Follow one repeatable method using the FTP testing guide, then validate the result in training.
They simplify high-intensity work
Normalized Power and TSS were built primarily around aerobic power-duration relationships. Short sprints and HIIT can create substantial neuromuscular and anaerobic strain without being represented perfectly by a single score.
They cannot measure every stressor
Heat, altitude, illness, poor sleep, dehydration, low carbohydrate availability and life stress can make the same external load feel very different.
They do not know your adaptation
A score describes the session model, not whether you recovered or improved. Training only works when load is absorbed consistently.
They can hide specificity
A threshold session should be judged by the work that solved its training purpose, not only by its final score. Review the planned intervals, recoveries and progression in our threshold cycling workouts guide before comparing sessions by TSS alone.
A high score from unstructured medium-hard riding may be less useful than a lower score from a carefully targeted session. Use the progression principles in How to Improve FTP to connect load with a clear training objective.
TSS vs kilojoules, heart rate and session RPE
| Metric | Measures | Strength | Limitation |
|---|---|---|---|
| Power TSS | Duration and intensity relative to FTP | Individualised, objective power-file estimate | Depends on FTP, NP and the model |
| Kilojoules | External mechanical work | Direct and easy to compare on the bike | Does not account for intensity or fitness |
| Heart-rate load | Cardiovascular response over time | Useful without power and for steady aerobic work | Lagged and affected by heat, fatigue and hydration |
| Session RPE | Duration multiplied by perceived difficulty | Captures the athlete's global response | Subjective and dependent on consistent scoring |
The metrics are complementary. Power describes external output; heart rate and RPE help explain the internal cost. Research on endurance training load supports monitoring both rather than treating one number as complete.
How triathletes should use cycling TSS
Cycling TSS is useful inside a multisport plan because the bike often carries the greatest duration. But the complete week also contains swimming, running and strength. Do not assume 100 cycling TSS, 100 running stress points and 100 swimming points create identical tissue load or recovery needs.
For a worked race application, our Half Ironman bike pacing guide combines expected duration, IF, TSS and run durability instead of applying one FTP percentage to every athlete.
- Keep sport-specific context: tag the discipline and workout purpose.
- Protect key runs: a high bike score matters if it repeatedly ruins planned running quality.
- Use race rehearsals: compare bike IF and TSS with the quality of the following brick run.
- Review the whole week: count hard sessions across all three sports before adding more cycling load.
- Preserve progression: increase workload gradually from what you can already absorb.
How TSS connects to CTL, ATL and TSB
Training platforms use daily stress scores to create longer-term models:
Longer-term load trend
Chronic Training Load is a weighted history of recent training stress and is often labelled fitness. It describes accumulated load, not fitness in every physiological sense.
Shorter-term load trend
Acute Training Load weights recent stress more heavily and is often labelled fatigue. It is a mathematical load estimate, not a direct fatigue measurement.
Difference between trends
Training Stress Balance compares the longer- and shorter-term models and is often labelled form. Read it alongside actual readiness.
A rising CTL is not automatically good, a negative TSB is not automatically dangerous and a positive TSB does not guarantee race readiness. The model becomes useful only when it is reconciled with your performance and recovery.
A practical post-ride workflow
-
Check the power file
Look for dropouts, calibration issues and incorrect device selection.
-
Review the work that mattered
Inspect interval power, duration and pacing before whole-session summary metrics.
-
Read NP and IF
Ask whether the relative intensity matches the session and selected time range.
-
Place TSS in the week
Compare the score with recent workload, the next key session and the workout's purpose.
-
Record your response
Add RPE, heart rate, sleep, soreness and notes so the model can be compared with the athlete.
Common TSS and IF mistakes
Chasing a weekly score
More load is not automatically more progress. The goal is a repeatable sequence of useful sessions, not the largest dashboard number.
Comparing athletes directly
TSS is relative to individual FTP, but different training histories, recovery capacities and power profiles still make direct comparison weak.
Ignoring an outdated FTP
Every downstream score is distorted when the threshold denominator is wrong. Retest when training evidence consistently stops matching the model.
Treating planned TSS as exact
Structured-workout estimates assume execution. Outdoor terrain, coasting, heat and modifications can make actual load different.
Using TSS as a recovery prescription
The same score can produce different fatigue depending on intensity distribution, novelty, fueling, environment and the athlete's current state.
Cycling TSS and Intensity Factor: frequently asked questions
What does 100 TSS mean?
By definition, one hour at FTP equals 100 cycling TSS. Other combinations of duration and intensity can also produce 100, so it does not identify the workout type.
What is a good TSS for a cycling workout?
There is no universal good score. It depends on training history, workout purpose, weekly structure and recovery. Judge the session by whether its load was appropriate and absorbable.
Can TSS be over 100?
Yes. Long rides commonly exceed 100 because duration accumulates load even at moderate IF. A short event can also approach or exceed 100 when intensity is very high.
What is a good Intensity Factor?
A suitable IF matches the purpose and duration. An endurance ride may sit around 0.55–0.75, while threshold work is higher. The same IF becomes more demanding as duration increases.
Why is my IF above 1.0?
It may be appropriate for a short hard effort. For a long ride, review FTP accuracy, power calibration, the selected time range and the limitations of NP.
Does TSS include stopped time?
Platform and file behaviour can differ. Paused recording, elapsed time and selected segments may change duration and NP. Use one platform consistently and verify the time range.
Is TSS better than session RPE?
No single metric is always better. TSS estimates external cycling load from power, while session RPE captures perceived internal difficulty. Together they provide more context.
How often should I update FTP for accurate TSS?
Update it when a repeatable test or clear training evidence supports a change—not simply on a fixed calendar or after one unusually strong ride.
Final takeaway
Intensity Factor and TSS turn a power file into useful relative context. IF describes intensity compared with FTP; TSS combines that intensity with duration. They are strongest for comparing consistent cycling data over time and weakest when treated as complete measures of fatigue, adaptation or workout quality. Keep FTP accurate, inspect the actual work, track internal response and use the score to support—not control—training decisions.
Definitions and equations were checked against TrainingPeaks' official documentation for Intensity Factor, Training Stress Scores and the published power-based TSS formula. Limitations for severe intervals were cross-checked against TrainingPeaks' discussion of TSS and IF during HIIT. The recommendation to combine external and internal load follows an endurance-sport training-load review and the broader distinction between internal and external training load. Cycling-specific context is informed by research comparing multiple training-load measures in professional cyclists, evaluating fatigue and load ratios and assessing training-load methods against fitness and performance in road cyclists. IF bands and workout examples are practical explanatory ranges, not universal prescriptions.
