Sub-20 5K and sub-40 10K runners hold the exact same pace: 6:26 per mile. The only real difference is holding it twice as long, and that changes what your training app needs to prescribe, not just how far you run.
Most running apps don’t know that. They treat a “5K plan” as a shorter, faster version of a marathon plan: same load model, same ramp-rate math, fewer weeks. That’s a problem. A VO2max interval session and a marathon long run load your body in completely different ways. One redlines your engine for three minutes at a time. The other cruises it for two hours straight. A load model built for the second one doesn’t know how to protect you from the first.
Why a Training App for Sub-20 5K and Sub-40 10K Needs a Different Load Model
Here’s the pace math. A 20:00 5K averages 6:26 per mile. A 40:00 10K averages the identical 6:26 per mile, held for 6.2 miles instead of 3.1. Sub-40 10K guidance generally assumes you can already run a 5K under 20:00, ideally under 19:00, before you start the block. In short: these aren’t two training populations. They’re one fitness level, tested at two distances.
That matters for pacing. It matters more for physiology. Trained runners sustain roughly 95-98% of VO2max (the highest rate your body can use oxygen) at 5K race effort, and roughly 90-95% at 10K effort. The gap looks small on paper. It isn’t small in a training plan, because the interval pace that builds 5K speed sits meaningfully harder than the pace that builds 10K durability.
Translation: even at 5K, your aerobic engine does 80% of the work. Speed work is the difference-maker, not the whole plan.
| Distance | Target Pace (this block) | % VO2max Sustained | Aerobic : Anaerobic Split | Primary Training Zone |
|---|---|---|---|---|
| 5K | 6:26/mile (4:00/km) | 95-98% | 80% : 20% | Interval |
| 10K | 6:26/mile (4:00/km) | 90-95% | 90-95% : 5-10% | Threshold / Interval blend |
| Marathon (for contrast) | — | lower, sustained | ~99% : 1% | Marathon pace |
The Interval Evidence Most Apps Never Cite
Jack Daniels’ VDOT system, the framework behind most pace calculators, defines Interval pace as 3-5 minute reps at 95-100% of VO2max pace, built from 3K-to-5K race effort. Threshold pace comes from 10K-to-15K effort instead. A generic app that only shows you “Tempo” and “Long Run” is missing the two zones a short-course block is actually built on.
That distinction isn’t theoretical. A 2025 study tested highly trained middle-distance runners. One group ran long VO2max reps: 3 minutes at 95% of the pace that elicits VO2max. The other ran short, harder-feeling reps: 30 seconds at 100%. The long reps produced roughly 63% more time spent above 90% VO2max. That’s 327.9 seconds versus 201.3 seconds. The short reps still felt harder. They also hit a higher percentage of max heart rate.
Feeling harder isn’t the same as training harder. The long, “boring” repeat did more work.
This lines up with older research too. Billat’s classic vVO2max work found four weeks of 3-5 minute reps near the pace that elicits VO2max improved that pace by about 3%. Running economy improved by about 6% in the same trained runners. That’s the evidence base under the Interval zone every VDOT calculator uses.
There’s an important counter-point, though. A 2010 study of elite distance runners found something surprising. How much of their VO2max they could sustain at 5K race pace did not correlate with their actual 5K time. Their raw VO2max did. So more “VO2max%” interval work isn’t a guaranteed lever once an athlete is already near-elite. For a sub-20 5K runner who isn’t there yet, both raw aerobic capacity and well-dosed interval structure still matter. Neither one replaces the other.
Polarized, Not Pyramidal
Stephen Seiler’s research on elite endurance athletes found they trained about 75% of sessions below their first ventilatory threshold, an easy, conversational effort. They spent 15-20% of sessions with real time above their second threshold, genuinely hard work. Very little time sat in the tempo-ish middle.
That’s a polarized pattern: easy days easy, hard days hard, not much in between. It’s the same logic behind why the 80/20 split gets miscounted in recreational training and why Zone 2 volume builds the base a fast finish gets layered onto. A 5K/10K block still needs that easy aerobic floor. It just needs a sharper, more deliberate hard end than a marathon-style tempo day provides.
ACWR and Ramp Rate: The Hidden Injury Risk in a Trimmed Marathon Plan
Here’s where most apps quietly fail short-course athletes. A 2-year study tracked 23 competitive runners. Researchers found that fortnightly spikes in the acute:chronic workload ratio were linked to injury. Call it the load ratio: a rolling comparison of your last week of training against your last month’s average. A separate, widely cited risk-banding puts the danger zone at a load ratio of 1.5 or higher, with a roughly two-to-threefold rise in injury odds. A weekly volume jump of 15% or more can push injury risk from under 10% up to 21-49%.
Think of your load ratio like a car’s temperature gauge, not the speedometer. It doesn’t care how fast you’re going. It cares how fast the engine’s heat is climbing.
Now picture a runner turning a marathon app’s plan into a “5K plan” by shortening the long run. Weekly mileage drops, so the load ratio looks fine on paper. But two easy runs just got replaced with VO2max reps. Those load your heart and nervous system much harder than easy miles do. The chronic average hasn’t caught up yet. None of the four major apps in this space publish a load model that treats an interval spike differently than a volume spike.
None of TrainingPeaks, Runna, Garmin Coach, or Final Surge expose a load ratio guardrail built specifically for intensity-dense blocks. The injury-risk math is the same generic ramp-rate check whether your hard session is a VO2max repeat or a marathon-pace long run.
TrainingPeaks vs Runna vs Garmin Coach vs Final Surge for 5K/10K Structure
Here’s what each platform actually does, fairly stated.
| App | Dedicated 5K/10K Plan? | Interval Zones From Your Own Threshold/VDOT? | Load Ratio / Ramp-Rate Tracking? | Adapts Mid-Block? | Price |
|---|---|---|---|---|---|
| TrainingPeaks | No dedicated distance plan; marketplace + manual build | You input it manually | Yes, fitness/fatigue/freshness ramp guidance (their CTL/ATL/TSB, built for cycling power) | Manual, coach-dependent | $19.95/mo or $134.99/yr |
| Runna | Yes, 6-16 week 5K/10K plans | Templated by duration, not derived from your fitness | Not exposed | Adapt for Heat, auto post-race recovery (2026) | $19.99/mo or $119.99/yr |
| Garmin Coach | Yes, 5K (6-20 wk) and 10K (10-21 wk) | Templated by a human coach per distance, adjusted by Training Status | Garmin Coach AI adds HRV/sleep/load balance (2026) | Yes, weekly based on completed runs | Free with Garmin watch |
| Final Surge | Depends entirely on the coach who uploads it | No, it’s a log and file host, not a generator | Premium add-on tracks HRV/readiness, no ACWR model | Only if your coach edits it | $19-39/mo (coaches); free for athletes |
TrainingPeaks gives serious athletes real data depth. But its ramp-rate guidance grew out of cycling power. It expects you to already know your threshold pace. Runna and Garmin Coach both publish genuinely dedicated 5K/10K plans, built by real coaches, which is more than most competitors offer. Neither one publishes how it derives interval pace from your current fitness the way a VDOT or vVO2max calculation would. Garmin Coach’s free price and 2026 AI layer make it a strong default for anyone already wearing a Garmin watch. Final Surge is honest about what it is: a log and coach-communication tool, not a plan engine. Its 5K/10K quality depends entirely on the plan someone loads into it.
A Short-Course Block, in Practice
Take a hypothetical runner, Marcus, 34, with a 22:40 5K best and a stalled 10K around 47:30. He’d been running a marathon-training app’s plan, trimmed down. Same long run, cut to 8 miles. Same weekly tempo. A couple of “speed” days that amounted to 30-second strides. His load ratio, unmonitored, spiked from 0.9 to 1.6 in the third week, right after he added two VO2max sessions without cutting anything else. His knee started barking by week five.
He rebuilt the block around 3-5 minute VO2max reps at his actual current fitness. He held total weekly volume roughly flat and watched his load ratio instead of guessing. Ten weeks later his 5K was 21:05. His 10K, run off the same fitness, came in at 43:50. Nothing exotic happened. The stimulus just matched the goal.
Short-course speed rewards patience with the ramp, not just hard days.
AthleteOS builds an 8-12 week short-course block from your own current threshold pace, not a trimmed marathon template. VO2max intervals get prescribed as 3-5 minute reps in the zone the evidence supports. Your training plan tracks load ratio through the block, too, so a hard interval day and a hard long-run day don’t get judged by the same yardstick.
If your tendons are already a question mark going into a heavier interval load, checking your reactive strength trend first is a reasonable extra step. If you’re unsure your easy days are actually easy enough to support the hard ones, that’s worth a look too.
Sub-20 and sub-40 aren’t two goals.
They’re one fitness level, and one block, run twice.