Most brick sessions are random. The research is specific.
A 30-minute jog after a long ride at whatever pace you feel is not a brick workout. It’s a cool-down. The distinction matters because the physiological deficit you’re trying to train is precise, measurable, and won’t respond to vague stimuli.
The Transition Deficit: 4–11% Slower in the First Kilometer
When you run off the bike, you’re slower than your fitness suggests you should be. The range spans 4–11%, depending on how much brick-specific training you’ve done. Athletes with no brick training experience the full deficit. Those with consistent, race-matched sessions can reduce it to 1–5%.
Weich et al. (2022) quantified the transition more precisely than any previous study. Using an “attractor method” to identify when running coordination normalized, they found that 82% of triathletes experience a transient uncoordinated phase after cycling. That phase averages 679 meters — compared to 294 meters in a fresh isolated run. The commonly recommended “5-minute shakeout jog” ends around 500–600 meters at most race paces. For 82% of athletes, that’s before the motor pattern has even normalized.
The rubber-leg feeling isn’t weakness. It’s your gait waking up after cycling rewired its motor pattern for 90 minutes. Cycling is hip-dominant, horizontal, and rhythmically locked to a fixed cadence. Running is ankle-driven, upright, and ballistic. The nervous system needs time to switch modes, and brick training shortens that switching time.
Knechtle et al. (2025), analyzing 687,696 IRONMAN finishers, found run split correlates with finish time at r = 0.89–0.90, stronger than cycling (r = 0.88–0.89) and far stronger than swimming. Protecting run quality off the bike is the highest-payoff adaptation in the sport.
What Cycling Does to Running Mechanics
The mechanical disruption is more serious than most athletes realize. Bonacci et al. (2010) found 46% of moderately trained triathletes show altered muscle recruitment after 45 min of high-intensity cycling. Ankle angle at foot contact explained 67.1% of the variance in post-cycling VO2 change. The specific problem is ankle mechanics, not general fatigue.
Millet et al. (2001) found the mechanical cost of running increases 7.1% ± 6.0% immediately after cycling for middle-level triathletes, vs 0.4% ± 6.9% for elites. By minute 6, groups were similar. That 6-minute window is where races are lost.
Millet et al. (2000) measured energy cost of running in 8 elite and 18 middle-level triathletes before and after maximal cycling.
Elite triathletes don’t just tolerate the transition. They run more economically post-bike than pre-bike. That’s the adaptation target. Brick training is the method for moving toward it.
Stewart 2022: The Efficiency Collapse That Explains Everything
The most important recent finding comes from Stewart et al. (2022). They measured mechanical efficiency in collegiate triathletes after 40km of cycling.
Running VO2 was unchanged between cycle-run and run-run. That’s the critical detail. The oxygen delivery system isn’t the problem. But mechanical efficiency collapsed from 48.2% to 42.1% post-cycling (p = 0.027, effect size 0.86). Anaerobic energy demand more than doubled: 7.6 kJ to 16.3 kJ (p = 0.004).
In practice: an athlete who rides too hard arrives at T2 already running a 16.3 kJ anaerobic tab. Go out at fresh-run pace and you’ll blow up by mile 3.
This explains why easy brick runs aren’t wasted. The mechanical inefficiency is already there. Moderate-effort post-bike running exposes the nervous system to the full biomechanical disruption. You don’t need to run hard in every brick. You need race-specific mechanics.
Race-Distance-Matched Brick Protocols
Brick goals differ by race distance. Sprint/Olympic bricks target the neuromuscular transition. 70.3 bricks add fueling and pacing calibration. Ironman bricks add fatigue resistance and heat management. Using the same brick across distances is a common mistake.
| Race Distance | Brick Bike Duration | Bike Intensity (% FTP) | Brick Run Duration | Run Intensity | Key Adaptation Goal | Frequency |
|---|---|---|---|---|---|---|
| Sprint | 25–35 min | 88–95% | 15–20 min | Race pace | Neuromuscular transition | 1–2x/week |
| Olympic | 60–75 min | 83–90% | 25–35 min | Race pace | Neuromuscular + lactate clearance | 1x quality + 1 micro-brick |
| 70.3 | 2–2.5 hr | 78–83% | 30–45 min | Race pace | Above + fueling + pacing calibration | 1x long + 1 micro-brick |
| Ironman | 3–4 hr | 72–78% | 60–90 min | Easy-moderate | Fatigue resistance + fueling + heat | 1x every 10–14 days |
“Race pace” has precise meaning. For a 70.3 athlete running a 1:45 half, race pace is ~8:00/mile. The brick run should be at that pace, not whatever feels manageable.
Micro-bricks apply across distances: 10–20 min bike, 5–10 min run at race cadence. Add one per week on top of your primary brick. See gut training for the 120g/hr fueling protocol.
Heart Rate Lies to You at T2
Heart rate at the start of the brick run is not a reliable pacing signal. Expect it to read 5–12 bpm higher than what steady-state running at that pace would produce. Two mechanisms drive this: elevated cardiac output from cycling carries over into the early run, and the shift to upright posture requires rapid hemodynamic redistribution as blood pooled in the cycling position moves to support the run.
Bentley et al. (2002) documented hyperventilation, increased HR, and exercise-induced hypoxemia during the transition run. These aren’t signs of going too hard. They’re the normal physiological cost of the mode switch. The mistake is responding to them by slowing down below race pace or, worse, chasing the elevated HR with more effort.
Pace by power or run pace for the first 8–10 minutes. Once HR settles, you can reference it again. This means knowing your race-pace power or pace targets before the session, not arriving at T2 and guessing.
Aerobic decoupling in the brick run’s second half is a more useful signal than T2 heart rate. A drift ratio above 5% in the back half of a 30-minute brick run suggests either the bike effort was too hard or the run pace is unsustainable for race distance. AthleteOS calculates your drift ratio automatically after each session so you can see this pattern develop over your build.
The Only RCT on Brick Training: What Hue 2002 Actually Found
Hue et al. (2002) ran the only RCT directly testing brick training. Twelve competitive triathletes, 6 weeks, two groups: brick vs separate-discipline.
The cited result: the brick group improved transition time by 11.2 ± 6.8 sec vs 1.2 ± 7.7 sec for control. A 9x difference in transition-specific improvement.
The misrepresented result: overall cycle-run gains were 3.3 ± 1.4% brick vs 6.1 ± 1.7% conventional. The conventional group gained more raw fitness because their training time wasn’t split. Brick training improves transition specifically; conventional training improves raw fitness in each discipline. An optimal program does both.
Micro-Bricks: The 5-Minute Habit
Consider a 70.3 athlete who jogs 20–30 min after every long ride at whatever pace, never varying. T2 remains a weak point. The problem isn’t effort. It’s lack of specificity. Jogging slowly post-bike trains jogging slowly post-bike.
She switches to race-distance-matched bricks: 2.5-hour ride at 79% FTP plus 35 min at goal 70.3 run pace. Four sessions in a 10-week build plus three micro-bricks/week (15 min bike, 7 min run at race cadence). Run split drops 4 min off her previous 70.3 best. The rubber-leg phase is gone by the 300-meter mark.
Race-pace bricks teach the nervous system to switch patterns at race-day speed. Slow bricks teach slow pattern-switching. Micro-bricks add transition repetition with minimal fatigue.
Zone 2 Base vs. Brick Intensity: Getting the Sequence Right
Brick work belongs in the build phase, not the base phase. In weeks 1–8 of a 20-week plan, the priority is aerobic base, not transition drills. The physiological systems that support a good brick run — aerobic capacity, lactate clearance, cycling economy — need to be in place first.
From week 8 inward, brick frequency and specificity increases. Start with one quality brick per week plus micro-bricks. By weeks 6–4 before the race, both the bike duration and run pace should match race targets. From 3 weeks out, reduce brick volume (shorter bike, shorter run) but keep the intensity and the transition pattern.
Pacing the bike leg correctly is the prerequisite for everything. Arrive at T2 having ridden at target FTP percentage, not at the edge of your capacity, and the run will follow the plan. Ride over target and the 16.3 kJ anaerobic demand awaits.
Common Brick Mistakes That Waste the Session
Hard bike, easy run. Athletes exhaust themselves riding, jog through the run, log it as a brick. The neuromuscular stimulus happens during the run. Below race pace = lost specificity.
Any pace, any distance, calling it done. A 10-minute slow jog doesn’t reach the 679m transient phase. Minimum effective run: 15 min at race pace.
Skipping fueling practice. Bricks are the best chance to rehearse race-day nutrition. A 70.3 brick run should match your race-day carb intake. See gut training for higher carb targets.
Doing full bricks year-round. Full bricks are build-phase work. One per week during a 10–12 week build is enough. More accumulates fatigue without speeding adaptation.
The rubber legs are trainable. The protocols exist. Random bricks are expensive cool-downs.
AthleteOS places race-distance-matched brick sessions in your build phase automatically, with bike intensity set to your current FTP percentage and run targets locked to your race-pace zones. Each brick session flags the first 10 minutes of run data as “HR adjustment period” and prompts you to pace by power. Build your race-specific plan here.