What is a brick workout?

A brick workout is a training session that combines two disciplines back to back, most commonly cycling followed immediately by running. The name may come from how your legs feel during the run - like bricks - or from the combination of disciplines (Bike + Run = BRick). The purpose is to train your body for the specific demands of transitioning between sports in a triathlon.

Why do my legs feel so heavy when I run after cycling?

Several physiological factors are at play. Blood flow has been concentrated in your cycling muscles (primarily quads and glutes in a different firing pattern than running). Your proprioception and motor patterns need to shift from a fixed, circular pedaling motion to the impact-based, reciprocal motion of running. There is also neural fatigue from sustained cycling effort. All of these improve with consistent brick practice.

How often should I do brick workouts?

During base training, one easy brick per week is sufficient. During the build phase, one to two bricks per week with varying intensity. During taper, maintain one short brick every week or two. More than two bricks per week is rarely productive and increases injury risk from running on pre-fatigued legs.

How long should the run be after a brick ride?

It depends on the phase. During base, 10-20 minutes is enough. During build, 20-45 minutes for Olympic and half-distance athletes, up to 60-75 minutes for Ironman athletes. The run should never be so long that your form completely breaks down - that trains bad movement patterns.

Should I do bricks at race pace?

Not most of the time. The majority of bricks should be at easy to moderate effort to build the neuromuscular adaptation without excessive fatigue. Race-pace bricks are valuable but should be limited to once every 2-3 weeks during the build phase. Save your hardest race-simulation bricks for the peak phase.

Can AI detect brick workouts automatically?

Yes. When your Strava data shows a bike session immediately followed by a run session (within a short time window), AI coaching identifies this as a brick workout. It then compares your brick run metrics - pace, heart rate, cadence - against your standalone run data to track your transition-specific fitness over time.

Brick Workouts for Triathletes - Complete Bike-to-Run Training Guide (2026)

What bricks are and why they matter

The first time you run off a bike, you understand the problem immediately. Your legs don't work right. Your quads feel like concrete, your stride is choppy, and a pace that normally feels easy suddenly feels like tempo effort. This sensation is universal among triathletes, and it is the reason brick workouts exist.

A brick workout is a training session combining two disciplines back to back - almost always a bike ride followed immediately by a run. The transition from cycling to running (called T2 in race terminology) is one of the most unique physical demands in all of endurance sport, and it only gets better with deliberate, specific practice.

In a race, your T2 run performance is often where time is gained or lost. Two athletes with identical standalone run fitness can have dramatically different results coming off the bike. The one who has trained the transition will settle into pace within the first mile. The one who hasn't will struggle for 10-15 minutes, burn through glycogen at a higher rate, and run significantly slower.

The physiology of running off the bike

Several things happen simultaneously when you dismount and start running.

Blood flow redistribution. During cycling, blood is concentrated in the muscles used for pedaling - primarily the quadriceps, hip flexors, and glutes working in a circular motion. When you start running, your body needs to redistribute blood to the hamstrings, calves, and hip stabilizers that bear impact forces. This redistribution takes time, and during that window, your muscles are relatively oxygen-deprived.

Motor pattern switching. Cycling is a constrained, repetitive motion with no impact. Running is a free-range, impact-based movement that requires balance, proprioception, and elastic energy return from tendons. Your neuromuscular system needs to completely switch coordination patterns. Research on muscle activation shows that running immediately post-cycling produces altered firing patterns, particularly in the quadriceps and hamstrings, compared to fresh running.

Neural fatigue. Hours of sustained cycling effort create central nervous system fatigue that affects motor unit recruitment. Your brain's ability to activate muscles efficiently is temporarily reduced. This is separate from muscular fatigue and explains why your legs feel "dead" even when they are not truly depleted of energy.

Metabolic state. After a long or hard ride, you've burned through a significant portion of your glycogen stores. Running off the bike means starting your run in a partially depleted state, which shifts your fuel utilization and affects pace sustainability.

All of these factors are trainable. With consistent brick practice, your body learns to make the cardiovascular, neuromuscular, and metabolic adjustments faster. The sensation never fully disappears - even elite triathletes feel the transition - but the duration and severity of the adjustment period shrinks dramatically.

Types of brick workouts

Not all bricks serve the same purpose. A smart training plan uses different types at different phases.

Short bricks (adaptation focus)

A moderate bike of 45-75 minutes followed by a 10-20 minute easy run. The ride is not hard, and the run is deliberately easy. The goal is frequency of exposure - teaching your body the transition pattern without creating significant fatigue. These are your bread-and-butter bricks during base training.

Long bricks (endurance focus)

A longer ride of 2-4 hours followed by a 30-60 minute run at easy to moderate effort. These simulate the duration demands of longer triathlon races and practice fueling through the transition. The run should start easy and stay easy. If you cannot maintain form for the planned duration, the run is too long.

Race-pace bricks (specificity focus)

A ride with the final 20-40 minutes at target race intensity, followed by a run at target race pace for 15-30 minutes. These are the most demanding bricks and simulate the exact physiological state you'll be in at T2 on race day. Limit these to once every 2-3 weeks during the build phase.

Reverse bricks (run-to-bike)

A run followed by a bike session. These are less common but useful for athletes doing duathlons or for adding variety. The physiological demands are different - running first creates more impact-based fatigue that you then carry onto the bike. Some coaches use these to build bike-specific endurance on pre-fatigued legs.

Progressive brick training

