Writing a 12-week race prep plan from scratch is one of those tasks that looks straightforward on paper and absorbs an entire weekend in practice. Most of the work is calendar arithmetic, not coaching judgement: figuring out which weeks should accumulate volume, which should deload, how the long run progresses, and where the taper fits. A training plan generator handles that structural work in seconds, which frees you up to focus on actually executing the plan.
This is a step-by-step walkthrough of how to use a free training plan generator to produce a usable race prep plan, what each input means, and how to adjust the output for your real-world constraints.
Step 1: Pick a Specific Race and Date
A training plan generator needs three pieces of information up front: the race distance, your goal time or experience level, and the date you want to peak. Vague goals produce vague plans. "Train for a half marathon sometime in the fall" gives the generator nothing useful to work with.
A useful exercise before opening any generator: write down the race name, the date, your current honest fitness level, and your goal finish time. If you do not know your current fitness, run a one-mile or 5K time trial at race effort. The result tells the generator what intensity zones to assign across the cycle.
The free training plan builder by EvvyTools at the Training Plan Builder tool page covers 5K, 10K, half marathon, and marathon distances, with three to four experience tiers per distance.
Step 2: Set Days Per Week Honestly
The most common mistake at this step is picking the number of training days you wish you could do rather than the number you can actually sustain. A plan that calls for six training days per week looks impressive in the abstract and gets abandoned by week three when life makes that schedule impossible.
The honest answer is usually one day per week lower than the optimistic answer. Most working adults running their first half marathon do better with a four-day-per-week plan they actually complete than a five-day plan with a 30 percent miss rate.
A useful sanity check: look at the last six weeks of training data (whatever you have). Count actual sessions completed. That is your sustainable rate, not the rate you intended to do.
Step 3: Choose Program Length Based on Your Starting Point
A generic "12 week half marathon plan" assumes a specific starting fitness level. If you are coming off a year of consistent base building, 10 weeks may be enough. If you are building from a low base, 16 to 20 weeks is more realistic.
A practical formula: take the difference between your current weekly mileage and the peak weekly mileage the plan will require. If you need to roughly double your volume, give the plan at least 16 weeks. If you need to add 20 percent, 10 to 12 weeks works.
Going too short and ramping too fast is one of the most reliable ways to get injured. The American Academy of Orthopaedic Surgeons has consistently flagged rapid mileage increases as a primary risk factor for running overuse injuries.
Step 4: Read the Output as a Template, Not a Contract
The plan the generator produces is a starting point. Real training plans get adjusted weekly based on how the previous week went. Treat the generated plan as a template that defines structure (which weeks are build, which are recovery, where the taper starts) and adjust specific workouts to your situation.
Some workouts will need substitution. Hill repeats may not fit your route. A 16-mile long run may need to be done on a treadmill due to weather. Tempo workouts may need to shift days because of work travel. These adjustments do not invalidate the plan. They are the normal process of executing one.
What you should not adjust without thinking carefully:
- The recovery weeks (these protect the rest of the plan)
- The taper structure in the final two to three weeks
- The total volume progression rate (cutting it lower is fine; pushing it higher is risky)
The structural decisions are where the generator adds the most value. The specific workout choices are where your judgement applies.
Step 5: Plan for Adjustments in the Middle Weeks
Every multi-week training plan hits a rough patch around weeks four to six. Volume is starting to feel real, the novelty has worn off, and minor aches start showing up. Plans that survive this stretch usually have explicit adjustment rules built in.
Useful rules to write down before week four arrives:
- If you miss two sessions in a row, the next session is easy effort regardless of what the plan calls for.
- If resting heart rate is elevated by more than 5 to 7 beats for three consecutive mornings, that week's intensity drops.
- If a soft-tissue ache shows up on consecutive runs, swap to cross-training (cycling, swimming) for two to four days before resuming.
These rules are not in the generated plan because they cannot be. They are the executor's job. But writing them out before week four lets you make better decisions in the moment than you will if you have to reason about them tired and stressed.
Step 6: Track the Two Numbers That Matter
A common mistake is tracking too many metrics and losing sight of the ones that actually indicate the plan is working. For race prep, two numbers usually carry most of the signal:
- Weekly mileage actually completed (not planned): this is the truth about your training volume. The planned mileage is a hypothesis. The completed mileage is the data.
- Pace at a benchmark effort: pick one workout that repeats across the cycle (a particular tempo run, a fixed-distance time trial every four weeks) and watch how the pace evolves at the same perceived effort. Drift in the right direction means the plan is working.
Modern guidance from places like Runner's World emphasizes process metrics over outcome metrics for exactly this reason. Outcome metrics (race day finish time) only update once. Process metrics update every week and tell you whether the plan is on track.
Step 7: Execute the Taper as Written
The final two to three weeks of a race prep plan are the taper. The taper reduces training volume while maintaining intensity, allowing accumulated fatigue to dissipate while preserving the fitness gains.
This is the single most commonly mishandled phase. Athletes who feel anxious about losing fitness in the taper often add unstructured training, which produces residual fatigue on race day. Athletes who feel tired in the early taper often cut intensity entirely, which produces detraining.
The correct execution: trust the plan. The taper exists because consolidated research on race performance consistently shows that planned recovery before competition produces better outcomes than continued accumulation. The National Strength and Conditioning Association summarizes this with the principle that performance peaks roughly two weeks after the highest training load, not at the highest training load.
Putting It All Together
A free training plan generator handles the structural work of designing a race prep cycle. The execution is still your job, but the calendar math, periodization, and recovery cadence are taken care of in the first five minutes rather than the first weekend.
The longer guide on this topic, How to Build a Multi-Week Training Plan That Actually Produces Progress, covers the underlying principles (periodization, progressive overload, recovery scheduling) in more depth. The walkthrough above is the practical application: a usable plan in seven steps, an honest assessment of where the generator helps and where it cannot help, and the discipline points that determine whether the plan actually pays off on race day.
For complementary calculators (calorie targets, pace conversions, VO2 max estimates), EvvyTools has a tools directory that covers the supporting math.
Top comments (0)