A training plan copied straight from a magazine or a generic app template often ignores the one thing that makes a plan work: it has to progress from where a runner actually is, not from a fixed starting assumption. Building one from scratch, or adjusting a template correctly, comes down to a handful of principles that generic plans frequently skip.
Start From Current Fitness, Not Goal Fitness
The most common training plan mistake is picking a plan built for the goal race pace rather than current fitness. A runner aiming for a 3:30 marathon who is currently running 10-minute easy miles needs a plan that builds toward that goal gradually, not one that assumes 3:30-pace fitness from week one. Following a plan designed for a fitness level not yet reached is the fastest path to overuse injury.
The fix is starting the plan at a mileage and intensity level matched to the last four to six weeks of actual training, then layering progression on top of that baseline. Most well-designed plans increase weekly mileage by no more than 10 percent per week, with a lighter "cutback" week roughly every third or fourth week to let the body absorb the load.
Structure: Easy, Threshold, and Long Run
A well-built week has three load-bearing pillars: easy running for aerobic base (roughly 80 percent of weekly volume, run at conversational pace), one threshold or interval session for speed and lactate tolerance, and a long run that builds toward race-specific endurance. Runners who skip the easy-pace discipline and run every run at a moderate-hard effort tend to plateau, because the body never gets the low-intensity stimulus that builds aerobic capacity without excess fatigue.
A Training Plan Builder generates this weekly structure automatically based on a goal race, current mileage, and available training days, which removes the guesswork of manually laying out 12 to 20 weeks of progressively harder sessions. Getting the progression curve right by hand is tedious enough that most runners either overdo it or undertrain without realizing it.
Periodization: Base, Build, Peak, Taper
Training plans generally move through four phases. Base building establishes aerobic volume and injury resilience. The build phase introduces race-pace-specific work: tempo runs, goal-pace intervals, and longer long runs. The peak phase holds the highest training stress of the cycle, typically two to three weeks before the goal race. The taper reduces volume sharply (often 40 to 60 percent) in the final two to three weeks while keeping some intensity, letting the body arrive at the start line recovered but sharp.
Skipping the taper is a frequent mistake among runners who feel "behind" and try to cram in extra mileage right up to race week. The Road Runners Club of America and most published training methodologies agree that a proper taper improves race performance more reliably than any additional training stimulus crammed in during the final two weeks.
Building In Flexibility for Missed Sessions
A rigid plan that cannot absorb a missed run due to illness, work travel, or bad weather sets a runner up to either skip the plan entirely after one disruption or unsafely double up sessions to "catch up." Good plans build in a buffer, sometimes an easy week every third week that doubles as recovery room for a missed session, so a single disrupted week does not derail the entire training block.
Periodization research, including work referenced by the USA Track & Field coaching education program, generally supports adjusting the plan around life rather than forcing life around a rigid plan. A missed long run is rarely catastrophic; a pattern of skipped easy runs that never gets addressed usually is.
How to Adjust a Plan Mid-Cycle Without Blowing It Up
Real life interferes with training plans constantly: a work trip cuts a week of running short, a minor illness knocks out five days, or a nagging ache means a planned speed session needs to become an easy run instead. The instinct to "make up" lost training by cramming extra mileage into the following week is almost always the wrong move, since it converts a manageable setback into a real injury risk.
The better adjustment is usually to shift the entire remaining plan back by however many days were lost, rather than trying to compress the same total volume into less time. A runner who loses a week to illness six weeks before a goal race is generally better off running a slightly shorter buildup than trying to hit every planned session on the original calendar. Coaches who work with the USA Track & Field certification programs consistently teach this principle: protecting the taper and avoiding injury takes priority over hitting every number on a pre-written schedule.
Common Plan-Following Mistakes
The biggest mistake is running easy days too hard. Generic plans label days "easy" without giving a runner a real pace target, and without a number, most runners default to a moderate effort that's harder than true easy pace, which blunts the aerobic benefit of the easy day and adds unnecessary fatigue heading into the next quality session. Tying easy pace to an actual calculated range, rather than a feeling, fixes this more reliably than willpower does.
A second common mistake is ignoring the long run's actual purpose. Long runs build aerobic endurance and mental toughness for race distance, not raw speed, yet many runners drift into running long runs faster each week as a personal challenge. This turns a recovery-adjacent aerobic session into another hard effort, stacking fatigue rather than building the specific endurance the long run is meant to develop. Keeping most long runs at a genuinely conversational pace, with occasional planned race-pace segments built in deliberately, preserves the intended training effect.
Choosing a Plan Length That Matches the Goal
Marathon plans commonly run 16 to 20 weeks, half marathon plans 10 to 14 weeks, and 5K or 10K plans as short as 8 weeks for runners with an existing aerobic base. A plan that's too short for the goal distance forces compressed progression that raises injury risk, while a plan that's too long for a runner's current fitness can lead to burnout well before race week arrives. Matching plan length to both the goal distance and current fitness level, rather than picking a popular template regardless of fit, is one of the more overlooked decisions in the entire process.
Runners returning from a break or coming off a lower-mileage period generally benefit from adding a few weeks of base-building before starting a structured plan's official week one, rather than jumping straight into a plan calibrated for someone already at a higher fitness level. This extra patience up front tends to pay off later in the cycle as fewer forced adjustments and less accumulated fatigue heading into the goal race.
Connecting the Plan to Race-Day Pacing
A training plan's ultimate output is race-day readiness, but readiness only pays off if it is paired with the actual pacing math covered in EvvyTools' guide to calculating race pace and building split plans. Training paces set early in a plan, based on current fitness, should be recalculated as fitness improves through the build and peak phases so that goal-race pace reflects the runner who shows up on race day, not the one who started the plan months earlier.
A good plan and accurate pacing math solve two different halves of the same problem. The plan builds the fitness; the pace math makes sure that fitness actually gets spent correctly across 13.1 or 26.2 miles instead of being wasted on a pacing mistake in the first five.
Top comments (0)