A cycling training plan is a set of decisions about what to train, when to train it, how the load should progress and what evidence will trigger a change. A useful plan connects a defined goal to the rider's available time, training history, current capacity, recovery and feedback. A calendar of workouts without those inputs is a template, not an individually reviewed plan.
This is Roadman's educational methodology guide. It does not sell a downloadable plan or prescribe one universal week. Use the Roadman cycling training plans page for the current coached service, the event-plan directory for event-specific frameworks, the training-plan selection guide to compare formats, and the 60-day case study for Anthony Walsh's documented N=1 experiment.
Roadman sells coached training plans. That commercial conflict is stated here so readers can separate the method from the offer. The named reviewer and review date are published above and in this page's structured data.
In this guide:
- Start with the rider brief
- The anatomy of a plan
- Periodisation without false precision
- Choose an intensity distribution
- Build the week
- Write review rules
- Choose a delivery format
- Measure whether it is working
- Scope and safety
Start with the rider brief
Write the brief before choosing sessions. At minimum, record:
- The outcome. Name the target event, discipline, performance task or consistency goal and its date.
- The starting point. Record recent training volume, relevant test data, training age and what the rider has actually completed—not what was scheduled.
- The real week. Mark the days and hours that can be protected, plus work, travel, family and terrain constraints.
- The event demands. Duration, climbing, repeated accelerations, technical skills, fuelling and likely environmental conditions all change the plan.
- The athlete's response. Include subjective feedback, sleep, soreness, illness, motivation and completed ride data where those inputs are available and useful.
- The review agreement. Decide who will review the plan, how often, which metrics matter and what will justify an adjustment.
The brief should expose contradictions. A rider cannot prepare for every event equally, add volume, lose weight, lift heavily and peak at the same time without trade-offs. The plan should state which goal has priority in the current block.
The anatomy of a cycling training plan
| Component | Question it must answer | What to avoid |
|---|---|---|
| Goal and deadline | What must the rider be ready to do, and when? | Vague goals such as “get fitter” with no review point |
| Current capacity | What load and session types has the rider recently tolerated? | Starting from an aspirational week |
| Weekly structure | Where do priority work, low-intensity riding, strength and rest fit? | Cramming missed sessions into the next available day |
| Progression | Which variable changes across the block? | Increasing duration, frequency and intensity together without a reason |
| Recovery | What lower-load days or weeks are planned, and what can change them? | Treating recovery as unused calendar space |
| Specificity | How does the work become more relevant to the event? | Copying professional volume or another rider's zones |
| Monitoring | Which process and outcome measures will be reviewed? | Reacting to one noisy reading in isolation |
| Adjustment | What evidence triggers more, less or different work? | Changing the plan because one session felt unusually good or bad |
A plan can be simple and still answer every question. Complexity is not evidence of individualisation.
Periodisation without false precision
Periodisation means organising training so the priority changes across time. Traditional, block and day-by-day models can all be coherent. A 2023 systematic review found only seven eligible studies in trained road cyclists and concluded that the evidence did not favour one periodisation model across eight-to-twelve-week interventions (Galán-Rioja et al., PubMed 36640771).
That evidence supports a decision process, not a universal base-build-peak calendar:
- work backwards from the event or review date;
- identify the main adaptation for the current block;
- retain enough low-intensity work and recovery to support the priority sessions;
- increase event specificity as the event approaches where appropriate;
- taper only when shedding fatigue is more valuable than adding another training load;
- review the response before choosing the next block.
Labels such as base, build, peak and transition are useful descriptions. Their length is not fixed. A rider with a long recent endurance history, a novice returning after illness and a racer between two events should not receive the same number of weeks in each phase.
Block periodisation is another option, not a guaranteed upgrade. A 2019 systematic review found possible benefits for some endurance variables but also highlighted the small, heterogeneous evidence base (Mølmen, Øfsteng and Rønnestad, PubMed 31802956).
Choose an intensity distribution
“Polarised,” “pyramidal” and “threshold” describe how work is distributed across intensity domains. Before using any percentage, check:
- whether the source counts session goals or every minute in a physiological zone;
- whether it uses three, five or seven zones;
- whether strength, racing and unstructured riding are included;
- the athlete level and intervention length;
- the outcome measured.
The evidence does not support “80/20 is always best.” A 2025 individual-participant network meta-analysis of 13 studies and 348 endurance athletes found no overall difference between polarised and pyramidal interventions for VO2max or time-trial performance when intensity was calculated from heart-rate time in zone; response also differed by performance level (Rosenblat et al., PubMed 39888556).
One often-cited nine-week randomised study of 48 trained endurance athletes found larger improvements in several variables in its polarised group than in its threshold, high-volume and high-intensity groups (Stöggl and Sperlich, 2014). That is useful evidence for a specific protocol and population, not proof that one ratio should govern every cyclist's year.
The robust practical point is more modest: most successful endurance programmes contain substantial low-intensity work, while the amount and placement of moderate and high intensity change by athlete, sport and phase. A review of 175 elite-athlete distributions found that more than 60% of endurance exercise was low intensity in 91% of the distributions, while both pyramidal and polarised patterns were common (PubMed 37964776).
Build the week around priority and recovery
Begin with constraints, then place sessions in this order:
- the event-specific or adaptation-specific priority session;
- any second demanding session the rider can recover from consistently;
- the long or skills-focused ride required by the goal;
- low-intensity volume that fits without compromising the priorities;
- strength work where it serves the rider and can be recovered from;
- complete rest or recovery work.
This is sequencing, not a claim that every rider needs two hard sessions or one long ride every week. A beginner, a masters rider in a demanding life period, a highly trained racer and a rider returning after illness may need different frequency and spacing.
Do not automatically “make up” a missed session. Ask whether the purpose is still relevant, whether enough recovery time remains before the next priority session and whether the missed work signals a larger schedule mismatch. Sometimes moving it is sensible; sometimes dropping it protects the block.
Write the review rules before training starts
Review rules make a plan adaptive without pretending that every data point is a command.
| Signal | Review question | Possible response |
|---|---|---|
| Repeated failure in a priority session | Is the target wrong, is fatigue accumulating, or is fuelling inadequate? | Adjust the target, add recovery or investigate the constraint |
| Sudden schedule disruption | Which session still has the highest value this week? | Keep, move or drop work rather than stacking it |
| Rising power with stable perceived effort | Is the change repeatable under the same conditions? | Progress only after confirming the trend |
| Persistent pain, illness or unusual symptoms | Is training still appropriate? | Stop or reduce training and seek qualified assessment when needed |
| Event-date change | Does the current block still lead to the new demand? | Rebuild the sequence from the new deadline |
Decide how many observations are needed before acting. Some safety signals require an immediate response; performance metrics usually need a trend and comparable conditions.
Static plan, app or coached plan
| Format | What it can do well | What the rider must verify |
|---|---|---|
| Static plan | Low-cost structure for a predictable schedule and clear goal | Fit, progression, modification rules and who answers questions |
| Adaptive app | Deliver workouts and change scheduling or targets from defined inputs | Which inputs and rules drive changes, and when the athlete must override them |
| Self-coaching | Join training decisions to detailed personal context | Objectivity, knowledge gaps and a repeatable review process |
| Coached plan | Assign a named person or team to review context and make changes | Scope, review cadence, contact, evidence, qualifications, data handling and terms |
Use the selection guide for a fuller comparison. Roadman's paid option is a coached plan rather than a one-off template; its current scope and price belong on the commercial owner page.
Event-specific planning
Event pages should translate the general method into observable demands: expected duration, elevation, repeated climbing, technical skill, pacing, fuelling, environmental exposure and the time remaining. They should not promise that a fixed number of weeks is enough for every starting point.
Use the Roadman event-plan directory to choose an event and weeks-out framework. Examples include the Wicklow 200, Mallorca 312 and Fred Whitton Challenge. These are planning frameworks; individual readiness still determines the appropriate load.
Measure whether the plan is working
Agree on process and outcome measures before the block:
- Process: priority-session completion, low-intensity discipline, fuelling execution, communication and reasons for changes.
- Response: perceived effort, repeatable power or pace, heart-rate response, recovery and tolerance of the planned load.
- Outcome: the specific event task, field test or performance marker the block was designed to change.
Use comparable conditions and avoid treating one FTP test, one HRV reading or one unusually good ride as the whole verdict. At the end of the block, ask whether the intended adaptation occurred, what the rider tolerated and what the next block should prioritise.
Scope, safety and referral
A training plan is not a medical diagnosis, injury-rehabilitation protocol, therapeutic nutrition plan or mental-health service unless appropriately qualified professionals are explicitly providing that work. Persistent pain, chest symptoms, fainting, unexplained performance loss, suspected low energy availability or illness requires suitable clinical assessment rather than a harder training week.
For online delivery, confirm which platforms can access health and training data, who can view it, how long it is retained and how it can be exported or deleted. Data volume does not replace informed judgement.
How Roadman uses the sources
The research above establishes boundaries: periodisation has several defensible models; intensity-distribution evidence depends on population, measurement and outcome; and no study guarantees an individual's response. Roadman's podcast interviews add practitioner context, while the 60-day experiment documents one rider's outcome. The Roadman training-plan service page states the current commercial offer. Those are different forms of evidence and should not be presented as interchangeable proof.