Choosing a Zwift Training Plan That Fits the Week You Actually Have

Introduction

Zwift is a training tool, not just a game. It ships structured plans built by coaches and will schedule them onto your calendar for you. The hard part is not finding a plan. It is picking one that matches the hours you actually have, the event you actually care about, and the fitness you have today.

I am Christian. I ride Zwift most weeks and I am training for Ironman Copenhagen alongside an engineering degree, so my weeks are rarely fully mine to control. What follows is what I would want to read before committing to a block: how to choose, what a real week looks like at 3, 5 and 8 hours, and a worked example of getting from 2.8 W/kg to under an hour on Alpe du Zwift.

The Three Questions That Determine Everything

Answer these before you look at a single plan name. Every decision downstream falls out of them.

1. How many hours can you genuinely commit?

Not your best week. Your median week over the last two months, including the ones with a deadline or a sick child. Weeks of 4, 6, 3, 5, 2, 5, 4 and 6 hours make your number 4.5, not 6. This decides your intensity distribution more than anything else, because riding mostly easy only works if you have enough easy hours for them to be a stimulus. At 3 hours a week, 80% easy is 2.4 hours, which drives very little. At 8 hours it is 6.4 hours, which is real training.

2. What are you training for?

A 45-minute Zwift crit, a sub-hour Alpe and a five-hour fondo demand different things. The Alpe is a 50 to 70 minute near-steady effort with no coasting, so threshold and sub-threshold work is what moves the needle. A category C race is a series of 30-second to 3-minute surges bolted onto a threshold ride, so repeatability above FTP matters far more. A fondo is about durability, and only long rides build that. If you have no target, invent one. A plan without a target cannot tell you what to cut when time runs short.

3. Where are you now?

Two numbers: FTP and weight. A 75 kg rider at 250 W is 3.33 W/kg. Then be honest about training age. Someone with two years of unstructured riding has low-hanging fruit and will respond to almost anything consistent. Someone who has finished three plans and stalled needs a different stimulus, not more of the same. Get a reliable FTP before you start - the FTP calculator turns a 20-minute or ramp result into training zones, and every target in every plan scales off that one number.

What Are Zwift Training Plans?

Think of them as virtual coaches that guide your workouts week by week. Zwift offers around 17 cycling plans plus triathlon and running plans, each tailored to a goal from basic fitness to race preparation [1]. They run from a few weeks to several months, land on your calendar automatically, and usually allow a 2-3 day window per workout when life interferes. Every target is a percentage of your FTP, so the same plan gives a 180 W rider and a 300 W rider the same relative stress.

Getting Your FTP Right

FTP is roughly the maximum power you can hold for an hour, and Zwift uses it to set every zone. If you don't know yours, Zwift provides FTP tests - the 20-minute test, the shorter 2x8, or a ramp test [2]. Doing one before a serious plan is strongly recommended [2]. Don't fixate on the absolute number - it is a baseline to improve from, not a verdict [3].

Here is the part riders underestimate. An FTP set 15 W too high does not make you 15 W stronger, it makes every interval in the plan too hard by that same proportion - on a true 210 W threshold, about 7%. You then fail the last repeat of every session and conclude you are weak, when the problem is arithmetic. If a workout you finished comfortably three weeks ago is now impossible, suspect the number first. The racing category calculator is a quick sanity check on where your figure actually places you.

Choosing the Right Plan

For riders new to structure, "Zwift 101: Cycling" or "FTP Builder" are sensible starts. FTP Builder is a 6-week plan aimed at raising aerobic capacity and FTP [4], about four workouts a week and most under an hour. "Build Me Up" is the 10-12 week version for people who can commit months. If you want to race, the "Zwift Racing" plan by coach Shayne Gaffney includes race-specific work and simulations [5]. TT Tune-Up leans on sweet spot and threshold, which also suits climbing, and Gran Fondo mixes long weekend rides with intervals [6].

