Your threshold is the hardest effort you can sustain for roughly an hour — expressed as swim pace, bike power, or run pace. In physiology it sits near the upper edge of steady aerobic work: breathing is heavy, lactate is rising, but you are still in control. Structured field tests turn that capacity into a number you can train and race against.
In triathlon you track three of them: CSS (Critical Swim Speed) for the swim, FTP (Functional Threshold Power) for the bike, and FT (Functional Threshold pace) for the run.
Most athletes already know that. The friction is practical: tests get skipped, results live in different apps or old notes, and it is hard to remember when you last swam a CSS set or rode an FTP block. After a race, few people line up their splits against the thresholds they thought they had going in. Without a current number in one place, zones drift, sessions target the wrong effort, and the simulator plans for fitness you no longer have.
WattX stores CSS, FTP, and FT in your profile — from threshold testing or, when the day is clean, from the race vault. One profile carries those numbers into the generator, plan, nutrition tool, and race tools so you are not re-typing them every time something updates.
Thresholds move. They climb after a productive build, slip when you are fatigued, ill, or under-recovered, and shift when life or sport emphasis changes. Testing is how you capture where your thresholds sit now; consistent training is how you move them up over time. Retest often enough that the data matches the athlete you are this month, not last season.
When I built the first coaching spreadsheet for my wife’s Ironman block, she was already an experienced triathlete — the point was a plan she could follow without drifting into the overtraining mistakes I had made on my own path. The thresholds in that sheet had to be honest; everything else hung off them. WattX is the same idea at platform scale: test, log once, let the rest of the tools read the same numbers.
Below: how those thresholds connect across WattX, when a race beats a Tuesday test, the three thresholds triathletes measure, and each protocol on threshold testing.
The stack
How WattX uses your thresholds
Z1–Z5 bands as % of CSS, FTP, and FT across swim, bike, run.
Generator targets from recovery through speed.
Simulator splits — % CSS, FTP, FT on race day.
Training plan load and fuelling targets (70.3 & full).
See training zones and workout structure for how those pieces differ.
Retest every 4–8 weeks — or after a camp, illness, or a race that truly reflects fitness — so your profile matches the athlete you are today, not the one you were last quarter.
In the session generator, Threshold is a workout intensity band aimed near this effort — separate from the swim, bike, and run numbers you test here.
Log swim, bike, and run threshold tests on threshold testing. Each result is dated in your profile — so you can see when you last tested — and syncs to the generator, simulator, nutrition tool, and plan without re-entering CSS, FTP, or FT.
From racing
When a race is your best threshold read
A clean race is often the truest reflection of your thresholds — more useful than a number you guessed months ago and never checked against a real result. You are tapered, fuelled, and racing at real intensity over full swim, bike, and run legs — conditions a Tuesday evening test rarely matches. Treat the result as a threshold signal when it represents your fitness, not when the day was hijacked by a mechanical, crash, extreme weather, GI failure, or a pacing mistake you would not repeat.
Log the race in the race vault. Race analysis compares your splits to the race pacing targets for your distance and to the CSS, FTP, and FT already in your profile.
When your splits and stored thresholds do not line up, WattX shows what probably happened — a swim faster than your CSS, an overcooked bike, an underestimated FTP, and the like — and can suggest proposed threshold updates from the race.
You choose what to accept. Sync updates your profile (marked race-sourced) so zones, the session generator, simulator, and plan all use the same numbers.
Threshold testing between races is still worth it for a controlled check; racing proves fitness, testing rehearses it.
Three thresholds
Triathlon's three thresholds
One sport, three disciplines — each needs its own test.
Pace per 100 m
Sustainable pool pace — drives swim zones and generator targets.
Watts
~1 h sustainable power — bike zones and power targets.
Min/km or min/mi
~50–60 min pace — run zones and simulator run targets.
Swim test
How to test swim threshold (CSS)
CSS is your theoretical sustainable pace in the pool — expressed as time per 100 m.
The 400 m / 200 m protocol
Warm up 400 m easy, rest 5 minutes.
Swim 400 m time trial — full effort.
Rest 5 minutes.
Swim 200 m time trial — empty the tank.
Formula: CSS (seconds per 100 m) = (400 m time − 200 m time) ÷ 2
Example: 6:40 (400 s) and 3:00 (180 s) → (400 − 180) ÷ 2 = 110 s/100 m (1:50/100 m).
A single all-out swim measures top-end speed, not aerobic threshold. The dual-distance test subtracts anaerobic contribution — the same math WattX applies when you log results on threshold testing.
When to retest CSS
Every 4–6 weeks; swim fitness often shifts faster than bike or run.
Bike test
How to test bike threshold (FTP)
FTP is the maximum average power you can sustain for roughly one hour. WattX uses shorter protocols that are easier to pace and repeat than a full-hour effort.
Choose 2×8 min time trials (average of both intervals × 90%) or a step ramp (75% of peak 1-minute power) on threshold testing. You can launch a structured prep ride from the same screen.
Warm up, then two 8-minute blocks at the highest steady power you can hold — full recovery between. FTP = 90% of average watts across both.
Example: 250 W + 245 W → avg 247.5 W → FTP ≈ 223 W.
Increase target power every minute until failure. Log peak 1-min power; WattX sets FTP at 75% of that peak.
When to retest FTP
Every 6–8 weeks in a build block, or after a significant fitness event — camp, illness recovery, or a big taper.
Run test
How to test run threshold (FT)
FT is the run pace you could hold for roughly 50–60 minutes — strong 10K to half-marathon territory.
On threshold testing, pick one run protocol: 20-minute time trial, Cooper 12-minute, or treadmill ramp (0.5 km/h per minute at 1% grade until failure).
After warm-up, run 20 minutes evenly hard on flat ground. Average pace = FT.
Run as far as possible in exactly 12 minutes. Log distance; WattX calculates FT.
+0.5 km/h each minute at 1% grade until failure. FT = 82% of peak speed.
Post-race calibration
A standalone 10K or half marathon can inform run fitness; a full triathlon is better handled through the race vault so swim and bike thresholds are judged in context — see When a race is your best threshold read above.
When to retest FT
Every 6–8 weeks, or after a key race that reflects true run fitness.
Schedule
Schedule your tests
Spread the three disciplines across 3–5 days — never stack maximal swim, bike, and run tests in one session. A simple order: swim, then bike, then run on separate days.
Log field tests on threshold testing.
Confirm zones feel right on easy and quality days.
Build sessions in the session generator with updated thresholds.
Model race day in the race simulator.
When thresholds move, your training and race models move with them. Test often enough to notice — and keep the last result somewhere you will actually use.