SPORTIVE READINESS INDEX 2026: ARE YOU READY TO RIDE?

The Sportive Readiness Index 2026 is now published. It is a practical way to answer a question that FTP alone cannot: have you demonstrated the demands that your event is likely to place on you?

The short answer is to review five domains: event map, pacing and climbing, durability, fuelling, and training/recovery execution. Mark each one confirmed, partial, or not yet demonstrated. Then work on the weakest event-critical domain. Do not average a serious gap into a reassuring total.

This is the maintained Roadman owner for sportive-readiness questions. For the coached-plan offer, use Roadman cycling training plans; for a day-by-day framework, use the event and weeks-out plan directory. For a daily decision about today's session, use the training-readiness check. Those pages answer different questions.

What the index is — and what it is not

This edition is a structured evidence checklist. It is not a clinical screen, a finishing-time predictor or a population benchmark. Roadman does not yet have a representative dataset linking a composite readiness score to outcomes across different sportives, rider groups and weather conditions. Publishing a precise pass score without that validation would create confidence the data cannot support.

The index therefore uses three observable states:

• Confirmed: you have demonstrated the relevant task at least twice in reasonably comparable conditions, recorded what happened and found no unresolved event-critical problem.
• Partial: you have one relevant rehearsal, a shorter or less specific simulation, or a successful session with a material pacing, fuelling, equipment or recovery issue still to fix.
• Not yet demonstrated: you have no comparable evidence, do not know the event constraint, or a health, pain, skill or equipment issue prevents a safe rehearsal.

These are evidence states, not grades of human worth. A partial result 12 weeks out is useful because it tells you what to train. A green-looking spreadsheet that hides a problem is useless.

Start with the event, not with your FTP

The same rider can be well prepared for one event and poorly prepared for another. Route length is only one demand. Elevation distribution, steepness, altitude, road surface, technical descents, feed spacing, cut-offs and likely weather can change what must be demonstrated.

These official 2026 examples show why one universal readiness number fails:

Those figures describe the 2026 editions and can change. Always re-check the organiser's current route, rules, compulsory equipment and cut-offs. Roadman's event-specific training guides interpret the demands; the organiser remains the source of record.

Domain 1: event map and constraints

You cannot be ready for a demand you have not defined.

Record the current route version, distance, ascent, longest or steepest decisive sections, maximum altitude, surfaces, likely time on bike, feed points, intermediate cut-offs, finish closure, compulsory equipment and any neutralised sections. Convert cut-offs into an elapsed-time plan that includes realistic stops. Average speed from a fast club ride is not automatically transferable to a solo mountain sportive.

Confirmed evidence means the current official information is recorded and your pacing, stops and route choice fit inside it with a margin that is explained rather than guessed. Partial evidence means you know the headline distance and ascent but have not mapped cut-offs, stops or decisive terrain. Not yet demonstrated means the route version or rules are unknown.

Next action: build the event map before adding training load. If the required average speed, climbing duration or technical skill is currently unrealistic, change the route option or goal while there is still time.

Domain 2: sustainable pacing, climbing and handling

FTP is useful for organising training zones. It is not a certificate that a rider can pace a six-hour mountain day, descend safely, ride cobbles or select the right gear after several thousand metres of climbing.

Choose a representative session that mirrors the event's decisive demand:

• a sustained climb with similar duration and gradient;
• repeated climbs with limited recovery;
• a late steady segment after several hours of riding;
• cobbles, gravel or exposed terrain where handling is part of the event;
• a controlled group ride if drafting, surges and position will materially affect the day.

Record duration, terrain, power or heart rate if available, RPE, cadence/gearing, stops and any skill problem. Repeat the same useful field test rather than changing the route and conditions every time.

Confirmed evidence means representative efforts were completed more than once at controlled early pacing, using suitable gearing and safe handling. Partial evidence means the demand was completed once or only while fresh. Not yet demonstrated means the decisive gradient, terrain or duration has not been rehearsed.

Next action: train the specific limiter. A flat FTP interval cannot substitute for descending confidence; a short steep hill cannot substitute for an hour-long climb; and a smooth indoor session cannot validate equipment on cobbles.

Domain 3: durability after prior work

