VDOT Calculator: Find Your Training Paces

The last time I trusted a feeling for easy pace, the feeling was last month's 10K and a bit of wind at my back. The watch looked fine. Wednesday did not.

A VDOT calculator is how I stop doing that. You put in a recent race, or an honest time trial on a route you already know, and it hands back pace ranges for the runs that are not races. The number is not the point. The point is that easy stays easy, and the faster day has a job.

Runapt's VDOT pace calculator is the same idea wired into the plan, so the ranges are not a screenshot you forget by Tuesday.

What you are actually estimating

VDOT comes from Jack Daniels' system. You give it a distance and a time. It estimates current fitness and turns that into training paces: easy, threshold, interval, repetition, and a set of race estimates. It is an estimate. It did not stand on your course. It does not know you went out too fast, or that the wind on the last 3 km was doing half the work, or that you raced on four hours of sleep.

I still use it, because the alternative is ego. Without a number, easy becomes "whatever felt smooth," which around here is often the grey zone people later call a normal Tuesday. Daniels puts easy running at roughly 59 to 74% of VO2max. In practice that is a conversation, not a sentence you have to earn. If the calculator and your lungs disagree, believe the lungs and slow down. The table is a starting point, not a dare. (Daniels, 2013)

What I feed it

A recent 5K, 10K, half, or marathon, run when you were not ill and the course was not a stunt. A controlled time trial on a loop you can measure twice. Something from this block, not a personal best from a spring you no longer live in.

I do not use the race I ran with a cold, or the one I jogged because a friend was visiting, or a goal time I have never approached. Those produce paces that look serious and then quietly wreck the next three weeks.

Once the ranges are there, they are guides. If threshold feels like a race from minute two, it is too fast for the day. If easy feels like a point to prove, you are not on an easy run. Heat, a headwind on the dike, hills, a bad night: Carl Foster's session-RPE work is the useful correction. The load is how hard the session felt, times how long you were out. The split on the watch is only one part of that. (Foster et al., 2001, Journal of Strength and Conditioning Research)

The paces, without turning them into a menu

Easy is most of the week. Warm-up, cool-down, the ordinary runs, a lot of the long run. It should not need forcing. If you only remember one Daniels number, use the slower half of that easy range after the halfway point, especially when the week is already tired.

Threshold is the controlled hard piece. Tempo, cruise intervals, the longer repeats that are supposed to stay repeatable. Strong, and still something you chose. Not a 5K in costume.

Interval pace is the sharper aerobic work, usually repeats with rest, on a track or a path that does not keep interrupting you. Repetition pace is faster still and shorter. The rest is the point. You are practising speed and mechanics, not grinding.

Race estimates are the part people screenshot. Treat them as a question, not a promise. A 5K can suggest a marathon pace. It cannot prove you can hold it at kilometre 35, with fuel, on a warm April morning in Rotterdam. The longer the race, the more the plan has to build the thing the calculator assumed.

The logic behind matching pace to the stimulus, rather than to last week's mood, is on the science page.

When the number feels wrong

It will, some days. Sleep, stress, a route full of turns, a soft path. Effort still has to match the job. Easy still easy. Threshold still controlled. Intervals hard and repeatable. If you cannot do that at the prescribed pace, the training effect you wanted is already gone, and chasing the split will not bring it back.

Newer runners feel this more, because fitness moves fast and so does fatigue. The calculator is structure. It is not permission to live at the top of every range.

If the day is heavier than the plan assumed, the better move is often a shorter session, an easier one, or a shift to another morning. That is not the plan failing. Runapt reads the paces next to readiness and coach notes in the AI running coach, so a bad night does not have to become a heroic workout.

Inside a plan, not on a sticky note

A pace table cannot tell you how many hard days the week can hold. That is the plan's job.

For 5K, the calculator keeps the fast work honest and the other days from impersonating it. For 10K, threshold and intervals earn their place, which is why the 10K training plan is mostly about not letting those two sessions eat the easy running. Half and marathon are where a predicted race pace is the least interesting number. Endurance, fuel, and the long run decide whether that pace still exists late. The half marathon training app and the marathon training app are built to grow that, not to print the estimate and walk away.

I do not update VDOT after a good Tuesday. One fast session can be rest, weather, or a loop that runs short. I update after a race, a planned time trial, or a clear change: coming back from time off, or several weeks where the same paces feel either silly or impossible. One bad run is not a new fitness. A pattern is.

If you want the ranges in the week instead of in a note on your phone, start with a plan. The wider picture of how those paces sit with routes and adjustments is on features.

Sources

Daniels, J. (2013). Daniels' Running Formula (3rd ed.). Human Kinetics.

Foster, C., Florhaug, J. A., Franklin, J., Gottschall, L., Hrovatin, L. A., Parker, S., Doleshal, P., & Dodge, C. (2001). A new approach to monitoring exercise training. Journal of Strength and Conditioning Research, 15(1), 109–115. https://doi.org/10.1519/00124278-200102000-00019