Brick workouts: what they're for, and what the evidence actually says

A brick workout is a bike session followed immediately by a run, with as little gap between the two as you can manage. It exists to rehearse the part of a triathlon that feels least like the training you did to prepare for it. Here is the honest version of the advice: bricks are worth doing, but mostly not for the reason people give for them. The evidence that combining a ride and a run into one session produces a physical adaptation you would not get from doing them on separate days is thin. What bricks reliably buy you is pacing judgment, transition and fueling practice, and confidence. That is enough reason to do them, and nowhere near enough reason to do one every week.

What counts as a brick

The standard form is bike to run. Swim-to-bike bricks exist and are worth doing occasionally — mostly to discover that your legs are fine and your neck is not — but bike to run is the one that matters, because that is the transition where races get lost.

The operative word is immediately. The thing you are rehearsing lives in the first five to ten minutes off the bike. Rack the bike, change shoes, stand around for a quarter of an hour, then run, and you have done two workouts on the same day. Useful, but not a brick. Under two minutes of changeover is the target, and under a minute if you are practicing the transition itself.

The origin of the name is folklore. There are competing stories about a coach's shorthand, a backronym, and the obvious one about how your legs feel. None of them are documented and none of them change how you train.

Why your legs feel like concrete

Three things change at once when you step off the bike.

Blood is in the wrong place. For the last hour your circulation has been organized around a seated, supported position and a specific set of working muscles, with a share diverted to your skin for cooling. Standing up and running changes that demand instantly, and supply takes a few minutes to catch up.

Your cadence and motor pattern flip. Pedaling is a smooth loop at 80–95 revolutions per minute with no impact and almost no eccentric loading — nothing has to absorb your body weight. Running is 170–180 steps per minute of landing, absorbing, and pushing off. Your nervous system has spent an hour rehearsing one rhythm and now has to produce a completely different one. The first few hundred meters are genuinely a coordination problem, not only a fatigue problem.

Different muscles are suddenly in charge. Cycling leans heavily on the quadriceps and glutes, working concentrically. Running asks far more of the calves, Achilles, and hamstrings, and asks them to absorb load on every single step. Those tissues have been along for the ride rather than doing the work, and they start cold on legs that are already tired.

Which of the three dominates is not settled, and you do not need to know. What matters is that the sensation is real rather than imagined — running mechanics and the oxygen cost of running are both measurably different in the first minutes off the bike — and that it goes away.

It fades in about ten minutes, whatever you did in training

This is the fact that reframes the whole session. The concrete-legs feeling settles within roughly the first five to ten minutes of running, call it the first kilometer, as circulation catches up and your stride normalizes. It does that for a first-timer and it does that for a professional.

More experienced triathletes do appear less disrupted by the transition. They are also better runners and better cyclists, which makes it hard to credit brick training specifically rather than simply being fitter at both sports.

What practice changes is not really the sensation. It is your response to it. An athlete who has run off the bike thirty times knows the heaviness is temporary and holds a sensible pace through it. An athlete who has never felt it assumes something has gone badly wrong, and either panics and slows to a shuffle or overcompensates and blows up at 3 km. That difference is worth real minutes on race day, and it is a rehearsal effect rather than a physiological one.

What the evidence actually says

There are two bodies of research here and they are in very different shape.

The descriptive one is solid. Running after cycling has been measured many times, and it reliably shows altered stride mechanics and a raised oxygen cost at a given pace in the early minutes, settling as the run goes on. The phenomenon is real and reasonably well characterized.

The intervention one is thin. The question that actually matters for planning — whether doing your bike and your run in one session produces adaptations that the same bike and the same run on separate days would not — has been studied far less, in small groups, over short periods, with mixed results. There is no strong body of evidence saying combined sessions beat separated ones physiologically.

Be careful about the direction of that claim. Thin evidence is not the same as proven useless, and endurance training research in general is small, short, and underpowered, so plenty of things that work have never been shown cleanly. But the honest reading is that the physiological case for bricks is an assumption the sport made early and then repeated, while the practical case — pacing, transitions, fueling, nerves — is the one that holds up.

What bricks are genuinely good for

Pacing judgment, which is the big one. The most common way to ruin a triathlon run is to ride slightly too hard. Slightly. You cannot learn where that line sits from a standalone ride or a standalone run, because in both cases you get to finish and go home. A brick is the only session that teaches you what a bike effort you can still run off actually feels like, and it teaches it in the currency you will be using on race day, which is feel rather than numbers.

