Training

Data-Driven Triathlon Training: Which Metrics Matter and How to Use Them

How to use training data in triathlon without drowning in it: the few metrics worth tracking in each sport (power, heart rate, pace, CSS), how TSS, CTL, ATL and TSB work with a worked example, a 10-minute weekly review, how to spot bad data, how to use HRV and sleep, the common traps, and what to track at each level from beginner to long-distance athlete.

By

14 min read 13 sectionsUpdated November 21, 2026

Training data helps triathletes most when it answers a few specific questions: am I training at the right intensity, is my load building steadily, and am I recovering? For most athletes that means tracking duration and effort in every session, power on the bike if you have it, pace and heart rate on the run, and pace per 100 m in the pool. Training Stress Score (TSS) combines duration and intensity; one hour at threshold scores 100. Fitness (CTL, a 42-day average), fatigue (ATL, a 7-day average) and form (TSB, the difference) turn those scores into trends. Use them alongside how you feel, check data quality before acting on a surprise, and change the plan based on trends, not single numbers.

Key takeaways

  • 1Use data to answer three questions: right intensity, steady load and good recovery.
  • 2Track duration and RPE everywhere, power or heart rate on the bike, pace and heart rate on the run and pace per 100 m in the pool.
  • 3TSS is hours times IF squared times 100; CTL, ATL and TSB turn it into fitness, fatigue and form trends.
  • 4Check sensors, settings and conditions before acting on a surprising number.
  • 5Review weekly and choose to keep, adjust or progress; symptoms always outrank scores.

Why data helps, and where it stops helping

A modern triathlete can record more numbers than any coach could have dreamed of a generation ago: power, heart rate, pace, cadence, stroke counts, sleep scores, heart-rate variability, training load and "readiness". Used well, that data answers useful questions. Used badly, it creates anxiety, encourages chasing scores and replaces judgement with a dashboard.

Good training data helps with three questions:

  1. Am I training at the right intensity? Easy sessions should be easy and hard sessions hard. Data is the best way to keep easy days honest.
  2. Is my training load building steadily? Sudden jumps in load are a common cause of injury and illness, and steady progression is how fitness grows.
  3. Am I recovering? Trends in performance, heart rate and how you feel tell you when to back off.

If a metric does not help answer one of these, you can probably ignore it. This guide explains which metrics are worth tracking, how the most common load model works, how to review your data each week and how to avoid the common traps. For the details of each metric, follow the links to our specific guides.

The metrics worth tracking in each sport

Every session: duration and RPE. Rating of perceived exertion (RPE) on a 1 to 10 scale, recorded after every session, is free, works for every sport and is surprisingly reliable. Multiply duration in minutes by RPE and you get "session RPE load", a simple load measure that works even without any devices.

Bike: power, then heart rate. A power meter measures what you are actually doing, regardless of wind, hills or fatigue, which makes it the most useful single device in triathlon training. Your functional threshold power (FTP) anchors your training zones. Our guides to power meters and the FTP test explain both, and the FTP calculator turns a test result into zones. Without a power meter, heart rate and RPE work well.

Run: pace and heart rate. Pace on flat ground tells you what you are doing; heart rate tells you how hard your body is working to do it. Each misleads on its own: pace on hills and in heat, heart rate in the first few minutes and on hot days. Use them together. Threshold pace or threshold heart rate, from a 30-minute test or a recent race, anchors your zones.

Swim: pace per 100 m. Your critical swim speed (CSS) is a good swim threshold. Swim a 400 m and a 200 m time trial; CSS pace per 100 m is the 400 m time minus the 200 m time, divided by two. For example, 8:00 for 400 m and 3:40 for 200 m gives (480 − 220) ÷ 2 = 130 seconds, or 2:10 per 100 m. Heart rate is less useful in the water, because wrist sensors struggle there and swimming heart rates run lower than on land.

Recovery: sleep, morning heart rate or HRV, and how you feel. These help you decide when to back off. We cover them below.

Zones in brief

Training zones turn your threshold into ranges for easy, steady and hard work. Different systems use five, six or seven zones, but the principle is the same: most training should be easy, with a smaller amount at threshold and above.

