Long Run Progression Templates By Starting Weekly Mileage

Increase your long run by 1-2 miles a week, or roughly 10% of its current distance — whichever is smaller — and insert a step-back week every 3rd or 4th week, where the long run drops 20-25%. That's the universal rule, but the table you actually need depends on where you're starting from. Which of these three is you: low base, moderate base, or high base?

Grab the wrong table for your starting point and it isn't just wasted effort — it's the exact overload pattern behind the IT band and shin problems each bracket below tends to produce. Find your bracket first, then treat the 3-hour and 48-hour recovery checks underneath as your real gauge for moving forward, not the calendar.

Low Base: Starting Under 20-25 Miles a Week

If you're building from a low weekly mileage, your risk is overload, not under-training. I cap the longest run at 16-18 miles for this group, not the 20+ you'll see on generic tables — runners who chase a 20-miler from a sub-20-mile-per-week base are, in my experience, the ones who end up with IT band or shin problems partway through the build. The ceiling isn't caution for its own sake; it's a pattern I've seen repeat often enough to treat as a rule.

Total weekly mileage, not just the long run, has to stay under a 10% weekly increase too — otherwise the long run outgrows what the rest of your week can support, and you'll be under-recovered for it no matter how gradually the long run itself climbs.

Moderate Base: 25-35 Miles a Week

This is the most common starting point among repeat marathoners. Because your aerobic base is already established, a steeper early build is tolerable in a way it isn't for the low-base group.

High Base: 35+ Miles a Week

Here the ceiling and risk profile change again. Above roughly 20 miles, I switch a runner from a mileage cap to a time cap — time-on-feet becomes the binding constraint once you're layering marathon-pace segments inside the long run, and a purely distance-based number stops reflecting the actual fatigue cost of the session.

This table is about distance progression only — the workout structure of how to layer marathon-pace miles inside the long run is its own topic, so I won't duplicate it here.

How Long Is Too Long, and When to Freeze the Progression

Regardless of which table you're following, roughly 3 hours time-on-feet is the practical ceiling for a long run — not distance, not pace, time-on-feet. And there's one decision rule I use with every athlete, on every table: if you can't recover to normal easy-run legs within 48 hours of a long run, freeze the progression. Repeat the same distance the following week rather than advancing on the calendar regardless. It's the actual test I use to decide whether an athlete is ready to move forward, not a fixed schedule followed blindly.

Back to the full long run progression hub. Once your base table is set, consider adding a second long run once your base table is set, and keep warning signs you're progressing too fast in mind as you climb. If you're not sure your plan length matches your starting point, see matching plan length to your starting mileage.

Some Other Pages You May Like