Leave less than 16 weeks between a marathon and your first Ironman, and the math already works against you. It’s not that your legs are still trashed. It’s that your fitness score can’t rebuild fast enough to hit a race-ready number by the time you toe the line.
Here’s the number that matters: safe fitness rebuild tops out around 5 to 8 points a week. A marathon taper plus recovery block can eat 6 or 7 of those weeks before your Ironman-specific build even starts. That gap is exactly where the popular “16-week rule” comes from. Almost nobody shows the arithmetic behind it.
Should You Run a Marathon Before an Ironman? Here’s the Math
Every triathlon coach has an opinion on this. Few show the numbers behind it. So let’s build them from the ground up.
Your fitness score (CTL) is a rolling 42-day average of your daily training load, weighted so recent days count more than old ones. In short: it’s your engine size, built up over roughly six weeks of consistent work.
Your fatigue score (ATL) works the same way, but over just 7 days. Translation: it’s how tired you are right now, separate from how fit you are overall.
Your form score (TSB) is fitness minus fatigue. Positive means you’re rested. Very negative means you’re cooked. Coach Joe Friel’s scale puts race-ready form between +5 and +25. Below -10, you’re stuck in what he calls the Grey Zone, tired enough that racing well gets hard.
None of these numbers move like a bank statement, where yesterday’s deposit shows up today at full value. They decay slowly, which is exactly why a marathon’s damage doesn’t just subtract and disappear. It lingers for weeks.
See the dip in the middle. That’s not a mistake in the plan. It’s the unavoidable cost of tapering for one race and recovering from it before starting another build.
What a Marathon Actually Costs You in CTL and TSB
A marathon-specific long run (16 to 20 miles) generates roughly 150 to 250 TSS, a single session’s training-load score. Race day itself, or a hard 20-plus mile effort, can push 250 to 350 TSS. Add it up over a full block and you get weekly totals from 250 to 400 TSS for a first-timer. Advanced runners chasing a big goal can hit 550 to 700-plus.
That’s a heavy, useful load. It’s exactly what builds your fitness score during the marathon block. The catch comes at the taper.
Tapering can cost up to 10% of your peak CTL before the gun even goes off. Think of it like maxing out a credit card for a big purchase, then making minimum payments while you recover. The marathon “purchase” buys you race-day freshness. But now you owe weeks of rebuilding before you can spend that fitness on anything else, including your Ironman.
After the race, most runners need real easy time. Pete Pfitzinger’s widely used heuristic is one easy day for every mile raced, about 26 days, or roughly 3.7 weeks, before resuming hard structured training. During that stretch your weekly load sits well below marathon-peak levels, so your fitness score keeps sliding even as you feel better.
Your legs recover faster than your fitness score does.
Interestingly, the research backs up the “feel better” part. In a study of recreational runners, VO2max changes one week after a marathon were “possibly trivial,” and running economy had mostly bounced back. Translation: your aerobic engine is basically fine within about 7 days. But a separate study found knee-extensor strength was still tied to soreness a full 24 hours post-race. Your engine heals fast. Your legs and your fitness score take longer.
The Ironman CTL Targets That Actually Matter (By Finish-Time Goal)
Age-group data shows a real, measurable link between race-day fitness score and Ironman finish time. It’s not a theory. It’s a pattern you can plan against.
If your goal is sub-10 hours, showing up at 90 CTL because a poorly timed marathon ate your rebuild weeks isn’t a small miss. It’s a 30-point gap, and 30 points takes 4 to 6 more weeks to close at a safe ramp rate.
Does Marathon Fitness Transfer to the Ironman Run Leg?
Partly, and the gap is bigger than most athletes assume. A controlled comparison of 15 marathoners and 15 Ironman triathletes found something telling. Marathoners trained just 5.2 hours a week versus 12.9 hours for triathletes. But marathon training was far more intense per hour, at 99.3 load units per hour versus 65.8 for triathletes. Marathon training is a short, sharp stimulus. Ironman training is a long, broad one. They’re not the same tool.
The heart rate story makes this concrete. Standalone marathoners run at 85 to 90% of max heart rate for most of the race. Triathletes running the marathon leg off the bike, at a matched effort, typically only reach 75 to 80% of max heart rate. That’s because the cardiovascular system is already fatigued from six-plus hours of swim and bike. Same distance. Different demand entirely.
A fast open marathon says your engine works. It says almost nothing about how that engine performs after 112 miles on a bike.
Where the 16-Week Rule Actually Comes From
Here’s the worked example nobody publishes. Compare two athletes with an identical post-marathon fitness score of 65, both aiming for a sub-10-hour Ironman that needs roughly 120 CTL on race day.
| 12-week gap (too tight) | 20-week gap (works) | |
|---|---|---|
| Weeks lost to marathon taper | 2 | 2 |
| Weeks lost to easy recovery | 4 | 4 |
| Weeks left for Ironman-specific rebuild | 6 | 14 |
| CTL gained at 6 points/week | +36 | +84 |
| Projected Ironman race-week CTL | ~101 | ~149 |
| Hits the ~120 CTL target? | No | Yes, with room to taper |
The 12-week athlete arrives 19 points short of goal. The 20-week athlete arrives with fitness to spare, enough to taper properly and still land in Friel’s Freshness Zone.
Take a triathlete I’ll call Priya, 34, training for her first Ironman. She ran a road marathon in early June, finishing in 3:42, then lined up for an Ironman just 13 weeks later. Her post-marathon fitness score sat at 68. Rebuilding at a realistic 6 points a week, she reached the start line around 79 CTL, nowhere close to the 100-plus mark tied to her sub-11-hour goal. She finished the race, but her run split fell apart over the final 10 miles, and she added 90 minutes to her target time.
Spring Marathon, Fall Ironman: Does Your Calendar Actually Work?
The industry guidance is a hard floor of 16 weeks between a standalone marathon and a full Ironman, versus 10 to 12 weeks for a 70.3. That’s not a random number. It’s the shortest gap that covers taper loss and recovery decay while still leaving enough weeks to rebuild at a safe ramp rate.
There’s a training-style conflict layered on top of the math. A marathon block wants 4 to 6 runs a week and multiple 20-mile long runs. An Ironman block wants roughly 3 runs a week, long runs capped by time rather than distance, plus regular brick sessions off the bike. You can’t run both programs at once without one undercutting the other.
This is exactly the kind of planning problem that’s easy to get wrong on a spreadsheet and easy to catch with real data. AthleteOS’s Performance Management Chart tracks your fitness, fatigue, and form scores from your actual Garmin or Strava history. It then projects that curve forward through a marathon taper and into an Ironman build, using your own ramp-rate capacity instead of a generic 6-points-a-week assumption. If your specific spring-marathon-to-fall-Ironman gap won’t get you to a race-ready number, it says so in plain language. That happens before you’ve committed to a race calendar that can’t deliver your goal time.
Understanding the fitness, fatigue, and form math behind the Performance Management Chart is the foundation for this whole decision. Pair it with how training stress score compares to heart-rate-based load if you’re stacking swim, bike, and run stress into one weekly number. And if your aerobic base is the real question mark, aerobic decoupling will tell you whether your engine, not just your calendar, is ready for race day.
If you want AthleteOS to run this projection against your own training history, start a free account and connect your Garmin or Strava data. The calendar conflict, if you have one, shows up automatically.