A triathlon does not fall apart because you forgot how to swim, bike, or run. It usually falls apart in the spaces between them.
The first climb out of T1. The headwind you did not pace for. The first mile of the run when your legs feel borrowed. The moment you realize your “comfortable” bike effort was not comfortable enough.
That is why course simulation bricks are so useful. Not every brick needs to be hard. Not every race rehearsal needs to be long. But at the right time in your season, a well-built simulation brick can teach you what your goal race will actually demand.
The key is to rehearse the course, not just the distance.
What Is a Course Simulation Brick?
A course simulation brick is a bike-run workout designed to copy the most important demands of your race. That might mean hills, heat, wind, technical turns, a long aero position, or a run that starts on tired legs after a sustained bike effort.
It is different from a standard brick because the purpose is not simply “ride, then run.” The purpose is to answer specific race-day questions:
- Can you hold your target bike effort without spiking on climbs?
- Does your run pace still feel controlled after race-intensity riding?
- Can you execute T2 calmly when your heart rate is elevated?
- Do your shoes, kit, bottle setup, and gear choices work under pressure?
- Where does your pacing start to drift?
This is not a fitness test for every weekend. It is a rehearsal tool. Used well, it gives you confidence and exposes weak points early enough to fix them.
Start With the Course, Not the Workout
Before you build the session, study your race. Look at the bike elevation profile, road surface, turn frequency, likely wind direction, and the first two miles of the run course. For open-water races, note the swim exit distance to transition and whether you will face sand, stairs, grass, or pavement before reaching your bike.
You do not need to copy the entire race. You need to copy the parts that can change your outcome.
For example, a flat Olympic-distance race with strong coastal wind demands steady aero riding and disciplined effort control. A hilly 70.3 asks for power restraint on climbs and smooth fueling while terrain changes. A sprint race with a short, fast run rewards quick T2 execution and the ability to settle into pace immediately.
Specificity matters. The closer you get to race day, the more your key sessions should look like the race you are training for.
When to Use Course Simulation Bricks
The best time for this type of session is usually 3 to 8 weeks before your goal race, depending on the distance and your experience.
Too early, and you may not have enough fitness for the session to be useful. Too late, and you may carry fatigue into your taper. If you are already managing a dense block, place this workout carefully. The goal is quality rehearsal, not proving how much suffering you can absorb. For more on spacing demanding sessions, see The Fatigue Budget: How to Place Key Triathlon Workouts Without Burning Matches.
As a general guide:
| Race Distance | Best Timing | Simulation Focus |
|---|---|---|
| Sprint | 2–4 weeks out | Fast T2, hard but controlled bike, quick run rhythm |
| Olympic | 3–5 weeks out | Bike pacing, run settle-in, transition flow |
| 70.3 | 4–7 weeks out | Sustained aero riding, fueling practice, controlled run durability |
| Iron-distance | 6–10 weeks out | Long steady effort, nutrition timing, fatigue management |
How to Build the Session
A good course simulation brick has three parts: a race-specific bike, a realistic T2, and a controlled run off the bike.
1. Make the bike match the race demand
If your race has climbs, include climbs. If it is flat, practice staying aero without coasting. If the course has frequent corners, choose a route where you need to brake, shift, and accelerate smoothly.
A common mistake is making the bike too hard. Your goal is not to set a training personal best. Your goal is to learn whether your planned race effort leaves you able to run.
For most athletes, the bike should sit around goal race intensity, with only short controlled surges if the course demands it. If you use power, watch for spikes. If you train by heart rate, expect some lag and focus on effort. If you use RPE, the ride should feel “firm but repeatable,” not desperate.
2. Treat T2 like part of the workout
Do not finish the ride, check your phone, refill bottles, chat, and then start the run ten minutes later. That removes one of the most important parts of the rehearsal.
Set up a simple transition area before you ride. Helmet off. Shoes changed. Race belt or hat on. Start the run. You do not need a perfect replica of a race venue, but you do need the same sequence under mild pressure.
If you want to sharpen transitions without adding another demanding session, pair this approach with the ideas in The Micro-Brick Method: Build Faster Triathlon Transitions Without Adding More Fatigue.
3. Run controlled, not heroic
The run should tell you whether your bike pacing worked. If you blast the first mile, you lose that feedback.
Start slightly easier than goal pace for 5 to 10 minutes. Let your cadence come back. Let your breathing settle. Then move toward your planned race rhythm.
A strong simulation run often feels boring at first. That is a good sign. Race-day success usually comes from restraint early and strength late.
Sample Course Simulation Bricks
Use these as templates. Adjust volume based on your current fitness and race distance.
Sprint Triathlon
- Bike: 40–50 minutes with 3 x 6 minutes at goal race effort
- T2: Full shoe change and run exit practice
- Run: 12–20 minutes, building from controlled to goal pace
Olympic Triathlon
- Bike: 75–90 minutes on terrain similar to race course
- Include: 2 x 20 minutes at goal effort with easy riding between
- T2: Full practice, no extended break
- Run: 25–35 minutes with the middle 15–20 minutes at goal pace
70.3 Triathlon
- Bike: 2.5–3.5 hours with 2 x 45 minutes at planned race effort
- Practice: Aero position, fueling schedule, terrain management
- T2: Full practice including socks, hat, race belt, and run nutrition
- Run: 35–60 minutes, first 10 minutes easy, then settle into target effort
For long-course athletes, this session should leave you tired but not wrecked. If you need several days to feel normal, it was probably too long or too hard.
What to Measure Afterward
The workout is only useful if you review it. Look beyond pace and average power.
- Bike variability: Did you surge too much on hills or out of corners?
- Run fade: Did your pace drop while effort climbed?
- First-mile control: Did you start too fast off the bike?
- Transition time: What slowed you down?
- Body signals: Any cramps, hot spots, stomach issues, or equipment problems?
If the run felt rough, do not automatically blame your run fitness. The problem may have started on the bike. Many triathletes think they need more running when they really need better bike pacing.
How Often Should You Do Them?
Most athletes only need one to three course simulation bricks in a build. Sprint and Olympic athletes may use shorter versions more often. Long-course athletes should be more selective because the cost is higher.
Do not stack a hard swim, heavy strength session, and long simulation brick into the same 48-hour window unless you are very experienced and have planned recovery afterward. The session should sharpen your race plan, not bury it.
A smart pattern is:
- One early simulation to find problems
- One mid-build simulation to practice corrections
- One final lighter rehearsal before taper
Final Takeaway
A course simulation brick is not about proving toughness. It is about removing surprises.
Build the session around your race course. Ride at the effort you actually plan to use. Move through T2 with purpose. Start the run under control. Then review what happened honestly.
If you can rehearse the hard parts before race day, you give yourself a better chance to execute when it counts. Not because the race will feel easy, but because it will feel familiar.
Leave a Reply