VDOT Training Paces for Half Marathon Runners

VDOT is a performance-based score that places a recent race time on a common scale and estimates related race performances and training paces. It is not a laboratory measurement of your actual oxygen uptake. Its value is practical: one representative result can give you coherent starting points for easy running, threshold work, intervals, and half-marathon race pace.

The word “starting” does the responsible work. Equivalent-performance estimates assume that preparation transfers across distances. A runner with strong 5K speed but limited long-run history may receive a half-marathon prediction they are not yet prepared to sustain. Heat, hills, course measurement, wind, pacing, and fatigue also shape the source result. VDOT describes what that performance implies under broadly comparable conditions; it does not guarantee another performance.

Use the number to coordinate workout intensities, then verify each pace by its job. Easy pace must remain conversational. Threshold pace must be controlled and repeatable. Interval pace must allow even repetitions. Race pace must become plausible through specific training. If the number conflicts with those cues, adjust the pace—not your perception of reality.

A pace range acknowledges the precision limit of the input and the variability of outdoor running. If threshold work is suggested near 8:00 per mile, building a corridor around that value lets the runner start conservatively, account for minor grade and wind, and maintain the intended effort. A single target encourages constant watch corrections that create surges.

Use the slower edge for the first repetition, warm conditions, unfamiliar routes, or a runner new to the workout. Use the faster edge only when the entire session remains controlled under comparable terrain. Do not treat the fast edge as an achievement. Both edges are valid execution.

For easy running, the useful range may be especially broad. Day-to-day easy speed changes while the purpose stays constant. For short intervals, GPS instant pace may be too noisy; time over a measured repetition or lap average is more stable. Match the measurement method to the session rather than demanding identical precision everywhere.

Update after a recent, meaningful performance rather than on a fixed weekly schedule. A tune-up 5K or 10K midway through half-marathon training can recalibrate paces. If the race occurred in severe heat, on unusual terrain, or during a heavy week, keep notes and use the result conservatively.

A small score change does not require rebuilding every run. Pace suggestions already represent ranges, and normal daily variation can exceed the shift. Update the quality-session targets gradually and observe whether the same workout remains controlled. Easy pace should emerge from effort within the new range rather than being forcibly accelerated.

A worse result also deserves context. One poor race may reflect pacing or conditions. Repeated difficulty across workouts and races is stronger evidence that paces need slowing or training load needs review. The model helps organize data; it should not amplify every fluctuation.

Miles-first runners often receive minutes per mile, while tracks and international races use kilometers. Convert the pace, not just the distance label. A mile is approximately 1.609 kilometers, so minutes per kilometer is not the same number with a different unit. Use the calculator's built-in display rather than mental arithmetic during a workout.

On a 400-meter track, a per-mile pace must be translated into lap time. Four laps equal 1,600 meters, slightly short of a mile. For most training, the difference is small enough to manage with a proper calculator, but repeated manual rounding can make a threshold workout faster than intended. Save the target lap range before starting.

Avoid targets such as 8:07.3 per mile. Neither the source race nor outdoor conditions justify tenths-of-a-second certainty. Round to a usable range and pair it with effort. The goal is better judgment, not more digits.

Workouts include recovery, route choices, and submaximal intent. Completing 5 × 3 minutes faster than listed does not equal a continuous 5K performance. It may mean the source score is conservative, but it may also mean the repetitions were too short, recovery too long, or effort too high for the session.

Look for several converging signs before updating: threshold work repeatedly feels controlled at the fast edge, easy pace improves at the same effort under comparable conditions, and a representative race confirms the change. The race does not need to be perfect; it needs to be more valid than inference from fragmented work.

Do not withhold progress either. If multiple weeks and a new race support a higher score, update the ranges gradually. The purpose is to keep training aligned, not to protect an old number. Both inflation and stubbornness reduce calibration.

Enter the most representative recent performance in the free VDOT calculator. Save the source race, date, course, and conditions beside the score. Choose only one pace category to verify this week—easy if you are building consistency, threshold if easy volume is stable, or intervals if structured faster running already belongs in the plan.

Use the matching calibration workout and record pace, RPE, breathing, and next-day response. Keep or adjust the range from that evidence. A personalized plan can then sequence those calibrated paces around your schedule and race date; it should not treat the score as a reason to make every day faster.

Save the calculator input with the output. Six weeks later, “VDOT 44” is less informative than “VDOT 44 from a cool, certified 10K with even splits.” The provenance tells you whether a new result is genuinely more representative and prevents an unusually favorable performance from silently controlling months of training. Use the race-time predictor when the next question is an outcome range rather than a training pace.