Your legs feel like lead the first quarter mile off the bike. That heavy, disconnected feeling isn’t in your head, and it’s measurable.
For most of a 70.3 build, one well-executed brick workout a week is enough. Push to two a week only in the final month before race day. Do three a week for months and you’re not building fitness faster. You’re stacking injury risk on top of fatigue you never needed.
The Run-Off-Bike Deficit: What a Brick Actually Costs Your Legs
In a controlled trial, 10 trained triathletes ran 12 minutes flat out, once cold and once straight off a bike ride. Running off the bike cut their distance by 5.8%. Stride length dropped 4.2%. Same effort, noticeably less ground covered, and a shorter, choppier stride.
This isn’t just tired legs. Researchers also tracked muscle oxygen saturation (SmO2), a measure of how well your muscles pull oxygen from the blood. SmO2 averaged 55.1% during the bike-run compared to 41.5% on the isolated run, a 35.7% relative gap (Olcina et al., 2019). In plain English: running off the bike puts your muscles into a different fuel-delivery state. It’s not just a more tired version of the usual one.
A separate study used motion sensors to measure how far runners had to go before their gait stabilized. After a normal run, it took 294 meters. After running off the bike, it took 679 meters, more than double. Eighty-two percent of athletes showed a clear disruption phase after cycling. Only 32% showed one after an isolated run (Weich et al., 2022).
Bike-to-run is a different sport, not harder running.
That’s why the transition needs practice. It’s also why more practice than necessary comes at a real cost.
Why 2-3 Bricks a Week Backfires
A systematic review pooling 5,996 long-distance triathletes found overuse injury rates ranging from 37% to 91%. Weekly training volume tracked positively with injury risk (Rhind et al., 2022). More sessions, more injuries, in a fairly straight line.
Here’s the detail that should shape how you plan bricks specifically. The knee takes the worst of it, accounting for 43% to 63% of all overuse injuries in the review. Running is involved in 58% to 72% of every overuse injury a triathlete picks up. Running on legs already altered by cycling is exactly the load pattern most likely to hurt your knee.
Elite athletes, despite training the most hours, had the lowest overuse injury rate in the review at 37%. That’s not a volume story. That’s a structure story. The best-coached athletes hit the dose that produces the adaptation, then stopped chasing more.
Think of the run-off-bike pattern like wet concrete. Give it a week to set between pours and it hardens into the shape you want. Disturb it again before it sets, on tired legs, and you get a weaker, lumpier slab.
Motor-learning research backs this up. Space a single, well-executed rep about a week apart and it consolidates a movement pattern just as well as several fatigued reps crammed together. Sometimes better. Fatigued practice can groove in the wrong mechanics instead of the right ones.
Fatigued reps don’t train good form. They rehearse bad form.
The Minimum Effective Dose: Brick Workout Frequency by Training Block
A 9-to-12-hour-per-week athlete has very little slack for a session type that costs this much mechanically for a modest training-stress return. That argues for a low, well-timed frequency, not a high, constant one.
The race-simulation row below targets roughly 83% of your FTP (Functional Threshold Power). That’s the highest average power you can hold on the bike for about an hour. Pair it with a run near 70 TSS (Training Stress Score) per hour. TSS is a single number that blends how hard and how long a session was.
| Block | Weeks out | Bricks/week | Typical session | Purpose |
|---|---|---|---|---|
| Base | 16-11 | 1 every 2 weeks | 45min bike + 15min easy run | Introduce the transition, low mechanical cost |
| Build | 10-5 | 1/week | 60-90min bike + 20-30min run at race effort | Groove the pattern under real fatigue |
| Race simulation | 8 and 4 weeks out | 1/week | ~83% of FTP bike into ~70 TSS/hour run | Confirm pacing and fueling under race load |
| Final taper | Last 4 weeks | 2/week | Shorter, sharp, race-pace bricks | Peak specificity while cutting total volume |
That progression tracks a meta-analysis pooling 27 studies across every triathlon discipline. The optimal taper runs 8 to 14 days. Volume drops 41% to 60% while intensity stays roughly the same. You don’t get faster by doing less of everything. You get faster by cutting volume while keeping the sessions that matter sharp. That’s exactly why brick frequency should concentrate late, not spread evenly across the whole build.
How to Know the Adaptation Is Landing: Run-Off-Bike Decoupling
Guessing from how your legs feel is unreliable. Feelings lie. The drift ratio doesn’t.
Coaches use aerobic decoupling, the change in your heart-rate-to-pace efficiency between the first and second half of a steady effort, as the standard test for aerobic durability. A reading of 5% or less is the usual target for a clean, sub-threshold effort.
Apply the same test to your run-off-bike segment and compare it against your decoupling on a matched open run. If the brick-run number keeps running several points higher than the open-run number, week after week, the pattern isn’t consolidating yet. If the gap closes, it’s landing. That single comparison replaces guesswork with a number. It’s a much better signal than how heavy your legs felt at minute two.
AthleteOS runs this comparison automatically. Inside a 70.3 training plan, it places one quality brick per week by default. It escalates to two per week only in the final four weeks. That mirrors the taper evidence, not the “brick every week from day one” habit most plans default to. After each brick, it calculates your run-off-bike drift ratio, then lines that up against your most recent open-run drift ratio. Both track alongside your fitness and fatigue scores, so you can see whether the gap is closing instead of guessing.
One Athlete’s 12-Week Build
Take a first-timer I’ll call Diego. He’s 34, training 10 hours a week for his debut 70.3 with 16 weeks to go. His first two bricks landed at week 3 and week 5, spaced out, 45 minutes of bike into 15 minutes of easy running. Nothing dramatic.
By week 10, his run-off-bike drift ratio, the gap between his brick-run efficiency and his open-run efficiency, still sat near 14%. His coach didn’t add more bricks. They kept it at one a week and sharpened the intent. They also made sure his easy days stayed genuinely easy, so his legs actually recovered between sessions. By week 15, the second of two bricks in his final month, that gap had closed to 4%. His race-day 10K off the bike came in 6 minutes faster than his best training estimate.
More bricks wasn’t the lever. Better-timed bricks were.
If you’re building toward your own 70.3, pair your brick placement with a real Zone 2 base underneath it. The transition practice only pays off if the aerobic engine under it is already sound.