Polarised, Threshold-Heavy or Sweet Spot?

Underneath the plan names sit three philosophies about where your quality time goes. None is settled science. Here is what each asks of you and who it suits.

Polarised

Roughly 80% of sessions genuinely easy at 55-70% FTP, roughly 20% genuinely hard, almost nothing in between. It asks for volume and patience: the easy rides have to feel almost pointless, which is hard on a trainer where every watt is on screen. The case rests partly on descriptive studies of elite endurance athletes, who tend to train this way, and partly on a modest number of comparison trials. Suits riders with 7+ hours, riders who race often enough that races supply the hard 20%, and riders who plateau because every ride drifts into tempo.

Threshold-heavy

Most quality time at 95-105% FTP: 2 x 20 min, 3 x 15 min, 4 x 10 min. It asks for tolerance and good recovery, because threshold work costs a lot of fatigue per hour. The case is specificity - if your event is a 50 to 70 minute steady effort, training near the power you will hold is directly relevant. Suits time-crunched riders with a steady-state goal and a stable schedule. Punishes anyone who adds races on top, because that fatigue stacks quietly and then arrives all at once.

Sweet spot

Intervals of 10-20 minutes at 84-97% FTP. It asks for consistency rather than heroism: uncomfortable but finishable, three times a week. The case is efficiency - for a rider with 4 hours it delivers far more aerobic stimulus per minute than Z2 at much lower recovery cost than true threshold. The fair criticism is that it is easy to live there forever, and riders who do often stall after a few months with a decent FTP and no top end. Suits a build block or a return from a layoff. Suits nobody as a year-round diet.

What a Week Actually Looks Like at 3, 5 and 8 Hours

Percentages are of FTP. Warm-up means 10-15 minutes building from 50% to 70%; cool-down means 5-10 minutes under 60%.

3 hours a week

• Tue, 60 min: warm-up, 3 x 10 min at 88-93% with 5 min easy, cool-down.
• Thu, 45 min: warm-up, 5 x 3 min at 105-110% with 3 min easy, cool-down.
• Sat, 75 min: steady at 70-78%, last 20 min as 2 x 8 min at 90% if still fresh.

No recovery rides, because at 3 hours you cannot afford a session that does nothing. About a third of the 180 minutes sits at 88% or above, which is a high proportion by any standard. That is a build block, not a way of life - run it 8 to 10 weeks, then back off.

5 hours a week

• Tue, 75 min: 2 x 20 min at 95-100% with 8 min easy between.
• Wed, 45 min: steady 60-70%, including 3 x 5 min at 95-100 rpm for smoothness at low force.
• Fri, 60 min: 6 x 3 min at 108-115% with 3 min easy between.
• Sun, 2 h: endurance at 65-75% with 3 x 12 min at 88-92% in the middle hour.

That totals 300 minutes, of which roughly 95 are at or above sweet spot - close to a third. This is the most useful week for the largest number of riders, and close to what the better built-in plans prescribe.

8 hours a week

• Tue, 90 min: 5 x 5 min at 108-115% with 5 min easy, remainder at 60-65%.
• Wed, 75 min: steady 62-72%. No intervals, no drifting up.
• Thu, 45 min: recovery at 50-60%, high cadence, genuinely easy.
• Sat, 2 h: 3 x 20 min at 92-97% inside an easy ride - or a Zwift race instead.
• Sun, 2.5 h: endurance at 65-75% including a full climb at 80-85%. Alpe du Zwift is 12.2 km and 1,036 m of gain, which makes a near-perfect long sub-threshold block.

That is 480 minutes with about 85 of them genuinely hard, so roughly 80% easy and 20% hard - polarised in practice rather than in name. The volume is what makes it work: cut it to 5 hours by deleting the easy rides and you get the worst of both. For how these weeks chain into months see Zwift training periodization, and if a seven-day cycle never fits your life, the 10-day training week is a genuinely useful alternative.

