How to Build a Training Plan When You Have Two Races Close Together
by The Next Race
One race is a target. Two races is a season.
Most training advice is built around a single peak. You build, you taper, you race, you recover. It's clean. It's logical. It works. But it doesn't reflect how most triathletes actually race — with a spring race, a summer race, and maybe a late-season one thrown in because registration was open and optimism was high.
Managing two races that are close together — four to eight weeks apart — is one of the most common planning challenges in age-group triathlon. It's also one of the least written-about. Here's how to think about it.
First: decide which race actually matters
This sounds obvious. It isn't. A lot of athletes treat both races as A-races, which means they peak for neither. You need to be honest about priority before you build anything.
The A-race is the one you're targeting for performance — a goal time, a qualification slot, a distance PB. The B-race is a training race. You go, you race it competitively, but you don't taper extensively for it and you don't fall apart if it doesn't go perfectly. It serves your A-race preparation, not the other way around.
Once you've decided which is which, the planning becomes much more straightforward.
The four to six week gap
If your races are four to six weeks apart, the B-race typically falls somewhere in the middle of your build phase. The week before the B-race, you do a mini-taper: reduce volume by about 30%, keep a couple of short sharp sessions in, and go into the race feeling fresh but not flat.
Race the B-race. Treat it as a hard training day with a medal at the end.
The week after, you take one easy recovery day — not a week, not two weeks, one day — and then you return to training. You've just done a race-simulation brick at full distance. That's incredibly valuable. Use it.
The final two to three weeks before your A-race is your real taper. You're going into it with more race-specific fitness than you'd have from a single peak build, which is the whole advantage of the two-race approach.
The eight week gap
Eight weeks gives you more room. The B-race can sit at the end of a build block rather than the middle of it, which means you can legitimately taper for it without disrupting the A-race preparation.
The structure looks like this: build hard through week four, mini-taper in week five, race the B-race in week six, recover in week seven, then do a final sharp two-week push into the A-race taper.
You won't be at peak fitness for the B-race — you're not supposed to be. You'll be fatigued from four weeks of hard training. Don't use that as a reason to go conservative; use it as a reason to practise racing under fatigue, which is a skill in itself.
What to protect
The long ride. Whatever else shifts in the weeks around your B-race, keep your long rides happening. Bike fitness takes the longest to build and the longest to lose. Drop a swim session before you drop a long ride.
Your sleep. Racing fatigues you in ways that are different from training fatigue — emotional energy, travel, disrupted sleep, pre-race nerves. Plan for that. Don't schedule a hard track session the morning after your B-race because you think you can handle it.
The transition brick. If anything, do more of these in the weeks between your two races. You've just raced. You know exactly what your weaknesses are. The window between races is the best time to address them with targeted, specific sessions.
The biggest mistake
Using the B-race as an excuse to reset. Athletes finish the B-race — especially if it goes well — and subconsciously treat it as the culmination of a training block rather than the midpoint of one. They rest more than they should. They let the urgency of training fade. They arrive at the A-race underprepared.
Your B-race is a data point. A useful, enjoyable, legitimately motivating data point. But it's not the finish line.
Using your data to make this easier
The hardest part of two-race planning isn't the structure — it's calibrating the effort. How hard should you go at the B-race? How should you adjust the taper? How much recovery do you actually need?
The answer is in your history. Athletes who track their training load and recovery over time can see exactly how long it takes them to bounce back from a race. They can see what a 30% volume reduction actually does to their fitness metrics. They can make informed decisions instead of guessing.
If you don't have that data yet, now is the time to start building it. Every race you do, every taper you navigate, every recovery week you track — that's the database that makes the next season sharper.
Two races is better than one. You just need to plan them that way.