Five weeks before my second Ironman World Championship in Kona, I raced the Big Kahuna Half Ironman in Santa Cruz, California. I didn't taper for it. No reduced volume, no sharpening, no race-week rest. I showed up on the back of a full training week, raced it at Ironman effort, and finished in 4:19. Third overall out of a strong field.
That 4:19 told me more about my Kona readiness than any training session could have.
What a Build-Test Race Is
Most athletes categorize their races as A-races (the ones that matter) and B-races (everything else). The problem with this binary is that B-races don't actually serve a clear purpose. Athletes either race them too hard and compromise recovery for their A-race, or they race them too casually and learn nothing useful.
A build-test race is a third category. It has a very specific purpose: validate that race-specific fitness exists, in race conditions, without the taper that would mask underlying fatigue.
The rules are simple. Schedule it 5-6 weeks before your A-race. Race at half the A-race distance. Don't taper. Race at A-race effort, not A-race pace. Use the same nutrition, equipment, and protocol you'll use on race day.
The result tells you whether the engine is ready.
Big Kahuna 2013
I went into Big Kahuna 2013 on a week that included 15 hours of training. My CTL was climbing toward its pre-Kona peak. I was tired. This was the point.
The swim was 25 minutes. The bike was 2:20 at 261 watts normalized. The run was 13.4 miles at 6:36 per mile.
Every one of those numbers was directly relevant to my Kona plan. The swim told me my pacing was dialed. The bike at 261W told me my power target of 240W for the full Ironman was conservative but achievable. The run at 6:36 per mile off a hard bike told me my Kona run target of 6:50-7:00 per mile had real margin.
Most importantly, I did all of this without a taper. On fresh legs with a proper taper, the numbers would be even better. That meant the fitness wasn't just there. It was there with room to spare.
The HIM-to-IM Conversion
Here's where it gets useful. A half Ironman raced at Ironman effort gives you a direct conversion to your Ironman potential.
The conversion varies by athlete, by course, and by conditions. But for most age-group athletes, the relationship is roughly: add 20-30 seconds per mile to your HIM run pace for cool conditions, and add 45-60 seconds per mile for hot conditions like Kona.
My Big Kahuna run was 6:36 per mile. Adding 60 seconds for Kona heat predicted a Kona marathon at 7:36 per mile. My actual Kona 2013 marathon was 7:59 per mile, but that included the glute seizure at the start of the bike that compromised my entire race. In a clean race, the 7:36 prediction was probably close to my ceiling.
On the bike, the conversion is more straightforward. HIM at Ironman effort already tells you what your IM bike should look like. I biked Big Kahuna at 261W and planned Kona at 240W. The 21-watt difference accounts for the additional 2.5 hours of riding and the heat.
The point isn't precision. The point is that a build-test race gives you an evidence-based prediction instead of a hope-based one.
Why the "No Taper" Part Matters
If you taper for your build-test race, it stops being a build-test and becomes a regular B-race. The whole value is that you're testing race-pace ability under training fatigue.
When you're fresh and tapered, of course you can hit your numbers. The question is whether you can hit them when you're tired, because that's what your A-race taper is supposed to produce: the same fitness you're carrying now, plus the freshness of a proper rest.
If you can hit race-pace numbers under fatigue, you know two things. First, the fitness is real. Second, the taper will produce something even better. Both of those are confidence you can't get from a training session.
If you can't hit race-pace numbers under fatigue, that's also useful information. It means either the fitness isn't there yet (and you have 5 weeks to build it), or your A-race targets are too aggressive (and you have 5 weeks to revise them).
Either way, you're making decisions based on race-condition data instead of training-log optimism.
How to Schedule One
The ideal window is 5-6 weeks before your A-race. Closer than 4 weeks and you risk compromising the taper. Further than 7 weeks and the fitness snapshot is less representative of race-day fitness.
The distance should be roughly half the A-race distance. For Ironman, that's a half Ironman. For a marathon, that's a half marathon. For an ultra, scale accordingly.
The effort should be A-race effort, not B-race effort. You're not trying to PR the build-test. You're trying to simulate the physiological state of your A-race. If your Ironman bike target is 220W, ride the half at 220W, not at 250W.
After the build-test, you'll need 3-5 days of easy recovery before resuming training. This is not a taper. It's just letting the acute fatigue clear so you can get back to building.
What I Do Differently Now
Since Big Kahuna 2013, I've built a build-test race into every A-race season. For my athletes, it's a mandatory calendar artifact, not an optional extra.
The athletes who resist it most are the ones who say "I don't want to waste a weekend on a race I'm not going to PR at." That's exactly the mindset that makes build-test races so valuable. They force you to shift from "every race must be a PR attempt" to "some races are diagnostic tools."
The best race plan in the world is worthless if it's built on a fitness assumption that hasn't been tested. A build-test race tests the assumption. Five weeks out. Half distance. No taper. Ironman effort.
If the numbers come back clean, you go into your A-race with confidence backed by evidence. If they don't, you have 5 weeks to adjust.
That's not a wasted weekend. That's the most useful race of your season.
Want to work with me? I coach athletes from first-time Ironman to Ultraman.