Triathlon Brick Run Test: Measuring Cadence Collapse in the First Kilometer Off the Bike

You rack the bike, rip off the helmet, and start running - and your legs answer with something between a shuffle and a stagger. Splits confirm what the body already knows: the first kilometer is 20-30 seconds slower per kilometer than your open 5K pace, cadence sits noticeably low, and it takes what feels like forever before the stride starts looking like running again instead of a controlled fall forward. Most athletes chalk this up to just how brick runs feel and move on. Some of that is normal physiology. But the size of the collapse - how far cadence and pace drop, and how long they take to recover - varies enormously between two athletes with identical open-run fitness, and that variance is exactly what a standalone run test can't see.

This guide sets up a specific test: measuring cadence and pace decay in the first kilometer after dismounting, benchmarked against the same athlete's settled pace a few minutes later. It's built to isolate transition conditioning as its own trainable quality, separate from bike fitness and separate from run fitness, using two numbers - a cadence-collapse percentage and a recovery distance - that a stopwatch and a footpod can capture without a lab.

A fresh-legs 5K time trial tells you how fast an athlete can run when the neuromuscular system starts from zero fatigue. It says nothing about what happens when that same system has spent the last 60-180 minutes producing force through a completely different movement pattern - fixed cadence, seated hip angle, minimal eccentric loading through the calf and Achilles - and then has roughly 45 seconds to reorganize into an entirely different one. Two triathletes can run identical open 5Ks and still diverge by 15+ seconds per kilometer on the first kilometer off the bike, because the gap isn't about aerobic capacity or running economy at rest. It's about how quickly the nervous system re-establishes an efficient stride pattern once the demand changes.

Coaches who only test the run in isolation end up prescribing more running to an athlete whose actual limiter is the transition itself - and the athlete keeps hitting solid open-run splits in training while racing to a flat, shuffling first kilometer every single event. The Off-Bike Cadence-Collapse Test exists to catch that mismatch before race day does, using the same kind of stride-rate and pace data most triathletes already generate on a GPS watch or running pod, just captured and compared in a specific, repeatable way.

Run this as a standalone session or tacked onto a normal brick day, ideally once every 3-4 weeks so the trend line means something. The bike portion needs to mimic race-specific fatigue, not just get the legs a little tired - a short, easy spin before running defeats the purpose entirely.

Two numbers come out of this. The Cadence-Collapse Index (CCI) is the percentage drop between average cadence in the first 1 km and the reference split: (Reference cadence - First-km cadence) / Reference cadence x 100. The Recovery Distance is simply how far into the run (in meters) cadence first comes within 3% of the reference value and stays there for at least 400m. An athlete who opens at 158 spm and settles at 172 spm by km 3 posts a CCI of about 8.1%; if that recovery happens by the 900m mark, recovery distance is 900m.

Run the identical protocol - same bike duration/effort, same transition time target, same run distance - every time you retest, and log outdoor temperature and course profile too, since a downhill-heavy first kilometer will flatter cadence numbers regardless of transition fitness.

The physiological basis for testing this transition separately from either discipline in isolation is well established, even if the specific cadence-collapse framing here is a practical adaptation of that research rather than a lab-validated instrument itself. Millet and Vleck's widely cited 2000 review in the British Journal of Sports Medicine synthesized cycle-to-run transition studies and reported that running economy is measurably impaired for several minutes after cycling - commonly a 3-6% increase in oxygen cost at a given running speed compared with an isolated run - alongside kinematic shifts including altered stride pattern and reduced hip extension during early stance. The review's central limitation is one of synthesis rather than a single dataset: the underlying studies vary in cycling duration, intensity, and athlete caliber, so the exact magnitude and duration of the economy penalty differs across the literature it draws from rather than converging on one number.

More directly relevant to cadence specifically, Bernard and colleagues (2003, British Journal of Sports Medicine) had well-trained triathletes cycle for 30 minutes at three different pedaling cadences - 60, 80, and 100 rpm - at matched power output, then immediately run a 3 km time trial. Running velocity after the 100 rpm bout was significantly slower than after the 60 rpm bout, with the low-cadence condition producing roughly a 3-4% faster subsequent run time despite identical bike power output across conditions. The authors attributed the effect to differences in muscle fiber recruitment pattern carried over from the bike leg - high cadence cycling recruiting relatively more fast-twitch fiber activity, which appears to interfere more with the neuromuscular reorganization running demands immediately afterward. The obvious caveat: the study used a fixed, prescribed cadence rather than each athlete's freely chosen race cadence, and the sample was small and drawn from trained-but-not-elite triathletes, so the exact percentages shouldn't be read as a universal target - but the direction of the effect (bike cadence choice measurably changes off-bike running output) is the key takeaway a cadence-collapse test is built to detect at the individual level.

A CCI in isolation doesn't diagnose anything - it needs to be read alongside recovery distance, since a moderate collapse that resolves fast is a different problem than a small collapse that never fully resolves.

An athlete posting a strong open-5K time but landing in the bottom two rows here is a common and specific pattern: their aerobic and muscular running capacity is fine, but the bike-to-run reorganization itself is the bottleneck. That's a training prescription issue, not a fitness issue, and it responds to a different stimulus than adding more mileage.

The most common corruption of this test is an under-cooked bike leg. Fifteen easy minutes on the trainer before a run test won't produce anything close to race-specific fatigue, and the resulting CCI will look artificially clean - flattering a transition weakness that shows up brutally on race day once the bike leg is actually hard. The bike segment has to hurt in a race-representative way for the numbers to mean anything.

• Testing on a course with a downhill or tailwind-favored opening kilometer, which inflates early pace and cadence independent of true transition fitness - always retest on comparable terrain.
• Comparing CCI across athletes rather than tracking one athlete's trend over time; individual stride mechanics and habitual cadence vary enough that cross-athlete comparison is close to meaningless.
• Ignoring transition time itself - a rushed 40-second transition and a relaxed 3-minute one produce different starting states for the run, so hold transition duration constant between tests or the CCI stops being comparable.
• Treating one session as diagnostic. Heat, bike-fit changes, hydration status, and simple day-to-day variability can shift CCI by several points; three or four tests across a training block are what actually show a trend.

None of these require special equipment to control - just the same discipline that makes any repeated-measure fitness test worth trusting in the first place.

A high CCI responds to brick-specific practice far more than it responds to isolated bike or run volume, because the deficit lives specifically in the transition between the two movement patterns rather than in either discipline's raw capacity. Short, frequent bricks - even 20 minutes of bike followed immediately by 10-15 minutes of run, done weekly - build the neuromuscular transition far more efficiently than the occasional long brick session most age-group athletes default to once a month. The final 10-15 minutes of the bike segment in any brick session matter more than the total bike volume: cadence and effort in that window should mirror actual race pacing, since that's the state the legs carry into the transition.

Cadence discipline late in the bike leg is also worth coaching directly given the Bernard et al. findings above - an athlete who drifts toward a low, grinding cadence in the final race-pace kilometers of the bike, rather than their habitual cruising cadence, may see a measurably cleaner run off the back of it, though this is worth testing individually rather than assumed as universal. For athletes managing the interference between bike-specific strength work and run economy more broadly, our concurrent power and endurance training guide covers how to sequence that work across a week without one discipline eroding the other, and our guide on finding critical velocity from field time trials is useful for setting the standalone-run pacing benchmark this test compares against. Retest the CCI every 3-4 weeks through a build phase; a shrinking index and shortening recovery distance are the signal that brick-specific work is closing the gap, independent of what's happening to open 5K time on its own.