VDOT: Running Its Most Accurate Intensity System

Jack Daniels (the coach, not the whiskey) spent forty years watching runners over- and under-train in equal measure. Everyone was training hard. Most were training wrong. In 1998 he published Daniels' Running Formula and gave the sport a single number that fixed both problems at once.

VDOT. Not quite VO2 max, not quite race pace, not quite anything else — but uncannily accurate at telling a runner how fast every workout should be. Almost three decades later, the VDOT tables still show up in high school distance programs, Olympic coaching manuals, and the phones of runners who have never heard of Jack Daniels by name.

What VDOT Actually Is

VDOT is a virtual VO2 max — calculated not from a lab test, but from a recent race performance, adjusted for the efficiency profile of a typical competitive runner. It answers the question: "If you ran this race, what VO2 max does your performance imply, assuming average running economy?"

Run a recent 5K, 10K, or half-marathon through the VDOT calculator and you get back a number that looks suspiciously like a VO2 max (usually 30-75). That number then maps to a complete set of training paces.

The insight Daniels had was that actual lab-measured VO2 max varies too much between runners with similar race times to be useful for prescribing paces. But if you assume average economy and back-calculate from a race, you get a number that reliably predicts the pace any given runner should train at for any given workout intensity. It's not a true physiological measurement — it's a calibration tool that works.

Why It Beats Training by Pace Alone

A runner decides they should do a "tempo run" at 7:30/mile. Is that the right pace? Who knows. Tempo means roughly threshold pace — the pace you could sustain for about an hour. If your actual threshold is 7:10, you're running tempos too slow. If it's 7:50, you're running them too fast and failing to accumulate the right stimulus.

Pace alone gives you no mechanism to correct this. Heart rate gives you a better signal, but heart rate drifts with fatigue, heat, and hydration — so a single HR target across a workout can mislead.

VDOT solves this by anchoring every workout to a recent race. If your current 5K is 22:00, that's a VDOT of 44, and Daniels' tables give you precise pace ranges for every workout intensity:

Bump your 5K to 21:00 and every pace tightens accordingly. The structure is the same; the intensity anchors shift with your fitness.

How VDOT Relates to VO2 Max

Not identically. VDOT is a virtual VO2 max that assumes average economy. Your actual VO2 max — if you measured it in a lab — might be higher or lower than your VDOT, depending on how efficient your stride is.

A runner with excellent economy will have race times that correspond to a higher VDOT than their true VO2 max. A runner with poor economy will have race times corresponding to a lower VDOT. This is a feature, not a bug: Daniels' system doesn't care about your lab number; it cares about the pace you're actually capable of holding, and it prescribes workouts relative to that.

The companion metric is your actual cardiovascular ceiling — which VO2 max testing estimates more directly. Reading the two side by side tells you whether you're economy-limited or aerobic-ceiling-limited, which shapes what kind of training will move you forward. The VO2 max guide covers the physiology in more depth.

Using VDOT to Actually Train

The workouts that made Daniels' system famous are structurally simple:

E-pace (Easy). 70-80% of your total weekly mileage, conversational, building aerobic base.

M-pace (Marathon). Used in longer runs or intervals as race-specific work for marathoners. Most shorter-distance athletes don't need it.

T-pace (Threshold). "Comfortably hard" — the pace you could hold for about an hour. Run as 20-minute steady tempos or 4-6 x 1 mile with short recoveries. This is the single most productive intensity for most distance runners. Two sessions per week at threshold, done consistently for three months, will move a mid-pack runner significantly.

I-pace (Interval). Approximately 3K-5K race pace. Held for 3-5 minutes at a time with equal recovery. These are the VO2 max stimulus workouts — brutal, but the top-end contribution they make to race performance is unmatched. One session per week is plenty.

R-pace (Repetition). Shorter, faster (200-400m intervals), full recoveries. Develops speed, stride, and neuromuscular efficiency rather than aerobic adaptation. Useful but not mandatory for endurance runners.

A typical week at moderate training volume might look like: four E runs, one T workout, one I workout (or a race substituted for it), one long E run. Over 8-12 weeks, your 5K drops, your VDOT climbs, and your new paces recalibrate the entire table.

Adjusting VDOT for Reality

The tables are built for cool, flat, sea-level conditions. Real running happens in heat, altitude, wind, and hills — and VDOT workouts fall apart if you force the prescribed pace regardless.

Rough adjustments:

• Heat. Add 3-5 seconds per mile for every 5°F above 60°F on T and I work. In heat above 85°F, switch to effort-based training or shorten the session.
• Altitude. Above 5,000 feet, expect paces to slow 10-15 seconds per mile on threshold and interval sessions during the first two weeks of acclimatization.
• Wind. Use loops or out-and-backs for interval sessions so wind averages out.
• Hills. Convert hilly T sessions to effort-based ("threshold effort for 20 minutes") rather than pace-based.

The goal is to hit the physiological target — threshold lactate accumulation, VO2 stress, whatever — not to hit the pace number. Heart rate gives you a useful sanity check on effort when conditions degrade pace.

Combining VDOT with Race Prediction

Once you have a reliable VDOT, equivalent performances across distances are remarkably consistent. A VDOT of 50 corresponds to roughly: 5K 20:18, 10K 42:21, half-marathon 93:52, marathon 3:16:15. The race predictor lets you convert a recent time at any distance into forecasts at others, which is useful for goal-setting and pacing.

There are limits to this. The VDOT projection from a 5K to a marathon assumes adequate long-run training — which many fast short-distance runners don't have. If you're extrapolating to a distance you haven't trained for, the number is aspirational, not reliable.

For pace-specific workout structuring beyond what VDOT provides, the running pace calculator handles split-level work. And the heart rate training zones guide covers the complementary system when you're training somewhere pace doesn't translate.

The Point

VDOT isn't a magic number. It's a calibrated framework that keeps you honest. Most runners' training problems boil down to either running easy days too hard (compressing recovery) or running hard days too easy (compressing stimulus). VDOT's discipline is that it tells you exactly how fast to run each workout — and as your fitness changes, the whole table recalibrates with it.

Run a race this month. Plug it into the calculator. Train the paces it gives you for eight weeks. Run another race. Watch the number move.

References

1. Daniels, J. (2013). Daniels' Running Formula (3rd ed.). Champaign, IL: Human Kinetics.
2. Daniels, J., & Gilbert, J. (1979). Oxygen Power: Performance Tables for Distance Runners. Tempe, AZ: Oxygen Power.
3. Jones, A. M., & Carter, H. (2000). "The effect of endurance training on parameters of aerobic fitness." Sports Medicine, 29(6), 373–386.
4. Billat, L. V. (2001). "Interval training for performance: a scientific and empirical practice." Sports Medicine, 31(1), 13–31.
5. Joyner, M. J., & Coyle, E. F. (2008). "Endurance exercise performance: the physiology of champions." Journal of Physiology, 586(1), 35–44.
6. Lucia, A., et al. (2006). "Physiological characteristics of the best Eritrean runners." Journal of Applied Physiology, 100(2), 427–431.