You've signed up for your A-race 70.3. It's circled on the calendar in red. Training is going well. And then your running buddy sends a text: "Sydney Marathon is 10 weeks out — we should do it."
And now you're spiraling. Because on one hand, free speed. On the other hand, your coach's voice is echoing in your skull. So let's settle this — honestly, without the corporate liability hedging that most coaching articles hide behind.
First, Let's Understand What a Marathon Actually Does to You
Running 42.2km is not a long training run with a medal. It is a systemic assault on your body. Muscles, tendons, ligaments, immune system — everything takes a hit. The old coaching wisdom — one day of recovery per mile raced — puts your full return to hard training at roughly 26–28 days post-race. That's not being dramatic. That's biology.
Add in the pre-race mini-taper (5–7 days of reduced load so you don't destroy yourself on race day) and you're looking at a window of roughly five to six weeks carved out of your 70.3 build. For a 10-week gap, that leaves you about four weeks of quality, specific triathlon training before you start tapering again.
Four weeks. To rebuild swim fitness you let slip. To get your bike legs back. To start feeling like a triathlete again rather than a one-legged zombie with a foam roller obsession.
That's the math. Uncomfortable, isn't it?
The Case For Doing It Anyway
Before we drag the marathon through the mud entirely, let's be fair — because there are legitimate reasons experienced athletes build marathons into their season.
1. It sends your aerobic engine to graduate school. The sheer volume of running during marathon prep — weeks of 60–80km — forces cardiovascular adaptations that years of triathlon-specific training sometimes can't replicate. Your fat oxidation improves. Your lactate threshold climbs. Your mitochondria multiply like they're on commission.
2. Mental toughness is a real training variable. There's something about suffering through the wall at kilometer 35 that recalibrates what "hard" means. Athletes who've raced marathons often report that the 70.3 run leg — even after a 90km bike — feels mentally manageable by comparison. You've already been to that dark place. You know the way out.
3. Confidence in the distance. A lot of first-timers want proof they can run a half-marathon off the bike. Ironically, many find that running a full marathon a few months prior gives them that psychological bedrock — even if physiologically, the triathlon run is a completely different animal.
4. Testing nutrition under pressure. Race-day fueling is a skill. A marathon gives you a 4+ hour window to trial your gels, hydration strategy, and sodium intake under race conditions. That intel is genuinely useful for your 70.3.
The Case Against (And Why Coaches Lose Sleep Over This)
Here's where we get real.
The injury risk compounds exponentially. Marathon training is high-impact and high-volume. Stack it on top of a triathlon build — where you're already swimming, biking, and running — and you are playing injury roulette with loaded chambers. Bones and tendons adapt slower than your cardiovascular system. Your lungs might be fine. Your tibias and Achilles are filing formal complaints.
Triathlon-specific fitness doesn't pause for your marathon ego. Every week you spend logging marathon miles is a week your swim efficiency is degrading and your cycling power is going stale. You can maintain with minimal volume, but "maintain" and "build" are not the same word. Your 70.3 competitors who didn't run a marathon are in the pool and on their TT bikes while you're cramming miles in the dark.
The aerobic plateau problem. Research suggests most physiological stimulus from long runs occurs between 60 and 90 minutes. After three hours, the marginal gain shrinks toward zero while injury risk keeps climbing. Put bluntly: you don't need to run 42.2km to get the aerobic benefit. A well-executed 28km long run gets you most of the adaptation at a fraction of the cost. The marathon distance becomes a vanity exercise — which is fine, but let's call it what it is.
The recovery hole is real and it will wreck you. Ten weeks sounds like enough buffer. It isn't. You'll spend weeks 10–8 tapering and racing. Weeks 8–6 recovering, shuffling around like you've been hit by a bus. By week 6, you're just getting your legs back. And now you have to cram bike fitness, swim fitness, and race-specific run work into a four-week block before your 70.3 taper kicks in. Good luck.
The Sydney Factor: When Race Prestige Breaks the Spreadsheet
Let's address the elephant in the room — or more precisely, the kangaroo on the starting line.
Some marathons aren't just races. They're bucket list events. The Sydney Marathon is now a World Marathon Major. Tokyo, Berlin, Boston, London, Chicago, New York — and Sydney. Running one of these isn't just about the training stimulus. It's about crossing a bridge with fireworks going off and the Opera House in the background. It's a life moment.
And here's where we acknowledge that triathlon training isn't the only thing that matters. If you've been chasing a World Major entry for two years and you finally get it — 10 weeks before your 70.3 — the honest answer might be: do the marathon and adjust your expectations for the triathlon.
That's not failure. That's being a human who does endurance sport for the experience of it, not just the finish times. Lower the pressure on your 70.3, treat it as a strong B-race, and don't stand at the start with expectations set during peak training. The race will still be there. Sydney won't always be on your doorstep.
The key is honesty with yourself about which race is actually your A-race. You cannot optimize both. Pick one. Race the other for joy.
The Decision Framework: Ask Yourself These Four Questions
Before you RSVP to your own physical destruction, run through this checklist:
1. How experienced are you? If this is your first or second 70.3, skip the marathon. You don't have the training base to absorb both. If you're an experienced triathlete who regularly handles 15+ hour training weeks without breaking down, the calculus changes.
2. What's your injury history? If your Achilles has ever been a problem, or your IT band has its own personality, the marathon is a grenade with the pin half-pulled. Walk away.
3. Can you genuinely treat the marathon as a B-race? And we mean genuinely — not "I'll take it easy" followed by running a 10-second negative split because the crowd was electric and your ego took the wheel. If you can't commit to a controlled, honest race effort (think: conversational pace, no heroics), you will dig a recovery hole you won't climb out of in time.
4. Is this marathon special enough to justify the tradeoff? A local community marathon to "test your fitness"? Hard pass. A World Major you've been chasing for three years? That's a legitimate counter-argument to everything above. Know the difference.
If You Do Both: The Survival Protocol
You've decided you're doing both. Fine. Here's how to not implode:
- Run the marathon honest and controlled. Not slow — honest. Don't blow up chasing a PB. Finish feeling like you could run another 5km, not like you need a stretcher.
- Spend the first week post-marathon doing nothing hard. Easy swim, easy bike, easy walk. Let your body start the repair process without interruption. This is not optional.
- Return to training progressively in week two. Moderate swim and bike sessions. Short, easy runs. No intervals. No ego.
- By weeks three and four, resume structured training. This is your brief window for quality. Make it count: race-pace bike intervals, brick sessions, open-water swims.
- Execute a standard 70.3 taper from week four onward. You won't be at your absolute peak. You will be fit enough to race well if you've been smart.
- Recalibrate your 70.3 goal. If you were eyeing a PB, soften that expectation. If you were hoping to finish strong and enjoy the race, you'll probably nail it.
The Bottom Line
Running a marathon 10 weeks before a 70.3 is not smart training. It is, however, sometimes worth doing anyway — and those are two different things.
If your motivation is "it'll make me faster," the evidence mostly disagrees. If your motivation is "this is Sydney Marathon and I've been chasing this entry for years," then you're not making a training decision — you're making a life decision. Those are allowed.
Just don't lie to yourself about which category you're in. And whatever you decide, do not — under any circumstances — go out at race pace in the first 10 kilometers of that marathon because you're feeling fresh and the crowd energy is unreal.
That's how you end up DNF'ing both races and spending your 70.3 weekend watching from the sidelines, icing your knee, and reconsidering all your choices.
You're better than that. Run smart. Race hard. Do it on purpose.
