VDOT Explained: How Race Fitness Turns Into Training Paces

VDOT is a single number derived from a recent race result that stands in for your current running fitness, and it maps to five training paces with distinct jobs: easy, marathon, threshold, interval, and repetition. Jack Daniels built the system so that one honest race, rather than a laboratory test, sets every pace in your week.

What VDOT represents

Daniels developed VDOT as a pseudo-VO2max: a value that reflects both oxygen uptake and running economy, calibrated by performance rather than by gas exchange. Two runners can share a laboratory VO2max and still race differently because one wastes less energy per stride. VDOT collapses both factors into one number because both show up in the finishing time.

That design has a practical consequence. You do not need a treadmill test to prescribe training. You need a recent, honest race effort, and the numbers follow. It also means VDOT is only as good as the input. A race run in 30 degrees Celsius, on a hilly course, or after three broken nights understates your fitness, and paces built on it will feel too easy.

Which race should set your VDOT?

Use the most recent hard effort at a distance between 3 km and 10 km, run on a flat course within the past six weeks. Shorter races lean on anaerobic contribution that fades quickly and does not describe your aerobic ceiling. Longer races reward endurance you may not yet have, and understate fitness in runners whose weekly volume is still building.

If you have no recent race, run a 5K time trial on a track. Warm up for 15 minutes with a few short accelerations, run the effort evenly rather than starting fast, and record the conditions. Expect a solo trial to land 2 to 4 percent slower than a race with a field and a proper taper, and keep that offset consistent so your progression is comparable over time.

The five paces and what each one does

Two rules govern the table. First, each pace has one job, and running a session between two paces usually accomplishes neither. Threshold work run at interval pace ends early and leaves you too tired for the long run. Interval work run at threshold pace never reaches the oxygen demand that makes it worthwhile. Second, the durations exist to protect intensity. Threshold work is defined by the pace being sustainable for roughly an hour in a race, which is why a 40-minute threshold session is broken into cruise intervals rather than run continuously.

Faude and colleagues (2009) reviewed 25 different lactate threshold definitions and found that thresholds correlate strongly with endurance performance, particularly in running, which is the physiological reason a pace anchored near threshold transfers so directly to race results.

How the paces fit into a week

VDOT tells you how fast; it says nothing about how often. That decision comes from intensity distribution. Seiler (2010) summarized descriptive studies of nationally and internationally competitive endurance athletes and found a consistent split of roughly 80 percent of sessions at low intensity and 20 percent dominated by high-intensity work, with little time spent at threshold. For a recreational runner training four to six times a week, that translates to two quality sessions and the rest easy.

A five-day week for a 10K build might look like this:

• Tuesday: interval session, for example 5 x 1000 m at interval pace with 3 minutes jogging recovery
• Wednesday: easy 45 to 60 min
• Thursday: threshold session, for example 4 x 8 min at threshold pace with 2 minutes jogging
• Saturday: long run, 80 to 100 min easy
• Sunday: easy 40 min, with 6 x 20 s hill sprints if legs allow

The easy days are not filler. They are what makes the two hard days possible, and they are the sessions most often ruined by running slightly too fast.

What equivalent performances tell you

One VDOT value implies a finishing time at every distance, and comparing your actual results against those equivalents exposes what is missing from your training. Approximate equivalents around a mid-range fitness level look like this:

Read the gaps rather than the numbers. If your 5K matches the table but your half marathon is four minutes slower than the equivalent, you have speed without the endurance to hold a fraction of it for 90 minutes, and the fix is weekly volume plus longer threshold blocks. If your half marathon matches but your 5K is 40 seconds slower than the equivalent, you have a large aerobic base and no top end, and the fix is interval and repetition work.

Marathon equivalents deserve extra caution. Daniels notes that the marathon prediction assumes appropriate training volume, and a runner on 45 km per week will not run the equivalent marathon time regardless of what a 10K result implies. Treat the shorter-distance equivalents as reliable and the marathon column as a ceiling that training volume has to earn.

Why GPS pace and heart rate disagree

Both of your primary feedback channels are noisy, and they break in different situations.

GPS distance error is systematic rather than random. Gilgen-Ammann and colleagues (2020) tested eight consumer sport watches from Apple, Coros, Garmin, Polar, and Suunto and reported mean absolute percentage errors of 3.2 to 6.1 percent across urban, forest, and track settings. Distances were generally underestimated in urban and forested areas and slightly overestimated on the track, and error rates were higher while running than while walking or cycling. A 4 percent distance error on a 1000 m repeat is roughly a 7-second-per-kilometre pace error, which is enough to make a correctly executed interval look slow.

Wrist heart rate has its own failure modes. Wang and colleagues (2017) compared four wrist-worn monitors against ECG and found accuracy was best at rest and degraded during exercise, with wide limits of agreement for several devices. Heart rate also lags the effort by 30 to 90 seconds at the start of an interval, drifts upward during long efforts in heat, and stays suppressed when you are dehydrated or very fatigued.

Use them in this order:

1. On flat ground in mild weather, pace is the primary signal and heart rate is the sanity check.
2. On hills, trails, or in heat and humidity, effort is primary and pace is the record, not the target.
3. For threshold work, if pace is on target but heart rate is 8 to 10 beats above normal for that pace and breathing is heavier than usual, shorten the session.
4. For easy runs, if heart rate is normal but the run feels hard, believe the feeling.

Vitadel Run keeps VDOT paces and the day's readiness signal in the same view, so a session written at threshold pace can be shortened rather than abandoned when the two disagree.

Updating VDOT without chasing noise

Recalculate every four to eight weeks, or after any race that implies a change of more than one VDOT point. Two guardrails help.

Do not raise VDOT because a single interval session felt easy. Interval sessions feel easy on good days, and a pace jump applied to every session compounds into a week that is 3 to 5 percent too hard everywhere. Also avoid lowering VDOT after one bad race in heat. Heat costs measurable time, and rebuilding paces around a hot-weather result will make autumn training too gentle.

When VDOT does move up, apply it to quality paces first and leave easy pace alone for a week or two. Easy pace is the least sensitive to fitness and the most sensitive to fatigue, so it is the wrong place to test a new number.

Common mistakes with VDOT paces

• Setting VDOT from a personal best you ran two years ago. Paces then punish you now, and the first casualty is the easy run.
• Running repetition sessions with short recovery. Repetitions target mechanics and speed, which requires nearly full recovery. Cutting recovery turns them into a badly designed interval session.
• Treating marathon pace as a training staple in a 5K block. Marathon pace has narrow value outside marathon preparation, and it eats the recovery that interval sessions need.
• Converting every session to a percentage of heart rate maximum. Maximum heart rate estimates from age formulas carry error of roughly 10 beats or more, which makes derived zones less accurate than paces from a recent race.
• Ignoring altitude and terrain. Trail and hill sessions should be run by effort and duration, with pace treated as an outcome.

The system works because it is closed-loop: race, derive, train, race again. Each cycle recalibrates the paces with better information than the last, which is more than any single test can offer.