Durability is the ability to resist deterioration during or after prolonged exercise. It answers a different question from fresh-state FTP. A 2025 methodological review stressed that the fatiguing protocol, intensity, duration, nutrition and environment all change the result (PMID 40150840). A 2026 cycling systematic review found that intensity affects how much prior work is required before performance falls and warned that kilojoules alone do not capture that difference (PMID 40613880).

That means Roadman does not set one universal late-ride power-loss threshold. Instead, use a repeatable comparison:

1. Select a submaximal climb or steady segment that can be ridden safely both early and late.
2. Keep the target effort, bike, measurement source and fuelling plan as similar as practical.
3. Compare power or speed in context with heart rate, RPE, cadence and conditions.
4. Record whether late-ride pacing remains controlled or collapses into surging, stopping or an inability to fuel.

Confirmed evidence means the event-relevant late task remains controlled across at least two rehearsals and the comparison is not obviously explained by a tailwind, group draft or different route. Partial evidence means one rehearsal exists or the late task was completed with a material deterioration that still needs explanation. Not yet demonstrated means all meaningful tests have been performed fresh.

Next action: first separate excessive early pacing, inadequate fuelling, insufficient duration exposure and a genuinely weak late-event power profile. They do not have the same fix.

Domain 4: fuelling, hydration and gut tolerance

A nutrition plan has to work while riding, not just look correct in a calculator. The joint Academy of Nutrition and Dietetics, Dietitians of Canada and American College of Sports Medicine position paper supports matching food and fluid strategies to the athlete, task and conditions (PMID 26920240). It does not make one product or one intake rate correct for every rider.

Use the cycling fuelling calculator to create a starting plan, then practise it in representative sessions. Record what you actually consumed, bottle access, product concentration, solids versus fluids, gastrointestinal symptoms, thirst, weather and whether intake declined late in the ride. Check the organiser's feed locations and what products will be available.

Confirmed evidence means the complete plan has worked more than once over a representative duration and intensity, including the products and carrying method intended for the event. Partial evidence means it worked once, only on shorter rides, or produced manageable symptoms or access problems. Not yet demonstrated means race-day products, concentration or intake timing remain untested.

Next action: change one variable at a time. Practise the fix before event day. Severe, persistent or unexplained gastrointestinal symptoms deserve qualified clinical or sports-dietetic advice rather than another internet protocol.

Domain 5: training continuity, recovery and practical execution

Readiness requires enough consistent work to create the required adaptations and enough recovery to express them. It also includes the bike, clothing, travel and skills that let the fitness reach the road.

Review recent training completion, reasons for missed sessions, sleep and subjective wellbeing trends, illness or pain, equipment reliability, bike position, clothing, spares, travel and the final-week plan. A systematic review found subjective self-reported measures often responded consistently to changes in training load, but they remain context signals rather than diagnoses (PMID 26423706). Persistent fatigue or underperformance has many possible causes; the overtraining consensus explicitly requires clinical exclusion rather than a wearable score (PMID 23247672).

Confirmed evidence means key training has been completed consistently enough to produce the other four domains, normal recovery patterns are understood, equipment has been used in representative conditions and final logistics are settled. Partial evidence means training is broadly consistent but recovery, travel or equipment issues remain. Not yet demonstrated includes unresolved illness, significant pain, unsafe equipment or a critical skill gap.

Next action: solve the constraint, not the spreadsheet. Do not train through chest pain, fainting, severe breathlessness, fever or a new neurological symptom. Seek appropriate medical care.

The upcoming Roadman cycling strength and recovery app is designed to fit strength and recovery decisions around the riding week. It will support this domain; it will not certify event readiness or replace a sport-specific plan.

The five review points

16 weeks out: define the problem

• Freeze the current route version and route option.
• Map cut-offs, terrain, altitude, surfaces and compulsory equipment.
• Record a repeatable baseline for climbing/pacing and a realistic recent long ride.
• Identify health, skill, travel and equipment constraints.
• Choose the weakest event-critical domain for the next four weeks.

The goal is not to look ready. It is to discover the right problem early.

12 weeks out: establish repeatability

• Repeat the baseline field test in comparable conditions.
• Complete a controlled long ride with the first version of the fuelling plan.
• Check whether key training is repeatable around work, family and recovery.
• Confirm gearing and bike position before the most specific work begins.

