Combining a Marathon and a Triathlon in One Season

A marathon personal best in spring, a first middle-distance triathlon in summer — that is the most common double ambition among endurance athletes, and it is achievable. What is not achievable is doing both at peak level in the same year. Plan the combination properly and you lose less form than you would expect while gaining a huge aerobic base. Plan it badly and you arrive in June with a tired marathon in your legs and a half-trained bike split on race day.

Why the combination makes sporting sense

Marathon and triathlon share roughly 80 percent of their training foundation: aerobic capacity, fat metabolism, running economy, load tolerance. A marathon block builds exactly the base an Olympic or middle-distance triathlon profits from — provided the bike training continues in reduced volume. In the other direction, a triathlon block adds swim and bike volume that raises cardiac output without extra impact load on knees and Achilles tendons.

The real gain lies in the distribution: instead of running two separate twelve-week builds, you create a continuous load curve across seven to nine months. That is the more favourable route in training terms, because fitness (CTL) does not restart from zero twice. The prerequisite is that you steer the load via Training Stress Score rather than by feel — otherwise three sports quickly add up to a curve that climbs for four weeks and then collapses.

The ground rule: one A-race, not two

The most important decision, and the one most often dodged: one race is the A-race, the other is a B-race. The A-race gets full periodisation, a genuine taper and the entire goal setting. The B-race is raced off ongoing training — no build-up, no recovery week beforehand, and with the expectation that your legs are tired from training.

In practice: if a marathon target time is the priority, the marathon is the A-race and the triathlon is a test under load. If age-group placing or qualification is what counts, the triathlon is the A-race and the marathon becomes a long training run with a bib — with an adjusted target time, not a personal best attempt.

Two season models that work

Two sequences have proven themselves. Both require enough time between the races for a real recovery and rebuild phase.

• Spring marathon → summer triathlon. The marathon in April or May is the A-race, followed by two weeks of recovery, then eight to ten weeks of building for the triathlon in July or August. This is the more robust model, because the marathon block lays the aerobic base and the triathlon block only adds swim and bike stimuli on top.
• Summer triathlon → autumn marathon. The triathlon in June or July as the A-race, then a transition week, then twelve weeks of marathon building for October. More demanding, because marathon preparation falls in the hottest period and running volume has to be rebuilt after the triathlon first.

The reverse order with a short gap is not recommended: marathon in autumn and a triathlon three weeks later, or vice versa. That is not a season model, it is a load test with an entry fee.

How much time should be between the races?

The rules of thumb from practice: after a marathon you need at least six weeks before the next race at Olympic distance, better eight to ten. After a middle-distance triathlon, allow eight to twelve weeks before a marathon. The reason is not recovery alone but the specific volume: a marathon demands long runs of 30 to 35 kilometres, and those cannot be caught up in four weeks.

Recovery time after a marathon is routinely underestimated. Muscle is loadable again after two weeks; tendons and neuromuscular coordination take longer. Swimming is the ideal re-entry in that phase: no impact load, good circulation, no risk to the structures involved. Cycling follows after about ten days, short easy runs after two to three weeks.

The weekly structure: three sports, seven days

The core of the problem is not volume but distribution. Three sports in one week means three sources of fatigue, and the sum counts — not the individual session. A typical build week in a combination block looks like this:

• Monday: rest or 30 minutes of mobility. No training. The day is part of the plan, not a sign of weakness.
• Tuesday: run with a pace stimulus. Threshold run or intervals, 60 to 75 minutes. The key quality session of the week, so it goes on fresh legs.
• Wednesday: swim, 45 to 60 minutes. Technique and volume, no hard set. Swimming is the joint-friendly buffer between running stimuli.
• Thursday: bike, 60 to 90 minutes. Easy to moderate, with a few longer blocks at tempo. Optionally with a short 15-minute brick run.
• Friday: strength, 30 to 40 minutes plus an optional short easy run. With three sports, strength training is not a luxury — it keeps tendons and trunk stable, which are the first things to break down otherwise.
• Saturday: long run, 90 to 150 minutes. Easy pace, this is the load-bearing session for both goals.
• Sunday: long ride, 2 to 3.5 hours. Easy, with fuelling practice. Then a 10 to 15-minute brick run to rehearse the transition.

