The progression run is the most underused workout in Indian distance training. It sits quietly in the published plans of every major coach - Daniels, Pfitzinger, the Hansons - and it asks one thing of you: start slow, finish strong. No other workout teaches discipline at the front and strength at the back as precisely. The first time I did a real progression run, in Bengaluru's Cubbon Park, I learned more about pacing in 75 minutes than three months of unstructured long runs had taught me. This is the founder's note on how to do one correctly.
The argument runs in four parts: what a progression run actually is, what it builds, how to structure it, and how to integrate it into an Indian training week.
What a progression run is, and what it is not
The terminology in running coaching is inconsistent across blogs. The published definitions agree on the substance.
The definition
A progression run is a single continuous run in which pace increases incrementally from easy at the start to moderate or hard by the finish. The transitions are deliberate, not accidental. The final portion may approach marathon pace, half-marathon pace, threshold pace, or 10K pace depending on the variant. The Daniels Running Formula formalises this as the 'progression long run' and uses it as a core workout in the marathon training block.
What it is not
A progression run is not a tempo run. Tempos sit at a fixed near-threshold pace for the whole effort. A progression run is not an interval session - there are no recoveries. A progression run is not a long run with a fast finish thrown in at the end as an afterthought; the structure is engineered, with specific pace bands and time blocks.
The pacing structure
The most common structure is three or four pace bands. A typical 75-minute progression run for a marathoner: 25 minutes easy, 25 minutes steady (roughly marathon pace plus 20 seconds per km), 20 minutes at marathon pace, 5 minutes at marathon pace minus 10 seconds. The exact splits scale to the runner. The principle is consistent: each band is faster than the last, and the transitions are clean.
What the progression run actually trains
Each block of the run targets a different physiological and psychological adaptation.
Pacing discipline at the start
The hardest part of any progression run is the easy beginning. Indian runners trained mostly on group runs and Strava-driven competition find this hard. The discipline is the work. Starting slow recruits the aerobic system and trains the mental ability to hold back when you feel fresh. This is the same skill that prevents marathon positive splits.
Aerobic strength in the middle
The steady and moderate blocks accumulate fatigue while maintaining aerobic dominance. The 2018 review in Sports Medicine on polarised training identified the moderate-intensity domain as the band where most distance runners spend insufficient time. Progression runs are one of the cleanest ways to spend structured time there.
Race-pace closing strength
The final block - run on accumulated fatigue at goal race pace or faster - trains the specific neuromuscular and metabolic strength of running fast when tired. This is the marathon's central demand. The progression run replicates it in 75 to 120 minutes rather than 3 to 5 hours.
The cumulative lesson
You learn that pace is a choice. You learn that fatigue is not the enemy of speed - dosage is. You learn what it feels like to negative-split. The body learns. The mind learns. Most importantly, the mind learns to trust the body when the body is tired.
How to structure a progression run
The published frameworks offer specific structures by training goal.
The marathon progression run
For a marathoner: 90 to 120 minutes total, in three or four bands. A useful default for a 4-hour marathoner: 30 minutes easy (6:00 to 6:15 per km), 30 minutes steady (5:50 per km), 25 minutes marathon pace (5:40 per km), 15 minutes marathon pace minus 5 (5:35 per km). Use our pace calculators to convert these to your specific target.
The half-marathon progression run
For a half-marathoner: 60 to 75 minutes total. The final block targets half-marathon pace rather than marathon pace. A useful default: 20 minutes easy, 20 minutes steady, 15 minutes half-marathon pace plus 10, 10 minutes half-marathon pace.
The 10K progression run
For a 10K racer: 45 to 60 minutes total. The final block targets 10K pace or slightly slower (10K plus 5 to 10 seconds). The first block is correspondingly shorter. The structure compresses but the principle holds.
The short progression run for mid-week
A 35 to 45-minute mid-week progression - 15 minutes easy, 15 minutes moderate, 10 minutes at threshold pace - is one of the highest-value workouts in a busy training week. See our types of run guide for the full taxonomy.
How to execute it without ruining the workout
Most failed progression runs fail in the first 20 minutes.
Trust the easy block
Run the first block at the pace specified, not at the pace you feel like running. If you feel fresh, the workout is still working. The fatigue arrives later. Many first-timers run the easy block too fast and then cannot accelerate at the end. The result is a flat tempo, not a progression.
Use kilometre splits
Set your watch to alert at every kilometre. Pre-calculate the cumulative time. A progression run requires conscious pace management - especially at the transitions between blocks. Daniels VDOT tables, accessible through our Daniels VDOT guide, give you the specific paces for your fitness level.
Pick a forgiving surface
The final block of a progression run, at marathon pace and faster on tired legs, is harder on connective tissue. Choose a forgiving surface where possible. The track is fine if mentally tolerable. The dirt loops at Hebbal in Bengaluru, the cantonment roads in Pune, the Worli Sea Face stretch in Mumbai, the Lodhi Garden loop in Delhi - all are reasonable. Avoid uneven concrete pavements.
Respect the recovery the next day
A real progression run is a hard workout. Treat the next 24 hours as recovery: an easy run of 30 to 40 minutes or a rest day. Stacking another quality session within 24 hours significantly raises injury risk and limits adaptation.
Where progression runs fit in the Indian training week
The integration is straightforward once the workout is understood.
The weekly placement
For most Indian distance runners training for a marathon or half-marathon, one progression run per week is appropriate, replacing the standard moderate-paced steady run. Two per week is the upper limit, and only for runners with high training age and clean injury history. Our marathon plans integrate progression runs as a core weekly workout.
The seasonal placement
Progression runs are most useful in the middle of a training block, between base and peak. They prepare the body for the more specific race-pace work that follows. In a 16-week marathon plan, progression runs typically appear in weeks 6 through 13.
The climate calibration
In Indian summer or monsoon heat, the final hard block of a progression run is the hardest to execute. Heat reduces sustainable pace by 8 to 12 seconds per kilometre above 28 degrees Celsius. Adjust target paces accordingly rather than abandoning the workout. The discipline of the progression - start slow, finish strong - is exactly the discipline that hot weather training rewards.
The race-day translation
Progression runs train the most important race-day capacity: the capacity to run faster at the end than the beginning. The data on marathon finish times is clear that negative-splitters finish faster than positive-splitters. The progression run is the most direct training intervention for this. Use our plan generator to build a marathon block that includes weekly progression runs at the right intensity for your current fitness. Visit the Running Lab for the supporting reads on race-day pacing and execution. Start slow. Build through the run. Finish strong. The race wants what the workout teaches.