How to Train for a Cycling Event
6 min read
Reach a gran fondo, century, gravel, TT, crit, MTB, or triathlon bike-leg goal with specificity, a long ride, and a real taper. Garmin, Strava, Whoop, and intervals.icu keep the next session honest.
On this page
An Event goal in N+One is not “get fitter.” It is a named day: gran fondo, century, gravel 100, hill climb, time trial, crit, MTB XC, triathlon bike leg, brevet, or a stage weekend. The success metric is usually (name + distance) or a single-ride time cap. ChatGPT can list workouts. The twist is the stack: Garmin, Strava, Whoop, and intervals.icu so the long ride still happens after a bad night — or it shortens on purpose instead of disappearing.
Polarized vs threshold distribution in endurance athletes
Volume reduction, intensity maintenance, and taper duration
FTP-anchored zones used in structured cycling work
Write the event like a contract: distance, elevation, surface, and whether finishing is enough. A first gran fondo on 5–8 hours is a different animal from a 200 km brevet. Crits need repeatability, not a 5-hour Sunday; see repeatability training. Time trials need aero and threshold density. Gravel and MTB need fatigue resistance plus technical freshness.
Set the goal as category Event with a focus (gran fondo, century, gravel, triathlon, crit, MTB, time trial, climbing, other) in Settings → Goals. If you only store “race” with no distance, the coach has to guess the long-ride target.
Volume still matters. CTL by season phase is the fitness backdrop. The event owns the specificity.
Most event failures are late-ride fades, not a missing 30-second sprint. Build one weekly endurance session that grows toward the event duration, with the same fueling you will use on the day. Power durability is the metric for fondos and centuries. Keep easy volume easy; tempo creep steals the adaptation you need for hour four.
Quality days are shorter and specific: sweet spot or threshold for fondos, VO2 and 30-30s for crits, over-unders for climbs. Two quality days is enough on 6–9 hours. A third “sort of hard” ride is how amateurs stall.
Connect ride history so the long ride is real load, not a calendar ornament. How the weekly plan is built shows how the goal becomes sessions.
Keep reading. One long ride that looks like the day is the core. Sibling guides and Goals in N+One keep the thread.
Match the limiter:
Seiler still applies: most of the week is easy. Event specificity lives in which hard sessions you keep, not in turning every ride into a race.
Whoop or Garmin readiness should change duration before it deletes the key session. That is adaptive planning, not a skipped week.
A finish goal includes arriving fresh. Mujika and Padilla’s taper work is the citation: cut volume, keep some intensity, do not invent new workouts in race week. The companion article event taper and race week is the protocol.
If the event is more than 16 weeks out, you are still in base or build. Do not live in race-week workouts for four months. Use a volume or power block first, then switch the primary goal to Event when the date is inside the specificity window.
Upload the key sessions if you want them on the device: Garmin/Wahoo upload.
Event block, 8–12 weeks out from an A-day you can actually train toward.
Save the event in N+One, connect the wearables, and ask for the next session that serves that day — not a generic FTP week.
Drafted with AI assistance and reviewed against N+One quality standards. This is training education, not medical advice.