Article

How to Read a Race Elevation Profile and Build a Trail Pacing Plan

A race elevation profile shows where the course goes up and down.
It does not tell you how fast you can move through it.

A smooth descent and a loose, rocky descent can look identical on the chart.
Your pacing plan needs to account for both the shape of the course and the ground under your feet.

The goal is not to predict every mile split.
It is to decide where to conserve energy, where to hike, and where running will give you useful speed without excessive cost.

1. Read the axes before judging the climbs

Start with the horizontal axis, usually distance, and the vertical axis, elevation.
Check the units before making any calculations.

The chart’s proportions can distort your first impression.
A compressed horizontal axis makes climbs look steeper.
A stretched horizontal axis makes the same route look gentler.

Use the numbers, not the silhouette.

For each major climb, note:

  • Where it starts and finishes.
  • How much elevation it gains in feet.
  • How many miles it covers.
  • Its highest elevation.
  • What comes immediately afterward.

You can estimate average uphill grade with this calculation:

Grade (%) ≈ elevation gain in feet ÷ (distance in miles × 5,280) × 100.

A climb gaining 1,500 feet over 3 miles averages roughly 9.5%.
That tells you much more than a sharp-looking triangle on a chart.

Average grade still hides variation.
That climb could be steady throughout, or include runnable traverses between steep pitches.
Use a course map, route file, race notes, and recent trail reports to fill in those details.

Also separate total elevation gain from net elevation change.
A race that starts and finishes at the same elevation can still contain thousands of feet of climbing.

2. Divide the course into effort blocks

Do not build your plan around equal-distance splits.
Build it around terrain changes.

Useful boundaries include the base of a climb, a summit, the end of a technical descent, and an aid station.
For each block, label the likely movement: steady running, uphill running, hiking, or controlled descending.

Consider a 20-mile course:

  • Miles 0, 4: Rolling trail, 600 feet of gain. Run easily and resist racing the opening miles.
  • Miles 4, 7: A sustained 1,500-foot climb. Hike steep pitches before running becomes a strain.
  • Miles 7, 11: A rocky 1,800-foot descent. Prioritize secure footing and controlled steps.
  • Miles 11, 16: Runnable rolling terrain. Return to a sustainable running rhythm.
  • Miles 16, 20: A final climb and descent. Reassess effort against remaining distance and leg condition.

The most important question is often what follows a climb.

If a long descent comes next, reaching the summit exhausted can cost more time than you gained uphill.
If another climb follows a short saddle, treat both climbs as one sustained effort block.

Mark exposed ridges and high points too.
Wind, heat, and altitude can change the effort required even when the grade stays constant.

3. Set effort targets, then estimate time

Start with effort limits rather than target pace.

For a long trail race, early climbs should generally feel controlled enough to speak a full sentence.
If you are breathing hard before the course’s main difficulties, ease back.

Hike when running demands noticeably more effort for little extra speed.
There is no universal grade where everyone should switch.
Fitness, footing, climb length, and race duration all matter.

On a training climb, compare purposeful hiking with easy running over the same stretch.
Record elapsed time and perceived effort.
That gives you a practical switching point for similar terrain.

Estimate segment times from comparable training outings.
Match gradient and technical difficulty, not just distance.

If a similar 1,500-foot climb usually takes you 55, 65 minutes at sustainable effort, use that range as your starting point.
Allow more time if it comes late in the race or reaches unfamiliar altitude.

Do not assume descending will recover all the time spent climbing.
Technical descents demand concentration, and aggressive downhill running loads the quadriceps early.
Those tired legs still need to run the final miles.

Add aid-station time separately.
Four stops of three minutes add 12 minutes, even if your moving pace stays exactly on plan.

4. Carry a plan you can adjust

Turn your notes into a small checkpoint table.
Include cumulative arrival-time ranges, the next major climb, and any official cutoff.

Use the slower end of your estimates to check your cutoff margin.
Do not treat a generous-looking average pace as proof that the schedule works.

During the race, assess effort before checking whether you are ahead or behind.

If heat or poor footing slows you, revise the time estimate rather than forcing the original pace.
If you feel strong early, keep the reserve.

A good pacing plan protects your ability to move well late.
The elevation profile tells you where that protection matters most.