Race Season Planning: Time Multiple Races Right

Finishing one race a year in top shape is achievable. Two or three true peaks — without crashing into a slump in between or overtraining yourself — are the real art of season planning. The difference is not in the training itself but in the calendar: which races get priority, what the blocks between them look like, and where recovery has its place. This article shows how to structure a season with several races so that you are genuinely fresh at the starts that matter.

Why a race rarely stands alone

Very few ambitious athletes race only once a year. There is the spring half marathon as a fitness test, the main marathon in autumn, maybe a gran fondo in summer or a club race in between. The problem: every race you take seriously costs form — not just on the day itself, but in the weeks before (tapering) and after (recovery). Treat every start like a peak and you spend half the season reducing and rebuilding — and paradoxically train too little to actually get better.

The solution is a classic from elite sport: not all races are equal. Good season planning sorts first, then builds.

A-, B- and C-races: the priority pyramid

The first step of any season plan is brutally honest: every planned race gets exactly one of three categories.

• A-races (maximum 2–3 per year): The season goal. The entire training build runs towards this date, including a full taper over 10–14 days. This is where you want the best form of the year. Everything else is subordinate to this date.
• B-races (2–4 per year): Important fitness tests or races you take seriously but do not have to win at all costs. Before a B-race you reduce for only three to five days — a freshening-up, not a real taper. Afterwards the build continues almost seamlessly.
• C-races (as many as you like): Training with a bib number. You race them straight out of a loading week, without any reduction — for example a pace-controlled 10K instead of a threshold session. A C-race must never blow up the plan.

The most common trap: two weeks out, a B-race suddenly feels like an A-race. Fully tapering anyway sacrifices two build weeks — and exactly those weeks are missing at the real peak.

How many peaks can a season handle?

Form is not a permanent state but a wave: you build it over weeks, hold it briefly at the crest, and have to let it flatten again afterwards. Physiologically, two factors limit the number of peaks per year. First, a clean build from a solid base to race specificity takes twelve to 16 weeks. Second, the body needs a genuine transition phase after a peak — especially after a marathon or long-distance triathlon — otherwise you drag fatigue from block to block until overtraining looms.

From this follow robust guidelines:

• Two A-races per year are the gold standard: typically one in spring (April/May) and one in autumn (September/October). In between lie 18–22 weeks — enough for recovery, a complete rebuild and even a switch of sport (e.g. spring marathon, autumn gran fondo).
• Three A-races work at shorter distances (5K to half marathon) because the recovery cost per race is lower. For marathons and long-distance triathlons it gets tight.
• Four or more "top forms" is no longer planning but wishful thinking. The form curve does not have four summits — it then only has mediocrity.

Think of the season in blocks

Between two peaks there is no no-man's-land but a clear sequence of phases — the core of training periodization:

• Transition phase (1–2 weeks after the A-race): Very easy, free, no plan pressure. After a marathon even a complete week without running is fine — the feared fitness loss is a myth; real detraining only sets in after two to three weeks of complete inactivity.
• Base phase (4–8 weeks): High easy volume, strength training, technique work — the foundation everything later stands on. Ideal for fixing weaknesses there is no time for during the racing season.
• Build phase (4–6 weeks): Load rises in blocks, more specific stimuli are added — threshold work, longer tempo blocks, race-like efforts.
• Peak phase (2–3 weeks): The hardest, most race-specific sessions of the year — long runs at marathon pace, race simulations.
• Taper (1–2 weeks): Volume down by 40–60%, intensity stays. Then: A-race.

Throughout, the 3:1 rhythm applies: after every three loading weeks comes a deload week with reduced volume. This micro-structure is what keeps the macro-structure healthy at all.

Example season: spring and autumn

It becomes concrete with a realistic calendar for a runner with two A-races — half marathon mid-April, marathon early October:

• January–February (9 weeks): Base and build phase towards the half marathon, volume rising in a 3:1 rhythm.
• March (4 weeks): Peak phase focused on half-marathon pace; a 10K C-race mid-March as tempo training.
• Early April: Short taper (8–10 days), then A-race 1: half marathon.
• Rest of April (2 weeks): Transition phase — one week off, one week of easy running by feel.
• May–June (8 weeks): Second base: volume expanded further, strength training stepped up. A B-race (e.g. 10K) late May with only three days of freshening up.
• July–August (8 weeks): Marathon build and peak phase: long runs of 30–35 km, marathon-pace blocks, a half marathon in August as a C- or B-race — depending on the day, but without tapering.
• September (3–4 weeks): Final peak, then a full two-week taper.
• Early October: A-race 2: marathon — on the broadest training base of the year. Afterwards: a well-earned off-season.

Not a runner? Simply swap the dates: the same logic applies to a gran fondo in June plus an autumn classic, or an Olympic-distance plus half-ironman triathlon season.

Fitting B- and C-races into training

Secondary races are valuable — if you use them for what they are: high-quality training under race conditions. Three rules keep them plan-compatible:

• A C-race replaces a quality session, it is not added on top. A 10K on Sunday replaces the planned tempo workout — it does not come on top of it. Weekly load stays the same.
• A B-race gets a mini freshening-up. Reduce volume by 30–40% three to five days beforehand, keep one short race-pace session. Afterwards two easy days — then the build continues.
• Choose the race pace deliberately. A B-race during a half-marathon build is run at planned race pace or as a controlled progression — not in survival mode. The training stimulus counts, not the placing.

The side effect: every secondary race is a dress rehearsal for the A-race — breakfast, timing, fueling, clothing. Anyone who has nothing left to test at the main race has already eliminated the biggest source of error.

Common season-planning mistakes

• Declaring too many A-races. Three marathons in six months, "all for a personal best" — that ends in three mediocre results or a breakdown. Honest prioritizing beats ambitious overloading.
• Skipping the transition phase. "Training resumes on Monday" right after the race — that drags fatigue and mental wear into the next block. The one to two easy weeks are planned, not lost.
• Fully tapering for every B-race. Four B-races with two weeks of reduction each means eight lost build weeks — almost a fifth of the year.
• Letting the calendar drive the training. Collecting entries first, then checking how they fit: backwards. Fix the A-dates first, plan the blocks in reverse, then slot in secondary races.
• Forgetting buffers. Infections, injuries, work crunches happen. A season planned on a knife's edge collapses at the first disruption. Build a reserve week between blocks.

How Peakora plans your season

In Peakora you set your A-race as the goal — the engine plans the entire path backwards from it: base, build and peak phases, deload weeks in a 3:1 rhythm, and the taper in the final two weeks. After the race you mark the next goal and the build starts anew — including transition time instead of grinding on seamlessly. The recovery monitor with your form score (TSB) shows across the whole season whether the wave is on track: build fatigue, bring freshness back at exactly the right moment.

Frequently asked questions about season planning

How many A-races per year make sense?

Two to three true peaks per year are ideal for most athletes. Each peak needs its own 12 to 16 week build plus tapering and recovery afterwards — more than three peaks can hardly be fitted cleanly into twelve months.

How much time do two marathons need between them?

At least eight to twelve weeks. After the marathon come one to two weeks of recovery, then a new build block with base and intensity phases, then the taper. Shorter gaps only work if the first race is deliberately run below maximum effort.

Do I need to taper before a B-race?

No, not fully. Before a B-race a short freshening-up of three to five days with reduced volume is enough. The full two-week taper is reserved for the A-race — otherwise the season fragments into endless mini-breaks.

What should I do between two season peaks?

First a transition phase: one to two weeks of very easy, unstructured training for physical and mental recovery. Then a new block starts with a base focus that gradually becomes more specific towards the second peak.