Brick fitness builds progressively over weeks, not days. Rushing the progression is one of the most common training errors in triathlon.

Weeks 1-4: Introduction. One short brick per week. Ride 45-60 minutes at easy effort, then immediately run 10-15 minutes easy. The run pace does not matter at all. You are training the transition, not the run. Record your average pace and heart rate during these initial brick runs - this is your baseline.

Weeks 5-8: Extension. Increase the run to 20-30 minutes. The ride can extend to 60-90 minutes. Keep effort easy to moderate. Start noticing how your brick run pace compares to your fresh run pace at the same heart rate. Early on, expect a gap of 20-45 seconds per mile.

Weeks 9-12: Specificity. Introduce one race-pace brick every 2-3 weeks. The ride includes 15-20 minutes at race effort near the end, and the run starts at race pace for 15-20 minutes before easing off. On alternate weeks, continue with easy bricks but extend the run to 30-45 minutes.

Weeks 13-16: Simulation. For half and full-distance athletes, one brick should approach race-simulation intensity and duration. A 3-4 hour ride with the last 30 minutes at race effort, followed by a 30-45 minute run with the first 15 minutes at race pace. This is the peak brick session and should only happen 2-3 times during the entire training cycle.

Weeks 17-20: Maintenance and taper. Brick volume drops with overall taper, but maintain one short brick per week to keep the neuromuscular pattern fresh. A 45-minute moderate ride followed by a 15-minute easy run is enough to maintain the adaptation without creating fatigue.

How AI tracks brick performance

The most valuable metric for measuring brick-specific fitness is the gap between your T2 run performance and your standalone run performance at equivalent effort.

When your Strava data shows a bike session immediately followed by a run session, AI coaching identifies this as a brick workout. It then pulls out the key metrics:

Brick run pace vs. fresh run pace at the same heart rate zone. This is the primary adaptation marker. A shrinking gap means your body is getting better at the transition.
Heart rate settlement time. How quickly your heart rate stabilizes into a normal running pattern after the transition. Early in training, it may take 8-10 minutes. With adaptation, it drops to 2-3 minutes.
Pace stability. Does your brick run pace hold steady, or does it degrade over the run? A stable or negative-split brick run indicates strong transition fitness.
Cadence comparison. Many athletes start their brick run with an abnormally low cadence (the ghost of pedaling rhythm). AI tracks how quickly your cadence normalizes to your typical running cadence.

Over weeks and months, these trends paint a clear picture of your transition-specific fitness. You can see the adaptation happening in the data before you feel it in your legs.

How often to brick at different training phases

Getting brick frequency right matters more than most triathletes realize. Too few bricks and you never develop the adaptation. Too many and you are running on fatigued legs so often that your run form deteriorates and injury risk climbs.

Base phase (12+ weeks out): One easy brick per week. That is it. Your body needs time to build general endurance before you layer on transition-specific stress.

Build phase (6-12 weeks out): One to two bricks per week. One should be easy, and no more than one every 2-3 weeks should include race-pace elements. If you are doing two bricks in a week, ensure at least two days of separation.

Peak phase (3-6 weeks out): Maintain one brick per week. This is when your longest and hardest race-simulation bricks happen, but they should be rare events - one or two total - not weekly features.

Taper (final 2-3 weeks): One short, easy brick per week. Just enough to maintain the neural pattern. Do not test your fitness with a hard brick during taper. The data from the previous weeks tells you everything you need to know.

Common mistakes

Making every brick hard. This is the most common error. Athletes treat every brick like a race simulation - hard ride, hard run. The result is chronic fatigue, deteriorating run form, and increased injury risk. Most bricks should be easy. You are training a transition skill, not hammering your cardiovascular system.

Ignoring the run portion. Some athletes finish their ride, think "good enough," and skip the run or cut it short. Even a 10-minute jog after a ride has training value for the neuromuscular transition. The run matters - it is the whole point.

Running too far on fatigued legs. If your form is falling apart - shuffling feet, excessive forward lean, asymmetric gait - the run has gone too long. Running with broken form on tired legs is a direct path to injury. Cut the run short and build duration gradually.

Skipping bricks entirely. Some athletes figure that being a strong cyclist and a strong runner will be enough. It won't. The transition is a distinct skill. You wouldn't skip practicing T1 (swim-to-bike) if you wanted a clean race. T2 deserves the same respect.

Not tracking brick-specific data. Without tracking, you have no idea whether your brick fitness is improving. You might feel better, but feelings are unreliable indicators of performance changes. Connect your Strava data to athletedata.health and let AI track your T2 run performance over time. The trends in the data tell you exactly where you stand and whether your brick programming is working.

Putting it together

Brick workouts are one of the few training tools that are unique to triathlon. No single-sport athlete needs them. They exist because the transition from cycling to running is a distinct physiological challenge that only improves with specific practice.

The approach is simple: start easy, build gradually, track the data, and resist the urge to make every brick a sufferfest. Your race-day T2 performance will reflect the work you put in over months of consistent, progressive brick training - not the one monster brick session you did three weeks before the race.

For a broader look at triathlon training with AI coaching or a deep dive into Ironman-specific preparation, check the related guides. And if you want an AI coach that automatically detects your brick workouts, tracks your transition fitness over time, and adjusts your training based on recovery data from WHOOP, Oura, or Garmin, connect your apps at athletedata.health.

Key takeaways

Brick Workouts for Triathletes: The Complete Guide to Bike-to-Run Training