Periodization is the reason two runners with identical VDOT scores can produce very different race results. One follows a coherent training structure that builds fitness systematically and peaks at the right moment. The other trains hard year-round without a framework — accumulating fatigue, not fitness.
The concept is simple: training stress should not be constant. Different phases of preparation target different physiological systems, and those adaptations require different types of stress delivered at the right time.
I learned this the hard way. For two years I ran high-mileage training blocks that never translated to better race times. I was fit in the middle of training and flat on race day. The problem wasn't volume or effort — it was sequencing. I was training hard when I should have been building, and backing off when I should have been peaking.
What periodization actually means
Periodization is the organization of training into blocks — each with a specific physiological goal, a defined duration, and a progression of volume and intensity that feeds into the next block.
The underlying logic comes from Hans Selye's General Adaptation Syndrome: apply a training stress, allow adaptation, then apply a higher stress. Do this systematically and fitness rises. Apply stress without structure and the body either adapts insufficiently or breaks down.
For marathon and half marathon runners, the standard periodization model has four phases.
Phase 1 — Base (aerobic foundation)
Duration: 6–10 weeks
Primary goal: Build aerobic capacity and connective tissue resilience
Volume: High
Intensity: Low (mostly E pace)
Base phase is where your aerobic engine is built. The workouts are not exciting — long easy runs, steady mileage, occasional strides. The physiological changes happening are invisible: mitochondrial density increasing, fat oxidation improving, capillary networks expanding in working muscles.
This is also where tendons, ligaments, and bones adapt to the mechanical load of running. Connective tissue adapts slowly — more slowly than cardiovascular fitness. Skipping base phase and jumping to high-intensity training is the most reliable way to get injured six weeks into a training block.
CTL target: Build from your starting point at +3–5 points per week. TSB will be slightly negative but should not fall below −15.
What most runners do wrong: They start base phase with good intentions and cut it short when they feel fit enough to run faster. The aerobic adaptations from base phase take 6–8 weeks to materialize — they don't show up in your workouts until the phase is nearly over.
Phase 2 — Build (quality and specificity)
Duration: 6–8 weeks
Primary goal: Raise lactate threshold and introduce race-specific stress
Volume: Moderate to high
Intensity: Increasing (E + T + M pace)
Build phase is where the training starts to feel like preparation. Threshold sessions appear: cruise intervals, tempo runs, marathon-pace long runs. Volume stays high but intensity climbs.
The physiological target here is your lactate threshold — the pace above which lactate accumulates faster than it can be cleared. Lactate threshold is the single most trainable variable for marathon performance, and build phase is when you train it directly.
Weekly structure typically alternates a hard day with an easy day, with one long run per week gradually incorporating race-pace miles. CTL continues to rise. ATL will spike after hard weeks and recover during easy ones. TSB will oscillate between −10 and near-zero.
What most runners do wrong: They add intensity too quickly, before the aerobic base can support it. T-pace runs feel fine for two weeks, then performance plateaus and minor injuries appear. The fix is patience in base phase, not backing off in build phase.
Phase 3 — Peak (maximum stress)
Duration: 2–3 weeks
Primary goal: Maximum CTL — the highest training load of the cycle
Volume: Highest of the cycle
Intensity: Highest of the cycle (all pace zones in play)
Peak phase is the hardest training of the cycle. It's also the phase that feels worst. Easy runs feel hard. Your legs feel heavy. VDOT-derived paces feel out of reach. This is expected — not a sign of overtraining.
What's happening physiologically: CTL is at its highest, ATL is elevated, and TSB is deeply negative (−20 to −30). You are accumulating fatigue faster than you're recovering from it. This is intentional. The fitness gains from this stress will only manifest after the taper.
Peak phase typically includes the longest long run of the cycle (28–35 km for marathon), one or two race-specific workouts at marathon pace, and interval sessions at I pace.
What most runners do wrong: They panic during peak phase. The fatigue feels like failure. They cut sessions short, add rest days, and arrive at taper with less accumulated stress than needed. The result is a race performance that falls short of their CTL potential.
Phase 4 — Taper (fatigue shedding)
Duration: 2–3 weeks
Primary goal: Drop ATL while preserving CTL → achieve positive TSB on race day
Volume: Rapidly decreasing
Intensity: Maintained (short quality sessions)
Taper is not rest. It is the calculated reduction of training volume — keeping intensity present but brief — to allow the accumulated fatigue of peak phase to dissipate while the fitness adaptations from months of training fully express themselves.
The mechanism: ATL drops quickly when volume falls (7-day window). CTL falls slowly (42-day window). The gap between them widens — TSB turns positive. By race day, the target is TSB +10 to +20: high fitness, low fatigue.
The psychological experience of taper is notoriously unpleasant. Legs feel flat, motivation drops, phantom niggles appear. "Taper madness" is real and it's caused by the ATL dropping faster than runners expect. It is not a sign that fitness is fading — it's a sign the taper is working.
What most runners do wrong: They add back training when taper feels wrong. Extra runs, "just to stay sharp," reset ATL upward and arrive at race day with the same fatigue problem they were trying to solve.
Why periodization breaks down in practice
A periodized plan on paper assumes a runner who trains exactly as written every week. That runner doesn't exist.
Missed sessions, illness, travel, and life stress all disrupt the plan's assumptions. A two-week illness in week 8 means arriving at the build phase with a CTL 15–20 points lower than the plan expected. Following the build phase sessions as written — at the planned intensity and volume — produces ATL spikes the aerobic base can't support.
This is the core problem with static periodized plans: the phases are correct in concept but the prescription doesn't adapt to your actual state. If your CTL is lower than planned, your T-pace sessions need to be shorter. If you hit peak phase with less base than intended, your peak volume needs to be pulled back.
Adaptive training plans solve this by recalculating the prescription each week based on where your CTL, ATL, and TSB actually sit — not where the spreadsheet assumed they'd be.
Periodization and VDOT: the connection
Periodization defines when to train each intensity. VDOT defines at what pace.
Without VDOT, periodization is structurally correct but imprecise — you know to run threshold work in build phase, but not at what pace. Without periodization, VDOT gives you accurate paces for sessions that are sequenced randomly.
Together, they form a complete training framework: periodization provides the macro-structure, VDOT provides the intensity targets within each phase.
This is why Zarkus uses both. Your VDOT determines your E, T, M, I, and R paces. The periodization model determines which phases to run, in which order, and for how long — and the adaptive layer recalibrates both when your actual training data diverges from the plan.
Periodization is the difference between training that accumulates and training that peaks. The individual sessions matter less than the sequence they're arranged in — and that sequence only works if it adapts to the runner actually doing it.
Frequently Asked Questions
What is periodization in running training?
Periodization is the systematic organization of training into distinct phases — base, build, peak, and taper — each with a specific physiological purpose. Rather than training at the same intensity and volume year-round, periodization deliberately varies the training stimulus over time to maximize fitness on race day. It was first formalized in strength sports and later adapted to endurance running by coaches like Jack Daniels and Pete Pfitzinger.
How many weeks should each training phase be?
For a standard marathon cycle, base phase typically runs 6–10 weeks, build phase 6–8 weeks, peak phase 2–3 weeks, and taper 2–3 weeks — totaling 16–24 weeks. The exact duration depends on your current fitness, target race, and how much time you have. Shorter cycles compress base and build phases; longer cycles allow more aerobic development before adding intensity.
Why do runners skip the base phase?
Base phase is slow, unglamorous, and doesn't produce immediate performance gains — which makes it the phase most runners cut short when life gets busy or impatience takes over. But the base phase builds the aerobic infrastructure that everything else depends on: mitochondrial density, fat oxidation efficiency, capillary development, and connective tissue strength. Skipping it means adding intensity onto an inadequate foundation, which produces flat performances and elevated injury risk.