Many endurance athletes follow roughly an 80/20 split by time, with about 80 per cent at easy intensity and 20 per cent at moderate to hard. It is a useful rule of thumb rather than a precise target, and the right mix depends on your race distance and experience. Data makes this easy to check: look at your time in each zone over a few weeks.

Our guides to heart rate zones and heart rate vs power zones explain how to set them, and the training zone calculator does the arithmetic.

Our training zone calculator sets matching heart-rate, power, run-pace and CSS swim zones from your test results in one table.

How TSS and intensity factor work

Training Stress Score (TSS), developed for the TrainingPeaks platform, combines how long and how hard a session was into one number. The definition is simple: one hour at your threshold scores 100 TSS.

Two other numbers feed into it:

  • Normalised power (NP) is an adjusted average power that accounts for the extra cost of surges. A ride with lots of hard efforts has a higher NP than average power.
  • Intensity factor (IF) is NP divided by FTP. An IF of 0.75 means you rode at 75 per cent of threshold.

TSS is then hours multiplied by IF squared, multiplied by 100.

Worked example: your FTP is 200 watts. You ride for 90 minutes with a normalised power of 150 watts. IF = 150 ÷ 200 = 0.75. TSS = 1.5 × 0.75 × 0.75 × 100 = about 84. A 60-minute ride at 180 watts NP (IF 0.9) would score 81: shorter but harder sessions can score the same as longer easy ones.

For running, the same idea uses threshold pace (often called rTSS). For swimming, it uses CSS or threshold swim pace (sTSS). Without power or pace, many platforms estimate load from heart rate (hrTSS). These versions are not perfectly comparable with each other, so a run TSS of 80 does not necessarily feel the same as a bike TSS of 80, and running usually causes more muscle damage for the same score.

TSS depends entirely on your threshold being accurate. If your FTP is set too low, every session looks harder than it was. Retest every 6 to 8 weeks, or when you notice your zones no longer match how sessions feel.

Fitness, fatigue and form: CTL, ATL and TSB

TrainingPeaks and similar platforms turn daily TSS into three trend lines:

  • Chronic training load (CTL), often labelled "fitness", is an exponentially weighted average of daily TSS over about 42 days. It rises slowly when you train consistently and falls slowly when you stop.
  • Acute training load (ATL), labelled "fatigue", is the same average over about 7 days. It rises and falls quickly.
  • Training stress balance (TSB), labelled "form", is CTL minus ATL. It is negative when you are training hard and becomes positive when you rest.

These are useful for planning. A steady rise in CTL shows consistent training. A sharp jump in ATL shows a big week, and if it is far above CTL for long, you are piling on fatigue. A taper aims to let TSB rise into slightly positive territory by race day while losing as little CTL as possible.

Some practical guidelines that many coaches use:

  • Build CTL gradually. Increases of a few points a week are sustainable for most age-groupers; large jumps week after week usually end in illness, injury or a forced rest.
  • Watch long negative TSB. Being well below zero during a hard block is normal; staying there for weeks without a lighter week is a warning sign.
  • Do not chase a CTL number. A high CTL built with too much intensity or poor sleep is not the same fitness as one built steadily.

Remember that these are models. They do not know about your work stress, your sleep or the cold you are fighting. They are a starting point for a decision, not the decision.

A 10-minute weekly review

Most of the value of data comes from looking at it regularly and calmly, not from checking it after every session. Once a week, spend 10 minutes on these questions:

  1. Did I do the planned sessions? Note what was missed and why.
  2. Were easy sessions actually easy? Check heart rate or power on easy days. If they crept up, slow down next week.
  3. Did the key sessions go as expected? Compare power, pace or heart rate with the same session a few weeks ago.
  4. How is load trending? Look at weekly TSS or session RPE load and CTL. Is it rising steadily, flat or jumping around?
  5. How do I feel? Sleep, soreness, mood, motivation, resting heart rate or HRV trend.

Then choose one of three actions for next week: keep the plan as written, adjust it (for example, swap a hard session for an easy one or add a rest day), or progress it (add a little volume or intensity). Write the decision down. Over a season, these notes become more valuable than any chart.

Spotting bad data before you act on it

