
Read TSS, IF, and Variability Index together, check the power trace, and compare each ride with its goal before judging workout quality.
On this page

Photo by Jonny Kennaugh on Unsplash.
TSS summarizes workout load; IF and Variability Index add intensity and pacing context. Read them alongside the workout file before judging quality.
Your next move is to check whether the recorded ride matched its purpose before changing the next session. This refresh replaces score-based training prescriptions with a file-review process. The supplied evidence is a PubMed search page, not a specific study validating these metrics or universal cutoffs.
Treat these labels as different views of the recorded ride, with exact definitions checked against your platform’s documentation. They help you frame questions about the session, rather than settle whether it was good or bad.
Training Stress Score, or TSS, is presented as a summary of workout load, not a description of every effort. Ask what contributed to the displayed total, then look at the ride’s duration and the recorded power pattern.
Intensity Factor, or IF, describes session intensity against the reference value used by your platform for that file. Check that reference before comparing sessions, especially when settings or data sources have changed since your previous review.
Variability Index, or VI, describes how evenly power was distributed, rather than whether the workout met its purpose. For a closer look at pacing patterns, use this guide to steady and surge-heavy power traces.
Keep the session view separate from longer planning questions, including how fitness and form differ. Those questions need a wider view than the summary values displayed beside one completed ride.
Check your platform’s definitions before comparing its metrics with another service.
Use TSS to review reported load, not to judge the session alone.
Check the reference setting behind IF.
Use VI as a prompt to inspect the power trace.

Photo by Quino Al on Unsplash.
Consider a hypothetical comparison: your platform reports similar TSS for a steady road ride and a surge-heavy group ride. This example illustrates a reading problem, not evidence that either workout produces a better training result.
The steady ride shows a fairly even power trace, while the group ride shows repeated rises and falls. The shared summary score does not show where those efforts happened or whether they matched the planned session.
If your goal was steady riding, inspect the group ride’s surges before deciding that the session matched your brief. If your goal included changing pace, those same surges may belong in the workout rather than need correcting.
Use a side-by-side ride review to compare the session descriptions and power traces before drawing conclusions from similar totals. Keep your conclusion narrow: describe what the files show, rather than claiming that equal scores mean equal results.
In N+One terms: a summary score is one view of the session, not the whole session.
TSS gives a single summary of workout stress; it does not describe how that stress was distributed.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Start with the planned session, then inspect the recorded duration, route, power trace, and any notes you saved. A steady endurance ride and an interval session ask different questions of the same set of summary metrics.
Check how pauses, coasting, missing samples, and selected recording periods appear in the file before interpreting the summary. Where your platform offers whole-ride and selected-lap views, confirm which view you are comparing with the session plan.
For autumn rides with shorter daylight, note whether a route change or an early finish altered the planned session. Record that practical detail instead of assuming a different score means the workout itself was poorly chosen.
Place the session within the wider load-tracking picture, while keeping file review separate from decisions about your next ride. The supplied source establishes no universal TSS, IF, or VI threshold that proves a session succeeded or failed.
Name the intended session: steady riding, intervals, or variable terrain.
Compare the recorded work blocks with the planned structure.
Check pauses, coasting, recording gaps, and the selected file view.
Note route or schedule changes before interpreting the score.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Rebuilding CTL After a Forced Break Without Triggering Overreaching — Rebuild CTL after illness, travel, or another forced break without overreaching. Keep intensity controlled, reduce volume, and use recovery markers t...
- ATL Spikes After Camp Weeks: Soft-Landing Your Return to Normal Volume — After a camp week, ATL can spike. Use this seven-day soft landing: keep one intensity touch, cut volume, track recovery, and rebuild only when ready.
- Cranioadaptive Load Cycling: A Practical Interpretation — Interpret cranioadaptive load cycling and map it to CTL/ATL principles for adaptive load periodization and training load adaptation.
The first mistake is ranking workouts by TSS alone, without checking what each session was meant to include. A larger displayed total does not, by itself, show a closer match to your planned workout.
The second mistake is treating smooth power as the goal for every ride, regardless of the planned structure. Repeated changes in power may be part of the brief, so inspect their timing before calling them unwanted.
The third mistake is changing your next session from one unusual number before checking the underlying file and settings. First establish what changed in the recording, then decide whether that finding calls for a training change.
These metrics also leave personal context outside the file, so keep your ride notes alongside the numbers you review. If your concern extends beyond pacing, use a broader review of accumulating fatigue rather than treating a single score as a diagnosis.
Write the session goal before opening the summary panel, so the largest number does not set the agenda. Then choose the question you need answered: reported load, relative intensity, or the pattern of power across the ride.
Read the relevant metric and inspect the trace together, noting where the recorded session matched or departed from your intention. Compare with similar sessions where possible, and note any differences in route, duration, settings, or recording method.
Finish with one observation that you can check next time, rather than a broad verdict about your fitness. For example, record that planned steady riding became stop-start on a busy route, then choose a clearer route next time.
If the file leaves the cause unclear, write that uncertainty down instead of filling the gap with a training prescription. Your review is complete when it identifies what happened and the next detail you need to check.
Write down the workout goal before reviewing the numbers.
Choose the metric that best matches your question.
Check the power trace behind the summary value.
Record one observation and one clear next check.
Name the goal. Use the planned session description to state what the ride was meant to include.
Select the relevant metric. Review TSS, IF, or VI according to your question, checking platform definitions where needed.
Inspect the file. Compare the summary with the power pattern, planned work blocks, pauses, and recording gaps.
Record one observation. Note what the file shows and what remains unclear before changing your next session.
TSS summarizes workout load; IF and Variability Index add context about intensity and pacing. Judge the match between your goal and the recorded session, not the score alone. If you want day-to-day guidance without second-guessing, let N+One translate your latest training and recovery context into one clear next decision.
You can compare the reported totals, but do not assume that similar totals describe similar workouts. Check platform definitions, reference settings, duration, and power patterns before deciding what the comparison means.
No. Read VI against the session goal and recorded power trace. A changing power pattern may match planned intervals, while the same pattern may depart from a steady-riding brief.
Check the reference value, selected recording period, and underlying power file before changing your training. If the cause remains unclear, record the uncertainty rather than treating the value as proof of a performance change.