Where the Built-In Plans Work, and Where They Don't

They work well when four things are true: you are new enough to structure that any coherent plan helps, your FTP is correct, your week is predictable enough to hit 4 of 4 sessions, and you have 3 to 6 hours. Under those conditions they remove the decision-making entirely, which is worth more than riders admit - the biggest cause of failed training is not choosing badly, it is not deciding at all. They work poorly in four situations.

• You have a fixed event date. Plans start when you press start, not a set number of weeks before your event. If your fondo is in 9 weeks and the plan is 12, you peak after it is over. Count backwards and drop a base week, not a build week.
• You race two or three times a week. The plan does not know about your races and prescribes its own intensity anyway. That is how riders end up with five hard days out of seven and a falling FTP.
• Your FTP is wrong. Retest properly instead of accepting an auto-adjustment from one strong race effort.
• You have more than about 8 hours. The plans don't scale up, so you add endurance volume around them and change the distribution the plan assumed.

Quick self-test: look at your last four weeks. Completed 80% or more of what you intended? A built-in plan will serve you well. Under half? The problem is not the plan's design, and a different plan will not fix it.

Executing the Workouts

Workouts appear under the "Training" tab as colour-coded blocks with on-screen targets. Most use ERG mode on a smart trainer, which sets resistance so you hit the prescribed wattage without shifting: if a block calls for 200 W, ERG holds you near 200 W regardless of terrain. Follow the cadence prompts when given - 75 rpm and 95 rpm at the same power load the muscle differently. Without ERG you shift manually and watch the number yourself.

Progression Without Digging a Hole

There are four levers - session duration, number of intervals, interval intensity, weekly frequency - and the common mistake is pulling more than one at once. Move one per week and hold the rest still. Week 1: 3 x 10 min at 90%. Week 2: 4 x 10 min at 90%. Week 3: 4 x 12 min at 90%. Week 4: easy. Do not jump to 4 x 12 min at 95% in week 2 because week 1 felt fine. It felt fine because it was week 1.

As a rough guide I keep weekly training time growth under about 10% per week. That is a widely used heuristic rather than a proven law, and its real value is stopping you from going from 4 hours to 7 after one motivating race. The other guardrail: you should be able to finish the last interval of your hardest session. If you can't, the week was too big, not the workout.

Signals you have overreached

• Power at the same effort drops. An interval you held at 105% last week now feels like 115%. The clearest single signal.
• Heart rate won't climb. You are pushing hard and HR sits 10 bpm below where it normally lands. A suppressed ceiling under load warns you earlier than an elevated resting HR.
• Resting HR up several mornings running. One high morning is noise. Five in a row, 5-7 bpm above normal, is information.
• Sleep gets worse as training gets harder. Load should make you sleep better, not leave you wired at midnight.
• Two abandoned sessions in a row. One bad day is a bad day. Two consecutive quits is your body voting.
• The dread test. If a workout you normally enjoy has felt like a chore for a week, take the easy week now.

The response is the same every time: three to five days at 55-65% FTP with no intervals, normal food, more sleep. That usually resolves it. If it doesn't, you are past overreaching and the fix is measured in weeks.

Recovery Weeks, and Why Skipping Them Backfires

Training does not make you fitter. Training plus recovery makes you fitter, because the adaptation happens while you rest. That is why a lighter week every third or fourth week sits in every serious plan, and why skipping it is the most common way riders sabotage themselves. It is easy to skip precisely because you feel strong at that moment - and that feeling is fitness still masked by fatigue.

A recovery week is not a week off. Keep the same number of rides, cut total time by 40-50%, halve the interval volume, and keep the intensity of what remains. A 5-hour week becomes 2.5-3 hours, and Tuesday's 2 x 20 min at 95-100% becomes 2 x 8 min at the same watts. You keep the feel and lose the fatigue. The proof it worked: in the first hard session of the next block you produce more power at the same perceived effort. If you don't, either the recovery was too short or the block before it was too big - information you only get by taking the week.

