Five Training Paces From One 5K: Easy, Marathon, Tempo, Interval, Repetition

Good training plans look complicated from the outside — five paces, each with a purpose — but most are built from one anchor performance and a set of well-tested ratios. Run one honest 5K, and easy pace, marathon pace, tempo pace, interval pace and repetition pace all follow. This article explains what each pace is actually for, the effort it should feel like, and why the ratios in our training pace calculator are shaped the way they are.

The system comes from the tradition of Jack Daniels — the running coach and exercise physiologist, not the whiskey — whose VDOT tables demonstrated that one race performance could generate a full, coherent training vocabulary. Our calculator is a simplified descendant of that insight, and this article is its user manual.

Easy: the pace that builds the engine

Easy running sits roughly 30–40% slower per kilometre than 5K pace and should allow unbroken conversation. Its job is volume without damage: it trains the heart’s stroke volume, grows capillaries and mitochondria, and accumulates the aerobic base on which everything else stands. The paradox every beginner must swallow is that this pace feels embarrassingly slow and is doing more long-term good than any heroic session — most of a runner’s week, typically 70–80%, belongs here. If your easy days drift toward tempo, your hard days will silently become easy too, and the whole spectrum collapses into one grey effort that neither recovers nor adapts.

Tempo and marathon pace: the sustainable edge

Tempo pace — about 8–12% slower per kilometre than 5K pace, close to the effort sustainable for roughly an hour — trains the lactate threshold: the boundary below which effort can be held and above which it rapidly cannot. Marathon pace, a little slower still, is tempo’s endurance cousin: the specific efficiency of running at race rhythm for hours. Both live in the zone of ‘comfortably hard’, where conversation shrinks to short phrases. Sessions here are the highest-value hard work most runners do, and also the easiest to overcook by turning them into races.

Intervals and repetitions: the top end

Interval pace is 5K pace itself, run in doses of two to five minutes with recoveries that let you repeat the quality — this trains maximal oxygen uptake, the size of the engine. Repetition pace is faster again, around 5–8% quicker per kilometre than 5K pace, in short bursts with full recovery; its purpose is economy and form — teaching the body to run fast while relaxed, not to accumulate fatigue. The difference matters: intervals end tired, repetitions should end feeling like you could do one more, because their target is the nervous system, not the red zone.

A week arranged by the paces

Watch how the five paces furnish a real week for a runner training four days. Tuesday: intervals at 5K pace — six repetitions of three minutes with easy jogging between. Thursday: tempo — twenty unbroken minutes, or two ten-minute blocks, at the comfortably-hard edge. Saturday: the long run at easy pace, the week’s volume and patience. Sunday or Monday: recovery-easy or rest — and every few weeks, a handful of short repetitions after an easy run, run fast and relaxed, as a skills lesson for the legs. Marathon trainees swap some tempo work for marathon-pace blocks inside the long run. Nothing in the architecture is exotic; the magic is the separation — each session knows its pace, its purpose and its place, and none of them is ‘medium’.

The most common repair a coach makes to a self-written plan is not adding work but subtracting sameness: turning three moderate runs into one tempo, one interval session and genuine easy running.

Altitude, heat and treadmills: adjusting the dialects

Paces are printed for fair conditions and quietly assume them. At altitude, in serious heat, or on a treadmill (its own translation problem, covered in our treadmill article), the honest move is to convert pace targets into effort targets for the day: tempo is the effort that permits short phrases, whatever the watch says; easy is conversation, at whatever speed the weather allows. Runners who worship the printed pace in August learn suffering without adaptation. The anchor 5K should likewise be refreshed after any big environmental change of life — a move to altitude, a season’s turn, a return from a layoff — because the ratios are faithful messengers of a stale anchor’s lies.

When the paces disagree with the weather

Every printed pace assumes a standard day that rarely shows up: mild, still, flat, rested. Real days tax the numbers in predictable directions. Heat is the most expensive — above the mid-20s Celsius, easy pace can slow by 20–40 seconds per kilometre at the same heart rate, and tempo by similar margins, because the cardiovascular system is simultaneously running a cooling plant. Altitude starts taxing from about 1,500 metres. Wind, hills and heavy legs from yesterday’s session each take their own percentage. The professional response is to hold the effort constant and let the pace float — which is why the training calculator expresses outputs as ranges and why the talk test appears in nearly every article on this site.

Keep a weather note in your log beside any session you will later judge. A tempo run 15 seconds slow in a heatwave is not regression; read six months later without the note, it will look exactly like regression, and plans get needlessly rebuilt on such misreadings.

Anchoring honestly

Every ratio inherits the quality of the anchor. A 5K raced downhill, or jogged, or run in a storm, tilts the entire week. Re-anchor every six to eight weeks — a race is best, a solo evenly-paced time trial on a flat route is nearly as good — and treat heat as a pace tax you pay willingly: on hot days, run the effort and let the watch show slower numbers. Our calculator gives ranges rather than single seconds because real training is done in ranges; the runner who must hit 5:31 exactly learns anxiety, not pacing.

Common mistakes

• Running easy days at ‘moderate’ because slow feels unproductive
• Treating tempo runs as weekly races
• Never re-anchoring after fitness changes

Questions this raises

Related reading