Transition mechanics. Elastic laces, socks or no socks, where the gel lives, what happens when you stand up quickly after an hour in the aero position. Each of these is worth about a minute, all of them are learnable in ten seconds of practice, and all of them are expensive to discover for the first time in a race.

Fueling and gut tolerance. What you can absorb sitting on a bike and what you can absorb while running are different questions. If your race plan involves a gel in the first 20 minutes of the run, find out in training whether that actually works for you. Tolerance is trainable and it is specific to the situation you train it in.

Confidence. Worth naming plainly instead of filing it under soft benefits. Knowing from experience that the heaviness passes is what stops you making a bad decision in the first kilometer of the run.

The transition run: the version most people should do most often

Ten to twenty minutes of easy-to-steady running straight off an ordinary ride. That is the whole session. Change shoes, go.

This is the best value per unit of fatigue in the entire brick family. It costs almost no recovery, it attaches to a ride you were doing anyway, and it delivers most of the transition-specific practice: the coordination shift, the gear rehearsal, and the direct experience that the feeling passes. Once a week through a build is plenty, and it does not need to be a special occasion on the calendar.

Run it by effort, not by pace. The first kilometer off the bike will be slower than your normal easy pace at the same effort, and chasing your usual numbers there is how a ten-minute transition run turns into a hard session by accident.

Race-pace rehearsal bricks

The other format worth doing on purpose: ride at goal race effort, then run at goal race pace for long enough to find out whether the plan is honest.

The whole ride does not need to be at race effort. What matters is that the last 30–45 minutes of the bike are at the effort you intend to hold, because that is what determines the state your legs are in when the run starts. Then run long enough to get past the settling period and into real information — 20 minutes minimum, and rarely more than 40.

These belong in the build phase, in the last couple of months before the race, and there should not be many of them: three to five across a 70.3 build, three or four across an Ironman build. Treat them the way you would treat a hard interval session. Fresh going in, easy day afterward.

Brick formats by race distance

Two things to read off that table. The run off the bike gets proportionally shorter as the race gets longer, not longer. And nowhere does it ask you to rehearse the full race-day run off the full race-day bike. That session costs far more than it teaches, at every distance.

Long bricks are the most overused session in triathlon

The five-hour ride followed by a 90-minute run is a rite of passage and a bad idea for most age-group athletes.

The cost lands in two places. The obvious one is recovery: a session like that is closer to a race than to a training day, and it typically eats the following two or three days. The less obvious one is injury risk, which is concentrated in exactly this state — running on a fatigued, poorly coordinated stride, usually in the heat, usually at the end of a long day. Tired-legs running is where a lot of the sport's calf and Achilles problems come from.

The learning curve also flattens fast. Almost everything a long brick can teach you about pacing, fueling, and the mental shape of the transition, you have learned by 30–45 minutes into the run. Minutes 45 to 90 mostly buy fatigue.

A brick costs the training load of both halves, and the run half lands on legs that are already tired, so the recovery it demands sits closer to a race than to two ordinary sessions. PaceBeats prices both halves into the week's load and arranges the days around them, which mostly amounts to stopping the following three days from quietly turning into junk. The arithmetic behind that is in training load, TSS, CTL, and ATL.

How often, and where to put them

• Off-season and base: few or none. Nothing is race-specific yet, and this is the phase for becoming a better runner and a better cyclist separately.
• Build: one transition run a week off a normal ride, plus a race-pace rehearsal brick every two to three weeks.
• Peak: the last long race-pace brick roughly three to four weeks out from an Ironman, two to three weeks out from a 70.3.
• Taper: keep the short transition runs, drop the long ones completely. Ten minutes of running off a 60-minute ride in race week is a useful reminder. Anything bigger is fatigue you no longer have time to repay.

Two scheduling rules that save people from themselves. Do not put a brick the day after a hard run, and do not put a long run the day after a brick — the two sessions compete for the same tissues in the same fatigued state.

If your training week is six or seven hours total, one transition run a week is the right amount of brick, and everything else is better spent swimming or simply running more often. How many hours triathlon actually takes is the more useful question at that volume. PaceBeats builds the season backward from your race date, which is the mechanism that keeps race-specific sessions clustered in the last couple of months instead of sprinkled evenly through the year.

So do you need bricks?

You need some. You do not need many, and you almost certainly do not need the long ones you have seen on other people's training feeds.

If you take one thing from this: add ten minutes of running to the end of one ride a week during your build, run it by effort, and stop worrying about whether that is enough. Then do three or four proper race-pace rehearsals in the last two months so you know what your goal bike effort feels like from the run course. The rest of your week should be ordinary swim, bike, and run training, because that is the part that actually makes you faster.