That is eight to nine sessions and roughly eleven to fourteen hours per week — a lot, but no more than a pure marathon block with strength training. What matters is that the long run and the quality session never fall on consecutive days. If you put both at the weekend, you have already lost the rest of the week.

What to cut when time gets short

Most athletes cut in the wrong order. Swimming goes first, then cycling — and what remains is a marathon plan with two bike sessions that calls itself a triathlon. A better priority order:

• Untouchable: long run, running quality session, one long ride. These three sessions carry both goals.
• Reducible: second ride down to 60 minutes, swimming down to two 40-minute sessions. Swim technique degrades more slowly under low volume than running economy does.
• Cut first: the third short ride, extra strength sessions, all optional brick runs beyond one per week.

Anyone with fewer than ten hours a week should prioritise honestly instead of half-doing both. A well-trained marathon with two swims and one ride per week beats a mediocre triathlon with a mediocre run. On how to increase volume sensibly in the first place, increasing training volume is the companion piece.

Bike kilometres do not replace running kilometres

The most common fallacy in the combination: "I ride a lot, so I am aerobically fit — the marathon will come by itself." Aerobically yes, running-specifically no. Cycling loads neither the same tendons nor the same muscle coordination as running. The impact load per stride is missing, and with it the stimulus for bone density and tendon stiffness. Reduce running volume in favour of the bike and you lose exactly the adaptations that matter in a marathon.

The reverse also holds: running volume does not replace bike training. The specific position on the bike, the cadence and the muscular endurance of the thighs cannot be built with runs. That is why at least one long ride stays in every combination block, including the peak marathon week.

Recovery and load management

With three sports, subjective feel is a poor advisor. An athlete who feels "just tired legs" after a long ride often carries a higher total load than after a hard tempo run — and then trains too hard the next day. This is exactly where the CTL, ATL and TSB model helps: fitness, fatigue and form are calculated from all sessions together, regardless of sport.

Practical orientation for a combination block: form (TSB) should sit between −10 and −20 in build weeks, rise above −5 in recovery weeks, and reach values around +5 to +15 before the A-race. Anyone who stays below −25 permanently stops adapting and just accumulates fatigue. Details on interpretation are in CTL, ATL and TSB.

Sleep is the second control factor. In combination blocks of eleven to fourteen hours per week, sleep is not a lifestyle topic but a training prerequisite: sleeping seven hours while training three sports is training against your own regeneration. The link between sleep duration and injury rate is consistent across several studies — below seven hours, risk rises markedly.

The five most common mistakes

• Planning two A-races. The classic: marathon in spring for a personal best, triathlon in summer for a placing. Both at once does not work — periodisation can only point at one peak.
• Too short a gap. Four weeks between marathon and triathlon is not a recovery phase but a race on residual fatigue. Six weeks minimum, eight is better.
• Starting swimming in summer. Swim technique takes weeks, not days. Start front crawl in May and race in July and you swim the middle distance with technical deficits that cost the entire race.
• Skipping brick runs entirely. The switch from bike to run is its own skill. Without regular bricks, the transition costs two to four minutes on race day — more than the training would have cost.
• Dropping strength work because of "no time". With three sports, strength is the binding agent. Two short sessions per week keep tendons, trunk and hips stable — precisely the structures that overload first in combination blocks.

How Peakora plans the combination

Peakora's engine can map the season as a whole: you enter both races with date and priority, the A-race gets full periodisation including the taper, the B-race is flagged as a test rather than a peak. The weekly structure then distributes swim, bike and run stimuli so that no two hard sessions collide and total load across all sports runs along a single curve.

The practical benefit shows up after unplanned breaks: if a week is lost to illness, the engine shifts the build instead of tearing gaps into it — and it recognises when form is already too deep in the red before the triathlon. Athletes who run the combination without load management only find out on race day. Terms like periodisation, brick training or TSB are explained in the training glossary; the periodisation logic for the marathon sits in the marathon training section and the three-discipline side in triathlon training.

Frequently asked questions