Training
Periodization with Garmin: Base, Build, Peak, Taper Explained
April 16, 2026
Why Periodization Exists
You cannot train hard all year. This is the single most important sentence in endurance training, and it is the reason every serious coach and every well-designed training plan uses periodization.
Periodization is the deliberate structuring of training into phases, each with a different primary goal. Each phase builds on the previous one, and each phase is designed to push a different physiological system while allowing the others to either adapt or recover. The phases are sequenced so that peak fitness aligns with your goal race, and then the cycle resets for the next block.
The alternative — train consistently hard every week until something breaks — produces plateaus, injury, and burnout. It works for about 6-8 weeks before stagnating. Periodization is how athletes produce fitness gains over 20, 30, and 40 years of training, rather than one great year followed by chronic frustration.
Your Garmin watch captures everything you need to periodize intelligently: training load, load balance, heart rate distribution, VO2 max trend, recovery metrics. What it does not do is tell you which phase you should be in, how to structure that phase's training, or whether the phase is working. That is what this article covers.
The Four Classical Phases
Most periodized endurance training uses some version of a four-phase model: base, build, peak, and taper. The names vary (some coaches call them "general preparation, specific preparation, competition, recovery"), but the physiology is the same. Here is what each phase targets and what your Garmin data should look like during it.
| Phase | Primary goal | Typical duration | Target weekly intensity distribution | Load ratio target |
|---|---|---|---|---|
| Base | Aerobic capacity, mitochondrial density, capillary network | 8-16 weeks | 85% easy / 10% moderate / 5% hard | 1.0-1.15 |
| Build | Lactate threshold, VO2 max, race-specific work | 6-10 weeks | 75% easy / 10% threshold / 15% high-intensity | 1.15-1.35 |
| Peak | Race-pace fitness, neuromuscular sharpening | 2-4 weeks | 65% easy / 15% threshold / 20% race-pace & fast | 1.1-1.2 (declining) |
| Taper | Retain fitness, shed fatigue | 1-3 weeks | 80% easy / 10% threshold / 10% short race-pace | 0.7-0.9 |
This is a template, not a prescription. The exact durations shift based on your goal race distance, your training age, and how long you have between races. A first-time marathoner with no aerobic base needs 16+ weeks of base work. An experienced runner off a previous block may only need 6 weeks of base. But the sequence — base, then build, then peak, then taper, then recovery — is the invariant.
Phase 1: Base — Build the Engine
Base phase is where aerobic fitness is built. Everything in the later phases depends on what you do here. Skip the base, and there is nothing to build on later.
What you are trying to develop
The base phase targets the slow-twitch adaptations that take months to develop and years to lose: mitochondrial density, capillary network expansion, stroke volume of the heart, fat-oxidation efficiency, and muscular endurance. These are the adaptations that allow you to sustain effort without accumulating lactate, without burning through glycogen, and without your heart rate drifting upward at a given pace.
The metabolic system you are training is almost entirely aerobic. You do most of your work at an intensity that can be sustained for hours, not minutes.
What the week looks like
A typical base week for a runner training 5-7 hours per week:
- 3-5 easy aerobic runs in zone 2, 30-75 minutes each
- 1 long run, gradually increasing to 90-120 minutes (longer for marathon training)
- 1 weekly strides session — 6-8 short 20-30 second accelerations at the end of an easy run, to maintain neuromuscular speed without adding real intensity
- Optional: 1 session of hills or tempo effort at sub-threshold intensity, but these are optional in true base phase
Notice what is missing. No intervals. No VO2 max work. No race-pace efforts. This is deliberate. The adaptations of base phase are driven by volume and duration at low intensity, not by intensity.
What your Garmin data should look like
- Time in zones: 85%+ of weekly time in zones 1-2. If your zone 3 time creeps above 10%, you are drifting into gray-zone training and losing the base phase benefit. See zone 2 training with Garmin for the full explanation.
- Training load: Increases gradually week-over-week. A rule of thumb is 5-10% per week, with a slightly lower week every 3-4 weeks.
- Load ratio: Should sit in 1.0-1.15. You are building chronic fitness, not accumulating acute fatigue. Track your CTL, ATL, and TSB from recent workout TSS here.
- Training status: "Productive" most weeks, "Maintaining" occasionally. "Unproductive" is a signal that you are either not progressing volume or the intensity distribution is wrong. See the training status guide.
- VO2 max: May or may not climb much during pure base phase. Base is not primarily a VO2 max developer; that comes in build. A stable VO2 max during good base work is normal.
- HRV trend: Weekly average should be stable or slowly rising. Declining HRV across 3-4 weeks of base phase suggests your volume is climbing faster than your recovery capacity.
Where athletes go wrong in base phase
The most common base-phase error is running too hard. Motivated athletes interpret "easy" as "comfortable pace" when it should mean "strictly aerobic, well below threshold." The tell is that most of their zone 2 runs are actually in zone 3. They get fit enough to perform decently but never develop the deep aerobic base that supports real peak performance.
The second error is not enough volume. Base phase produces adaptation from time spent at low intensity, not from any specific workout. Four 40-minute easy runs per week is base phase maintenance, not base phase building. Real base-building for most athletes is 5-8 hours per week.
The third error is skipping base phase entirely and jumping to intervals because intervals feel productive. This works for about a month, then the training stalls because there is no aerobic foundation to support more intensity.
Phase 2: Build — Sharpen the Fitness
Build phase is where the fitness developed in base gets translated into race-specific capability. The training load climbs, the intensity diversifies, and the workouts start targeting the physiological systems that will matter on race day.
What you are trying to develop
Two main systems: lactate threshold (the intensity above which blood lactate accumulates faster than you can clear it) and VO2 max (the maximum rate of oxygen uptake during exercise). Improving either of these pushes out the pace at which fatigue sets in during a race. Accurate heart rate zones are essential for hitting the right intensities in this phase.
You are also developing race-specific fitness. A marathon build phase includes long runs with marathon-pace segments. A 5K build phase includes short intervals at 5K pace or faster. The intent is to adapt not just the metabolic system but the neuromuscular patterns of running at the pace you will race.
What the week looks like
A typical build week for an intermediate runner training 6-8 hours per week:
- 2 quality sessions per week — one threshold (longer intervals at tempo intensity) and one VO2 max or race-pace (shorter harder intervals)
- 3-4 easy aerobic runs in zone 2, 30-60 minutes each
- 1 long run with pace variation — could be a progression run, a run with race-pace segments, or a long run with hills depending on the goal race
Over 6-10 weeks, the quality sessions progress: interval length increases, recovery shortens, total quality volume climbs. The easy aerobic mileage stays roughly constant, serving as recovery between hard sessions.
What your Garmin data should look like
- Time in zones: 75-80% easy, 10% threshold, 10-15% high-intensity. Less easy time than base, more targeted hard time. See polarized training principles for the distribution logic.
- Training load: Continues climbing. Typical build phase adds 15-25% total weekly load versus late base phase.
- Load ratio: Rises to 1.15-1.35. This is the "productive overload" zone where adaptation happens faster but recovery demands increase correspondingly. See the load ratio guide.
- Training status: "Productive" with occasional "Overreaching" after peak load weeks. If "Strained" or "Unproductive" appears for more than a week, the build is moving too fast.
- VO2 max: Should climb. Build phase is the primary phase where your Garmin VO2 max estimate should move. A flat VO2 max through build is a signal that the intensity work is not producing adaptation — usually because the intervals are not hitting true VO2 max intensity.
- Lactate threshold pace: Should improve. See the lactate threshold guide. This is often more measurable than VO2 max for assessing build phase progress.
- Race predictor: Should start showing improved times for your goal distance.
The classic build-phase failure mode
Build phase is where overtraining risk is highest. Two hard sessions per week plus a long run plus increasing volume plus more frequent race-pace work adds up fast, and athletes who were handling base phase well sometimes crack in week 4-5 of build.
The Garmin signal for this is unambiguous. If across build phase you see HRV declining, resting HR rising, load ratio stuck above 1.4, training status flipping to "Strained," and VO2 max plateauing despite more intensity — you are in non-functional overreaching. The correct response is an unplanned recovery week, even if the plan does not call for one. See overtraining prevention with Garmin for the full early-warning system.
Phase 3: Peak — Sharpen the Edge
Peak phase is the 2-4 weeks immediately before your goal race, once build is finished. The primary goal shifts from building fitness to expressing it at race pace.
What you are trying to develop
Neuromuscular readiness for race-pace efforts. Your aerobic engine is already built. Your lactate threshold is already where it is going to be for this block. Peak phase is about teaching your body to execute race pace efficiently, sharpening the short-interval speed that sits on top of threshold fitness, and transitioning from volume-driven training to intensity-driven training.
What the week looks like
- 1 key race-pace session per week, usually longer race-pace intervals with short recovery (for marathon: 3x2mi at marathon pace; for 5K: 5x1000m at 5K pace)
- 1 short high-intensity session with small volumes (for 5K: 6-8x400m at 3K pace; for marathon: 6-8x800m at 10K pace)
- 2-3 easy aerobic runs, shorter than build phase
- 1 shorter long run (for marathon training: 90-120 min, not the 150-180 of build; for shorter races: 60-75 min)
- Some strides or hill sprints to maintain neuromuscular snap
What your Garmin data should look like
- Training load: Plateau or slight decrease. You are not adding volume anymore; you are refining it.
- Load ratio: 1.1-1.2 and declining through peak. If it is still climbing, you are not yet peaking — you are still building.
- Training status: "Peaking" is the correct label here. Garmin's algorithm specifically recognizes this pattern when intensity stays high but volume tapers slightly.
- VO2 max: Should be at or near its cycle peak. Small improvements are possible; large gains in peak phase are rare.
- Race predictor: Should be at or near its cycle peak. The predicted pace here is a reasonable benchmark for race-day pacing.
- HRV trend: Should be stable or slightly rising. If HRV is declining through peak phase, the taper needs to start earlier or be deeper than planned.
- Recovery time after key sessions: Longer than in build, because the race-pace sessions are more fatiguing than sub-threshold work.
The peak-phase balance
The temptation in peak phase is to stack workouts closer together because you feel good. This usually backfires — peak fitness is already present, and adding load at this point converts it into fatigue rather than further fitness. The Garmin signal to watch is training readiness. If readiness is consistently 70+ through peak, you can execute the sessions as planned. If it dips into the 40s between sessions, the recovery windows between quality days need to be longer.
Phase 4: Taper — Shed the Fatigue
Taper is the final 1-3 weeks before race day. This is where most of the final race-day performance is decided, and paradoxically, it is decided by doing less training rather than more. See the complete taper guide for the full protocol.
What you are trying to develop
Nothing new. The goal is to retain the fitness you have built while letting accumulated fatigue dissipate. The physiological research on tapering is unusually clear: athletes who reduce volume by 40-60% while maintaining intensity in the final 2 weeks race meaningfully faster than athletes who either taper too much or too little.
What the week looks like
A 2-week taper for a typical marathon:
- Week -2: 70% of peak volume, intensity maintained on quality sessions. Last long run 60-70% of peak long run.
- Week -1: 50-60% of peak volume, one light race-pace workout early in the week. Last hard effort 5-6 days before race day.
- Race week: Very short runs, some strides, one final short race-pace primer 2-3 days out.
Intensity stays roughly constant. Volume drops sharply. This is counterintuitive to most athletes, whose instinct is to rest completely. Complete rest dulls the neuromuscular sharpness you need for race day.
What your Garmin data should look like
- Training load: Dropping quickly in taper week 1, more gradually in taper week 2.
- Load ratio: Falls to 0.7-0.9 by race day. This is the "detraining" label in Garmin's algorithm, which is misleading — the drop in load is intentional and productive.
- Training status: "Recovery" or "Maintaining" is normal. "Detraining" appears in the final week for most athletes; this is expected and reflects the intentional volume drop, not lost fitness.
- HRV trend: Often paradoxically declines during the first week of taper, then recovers. This is a well-documented "taper paradox" — the body adjusts to the sudden reduction in training stimulus.
- Body battery: Should recharge higher. If you are seeing morning body battery 80+ with normal sleep in taper week 2, the taper is working.
- Resting HR: Should drop 2-4 bpm below training-phase baseline.
- Recovery time: Minimal between sessions, reflecting the light workload.
The classic taper mistakes
The first mistake is tapering too little — holding volume too high in the final 10 days because you feel like you need "one more big workout." You do not. The fitness is already there.
The second mistake is tapering too much — going almost zero for two weeks and losing neuromuscular sharpness. The body responds to the absence of stimulus by de-adapting faster than you expect.
The third mistake is ignoring the taper-paradox signals. Seeing HRV drop and body battery fluctuate in taper week 1 scares athletes into doing more training, which destroys the taper. These signals usually resolve by race week.
Recovery: The Hidden Fifth Phase
After your goal race, there is a phase that gets almost no attention in training plans but determines whether you can train well next block: recovery. This is 1-3 weeks of deliberately reduced training with no structure and no quality work.
Why it matters
You have been progressively building training load for 4-6 months. Your chronic load is high. If you launch straight into the next block of training without a recovery period, you carry the accumulated fatigue forward and your next base phase starts from a compromised baseline. The result is a less productive next cycle.
What the week looks like
- Week 1 post-race: almost nothing. 3-4 short easy runs, no structure, based entirely on how you feel.
- Week 2: gradual return to easy aerobic running, 50-60% of base-phase volume.
- Week 3: rebuild toward full base-phase volume. Resume strides. Start considering the shape of the next training block.
What your Garmin data should do
- Training load: Drops sharply, then begins the slow rebuild.
- Training status: Will cycle through "Recovery," "Detraining," and eventually back to "Maintaining" or "Productive" as you resume training.
- VO2 max: May drop 1-2 points during recovery weeks. This is normal and reverses quickly once training resumes. Do not let a short post-race VO2 max dip panic you into training too hard too soon.
Putting It All Together: A Full 20-Week Block
Here is how a full periodized block looks, with what the Garmin data should be telling you at each stage.
Weeks 1-8 (Base): Load ratio 1.0-1.15. Weekly load climbing 5-10%. Time in Z1-2 above 85%. HRV trending stable or up. VO2 max flat or slightly up.
Weeks 9-16 (Build): Load ratio 1.15-1.35. Weekly load climbing faster. Time in Z4-5 climbing. Training status mostly Productive with occasional Overreaching. VO2 max climbing. Race predictor improving.
Weeks 17-18 (Peak): Load plateaus or drops slightly. Load ratio stable at 1.1-1.2. Training status "Peaking." VO2 max at cycle high. Race predictor at cycle best.
Weeks 19-20 (Taper): Load dropping sharply. Load ratio 0.7-0.9. Recovery metrics recovering. Resting HR dropping. Body battery higher.
Race day (end of week 20).
Weeks 21-22 (Recovery): Training load low. No structure. Data just confirms that you are actually resting.
If your data looks like this across a 20-week block, your periodization is working. If it does not, the data tells you which phase needs adjusting.
The Self-Coaching Challenge
The challenge with periodization is not knowing the phases. The challenge is executing them. Base phase in particular is unpopular because it looks unglamorous in the data — no big intervals, no impressive paces, just a lot of easy aerobic mileage. Build phase is popular because intervals feel like productive training. Peak and taper are where athletes most often go wrong, because the correct action (reduce volume) feels counterintuitive.
A coach's value in periodization is not writing the plan. It is enforcing the phase discipline. "No, you are not doing intervals this week — we are still in base." "Yes, you need to cut volume by 50% this week — we are tapering." "Yes, you need 10 days of nothing — you just raced a marathon."
This is also where continuous data-driven coaching works well. Gneta reads your full Garmin data stream and can tell you whether your current training is consistent with the phase you think you are in. If your base-phase weekly zone distribution has crept to 60% Z3, the system flags it. If your build-phase load ratio has spiked above 1.5, the system flags it. If your taper-phase training is not actually reducing load, the system flags it. This works whether you are following a structured plan or self-coaching with AI assistance.
The Bottom Line
Periodization is not complicated, but it is disciplined. Four phases, each with a different goal, each with specific load and intensity patterns, each with Garmin data signatures that tell you whether the phase is working.
The common failure modes are all about ignoring the phase structure — doing intervals during base, piling volume on top of build, skipping the taper. Your Garmin data reveals all of these in real time if you know what to look for.
Build the phases. Read the data. Race fitter than last cycle. That is the loop.
Ready to periodize with data-driven guidance? See how Gneta reads your training phase continuously or compare plans and pricing.
Related reading:
