Run Training for Triathletes: How to Build the Run Leg

The triathlon run is the discipline that decides most races and the one athletes most often train by feel — a few runs squeezed in whenever the swim and bike leave room. This guide is about the design of your running: how often to run, how hard, what kinds of sessions to include and how to build them up safely, so the run leg becomes a strength rather than the place your race unravels.

It deliberately stays at the level of structure. For the parts that deserve their own deep dive, it points you to dedicated guides rather than repeating them:

• Technique and cadence → triathlon running form and run cadence explained
• Running off the bike → brick workouts and brick-run technique
• Injuries → common running injuries and prevention
• Pacing on race day → race pacing strategy
• Shoes → running shoes for triathlon

Think of this page as the map, and those as the detailed routes. If you get the design right here, every one of those specifics has something solid to attach to.

If you change only two things about your running, change how often you run and how easy most of it is.

Run frequency. Running fitness and, crucially, running durability respond to how regularly you run more than to the length of any single session. Three to five runs a week — even short ones — expose your tissues to running load often enough to adapt, while keeping each individual dose small. Two long, hard runs a week deliver the same volume with far more impact per session and far less consistency, which is a recipe for the soreness-injury cycle. Frequency, kept easy, is how you accumulate running without accumulating damage.

Easy volume. The large majority of your running should be genuinely easy — a conversational effort you could sustain and recover from. Well-trained endurance athletes spend most of their training time at low intensity and only a small, deliberate share at high intensity, and that distribution is what makes the hard sessions effective when they come. The pyramid at the top of this page shows the shape: a wide base of easy aerobic running, a controlled band of tempo and threshold work, and a small tip of speed.

The most common self-sabotage in run training is letting the easy runs drift into "moderately hard." That grey-zone running is tiring enough to compromise recovery but not focused enough to drive adaptation. Keep easy easy, so that hard can be hard. For how a single session's frequency, duration and intensity fit together in general, see triathlon training basics.

Run training is built from a small menu of session types. You do not use all of them every week; you choose the few that fit your phase and time. Each one has a distinct job:

Session	What it is for	How it should feel	Go deeper
Easy / recovery run	Aerobic base, durability, active recovery	Conversational, unremarkable	This guide
Long run	Endurance and fatigue resistance	Easy, but long enough to challenge	Long-run progression
Tempo / threshold	Sustainable "comfortably hard" speed	Talk in short phrases only	Running form
Intervals / speed	Top-end fitness and economy	Hard, in repeated short efforts	This guide
Brick run	Running off the bike	Heavy legs at first, then settling	Brick workouts
Strides	Cheap neuromuscular "polish"	Fast but relaxed, 15–20 s	Strength for running

A typical week for most age-groupers is mostly easy runs, one clearly long run, and — once a base is in place — one quality session (tempo or intervals, rarely both). The long run is the session to protect first; the quality session is the one to skip when life or fatigue intervenes. Strides are the small addition that adds turnover and economy for almost no fatigue cost, and they slot onto the end of an easy run once or twice a week.

Running is the highest-injury discipline in triathlon because it is the only one with repeated impact, and impact load is what tissues need time to tolerate. That single fact should shape how you progress.

• Ramp gradually. Increase your total running load in small steps, not leaps. Large, sudden jumps in training load are associated with higher injury risk, so a modest, boring progression beats an ambitious one you cannot repeat.
• Progress one thing at a time. Add frequency, then duration, then intensity — not all at once. If you introduce interval work, hold your easy volume steady that week rather than raising both.
• Consistency is the real training effect. Ten uninterrupted weeks of moderate running build a more durable runner than four big weeks followed by six weeks nursing a niggle. The goal is a load you can repeat.
• Respect early warnings. Niggles that sharpen, change your gait, or persist beyond a few days are signals to back off, not to push through.

Strength work for the hips, glutes and calves supports this durability and is covered in strength training for triathlon running. For the specific injuries triathletes run into, their early signs and how to prevent them, see common running injuries. This pillar's job is the load design around those; theirs is the detail.

Running economy is how much energy you burn to hold a given pace — the running equivalent of fuel efficiency. Two athletes with the same aerobic engine can run very different times if one is more economical, which is why it is worth training rather than ignoring.

The reassuring part is that the things that improve economy are mostly things you are already doing for other reasons: a large base of easy running, occasional faster running and strides, appropriate strength work, and letting cadence settle rather than overstriding. You do not need to obsess over a single metric or copy an elite's form.

Because form and cadence deserve their own treatment, this guide does not drill into mechanics — read triathlon running form for posture, foot strike and drills, and run cadence explained for the numbers and how to change them sensibly. Shoes also play a role in economy and comfort; the running shoes guide covers what to look for without chasing marketing claims. Train economy through the training itself, and treat any single number as feedback, not a target.

Standalone runners can build a week around running. Triathletes cannot — your run training shares a body with swim and bike load, and the run itself happens last, on legs that are already tired. That changes the design in a few concrete ways:

• Practise running off the bike if your plan calls for it. A short run after a ride can help rehearse the transition, but individual sensations vary and bricks are not a guaranteed fix. Follow a progression that fits your experience and recovery. See the brick workouts guide.
• Mind what sits next to a hard run. Do not stack a hard run beside a hard bike session; separate your two hardest days so each is done on relatively fresh legs. An easy run the day after a long ride is fine; a threshold run is often not.
• Protect recovery. Because impact is cumulative, a run on already-fatigued legs carries more injury risk than the same run when fresh. Place your key run session where you have the least residual fatigue from cycling.

To see how a whole week of swim, bike and run actually stacks up — including where the runs and bricks sit — read the training week examples, and for arranging sessions around your real availability, how to structure a training week.

Exact numbers depend on your background and how your body tolerates impact, but the shape of a run-training week scales predictably with race distance. Treat this as a starting frame, not a prescription:

Race distance	Runs per week	Typical emphasis
Sprint	2–3	Consistency, easy running, one short brick
Olympic	3–4	Add a weekly long run and one quality session
Half (70.3)	3–4	Longer long run; run durability becomes the limiter
Full (140.6)	3–5	High easy volume; run economy and durability under fatigue

Notice that even at long-course distances the number of runs stays modest and most of them are easy — the extra work is mostly more easy volume and a longer long run, not more hard sessions. For full multi-week plans that put these into a day-by-day schedule, use training plans; this guide is about the run-leg logic those plans rely on.

Most run-training problems come from a handful of predictable errors:

• Running everything at the same medium-hard pace. The single most common mistake — it leaves you tired without being fit. Slow the easy runs down.
• Chasing mileage instead of consistency. A big week followed by an injury sets you back further than a series of modest, repeatable ones ever would.
• Ramping load too fast after a break. Fitness returns faster than tissue tolerance; start back conservatively even when your lungs feel ready.
• Skipping bricks. If the only time your legs meet "running off the bike" is on race day, expect the run leg to feel far worse than in training.
• Neglecting easy-day discipline. Turning recovery runs into moderate efforts quietly removes the recovery that makes hard days possible.
• Running through sharpening pain. Discomfort that changes your gait or worsens is a stop signal; a few days off is cheaper than months out.

Fix these and the run leg improves without any exotic session. Run often, keep most of it easy, protect one long run, rehearse running off the bike, and build the whole thing up gradually — the rest is detail you can add from the linked guides once the foundation is repeatable.