Progression Runs (Start Easy, Finish Faster)
A progression run is a single run that gets faster as it goes: you start easy and finish at a strong, controlled effort. It gives you a hard session with a gentle start, and it lets you practice running well when you are tired. This guide covers what it is for, four ways to run one, how fast the finish should be, and where it fits in your training. This is general training guidance.
What a progression run is for
The rule is that effort only goes up. You begin genuinely easy, lift the effort in clear steps or as a smooth build, and finish strong but controlled, never in an all-out sprint. If you start too fast, it turns into an ordinary hard run.
The stimulus is the last stretch, run on tired legs and with your fuel stores low. That lets you feel late-race fatigue, practice a thought for the hard part of a race, and rehearse your fueling and gear while the effort is still controlled.
Four ways to run one
Pick the version that matches your race:
- Fast-finish long run (marathon): for runners who have already finished a marathon. Run 2 to 3 miles at your normal long-run pace, build to goal marathon pace and hold it for several miles, then run the last 1 to 3 miles (10 to 20 minutes) a little faster than marathon pace. Fatigue keeps it only a little faster anyway. See the guide on the long run.
- Sub-threshold progression (5K and 10K): start at marathon pace and build down into the zone just under threshold, so the run becomes your weekly high-end aerobic session. See the guide on tempo and threshold runs.
- Stepped three-mile progression (5K): a mile at half marathon pace, a minute of rest, a mile at 10K pace (10 to 20 seconds per mile faster), two minutes of rest, then a mile at 5K pace (another 10 to 20 seconds per mile faster).
- The light version: an easy or medium-long run with a 10 to 15 minute pickup at the end.
How hard to finish
Finish at a strong, controlled effort and never all out. In a fast-finish long run the closing miles sit only a little faster than marathon pace, and you treat them as a taste of race pace on tired legs. They are not your marathon-pace work, which belongs in its own sessions (see the guide on race-specific preparation).
Where it fits
A progression run with a tempo-effort or marathon-pace finish is a hard session. Count it in your two a week, and never put it next to another hard workout.
A fast-finish long run is a long run with pace work in it. It belongs in the race-specific phase, about the last two months before a marathon, and only after you have built a base of easy long runs and finished a marathon before. Add it gradually, as the long run guide describes: one in a training cycle, two in the next and three in the third.
Safety
Start easier than feels necessary, keep the closing segment controlled, and choose footing you can see clearly as the pace rises. Slow down or stop if an ache sharpens as you speed up (see the guide on pain versus soreness).
Common questions
What is a progression run?
One continuous run that starts easy and gets faster as it goes, finishing at a strong, controlled effort. Effort only goes up.
How fast should the finish be?
Strong and controlled, and never all out. In a fast-finish long run for a marathon, the last 1 to 3 miles are only a little faster than marathon pace.
Does a progression run count as a hard workout?
When it finishes at tempo or marathon-pace effort, yes. Count it in your two hard sessions a week and keep it away from other hard days.
Should a first-time marathoner do fast-finish long runs?
No. They are for runners who have already finished a marathon. A first-time marathoner builds with easy long runs (see the guide on the long run).
One running guide a week.
Calm, useful, no spam. Plain-English coaching from the Runsense team, once a week.