Progression Run Training: Build Race Speed by Finishing Fast

The progression run — start deliberately slow, get continuously faster, finish near race pace — is one of the most effective yet underrated tools in endurance training. Instead of a session at a single speed, you stack several training stimuli into one run: from fat-metabolism base work to a race simulation on tired legs. It is no coincidence that virtually every elite training plan includes regular progression runs. They are the most economical way to train fast running without paying the full recovery cost of a classic tempo workout.

What exactly is a progression run?

A progression run is a continuous run without breaks in which pace rises systematically from start to finish. You begin at an easy base pace (zone 1) and finish, depending on the goal, at threshold or race pace (zone 3 to 4). The key feature is the planned, controlled acceleration inside a single session — not random surges, not intervals.

It helps to separate the progression run from its relatives:

• Fartlek (speed play): pace changes by feel, with no fixed structure. A progression run is scripted — the acceleration follows a defined pattern.
• Interval training: short, very fast repetitions separated by jog recoveries. A progression run has no breaks — the acceleration happens in one continuous flow.
• Threshold run: a constant pace at the anaerobic threshold for 20 to 40 minutes. A progression run only touches that intensity at the very end.

That places the progression run precisely in the gap between easy endurance running and hard tempo work: intense enough to drive real adaptation, dosed enough to avoid becoming a fatigue trap.

Why progression runs work so well

The build-up structure is not a gimmick — it triggers a very specific cascade of stimuli that a single-pace session cannot deliver:

• Learning glycogen management: The slow start forces the body to rely mainly on fat metabolism and spare the limited glycogen stores. Exactly this metabolic discipline decides the second half of a race — it is the antidote to hitting the wall in the marathon.
• Race pace under fatigue: The final kilometres run on partly depleted stores — just like on race day. Your body learns to run fast when it matters, not only when it is fresh.
• Mental race rehearsal: Once you have practised accelerating while tired, you trust that ability at the start line. The progression run trains the mind: patience early, aggression late.
• Better form at speed: Because you are already warm and running economically when the pace rises, your technique in the fast segment stays cleaner than in cold interval starts.
• Lower injury risk: The slow beginning acts as a built-in warm-up. Fast segments on thoroughly warmed muscles are considerably safer than sprint work on cold legs.

Pacing guidelines: how to control the build-up

The most common question is about the numbers. As a rule of thumb: the last 10 to 20 percent of the session is the fastest part, while the first 40 percent stays deliberately gentle. A concrete example of a 60-minute progression run for a marathon runner:

• Minutes 0–20: zone 1, roughly 90 seconds per kilometre slower than marathon pace. Conversational, almost too slow.
• Minutes 20–40: zone 2, about 45–60 seconds above marathon pace. Relaxed but already working.
• Minutes 40–55: marathon pace (zone 3). Controlled, rhythmic, breathing calmly.
• Minutes 55–60: zone 4, half-marathon to 10K pace. The push home — fast, but not a sprint.

You can steer by pace, heart rate zones or perceived effort (RPE). For beginners, heart rate is the most honest control because it defuses the biggest progression-run risk: starting too fast. If you run by feel, make the first 20 minutes consciously “unnaturally slow” — what feels wrong at the start is usually right.

5 progression run workouts for every distance

• The classic (60 minutes): as described above — the all-purpose tool from 10K to marathon. Once a week during the build phase.
• The long run with a fast finish: 90–120 minutes with the final 30 minutes at marathon pace. The toughest and most valuable workout in marathon preparation — pure race simulation. At most every two to three weeks, ideally built into the long run of your peak week.
• The Kenyan progression (40 minutes): continuous acceleration without steps — every kilometre slightly faster than the one before, from very easy to “brisk”. No other session sharpens pace feel like this one.
• The short progression (30 minutes): 15 minutes zone 1, 10 minutes zone 2, 5 minutes at 10K pace. Ideal for 5K and 10K runners and as a quality session in high-volume weeks.
• The beginner progression: 40 minutes, of which 27 minutes easy and 13 minutes just “a little brisker” — no zone stress, just learning the pattern. The entry point for anyone new to structured training.

How to place progression runs in your week

In a classic training week with three to four runs, the progression run replaces the tempo run slot: midweek, with at least one easy or rest day before and after. If you run five to six times per week, you can add a second, milder build-up — such as the short progression — as long as the 80/20 balance holds: the fast parts of both sessions together should stay below 20 percent of weekly volume.

Phase logic matters too: in base training, mild progressions finishing at marathon pace dominate. The closer the race, the more specific the finish — half marathoners close at half-marathon pace, 10K runners at 10K pace. During the final two weeks before the race (the taper), progression runs are cut short but stay in the plan as brief stimuli, so your pace feel does not fall asleep.

Beyond running: progressions in cycling and triathlon

The principle transfers easily. On the bike, a build-up workout might be 60 minutes starting at 60 percent of FTP and ending at 90 to 95 percent — a popular way to make threshold work on the indoor trainer more engaging. Triathletes additionally use progression runs as race-specific brick work: if the second half of a run straight off the bike gets faster, you are rehearsing exactly the race situation — tired legs, rising pace. More on combining disciplines in our article on brick training.

The most common progression run mistakes

• Starting too fast. The classic error: ambition pushes the opening into zone 2 or higher — then there is no room left for a real build-up, and the session becomes a half-hearted tempo run. The first minutes have to feel too slow.
• Overcooking the finish. The final segment is fast, but it is not a sprint. If you grind the last minutes at VO2max level, you turn a controlled quality session into an exhaustion workout — with days of fatigue as the price.
• Progressing too often. The idea that every run should speed up leads to chronic moderate running with no real base. Easy runs stay easy; the progression is a quality session, not the default.
• Rigid pace targets in wind, heat or on a bad day. The build-up is designed relative to your starting pace, not to a wish pace. On hot days or hilly routes, steer by heart rate or feel — see also our guide to training in the heat.
• Skipping the cool-down. Stopping dead after the fast finale is a mistake. Plan five to ten minutes of very easy jogging — it does not count as part of the progression.

How Peakora builds progression runs into your plan

In the Peakora engine, progression runs are built into the plan by default: depending on your race distance and training phase, the plan schedules build-up sessions with clear pace and heart-rate targets — from the gentle beginner progression to the long run with a marathon-pace finish. When your training adapts because you missed a session or arrived exhausted, the plan adapts the progression with it: volume and finishing intensity are scaled instead of blindly followed. After the run, the recovery monitor shows what the session cost you — so you can see whether the build-up stayed in the green or the next workout should be easier.

Frequently asked questions about progression runs