Testing Progress Without Wrecking the Plan

A full 20-minute test costs a quality session plus two or three easy days, so the real price is half a week. Test every three weeks and you spend a sixth of your year measuring instead of improving. Three cheaper options:

• Formal tests at block boundaries only. One at the start of a 12-week plan and one at the end, placed on the last day of a recovery week when you are fresh and the cost is already paid. Put the result through the FTP calculator to reset your zones.
• A repeatable benchmark session. Keep one workout - 2 x 20 min at your current 100% target works well - and repeat it every fourth week under identical conditions: same time of day, same fan, same fuelling. If average heart rate for the same power drops 4-5 bpm, you have improved even though the FTP number hasn't moved.
• A climb as a field test. A full climb is a steady effort of known length, which makes it unusually clean. Ride it hard once per block and compare times. The Alpe du Zwift calculator, the Ven-Top calculator and the general climb time calculator convert a target time into the W/kg it needs.

The caveat on climb testing: it measures W/kg, not FTP, so a weight change moves your time with no change in fitness - see the power-to-weight deep dive for what that ratio does and doesn't tell you. Structured interval training raises the duration and intensity you can sustain [7], and Zwift will sometimes offer an FTP bump on its own after a strong effort. Treat that as a prompt to test properly, not as a test result.

Worked Example: 2.8 W/kg to Under an Hour on the Alpe

Take a concrete rider: 75 kg, FTP 210 W, so 2.8 W/kg. Alpe du Zwift is 12.2 km with 1,036 m of gain, roughly 8.5% average across 21 hairpins. This site's fit for the climb is time_seconds = 148.60*(W/kg)^2 - 1954.08*(W/kg) + 8329.87, which puts that rider at about 67:03. Going under an hour takes roughly 3.2 W/kg, or about 59:58. The gap is seven minutes and 14% in ratio terms.

The last column hides a second route. Reaching 240 W at 75 kg is a 30 W gain. Reaching 227 W at 71 kg is the same 3.2 W/kg from a 17 W gain plus 4 kg. For a rider carrying spare weight the split route is far more achievable, which is why I would not build this block around power alone. If you are already lean, power is the only lever and 12 weeks may not be enough.

A realistic 12-week shape

For pacing the attempt itself - where to sit relative to threshold, and why going out 10 W too hard on the first two kilometres costs more than it gains - see my guide to conquering Alpe du Zwift.

Fuelling, Rest and Consistency

Eat carbohydrate before hard sessions and during anything over an hour. Get a fan and a towel - indoor sweat rates are high and dehydration flattens power long before you feel thirsty. Take the rest days the plan gives you rather than cramming five sessions into three days, and don't add hard races on unscheduled days.

One specific point, because it trips people up: if you are eating in a deficit to lose weight for a climbing goal, don't run it through your hardest weeks - a deficit blunts the adaptation you are paying for with those intervals. My own working approach is a modest deficit of roughly 300-400 kcal a day during base and recovery weeks, then eating to fuel through the threshold and climb-specific blocks. That is reasoning rather than a study result, but the logic is straightforward.

Conclusion and Next Steps

A training plan is mostly a decision-removal device. Its value is that on a Tuesday evening when you are tired and undecided, the session is already chosen. Match the plan to your honest hours, your real event and your actual starting point. Set FTP correctly, take the recovery weeks even when you feel strong, and test rarely enough that you spend the year training rather than measuring. Consistent structured training will make you stronger [7]. When a plan ends, test, then choose the next block from what you found rather than what sounds fun.

To set a target before you start, run your numbers through the FTP calculator and the Alpe du Zwift calculator, then browse the rest of the training articles. If you think something here is wrong, tell me - the contact page works, and how I handle corrections is set out in the editorial policy.