Skip to content
TrailMath
Language EN FR

Grade-Adjusted Pace on Trails: Why Downhill Isn't Free

Grade-adjusted pace turns a hilly run into a single effort-equivalent number. Here is how it works, why steep descents cost more than runners expect, and how to use it for pacing.

TrailMath Team Published 2 min read

If you have ever run an 8:00/mile on the flat and then watched your pace balloon to 14:00 on a climb while your effort felt identical, you already understand the problem grade-adjusted pace (GAP) solves. Raw pace lies on hills. GAP translates every slope into the flat-ground pace that would cost the same effort, so you can compare a climb, a descent, and a flat section on equal terms.

What grade-adjusted pace actually measures

GAP is built on the energy cost of running at a gradient. The classic reference is Minetti’s laboratory work measuring how many joules per kilogram per metre it takes to run up and down slopes of varying steepness. The cost curve is not symmetric: going up is expensive quickly, and going down is cheap only for a while.

Our GAP calculator applies that cost model to your pace and a given gradient, returning the equivalent flat pace. Feed it a 12% climb at 14:00/mile and it will tell you that effort is closer to a 9:00/mile on the flat - which is why your heart rate agreed with the effort, not the watch.

Why descents are not the refund you expect

Most runners model downhill as “free speed” - a rebate for the climb. The cost curve says otherwise. Running downhill is metabolically cheaper than the flat only up to about -10% to -15%. Beyond that, the cost rises again, because you are braking hard with every step. That eccentric braking load is what shreds your quads at hour eight of an ultra, even though your pace looks fast.

So a steep descent is simultaneously faster on the clock and more damaging to your legs than a moderate one. GAP captures the metabolic side of this; it does not fully capture the muscular damage, which is why pacing by GAP still needs judgement on long, steep descents.

Using GAP to pace a race

  1. Find your sustainable flat effort. This is the GAP you can hold for the race distance, not your 5K pace.
  2. Convert it to real paces per section. On the climbs your real pace will be much slower; on runnable descents, faster. Both can map to the same GAP.
  3. Cap your descents. If GAP says you could run a -18% descent at a blistering flat-equivalent, your quads will disagree late in the race. Hold back.

Pair GAP with the incline calculator to turn a course profile into a segment-by-segment effort plan before race day.

The one caveat

GAP is a model, not a law. It assumes good footing and ignores altitude, technical terrain, and fatigue. Treat it as a way to normalise effort across a hilly course, not as a promise of finish time. Used that way, it is the single most useful number a trail runner can carry into a race.