Running VDOT & Training Pace Calculator

VDOT Training Guide (Daniels' Running Formula)

What is VDOT?

VDOT: a measure of running fitness, developed by Dr Jack Daniels (one of the most influential running coaches of the past 50 years). VDOT incorporates VO2max plus running economy and lactate threshold into a single score. Higher VDOT = faster runner. VDOT scale: 30: novice runner. 40: recreational fit (45min 10K, sub-1:50 half). 50: well-trained club runner (sub-40 10K, sub-90 half, sub-3:15 marathon). 60: competitive amateur (sub-35 10K, sub-78 half, sub-2:55 marathon). 70+: elite level, with times around sub-31 for 10K and correspondingly fast times across all other distances.

What do I need to know about The Five Daniels Training Paces?

Easy (E) pace: 59-74% of VDOT. Conversational pace. 60-75% of all training. Builds aerobic base, capillarisation, mitochondrial density. Most underrated training type — most runners run easy pace too fast. Marathon (M) pace: 75-80% of VDOT. Race pace for marathon. Used in long runs to develop race-specific fatigue resistance. Threshold (T) pace: 82-88% of VDOT. 'Comfortably hard' — fast but sustainable for 20-60 min in training. Builds lactate threshold. Tempo runs, cruise intervals. Interval (I) pace: 95-100% of VO2 max, hard, uncomfortable efforts typically run in shorter, more intense intervals with full recovery between.

Why Training Paces Matter?

Most recreational runners train too fast for their easy runs and not fast enough for their hard runs. The result: chronic medium intensity training — too hard to fully recover, too easy to drive adaptation. Polarised training (favoured by elite distance runners): 80% truly easy + 20% hard (threshold/interval). Limited 'grey zone' middle effort. Producing the workout the body needs: workouts only effective when run at the right intensity. Threshold workout run at 90% effort instead of the correct threshold pace becomes an interval-style session instead, training a different energy system than intended and undermining the workout's actual purpose.

What do I need to know about Building a Daniels Training Week?

Typical structure for 40-50 mpw runner targeting half marathon: Monday: 5 miles easy (E pace). Tuesday: workout day. Examples: 4×1 mile @ T pace (jog 1min recovery between). OR 5×1km @ I pace (jog 90sec recovery). Wednesday: 5 miles easy. Thursday: 7 miles easy or M pace. Friday: rest or cross-training. Saturday: race or hard workout (e.g. tempo intervals). Sunday: long run 10-14 miles, mostly easy with possibly 3-5 miles at M pace embedded. Higher mileage runners, at 60-80 miles per week, add double days and generally more easy mileage around the same core quality sessions, rather than increasing the hard workouts themselves.

How Accurate Is VDOT at Predicting Race Times Across Distances?

VDOT, developed by exercise scientist Jack Daniels, is calculated from a single race performance and is designed to predict equivalent performances at other distances reasonably well because it accounts for the physiological reality that running economy and VO2 max utilisation change predictably with race duration. It tends to be most accurate when the input race and the predicted race are reasonably close in duration (for example, using a 10K to predict a half-marathon), and somewhat less accurate across very different durations (using a 5K to predict a marathon), for the same reasons any duration-based prediction formula loses accuracy over a wider gap — longer races increasingly depend on fuelling, pacing discipline, and fatigue resistance that a short race doesn't test. Daniels' own guidance treats VDOT training paces as a strong starting point to be adjusted based on how workouts actually feel, rather than a fixed, unchangeable prescription.

What If VDOT Training Paces Feel Too Easy or Too Hard?

Because VDOT is calculated from a single performance, it can occasionally overestimate or underestimate true current fitness if that input race was run in unusual conditions (extreme heat, altitude, a poorly paced effort, or significant time since the race was run and fitness has since changed). Daniels' own system explicitly allows for adjustment: if prescribed easy or threshold paces consistently feel considerably harder than they should across multiple sessions, the athlete is advised to recalculate from a more recent or more representative performance rather than forcing paces that don't match current fitness. The training paces are also meant to be run by feel within a reasonable range around the calculated number rather than hit to the exact second, since weather, terrain, and fatigue all cause legitimate day-to-day variation that a rigid pace target does not account for.

Should VDOT Training Paces Be Adjusted With Age?

VDOT tables are built from physiological relationships between race performance and oxygen consumption, and they don't explicitly adjust for age — a VDOT of 50 implies the same training paces whether the runner is 25 or 55. In practice, most masters runners find that while the VDOT system still works well for setting internally consistent training paces (easy, threshold, interval and repetition pace relative to each other), the absolute numbers achievable tend to decline gradually from the late thirties onward as maximum heart rate, VO2 max and recovery capacity all shift with age. Rather than abandoning VDOT, most coaches recommend recalculating it periodically from a recent race or time trial rather than relying on a personal best from years earlier — this naturally captures age-related change because the formula is re-derived from current performance, not a fixed assumption about ageing. Recovery between hard sessions is the area where age tends to matter most practically: an older runner using VDOT-derived paces may get just as much benefit from the interval and threshold work prescribed, but often needs more recovery days between hard sessions than the pace tables alone would suggest, since recovery capacity tends to decline somewhat faster than peak performance does. Adjusting the training week's structure rather than the pace numbers themselves is usually the more effective fix.

How the VDOT Number Is Actually Calculated

VDOT isn't a measured VO2max — it's a fitness score derived mathematically from a real race performance, using the formulas Jack Daniels and Jimmy Gilbert published from their research. First, a raw oxygen cost is estimated from race velocity (v, in metres per minute): VO2 = -4.60 + 0.182258 × v + 0.000104 × v². That raw number is then adjusted for how large a fraction of VO2max can be sustained for the race duration (t, in minutes): %VO2max = 0.8 + 0.1894393 × e^(-0.012778t) + 0.2989558 × e^(-0.1932605t). Dividing the first result by the second gives VDOT = VO2 ÷ %VO2max. The %VO2max term is what makes VDOT fair across distances: it's close to 100% for an all-out mile and drops toward roughly 80% for a marathon, reflecting the fact that nobody can hold VO2max-level effort for over two hours.

Worked Example: Calculating VDOT from a 5K Time

A runner completes a 5,000 m race in 22:00 (1,320 seconds, or 22 minutes). Velocity: v = 5,000 m ÷ 22 min = 227.3 m/min. Step 1 — raw VO2: -4.60 + 0.182258 × 227.3 + 0.000104 × 227.3² = -4.60 + 41.43 + 5.37 = 42.2. Step 2 — %VO2max for a 22-minute effort: 0.8 + 0.1894393 × e^(-0.012778 × 22) + 0.2989558 × e^(-0.1932605 × 22) = 0.8 + 0.1894393 × 0.755 + 0.2989558 × 0.0142 = 0.8 + 0.143 + 0.004 = 0.947 (94.7%). Step 3 — VDOT: 42.2 ÷ 0.947 ≈ 44.6. A VDOT of roughly 44-45 is a realistic mid-pack recreational level, and it's this single number — not the raw VO2 figure — that the Daniels training-pace tables are built around.

Worked Example: Projecting a Marathon Time from a 5K VDOT

Using the VDOT of 44.6 derived earlier from a 22:00 5K, the same formulas can estimate a realistic marathon time. For a roughly 3.5-hour effort (210 minutes), %VO2max ≈ 0.8 + 0.1894393×e^(-0.012778×210) + 0.2989558×e^(-0.1932605×210) ≈ 0.8 + 0.014 + 0.000 ≈ 0.814. Target VO2 at marathon effort: VDOT × %VO2max = 44.6 × 0.814 ≈ 36.3. Solving the velocity equation -4.60 + 0.182258v + 0.000104v² = 36.3 for v (using the quadratic formula) gives v ≈ 202 m/min. Marathon distance is 42,195 m, so projected time ≈ 42,195 ÷ 202 ≈ 209 minutes, or about 3 hours 29 minutes. This matches closely with the published Daniels VDOT tables, which list a VDOT of roughly 44-45 against a marathon time in the same 3:25-3:30 range — useful cross-checking that a calculator's output lines up with the source tables it's built from.

Where VDOT Equivalence Breaks Down

VDOT is a powerful cross-distance predictor in the middle-distance-to-marathon range it was built from, but it gets progressively less reliable at the extremes. At the very short end (400m-1500m), anaerobic capacity and raw speed contribute so much to performance that two runners with identical VDOT scores can have very different mile times, because VDOT is calibrated around aerobic %VO2max sustainability, not sprint mechanics. At the very long end (50 milers, multi-day events), fuelling, terrain, pacing discipline, and fatigue resistance start to dominate over the aerobic-engine size VDOT is measuring, so a VDOT-predicted ultramarathon time is far less trustworthy than a VDOT-predicted 10K or half-marathon time. Daniels himself designed the tables primarily around the 1500m-to-marathon range for exactly this reason, and treating a VDOT-based prediction outside that range as anything more than a rough starting estimate is a common misuse of the tool.