What is a progression run? A coach's guide to the workout that trains pace control.

A progression run is a run that starts at your easy pace and finishes at a much faster one. You move from easy to moderate to hard across the distance, without any hard reset in between. Done well, it trains something no straight tempo does: your legs learn to hold pace after they get tired, which is what every race asks of them.

Most runners hear that and picture a tempo run. It is not the same workout. A tempo is a sustained effort at one hard pace, run on fresh legs. A progression is a smooth acceleration across the whole run, and the fast finish arrives when your legs are already three or four aerobic miles in. The last stretch of a good progression run is usually faster than a tempo would be, at lower total training cost. That difference is the whole point.

What a progression run actually is

The workout has three phases, and the shape matters more than the exact numbers.

• Phase 1: the first third to half of the run, all easy pace. Conversational, aerobic, no strain.
• Phase 2: the middle third, moderate. Steady effort, roughly a gear faster than easy.
• Phase 3: the last quarter to third, hard. Marathon pace at the shallow end, half-marathon pace in the middle, 10K pace on the sharpest versions.

The transition between phases is smooth, not stepped. You are not hitting split targets like intervals. You let the effort climb, check the watch every mile or so, and push the pace a little each check. By the last mile you are working, but you got there without ever surging.

Why it works when a straight tempo does not

A tempo run and a progression run look similar from outside. One runner runs 5 miles at half-marathon pace. Another runs 8 miles with the last 4 at half-marathon pace. Same fast miles, similar total load. The difference is where the effort happens.

In a straight tempo, you start fresh. Your legs are cooperative, form is clean, and half-marathon pace feels controlled. In a progression run, the fast miles come after you already have several aerobic miles in the legs. Half-marathon pace at mile six feels considerably less friendly than half-marathon pace at mile one. That is not a bug. That is the training effect.

Races demand the same thing. You cannot execute goal pace with fresh legs, because by the time it matters, they are not fresh. In 15 years of coaching, the runners I watch fall apart in the last third of a race are almost always the ones whose workouts trained fresh-leg fitness. The runners who hold form to the finish are usually the ones who practiced goal pace on tired legs a dozen times before the start.

That is what a progression run gives you, at lower physiological cost than a straight tempo would.

The three progression run formats I use

There is no single progression run. The workout is a family. Here are the three formats I write into training plans most often, from lightest to heaviest.

1. The easy progression

An 8 mile run with the last 3 at moderate pace, roughly marathon pace or a touch faster. No hard fast finish. This is the version I give athletes early in a training block, or on weeks where the calendar is already stressful and I do not want to add a second hard session.

Training cost is low. Aerobic benefit is high. You could do this weekly for a month and not compromise anything else in the week.

2. The classic progression

A 10 mile run: first 5 easy, middle 3 at marathon pace, last 2 at half-marathon pace. This is the version most training plans mean when they say "progression run." It has real fast-finish work, but the fast miles are short enough that you finish intact and can train hard again in three days.

I schedule this most often two to three weeks into a build, and again once or twice through the peak. It is the workhorse.

3. The finish-fast long run

A 16 to 20 mile run: first 60 to 70 percent easy, last 30 to 40 percent at goal marathon pace or a hair faster. This one is marathon-specific. It teaches goal pace on legs that have already run for over an hour, which is the most useful skill in marathon training.

It is also expensive. Recovery is real, and I only prescribe it every second or third week during the peak of a marathon build, never in back-to-back weeks.

How to pace it honestly

The most common mistake is starting Phase 1 too fast. If your easy pace on this run drifts a little quicker than normal, the whole progression collapses in the middle, and the last miles either blow up or come in slower than moderate. That is a workout you cannot rescue with willpower.

To make the shape concrete, here are the paces I would give a runner whose recent race points to a VDOT around 45, which is roughly a 3:35 marathon or a 1:42 half.

If you have not raced recently, put a recent time into the pace calculator and use the training paces it gives you, or read the primer on what VDOT actually is. Guessing your paces here is how progression runs get run at one flat middle pace, which is not a progression run at all.

The other thing that helps: cover the pace field on your watch for the first mile. Run by feel. Look at the watch at the first mile marker, adjust if you started too fast, and then run to the plan.

Where it fits in your training week

A progression run belongs on a workout day, not a recovery day. Do not run one the day after intervals or a long run. The pattern I use for a runner training five to six days a week:

If Thursday is too crowded, a progression can replace the long run on a lighter week instead. Two hard sessions plus a long run is the ceiling for most amateur runners. Adding a third is what turns a solid block into a hurt week.

The three mistakes that ruin the workout

After writing progression runs into a lot of plans, three patterns come up over and over. If you know them, you can catch yourself before the workout is already lost.

Starting too fast. The most common one. You feel good in mile one, drift 20 seconds per mile below your easy pace, and by mile six the moderate section is already effortful. The workout is done before you started the hard part. Fix: start slower than feels right. If mile one feels a little boring, you got it right. If you tend to drift fast, this is a good place to remember why easy pace has to actually be easy.

Skipping the moderate middle. Some runners jump straight from easy to hard. That is two workouts glued together, not a progression. The moderate middle is where you build the pace-holding muscle memory. Skip it and you get a warm-up plus a short tempo, which you could have run in six miles instead of ten.

Racing the last mile. The last mile does not need to be a personal best. It needs to be honestly at the target pace and finished under control. If you are gasping and reaching, you overshot in the middle and you will be tired for three days for no fitness gain.

What to do this week

If you have never run a progression run, start with the easy version. Pick a normal easy run distance. Run the first two-thirds at your usual easy pace. Run the last third at your marathon pace, or if you do not know that, at what feels comfortably steady, one gear up from easy.

Take Wednesday off if the workout is Tuesday. Do not follow it with an interval session. The workout is aerobic, but the last section adds up faster than it feels.

Log what you did: distance, splits by phase, how the last section felt. Progression runs get better fast when you have three or four in the log to compare against. If you want the difference between this workout and a straight tempo laid out end to end, the tempo run primer pairs with this one.

Written by

Coach Johnny Crain

2:12 marathoner. 4× US Olympic Marathon Trials qualifier. 4× NCAA national champion and 4× NCAA runner-up. Spoke at the RRCA National Convention. Founder and head coach at RunFitCoach, where he coaches every athlete personally.