TSS, IF, and Variability Index: Reading Workout Quality Beyond Total Stress
5 min read
Learn how to read TSS, IF, and Variability Index together so you can judge workout quality beyond total stress and choose one clear next training move.
On this page
Photo by Andrey Novik on Unsplash.
TSS shows total load, IF shows intensity, and VI shows how steady the effort was. Read all three before you judge workout quality.
Treat these metrics as signals from one ride, not as a full verdict on fitness. TSS, IF, and VI help you ask whether the work matched the planned session, then choose one clear next step.
Training Stress Score, or TSS, is a single workout load score built from duration and intensity. It helps you compare the size of rides, especially when their goals are broadly alike.
TSS is useful, but it does not tell the whole story. A long steady ride and a jumpy group ride can land near the same load score, while the ride feel and pacing look different.
Use TSS as the quantity check before you ask deeper questions about intensity and pacing. For a wider view of load trends, pair this ride-level score with how CTL, ATL, and TSB work.
Compare TSS mainly across rides with a similar purpose.
Check whether the load fits the day’s plan before judging success.
Do not use TSS alone to grade workout quality.
Look at IF and VI before changing next week’s plan.
TSS starts the read, but it needs IF and VI to show workout quality.
TSS tells you how much work the file reports, not whether the session was well aimed.
Photo by Andrey Novik on Unsplash.
Intensity Factor, or IF, compares normalized power with your FTP. In plain terms, it shows how hard the ride was relative to your current threshold setting.
That threshold setting matters. If FTP is stale or poorly set, IF can make a ride look too easy or too hard, so review threshold data when the number feels wrong.
IF helps you judge whether the session reached the planned intensity. If your field FTP and lab threshold do not line up, use which threshold number to trust before you rewrite zones.
Check IF against the workout’s planned intensity.
Review FTP if several rides feel mismatched to the file.
Do not chase IF when the goal was easy endurance.
Use session notes when the number seems out of place.
IF tells you how hard the session was compared with what your current threshold setting says you can hold.
TSS = total workout stress (volume × intensity). It’s a quantity, not a quality judgement.
Variability Index, or VI, compares normalized power with average power. A lower VI points to steadier riding, while a higher VI points to more surges, coasting, or uneven work.
VI does not say whether uneven pacing was good or bad. Intervals, hills, wind, traffic, and group dynamics can all make power less steady for valid reasons.
Read VI against the workout goal. If the plan called for smooth tempo but the file shows repeated surges, use pacing as the next fix before adding more load.
Use VI to spot surges, coasting, and uneven power.
Compare VI with the route and workout goal.
For steady work, make smoother pacing the first fix.
For intervals, check whether variability was planned.
VI completes the read by showing whether effort was steady or choppy.
VI tells you how the effort was applied, not just how large or hard it was.
The three numbers work best as a pattern. TSS answers how much, IF answers how hard, and VI answers how smooth or uneven the effort was.
A high TSS with low IF often points to a longer, lower-intensity ride. A moderate TSS with strong IF and low VI can fit controlled threshold work, if that was the plan.
A moderate TSS with high IF and high VI often points to surges or interval-style work. Before calling that bad, check whether the ride was meant to be variable.
This is where workout files become coaching signals. Use the trio to match the ride to its aim, then cross-check with power and cycling data basics.
Start with the session goal, not the largest number.
Use TSS to judge size, IF to judge intensity, and VI to judge pacing.
If one number looks odd, check the other two before acting.
Write one note on why the pattern happened.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Training Readiness: Optimize Your Next Session — Use training readiness—HRV, resting HR, sleep, and subjective wellness—to decide when to push and when to rest. Real-time, science-based steps for sm...
- Heart Rate Variability for Cyclists: How to Measure, Interpret, and Use HRV to Guide Training — A practical, science-based guide for cyclists: how HRV works, how to measure it reliably, how to interpret individual patterns, and how to use HRV wi...
- FTP Test Cycling: How to Measure Your Functional Threshold Power Accurately — Learn how to run reliable FTP test cycling protocols (20‑minute, ramp, 2x8/10, critical power), prepare and calibrate your power meter, and validate...
Once the pattern is clear, make one change. Changing volume, intensity, and pacing at the same time makes the next file harder to read.
If TSS ran high but IF stayed low, protect the key work and trim volume for the next week. If IF missed the target while VI was high, repeat the session with tighter pacing.
If IF was on target but VI was much higher than planned, do not add more stress right away. Replace the next hard ride with steadier sub-threshold work, then reassess the next file.
For broader load control, compare these ride-level choices with acute-to-chronic workload tracking and your recent response. Your next move should fit the whole week, not just one workout.
High TSS and low IF: trim volume, keep key intensity.
Low IF and high VI: repeat with smoother pacing.
On-target IF and high VI: choose steady sub-threshold work next.
Only change one lever before the next review.
One clear change keeps the next TSS, IF, and VI pattern easy to read.
The best adjustment is the smallest one that makes the next signal clearer.
Bad inputs can make good logic fail. An old FTP, a poorly zeroed power meter, or the wrong workout label can make TSS, IF, and VI less useful.
Check the setup before you change the plan. If the power file is noisy or the threshold setting is off, the next training choice may be based on a weak signal.
You also need the rider context. Readiness, sleep notes, and recent load help explain why a good-looking file may still feel flat the next day.
If you are returning from time off, avoid chasing the old load too fast. Use a safer CTL rebuild approach to keep the ramp clear and measured.
Check FTP before trusting IF and TSS trends.
Zero or calibrate the power meter as your device requires.
Label the workout goal before reading the file.
Pair numbers with perceived effort and recovery notes.
Day 1 — Baseline hard session: Do the planned hard workout, whether threshold or intervals. Record TSS, IF, and VI, then write two notes on effort and pacing.
Day 2 — Recovery: Ride easy or rest. Note recovery and sleep, and avoid hard efforts that blur the next file.
Day 3 — Controlled repeat: If Day 1 matched the goal, follow the plan. If it missed, repeat a controlled version with the same purpose and smoother pacing.
Days 4–5 — Adjust volume: If the week feels too large, trim the remaining volume while keeping the key quality session intact.
Day 6 — Assessment session: Do a short controlled workout at the planned intensity. Compare the TSS, IF, and VI pattern with Day 1.
Day 7 — Plan reset: Pick one next move for the coming week: trim volume, repeat quality work, or retest threshold if the data keeps disagreeing.
TSS shows total load, IF shows intensity, and VI shows pacing shape. Read the three as one pattern, then make one clear adjustment before the next key workout.
No. TSS helps size the workload, but it does not show whether the ride was steady, surgy, easy, or close to threshold. Add IF and VI before judging quality.
First check your FTP setting and power data. If those inputs are sound, compare IF with session notes and decide whether the workout goal or pacing broke down.
No. A high VI may be expected during intervals, hills, or group riding. It is only a problem when the workout goal called for steady power.
Use the pattern, not one number. If intensity was right but pacing was messy, fix pacing first. If total load was too large, trim volume before changing intensity.