How fast should you run off the bike? With brick training just 1 to 5% slower than your open 5K time instead of 10 to 15% without it.
How fast should you really run off the bike? Honest answer: much closer to your open 5K best than you might think — if you train bricks regularly. Without brick experience you typically run 10 to 15% slower than in an open race; with regular bike-to-run training, that gap shrinks to just 1 to 5%.
That's the key difference from middle or long distance: after only 20 km of biking, running just 5 km leaves you far less pre-fatigued than after 90 or 180 km. Your sprint run isn't a grinding survival mode like an Ironman marathon — it's a real, hard 5K race with a slightly tired body.
That's exactly why targeted brick training pays off more for sprint than for any other distance: the gap you close here directly affects your race pace across the entire run, not just the first few minutes.
Without brick training you run 10 to 15% slower than your open time for the same distance. With regular brick training, that shrinks to 1 to 5%. With a 5K best of 25 minutes, that's the difference between roughly 26 minutes (trained) and nearly 29 minutes (untrained) on race day.
"Dead legs" off the bike are real physiology — your running economy is directly 1.6 to 11.6% more costly right after cycling than in an open run, depending on your performance level. The feeling usually fades after the first 500 to 1,000 meters as your body adjusts.
Build bike-to-run combinations into your training regularly, even short ones. The more often your body practices the switch, the smaller the gap between open and sprint race pace becomes. That's the most direct lever for improving your race run time — more direct than pure running training alone.
Set your target pace not at your open 5K time, but 1 to 5% above it if you're well prepared. That's your realistic sprint race pace — noticeably more ambitious than many beginners give themselves credit for.
Run out of transition deliberately controlled, not at the pace that "feels easy" — leg feel often deceives in the first meters. Only after 500 to 1,000 meters, once your body has adjusted, do you pick up to your actual race pace.
A noticeably elevated pulse or moderate dizziness in the first running minutes off the bike is normal within limits — chest pain, real shortness of breath or visual disturbances are not. Slow down immediately and get help if warning signs go beyond the usual "heavy legs" feeling.
Build your race pace deliberately slowly in the first minutes out of transition instead of jumping straight to planned race pace — that also lowers the risk of cramps and strains under maximum effort.
Train bricks not just long, but also short and frequent: 20 minutes of biking plus 10 minutes of running, once a week, builds the adaptation just as well as rare mega-sessions — and fits far more easily into a full calendar.
Without brick training, 10 to 15% slower; with regular brick training, just 1 to 5%. This difference matters especially at sprint distance, because the 5K run is short enough that every percentage improvement shows up directly in your final pace.
That's real physiology: your running economy is directly 1.6 to 11.6% more costly right after cycling than in an open run. The feeling usually fades after 500 to 1,000 meters as your body adjusts.
Regularly, even in short form: 20 minutes of biking plus 10 minutes of running once a week is enough to noticeably close the gap between open and race pace.
Deliberately controlled, not at full race pace. Only after 500 to 1,000 meters, once your body has adjusted, do you build to your actual target pace.
Sprint Distance: Injury Risk From Short, Intense Effort