Structuring Your Season: The Science of A, B, and C Races
01 | The Colour-Coded Calendar
Every January the same spreadsheet lands in my inbox. It is colour-coded. The A race is circled in red, late August, a 70.3 in Germany or Spain that the athlete has been thinking about for two years. Leading up to it: a local 10k in March, a sportive in April, a sprint triathlon in May, two Olympic distances in June and July, and a half-distance in early August described in the email as "a B race I'll use as a training day." The athlete is clearly intelligent and has put real thought into this. They see a season with variety, pressure, and regular fitness tests. When I look at the same calendar, I see six weeks of compromised training wrapped inside what should be a sixteen-week build.
The reasoning is understandable. Racing forces effort that training rarely fully matches. Every competitive event is a hard session, so a calendar dense with events is a calendar dense with hard sessions, and hard sessions produce adaptation. That logic breaks down at the biology. Your body does not treat a race as a hard training session with better catering. It treats it as a physiological emergency, and the recovery debt it generates is categorically different to what a training day costs, regardless of how similar the numbers look on paper. Data captures cardiovascular load. It says almost nothing about the structural damage, hormonal disruption, and neurological fatigue a race generates. Relying on Training Stress Score to judge how much a race costs you is the most common reason well-intentioned season plans fall apart in the final build.
The fix is not to race less. It is to race deliberately, with a clear-eyed accounting of what each event costs and what you expect to get back from it.
02 | What Racing Actually Costs
A hard four-hour brick session might generate 250 TSS. A 70.3 generates 300 to 400. The jump looks manageable. It is not. In training, even during your hardest interval sets, micro-recoveries exist. Eight minutes at threshold, two minutes easy. Those gaps allow partial clearance of metabolic byproducts. In a race there are no gaps. You are locked into continuous, uninhibited metabolic expenditure from the gun, exhausting primary muscle fibres and forcing recruitment of larger, less efficient motor units just to maintain velocity. Your body is not working through the mild acidosis of a hard interval. It is submerged in it.
Running compounds everything. Every landing during the run leg is an eccentric load: muscles lengthen under tension to absorb impact, causing micro-tears in the sarcomeres. Exercise physiologists calls this Z-line streaming. This is actual tissue damage, and it cannot be trained through. The triathlon run is not the same problem as a standalone run and the eccentric load of the run leg lands on muscles that have already been working for two or three hours. The structural damage is multiplicative, not additive.
Central Nervous System fatigue is what most self-coached athletes fail to account for. CNS fatigue can persist three to five days after a short race and several weeks after a full-distance event. It is not tiredness that sleep fixes. It is a reduction in neural drive to the working muscles: the signal from brain to leg is weaker than normal. Muscles may be fuelled and structurally repaired, but the engine is misfiring. This is why athletes feel flat in the week after a race even when they slept well and ate correctly. Form under fatigue breaks down before fitness does, and the neurological component of that degradation takes longer to resolve than any physical marker suggests.
The hormonal cost is the one that lands silently. Racing triggers a cortisol response that mobilises energy through catabolic pathways, breaking down tissue rather than building it. Anabolic hormones are often suppressed or blunted for days afterwards. Race a B event hard on a Saturday and you spend the following week in a mild but real catabolic state. On its own, manageable. Against the backdrop of a forty-hour working week, four hours of sleep, and a training plan that does not account for any of this, it accumulates. Your body runs a single stress account. Life stress, training stress, and racing stress all draw from the same pool, and the age-grouper's pool is already half-full before the race gun fires.
03 | The Framework
The A, B, C system is not complicated. Its value depends entirely on how strictly you apply it, because most athletes assign priority labels to races and then prepare for all of them the same way. The label only matters if it changes what you do in the two weeks before and the ten days after.
An A race is the event your season is built around. One, occasionally two per year. You arrive fully tapered and physically primed to produce the best performance your training allows. The preparation window costs four to six weeks of total training time when you include the taper going in and the recovery coming out. That is the price. If an event is not worth six weeks of training time, it is a B race regardless of how important it feels.
A B race is a test event. You go to validate fitness, practise execution under pressure, test nutrition logistics, or qualify for something larger. You arrive carrying some fatigue because you do not taper fully: three to four days of reduced volume rather than two weeks. You race hard and accept that the performance is not your absolute ceiling. Athletes who take the full week easy before a B race consistently report heavy legs on race morning. The body has started adapting to rest but has not yet reached the performance peak side of that adaptation curve. A full taper requires ten to fourteen days to land correctly. Three easy days before a B race is a reduction in fatigue, not a peak, and that is the correct goal.
A C race is a training session. You do not taper. You do not alter the week. The race replaces whatever session it falls on — your long run, your brick, your Saturday ride — and you approach race morning as you would approach a session morning. Eat normally, warm up properly, execute well, go home. The C race carries a biological cost like any hard session, and you account for it accordingly: 24 to 48 hours of easier training in the immediate aftermath, then back to the plan.
04 | Racing as a Training Tool
There is a version of the A/B/C framework that treats lower-priority races as biological costs to be minimised. That approach misses what races are genuinely good for.
No training session fully replicates race conditions. Open-water navigation under pressure, pacing decisions in the presence of competition adrenaline, transition execution when the legs have already been working. These are skills, and skills develop through repetition in the actual environment. An age-grouper who arrives at their A race having done two or three training races in the preceding months will execute that race differently to an equally fit athlete who has trained the same hours but raced once. The fitness may be identical. The decision-making will not be.
Races also expose weaknesses that training conceals. A nutrition plan that works on solo training rides has never been tested against the metabolic context of a race start, elevated adrenaline, and ninety minutes of effort above your training norm. A sprint triathlon six weeks before your A race tells you more about your fuelling gaps than six weeks of interval sessions, and it tells you while there is still time to act. Running well off the bike in a race is a different problem to running well off a solo brick, and a B race is where you find out whether you have solved it.
Racing with training fatigue in the legs, at C events, also develops something specific: the capacity to produce quality effort when the body is not fresh. Long-course racing happens in a state of accumulated fatigue by definition. An athlete who has practised executing well while tired is training a quality that no fresh-legs session touches. An athlete who only ever races on a taper is training their body to perform in conditions they will not encounter during the race they actually care about.
Use this practically. For a September Ironman, a 70.3 in late June is the natural B race: far enough out that recovery does not compromise the final build, close enough that race-specific adaptation carries through. An Olympic distance in April or May works as a C race — short enough that the structural damage is minimal, hard enough to develop top-end speed that long aerobic training does not access. A standalone running race in late autumn or winter, treated as a C event, keeps race sharpness during the off-season while the periodised structure resets for the following year.
05 | What the Weeks Actually Look Like
The framework only has value when it changes specific behaviour, and the most important behaviour it changes is what happens on the Monday to Saturday before each race.
For an A race taper, volume drops 40 to 60 per cent across the final fourteen days, with an exponential rather than linear reduction. Most of the volume cut happens in days one to seven; the final week is lighter still but retains intensity. Short, sharp efforts at race pace, a few minutes per discipline, are kept in the schedule through the final week. Removing intensity during an A taper is the most common mistake athletes make. Blood plasma volume and the neuromuscular patterns that race pace demands both degrade when intensity disappears for ten days. Athletes who do nothing but easy aerobic work in the final fortnight frequently feel flat and sluggish on race morning despite being well rested. The fatigue is gone. The sharpness went with it.
For a B race, the week before looks roughly like this. Monday and Tuesday, normal sessions at normal intensity. Wednesday, moderate volume with no high-intensity work. Thursday, a short easy spin and a thirty-minute easy run at most. Friday, rest or a light swim. Saturday, race. The recovery on the other side takes three to five days for short-course events, five to seven days for a 70.3, and two to three weeks of genuinely reduced load after a full-distance. These are not conservative estimates. The common pattern is to feel surprisingly good on day two post-race — what I call the false dawn — and interpret that as evidence of complete recovery. Inflammatory markers often peak 24 to 48 hours after a race. What feels like recovery on Tuesday morning is the eye of the storm. The secondary wave of immune suppression and neural fatigue hits days three to five, and the athlete who launched into a threshold session on Tuesday afternoon will be wondering what happened by Thursday.
For a C race, the week is a normal training week. Do not skip your Thursday quality session because there is a sprint triathlon on Sunday. The race replaces your long run or your brick, and the following Monday is easy. That is the complete protocol.
06 | Calibrating for Your Volume
The A, B, C framework developed in professional coaching environments where athletes train twenty or more hours per week. Applying it without adjustment to an age-grouper on eight or ten hours introduces errors in both directions.
At eight to ten hours per week, the aerobic base is smaller and metabolic efficiency is lower. After a hard C race, the body cannot clear metabolic waste at the rate a professional athlete can, because the mitochondrial density and enzyme systems that support faster recovery are built over years of training volume. A sprint triathlon that a high-volume athlete absorbs in 48 hours may require four days of lighter training for someone on ten hours per week. Treat all races as B races during the early years of structured training. The three-day recovery protocol applies even to short events.
At fifteen or more hours per week, the risk runs in the opposite direction. A high-volume athlete generates enough race-day power to cause genuine structural damage in a sprint event, particularly on the run. The temptation at C races is to race harder because the fitness is there, which adds a recovery cost that was never in the plan and defeats the purpose of the C race designation entirely. The discipline required at a C event is constraint: execute the race properly, do not get drawn into an ego battle with someone who tapered for this race when you did not.
Masters athletes training through their forties and beyond need a further modification. Recovery from racing slows regardless of training volume once you are past forty-five, and the immune suppression window after hard events extends. Add a day to every standard recovery estimate and be genuinely conservative about how many B races sit in a single season. One A race and two B races across a calendar year, with everything else treated as C events or removed, produces better racing at the events that matter than an ambitious calendar does.
07 | Just Another Race
There is a predictable psychological trap at the A race, and the season structure itself creates it. You have circled the date for months. You made sacrifices for it. By the time you arrive, the race has accumulated enough psychological weight to distort your decision-making on the day.
My mentor and legendary coach Brett Sutton's framing for this is JAR: Just Another Race. It is not an instruction to be indifferent to the outcome. It is an instruction about cognitive approach. Treating an A race as categorically different from every other race tends to produce exactly the decisions you are trying to avoid: going out too hard in the swim because this is the one that matters, abandoning a pacing plan when conditions are not what you expected, failing to adjust to what the day actually presents because too much has been invested in what you planned for. The athlete who executes intelligently under imperfect conditions extracts more from the race than the athlete who chased a specific time and fell apart at kilometre thirty of the run.
The JAR mindset also reframes what happens if the race does not go as planned. A season built entirely around one central event generates all-or-nothing thinking about the outcome. A season built properly around A, B, and C races has provided a dozen moments of meaningful progress before the start line. You have raced a 70.3 six weeks out and corrected a fuelling problem. You have done a sprint in May and verified the top-end speed is there. You have learned something at each event. The A race is the culmination of accumulated evidence, and it should be raced with the confidence that comes from that evidence rather than the anxiety that comes from treating a single day as the only verdict on months of work. That quiet certainty is worth considerably more on race morning than any motivational framework.
08 | Building the Calendar
Start from the A race and work backwards. One, occasionally two per year, spaced to allow a full build and full recovery. Fifteen to twenty-two weeks is the effective building window. Below fifteen weeks you are compressing the adaptation timeline in a way that caps what is achievable. Beyond twenty-two weeks without a structured recovery period, adaptation quality drops as accumulated fatigue suppresses the training stimulus rather than responding to it. Fitness builds during recovery, not during load, and a block that never fully recovers is a block that never fully adapts.
Place B races six to eight weeks before the A race where course profiles allow. A 70.3 in that window before a full-distance race is close to a template: far enough out that recovery does not compromise the final build, close enough that race-specific fitness and execution sharpness carry through. An Olympic distance four to six weeks before a 70.3 works on the same logic. These are not rough guidelines. They are the windows that give you enough time to act on what the B race reveals.
C races can sit anywhere in the build, but use them sparingly. Every race, regardless of its label, carries a biological cost. One sprint triathlon mid-build, treated correctly with no taper and honest recovery, is a useful training stimulus. Three sprint triathlons across an eight-week build, each done with increasing competitive investment, turns the build into a racing season and the A race into a tired conclusion. The plateau that follows overracing is harder to diagnose and fix than most athletes expect, because it does not feel like overtraining. It feels like inconsistency, and the response is usually to train harder rather than race less.
Keep the calendar in pencil. A plan that cannot be adjusted is a liability. If a B race reveals a problem you did not know you had, the following six weeks need to address it, and that may mean compressing or removing a planned C event. If you are carrying more fatigue than expected at week ten, the B race expectations adjust accordingly. The time-crunched triathlete does not have enough training time to waste any of it recovering from races that were not earning their place.
If you want a season architecture built around your actual schedule and race calendar, Sense Endurance Coaching is built around exactly that. We plan the A, B, and C structure together, set the execution protocols for each event, and adjust when the plan meets reality.
If you want the periodised framework without one-on-one coaching, the Sense Endurance training plans are built on the same principles. The race structure is in the plan. The discipline to execute it is yours.
Stop collecting races and start building a season.