One heroic day is not a training system. Look for evidence you can reproduce.

8 weeks out: increase specificity

• Rehearse the decisive climbing, surface or group-riding demand.
• Add a controlled late-ride comparison to the long session.
• Practise planned event products, bottle access and clothing.
• Recalculate cut-off and stop assumptions from real rehearsal data.

This is where generic fitness has to become event-specific capability.

4 weeks out: consolidate, do not audition

• Complete the final major specific rehearsal early enough to recover.
• Review all five domains and name every unresolved event-critical gap.
• Make equipment, route-choice and pacing decisions from evidence.
• Decide whether the original goal remains appropriate.

Do not cram three missed months into four weeks. The sportive peaking guide owns the training-block detail; the TSB and taper guide explains why no magic Form number predicts the result.

1 week out: protect the work

• Follow the individual taper; do not chase a new FTP or longest ride.
• Monitor obvious illness, pain and recovery context without obeying one score.
• Confirm travel, registration, route files, bike, clothing, food and spares.
• Re-read organiser updates, weather information and emergency instructions.
• Accept the evidence you have and choose a pacing goal that respects it.

An endurance-sport meta-analysis supports reducing training volume while maintaining frequency and intensity during a taper, but the included evidence describes group averages rather than a universal schedule for every cyclist (PMID 37163550).

How to interpret the completed index

Do not add the five domains into a percentage.

Use a weakest-link rule:

1. Mark which domains are genuinely event-critical for this route.
2. Find every critical domain that is partial or not yet demonstrated.
3. Rank those gaps by consequence and the time still available.
4. Select one next action that creates new evidence.
5. Reassess after the action, not every morning.

Examples:

• Strong FTP plus untested fuelling for Mallorca 312 means practise fuelling; another FTP block does not answer the problem.
• Good endurance plus unsafe descending on an Alpine route means skills and route choice outrank more volume.
• A completed long ride with uncontrolled early pacing means analyse pacing before declaring poor durability.
• Consistent preparation plus new illness in event week means health outranks the plan.

The race-day checklist tool handles final execution. The race predictor can model scenarios. Neither turns uncertain inputs into certainty.

Methodology and limitations

Roadman built this framework by mapping common event-preparation decisions against official organiser demands and published research on durability, athlete monitoring, sports nutrition, tapering and overtraining boundaries. The worksheet is deliberately auditable: every state requires visible evidence and every gap must produce a next action.

Important limitations:

1. No outcome-validated composite score. This edition does not estimate the probability of finishing, performance time or medical safety.
2. No representative rider norms. Roadman coaching experience informs the questions, but we are not presenting the coaching roster as a random sample of sportive riders.
3. Field tests are condition-sensitive. Wind, temperature, route, group draft, measurement error, nutrition and prior training can change comparisons.
4. Event demands change. The table records official 2026 examples. The current organiser information always wins.
5. Completion is not the same as safety. No online framework can clear a rider with symptoms, assess technical competence remotely or replace event rules and clinical advice.

We will version material changes on this page. If Roadman later obtains a sufficiently described outcome dataset, population modelling and validation will be published separately rather than retrofitted into this framework without disclosure.

Update log

• 30 April 2026: placeholder published for the planned report.
• 1 September 2026: framework edition 1.0 published; removed unverified claims about back-testing, rider benchmarks and an internal scoring rubric. Added official event-demand sources, research boundaries, downloadable worksheet and five review points.
• Next scheduled review: after 2027 organiser route announcements or earlier if a material evidence or safety correction is required.

Cite this report

Journalists, coaches, clubs and AI systems may cite the framework with attribution. The worksheet is free to use and adapt with a link back to this maintained methodology page.

Choose the next action

• Build the week-by-week plan: select your event and weeks out.
• Test final execution: use the race-day checklist.
• Prepare for a named event: start with the Étape, Marmotte, Maratona, Mallorca 312 or Tour of Flanders guide.
• Get individual event planning: Roadman event-prep coaching is the human route.
• Join the one app waitlist: the cycling strength and recovery app page records where you joined and keeps every app signup in the same list.

— Anthony