A surprising number shows up: a heart rate 20 beats higher than usual, a pace that makes no sense, a power figure far above your best. Before changing your plan, check the data in this order:

  1. The sensor. Wrist heart rate is often unreliable during intervals, in the cold and in water. Chest straps can spike when dry at the start of a session. Power meters need calibration (a zero offset) before rides.
  2. The settings. Is the right threshold set? Did a software update or a new device change how a metric is calculated?
  3. The conditions. Heat raises heart rate. Wind, hills and surfaces change pace. Altitude affects everything.
  4. You. Poor sleep, stress, illness, caffeine and dehydration all change heart rate and how hard a session feels.

Only if the sensor, settings and conditions check out should a number change your plan. Even then, one session is not a trend. Our guide to aerobic decoupling shows a useful way to compare heart rate and output across a long session.

HRV, sleep and readiness scores

Heart-rate variability (HRV) is the variation in time between heartbeats. Higher HRV relative to your own baseline generally reflects a more recovered state, while a drop below your normal range can reflect fatigue, illness, poor sleep, alcohol or stress. Many watches and apps now measure it overnight or with a short morning reading.

Research has tested adjusting endurance training from daily HRV readings, including in recreational runners. Those studies suggest HRV-guided training can be at least as effective as a fixed plan for some athletes, but they do not show it works for everyone or replaces common sense. If you use HRV, measure it the same way every day, look at the trend against your rolling baseline rather than single readings, and combine it with how you feel. Our HRV guide explains the details.

Sleep matters more than any metric. A 2021 expert consensus on sleep in athletes recommends treating sleep as part of training and recovery, and notes that many athletes sleep less than they need. If your device tracks sleep, the useful information is usually the trend in total sleep time and regularity, not a nightly score. Our sleep and recovery guide covers practical steps.

"Readiness" or "body battery" scores combine several of these inputs using the manufacturer's own formula. They can be a helpful nudge, but treat them as a summary of other data, not as an instruction. If your watch says you are ready but you feel unwell, rest. Symptoms always outrank scores.

The common traps

Chasing numbers on easy days. Pushing an easy ride to keep average power or speed respectable is the most common mistake. Easy days build the aerobic base and allow the hard days to be hard.

Treating one bad session as a trend. Everyone has off days. Look at three or four sessions before concluding anything.

Comparing unlike sessions. A run on a hilly route in heat is not comparable with a flat run on a cool morning. Compare repeatable sessions: the same route, the same indoor workout or a regular test.

Using an old threshold. If your FTP or threshold pace is months old, your zones and TSS are wrong. Retest.

Comparing across platforms or devices. Different apps calculate load, readiness and even normalised power differently. A new watch can change your numbers without any change in fitness.

Sharing everything. Public activity feeds can push you to race your training. Consider making some sessions private, and check that your start and end locations are hidden from strangers.

What to track at each level

Beginners: duration, RPE and a weekly total. If you have a heart-rate monitor, use it to keep easy sessions easy. That is enough. Our 12-week sprint plan uses only a simple effort scale.

Improvers and Olympic-distance athletes: add zones based on a threshold test in each sport, and a weekly review of time in each zone and total load. A power meter becomes worth considering if you want structured bike training.

Long-distance athletes: add a load model (TSS and CTL, or session RPE load), regular threshold testing, and in long sessions, pacing and fuelling data such as normalised power, heart-rate drift and carbohydrate per hour. Use it to plan build and recovery weeks and to test race pacing in long rehearsal sessions.

At every level, keep a short training diary with how you felt. Many experienced coaches say the notes column is the most useful part of a training log.

A worked example: making a decision with data

Here is how the weekly review might work in practice. An athlete training for a 70.3 notices that their Thursday threshold run felt much harder than usual: heart rate was 8 beats higher at the same pace, and RPE was 8 instead of 6.

They check the data in order. The chest strap was worn correctly, and the route was the usual flat loop. But it was much warmer than the previous weeks, and their sleep data shows three short nights because of a work deadline. CTL has risen steadily, but ATL jumped after a big weekend, and TSB is lower than at any point this block.

Decision: adjust. They swap Saturday's long ride intervals for an easy endurance ride, protect their sleep, and repeat the threshold run the following week in cooler conditions. The next week, heart rate at that pace is back to normal. The data did not tell them what to do, but it helped them understand why the session felt hard and avoid an unnecessary change of plan.

