Calculating Interval Paces From a Recent Race Time

You've come from a session in the library that says "run at 5K pace" or "run at threshold effort" and you've got a blank where the actual number should go. Your interval paces come from a fitness-equivalency table - Jack Daniels' VDOT method - not a flat percentage of race pace. Plug in your most recent all-out race time and read off training paces for each interval distance. Below: what VDOT actually means, a full worked example, and when to trust the number over how a rep feels.

Most calculators built for this assume a 5K or longer sits in your recent results, and go quiet the moment a middle-distance runner shows up instead. If your last quality effort was an 800m or 1600m, you don't need to wait for a longer race to appear on the calendar - that time works as your input today.

Why Race Time Beats Guessing at Training Paces

I've seen this pattern more times than I can count: a runner anchors their 800m interval pace off a stale PR from two seasons ago, guesses 8-10 seconds per 400m too fast, and the session falls apart by rep four. Guessing feels like confidence. It's usually just outdated data wearing confidence as a disguise. A recent race time is the only honest input you've got - it reflects your fitness now, not who you were last spring.

VDOT Explained in Plain Language

VDOT is a single fitness score derived from a race performance that predicts equivalent performances - and equivalent training paces - at other distances. It works because it accounts for how efficiently you use oxygen at a given effort, not because it's measured your VO2max in a lab. It's an estimate from race time alone. This isn't proprietary to any calculator website - it's a lookup-table system from Jack Daniels' Running Formula, and every calculator you've found is drawing from the same tables.

Using a Short Race (800m/1600m) as Your Input, Not Just 5K-to-Marathon

Here's the gap I keep seeing on other sites: they'll all tell you to use a 5K or longer for a "stable" VDOT reading and leave middle-distance runners stuck. An 800m or 1600m time works perfectly well as a VDOT input. The one caveat: an all-out short-race effort skews slightly towards anaerobic capacity, so the endurance-pace predictions it generates - your threshold and easy paces - run a touch optimistic. If you've got a recent 5K or 10K as well, cross-check against it. If you don't, your short race stands on its own - use it with confidence.

From Race Time to Interval Pace: A Worked Example

Take a runner with a recent 5K of 18:00. Here's the process, step by step.

Step 4 is the one worth sitting with. If your most recent quality result is an 800m rather than a 5K, don't wait for a longer race to appear on the calendar before you commit to real numbers - work from what you've got.

When to Trust the Number vs. Trust How It Feels

If a pace feels 3 or more seconds per 400m off for more than two reps in a row, on a day when nothing else explains it, trust how it feels and adjust the session. If it's a single bad rep, trust the number and keep going - one rough interval isn't data, it's just a rough interval. Heat, unaccounted fatigue, and a stale race input are the three most common reasons the number and the feel disagree.

I had an athlete once whose calculated paces read comfortably fast on paper straight after a bout of illness. The table said one thing; his legs said another entirely. I dropped the target by several seconds a rep for two weeks rather than forcing the number, and his times caught back up once he'd properly recovered. The table's a starting point, not a contract.

Updating Your Paces as the Season Progresses

Recalculate after any genuinely all-out race effort, not only your goal races. With no racing on the calendar for 6-8 weeks, run a hard time trial and use that as a substitute input rather than training for two months on numbers that no longer reflect your fitness. Once you've got your paces sorted, head back to the full session library to see which sessions use them, or check which sessions use these paces across different event distances. If you're building a broader block, you can translate these paces into your periodised week.

Frequently Asked Questions

Why do different VDOT calculators give me slightly different paces for the same race time?

Small rounding and interpolation differences between tables - usually a second or two per 400m. Pick one source and stick with it rather than averaging several.

Can I use a hard time trial instead of a race to calculate my paces?

Yes, provided it's genuinely all-out. A time trial lacks race-day adrenaline, so treat the result as a slightly conservative estimate and recalibrate at your next real race.

Do I need to recalculate my paces every time I race?

Only after efforts that meaningfully differ from your last input. With no racing for 6-8 weeks, substitute a hard time trial instead.

What if my calculated pace doesn't match how a session feels?

Trust the number on a single off rep. Trust how it feels if a pace is off by 3+ seconds per 400m for more than two reps running.

Kind regards,
Dom