Building a structured cycling training plan doesn't require a coach or years of experience — it requires a clear process. This guide walks any cyclist, from motivated beginner to competitive amateur, through six concrete steps: setting a realistic goal, testing your current fitness with an FTP assessment, applying periodization across Base, Build, Peak, and Taper phases, structuring your training week, managing progression and recovery, and adjusting when life interrupts the plan.
Step 1: What goal should you set before training starts?
Pick a specific, dated event — a race, sportive, or gran fondo — before you write a single workout. That date sets the total weeks available and determines the shape of every phase that follows. Without it, periodization is impossible.
You need two types of goals working together. Outcome goals define what you want to achieve: a finish time, a podium, completing a century. Process goals define how you will get there: a weekly TSS target, an FTP gain measured in W/kg. Both matter equally.
Work backwards from race day. Count the total available weeks, then allocate them across Friel's four phases. A 24-week plan targeting a 160 km century ride splits roughly into 10 Base weeks, 8 Build weeks, 4 Peak weeks, and 2 Taper weeks. That structure is your roadmap.
Step 2: How do you assess your current fitness with an FTP test?
Before writing a single workout, establish your Functional Threshold Power — the highest average power in watts you can sustain for roughly one hour (Coggan & Allen). Every training zone and stress score anchors to this number. Get it wrong and everything downstream is wrong too.
Three testing options exist:
- Auto-detection from recent data via Intervals.icu — the platform estimates FTP from your hardest recent efforts. Fast and painless; good enough to start.
- The 20-minute test — ride as hard as you can sustain for 20 minutes, then multiply average power by 0.95. More accurate, but demanding.
- The ramp test — power increases every minute until failure; the app calculates FTP from your stopping point. Less painful, which makes it popular with beginners.
Once you have your FTP, it maps directly to the seven Coggan power zones:
Zone | % FTP | Description | Typical Duration |
|---|---|---|---|
1 | <55% | Active recovery | Unlimited |
2 | 56–75% | Endurance | 2–6 hours |
3 | 76–87% | Tempo | 1–3 hours |
4 | 88–94% | Lactate threshold | 30–60 min |
5 | 95–105% | VO2max | 3–8 min |
6 | 106–120% | Anaerobic capacity | 30 sec–2 min |
7 | >121% | Neuromuscular power | <15 sec |
Re-test every four to six weeks. As Coggan and Allen explain in Training and Racing with a Power Meter, an outdated FTP corrupts every zone, every TSS score, and every fitness trend built on top of them.
Step 3: How does periodization structure your training phases?
Periodization — as defined by Joe Friel — divides the training year into four phases, each with a distinct physiological target. Fitness accumulates progressively rather than randomly.
Phase | Primary Goal | Dominant Zone | Typical Duration | Key Workout |
|---|---|---|---|---|
Base | Aerobic foundation | Zone 2 | 8–12 weeks | Long, steady endurance rides |
Build | Sport-specific intensity | Zones 3–4 | 6–10 weeks | Sweet spot and threshold intervals |
Peak | Race-specific sharpening | Zone 5 | 3–5 weeks | VO2max efforts (106–120% FTP) |
Taper | Fatigue shedding | Mixed | 1–2 weeks | Short, sharp sessions |
During Base, Seiler's polarized 80/20 principle applies: roughly 80% of time at low intensity, 20% at high. Build shifts the balance toward sweet spot (88–93% FTP) and threshold work. Peak sharpens race fitness with shorter, harder efforts. Taper drops volume by 40–50% while maintaining intensity — CTL, ATL, and TSB metrics from TrainingPeaks guide the timing.
Step 4: How should you structure a training week?
A well-structured week alternates hard days and easy days, fitting four or five sessions into your available time. Always place the highest-quality workout when fatigue is lowest — typically the day after a full rest day.
A sample five-day week during the Build phase:
Day | Session Type | Zone | Duration |
|---|---|---|---|
Monday | Rest or active recovery | Z1 | — / 30 min |
Tuesday | Threshold intervals | Z4 | 60–75 min |
Wednesday | Easy endurance | Z2 | 60 min |
Thursday | Sweet spot | Z3–4 | 75–90 min |
Saturday | Long endurance ride | Z2 | 90–150 min |
Never stack two high-intensity days back-to-back. Recovery is where adaptation actually happens.
Use weekly TSS as your planning currency: beginners target roughly 200–300 TSS per week, intermediates 400–550, advanced athletes 600 or more. Seiler's polarized model — 80% easy, 20% hard by time — is supported by research and suits athletes with limited training hours particularly well.
Step 5: How do you apply progression and recovery weeks?
A 3:1 or 4:1 block structure — three or four weeks of progressive overload followed by one recovery week — lets the body absorb training stress and prevents overtraining. Progression without recovery is just accumulated fatigue.
Increase weekly TSS by no more than 5–8% per week. Friel's 10% rule sets the ceiling; exceeding it raises injury risk significantly.
A recovery week means cutting volume by 30–50%. Keep one short intensity session to maintain neuromuscular sharpness, then re-test FTP at the end to update your zones before the next block begins. Track fitness using the CTL/ATL/TSB model (Coggan & Allen / TrainingPeaks): CTL represents chronic training load — your fitness; ATL represents acute training load — your fatigue; TSB equals CTL minus ATL and signals readiness. A rising TSB after a recovery week tells you the adaptation has landed.
Step 6: How do you adjust the plan when life gets in the way?
Missed sessions and unexpected stress are inevitable. The rule is straightforward: protect quality over quantity. Skip easy rides before you skip key workouts, and never try to compensate for lost volume by cramming extra sessions into the following days.
Use this decision tree when things go off-script:
- Missed one easy ride → skip it entirely and move on.
- Missed a key interval session → move it one day, compress rest by one day accordingly.
- Missed a full week → resume at 70% of your previous load, not 100%.
- Illness → return only when resting heart rate is back to your personal baseline.
TSB also works as a real-time adjustment signal. A TSB below -30 means you need to back off regardless of the schedule. A TSB above +10 before a key session means you are fresh enough to push hard.
Tools like PlanWatts can automate these adjustments — the AI reads your live fitness data and reschedules workouts around your actual week, which is useful for athletes who find manual plan management time-consuming.
The most important principle: consistency over months beats perfect execution of any single week. A plan you adapt and follow is always more effective than a perfect plan you abandon.
Key takeaways: Start with a dated goal event and work backwards through Friel's four phases. Test FTP before training begins and re-test every four to six weeks. Structure each week around the hard/easy principle, track weekly TSS, and follow a 3:1 or 4:1 progression-to-recovery block ratio. When life disrupts the plan, protect key sessions, use TSB as your readiness signal, and return gradually after illness or missed weeks. The process is repeatable — run it again for your next event and the gains compound.
How long before my event should I start a cycling training plan?
Aim for at least 16–24 weeks before your target event. That window gives you enough time to complete a meaningful Base phase, a Build phase, and still leave room for Peak sharpening and a proper Taper. Shorter timelines are workable but require compressing phases, which limits total fitness gains.
What is a good FTP for a beginner cyclist?
There is no universal benchmark — FTP is highly individual. Most untrained beginners test between 150–200 watts, while recreational riders typically sit in the 2.0–3.0 W/kg range. What matters is establishing your personal baseline, then tracking improvement over successive test cycles every four to six weeks.
Can I follow a training plan without a power meter?
Yes, though precision suffers. Heart rate can substitute for power zones during endurance and threshold sessions, and perceived exertion (RPE) fills gaps where HR lags. TSS calculations and FTP-based zone targeting become estimates rather than data-driven metrics, making progression harder to measure accurately.
How do I know if I am overtraining?
Key warning signs include a persistently elevated resting heart rate, declining performance despite consistent training, disrupted sleep, and mood changes. In data terms, a TSB that stays below -30 for multiple consecutive days signals excessive accumulated fatigue. A scheduled recovery week — with volume cut by 30–50% — is the first corrective step.
How often should I update my training plan?
Revisit the plan at the end of every recovery week, roughly every four weeks. Re-test FTP to keep zones accurate, review whether your weekly TSS targets are realistic, and adjust phase lengths if your event date has shifted. Small, regular calibrations prevent the plan from drifting out of sync with your actual fitness.
Train smarter with your own AI coach
PlanWatts turns your data into a plan — and builds the workouts for you.
Start free