Using data on race day

Data is most useful in a race on the bike, where steady effort pays off on the run. Many athletes set an intensity factor target that falls as the race gets longer: higher for a sprint or Olympic, lower for a 70.3 and lower again for a full distance. Your own long rehearsal sessions are the best guide to the right number. Watch normalised power and avoid big surges on climbs and out of corners.

On the run, start by effort and heart rate rather than pace, especially in heat, then let pace come in the second half. In the swim, data is mostly for afterwards: your watch's distance can be off in open water because GPS loses signal under water.

After the race, compare your splits, heart rate and power with your plan. That review is often the most valuable data session of the season, because it shows what your training did and did not prepare you for.

Choosing devices and platforms

You do not need every device. In rough order of usefulness for most triathletes:

  1. A sports watch with GPS for run and open-water pace, and pool lengths. Our watch comparison by use case helps you choose.
  2. A chest-strap heart-rate monitor for accurate heart rate, especially for intervals.
  3. A power meter for structured bike training, or a smart trainer that measures power indoors.
  4. A bike computer if you prefer a larger screen on the bike. See our bike computer guide.
  5. A training platform that brings everything together, calculates load and lets you plan.

Buy the device that answers the question you actually have, and learn to use it well before adding another.

What to track in each sport

SportMain intensity measureThreshold anchorUseful extras
SwimPace per 100 mCritical swim speed (CSS) from a 400 m and 200 m testStroke rate, rest intervals, session RPE
BikePower (watts); heart rate if no power meterFunctional threshold power (FTP)Normalised power, cadence, heart-rate drift
RunPace and heart rateThreshold pace or threshold heart rateCadence, terrain, temperature
All sportsSession RPE (1 to 10) and durationn/aSleep, morning HRV, soreness, mood

Sources

Sources are listed so readers can verify consequential claims and dated details.

  1. Training Stress Scores (TSS) explained — TrainingPeaks (accessed September 30, 2026)
  2. Intensity Factor (IF) explained — TrainingPeaks (accessed September 30, 2026)
  3. Sleep and the athlete: narrative review and 2021 expert consensus recommendations — British Journal of Sports Medicine / PubMed (accessed September 30, 2026)
  4. Individual endurance training prescription with heart rate variability — Medicine and Science in Sports and Exercise / PubMed (accessed September 30, 2026)
  5. Individualized endurance training based on recovery and training status in recreational runners — PubMed (accessed September 30, 2026)

Frequently asked questions

Which metrics should a triathlete track?

Duration and RPE for every session, power on the bike if you have a power meter, pace and heart rate on the run, and pace per 100 m in the pool. Add sleep and a morning heart rate or HRV trend for recovery. Most other metrics are optional.

What does TSS mean in triathlon training?

Training Stress Score combines duration and intensity into one number. One hour at threshold scores 100. It is calculated as hours multiplied by intensity factor squared, multiplied by 100, and has versions for running (rTSS), swimming (sTSS) and heart rate (hrTSS).

What are CTL, ATL and TSB?

CTL (fitness) is a roughly 42-day weighted average of daily TSS, ATL (fatigue) is a roughly 7-day average, and TSB (form) is CTL minus ATL. TSB is negative during hard training and rises during a taper.

Can HRV tell me whether I should train today?

It can help when you compare a consistent daily reading with your own baseline, but it should be combined with how you feel, your sleep and your plan. A single low reading is not a reason to panic, and symptoms always outrank a score.

Why did my training score change after I changed devices?

Different devices and platforms measure and calculate metrics differently. A new power meter, heart-rate sensor or app can shift your numbers without any change in fitness. Retest your thresholds after changing equipment.

Do I need a power meter for triathlon training?

No. Many athletes train well with heart rate and RPE. A power meter is most useful for structured bike training and pacing long races, and is worth considering once you train regularly with a specific goal.

Should I train through symptoms if my watch says I am ready?

No. Pain, illness, chest symptoms or unusual fatigue override any readiness score. Rest, and get medical advice if symptoms are severe or persist.

One practical triathlon decision each week

A useful decision, tool, checklist, or evidence-backed update for your next training block or race.

No spam. Unsubscribe anytime.