Marathon Pacing For Hilly or Net-Downhill Courses

The give/cap rule for hilly or net-downhill marathons: on climbs, let your pace slow 15-25 seconds/mile per roughly 50-75ft of gain, rather than holding goal pace or matching flat-course effort. On descents, cap your pace gain at 10-15 seconds/mile faster than goal pace even when it feels easy — that cap protects your quads from damage that doesn't show up until it's too late to fix. The net effect across the course should be even or slightly negative effort, not even pace. Below: why banking time on downhills backfires, how to build a course-specific adjustment sheet, and when to hand pacing over to effort.

You've calculated a flat goal pace, and now an elevation chart is telling you that number is a starting point, not a target. Runners who ignore that gap make one of two mistakes: they grind uphill sections into unnecessary time loss, or they bank fast descents that feel harmless in the moment and quietly wreck their legs for the second half.

Why Banking Time on Early Downhills Backfires

Downhill running relies heavily on eccentric quad contraction to control your descent, which causes cumulative muscle micro-damage that doesn't show up as fatigue until much later. Runners who "bank time" hammering early downhills feel fine through halfway, then lose far more time to quad failure in the final 10K than the seconds they banked early.

Take a typical net-downhill, two-phase course — first half net descent, second half net climb then descent. Banking three to five minutes in the first half by running descents 20-30 seconds/mile faster than goal pace routinely costs eight to twelve minutes in the final 10K once the legs give out on the closing climbs. That's not a marginal trade — it's a losing one, every time.

I coach the eccentric-damage mechanism deliberately rather than just saying "don't go out too fast," because runners who understand why hold the discipline on race day when it feels easy to ignore. I coached a repeat Boston athlete who banked time on the early downhills in his first attempt and blew up on the Newton Hills. The following year, he followed the give/cap rule from mile 1 and ran a materially more even effort curve with a far stronger finish.

Building a Course-Specific Adjustment Sheet

Turn the general rule into something you can actually run with four steps. First, pull the course's official elevation chart and mark every sustained grade change over roughly 30ft. Second, apply the give/cap rule mile-by-mile against your flat goal pace to produce an adjusted per-mile target sheet. Third, identify the single hardest climb-after-descent stretch — on Boston, that's the Newton Hills after the early downhills — and treat it as the point where effort discipline matters most, not pace. Fourth, rehearse the adjusted pacing on a training run with comparable terrain, not just on paper.

When to Abandon the Pace Plan for Effort

One rule covers the rest: if your adjusted pace and perceived effort diverge by more than one full zone — goal-pace effort suddenly feels like tempo effort — on a climb, effort wins. Slow further. For the fuller framework on pacing by feel when the numbers stop making sense, see pacing by effort instead of pace.

Before you apply any of this, calculate your flat-course goal pace first — the give/cap rule adjusts that number, it doesn't replace it.

Back to the full marathon pacing strategy hub.

Some Other Pages You May Like