⏵ Conditions & terrain

How to Study a Course

Studying a course means turning the elevation profile into an actual plan. You read the profile (and learn where it lies to you), divide total gain by distance to see how hard it really is, use the true cost of climbing to decide which grades to run and which to power-hike, then chop the course into aid-station legs and give each one a terrain read, a tactic, and a time budget. I have toed the line at races where I knew the profile cold and races where I winged it, and the difference is night and day. This guide walks you through every step, with a difficulty table, a metabolic-cost cheat sheet, and a worked segment plan you can copy.

⏵ On this page

Step 1: Read the elevation profile

An elevation profile is just the course squeezed into one picture. The bottom axis is distance, the side axis is elevation, and the wiggly line is what your legs are about to deal with. Most people glance at it, say "yikes, lots of climbing," and move on. That is not studying it. Studying it means reading the line like a story.

Find the number that actually matters

First thing I do is grab two numbers off the page: total elevation gain and total distance. Divide gain by distance and you get feet of vert per mile, which is the single best one-number read on how hard a course is. Total gain alone fools you, because 10,000 feet over 100 miles is rolling and runnable, while 10,000 feet over 30 miles is a different sport. Get the per-mile number first and you instantly know roughly what kind of day you are signing up for.

Then walk the line left to right and mark the features. Where are the long sustained climbs? How steep do they look? Where are the long descents that are going to wreck your quads? Which stretches are flat and runnable? You are building a mental movie of the day, climb by climb, so nothing on race day is a surprise.

Where a climb sits matters more than how big it is

This is the part most runners miss. A 2,000 foot climb is one thing at mile 4 when you are fresh and full of snacks. The exact same climb at mile 80, in the dark, on dead legs, is a wall. So do not just note that a climb exists, note WHERE it falls in the race and what shape you will be in when you hit it.

I literally annotate the profile: "big climb early, hold back here," "runnable middle, this is where I make time," "brutal climb at mile 78, this is going to hurt, plan to hike it and eat before it." That turns a chart into a plan. The profile tells you where you will be strong and where you will be suffering, and that is the whole point of looking at it.

Step 2: Know where the chart lies to you

Here is the thing nobody tells you: the elevation profile is not a photograph, it is a drawing, and drawings can mislead. Two things distort almost every profile you will ever look at, and if you do not correct for them you will plan around a course that does not exist.

The vertical scale is almost always exaggerated

To make a profile readable, the vertical axis gets stretched way out of proportion to the horizontal. So a climb that is really a gentle 5 or 6% grade can look like a sheer cliff on the chart, and a short steep punch can hide inside a stretch that looks dead flat. This cuts both ways. Relentless gradual grades scare people more than they should, and sneaky steep little kickers get missed entirely.

The fix is to stop trusting the SHAPE and start doing the math. Pick a climb, read how much it gains and over what distance, and work out the actual grade (rise over run). A 600 foot climb over a mile is about an 11% grade. That tells you far more than how pointy it looks on the chart.

The gain number itself can be wrong

GPS is great horizontally and pretty lousy vertically, so raw tracks pick up a lot of elevation noise. A jittery file can inflate total gain by hundreds or even thousands of feet, which is why the same route shows different gain on different watches and apps. On the flip side, heavy smoothing (which apps use to kill that noise) can sand real rolling terrain down and under-report gain. Barometric data helps, pure-GPS data drifts more.

So do not treat any single gain number as truth. Cross-check it: compare the race director number against Strava or a mapping tool, and if they disagree by a lot, split the difference and plan conservative. And remember the profile shows you grade, never footing. Rocks, roots, mud, and scree can turn a gentle-looking grade into a crawl, so read other runners reports and a real map for what the line cannot show.

Step 3: Classify the course by vert per mile

Once you have an honest gain-per-mile number, you can size up the course at a glance. These bands are rough guidance used all over trail coaching, and they assume reasonable footing, but they are a great gut check on how much you will run versus hike and how far off your flat pace you should expect to be.

Course type	Vert per mile	How it feels
Smooth / rolling	Under ~150 ft/mi	Runs a lot like a road race with bumps. You can run almost all of it. Pace is close to your flat pace.
Moderate / hilly	~150 to 300 ft/mi	The bread-and-butter trail race profile. Real climbs, but most are runnable if you stay patient and pick your moments to hike.
Strong climbing	~300 to 500 ft/mi	Now you are power-hiking real chunks of it. Plan your fuel and effort around long climbs, not around mile splits.
Mountainous	~500 to 800 ft/mi	Big sustained ascents and quad-wrecking descents. Hours, not miles, are the unit. Your flat pace is almost meaningless here.
Very steep / alpine	~800+ ft/mi	Hands-on-knees climbing and technical descending. This is mountain running. Forget pace, think vertical feet per hour and survival.

Use this to set expectations, not to predict a finish time to the minute. Once you know the course is, say, mountainous at 600 ft/mi, you know to train your climbs and descents hard and to fuel by the hour. For a deeper build, see how to train for elevation gain and vert.

Step 4: Decide which grades to run and which to hike

This is where studying the profile turns into a real tactic. Running uphill costs way more energy than running flat, and the cost is not linear. Below are the net energy-cost multiples by grade from the classic exercise-physiology work (Minetti and colleagues measured the cost of running across a wide range of grades on a treadmill). The takeaway is simple: steep climbs cost a fortune in energy for almost no speed, so you hike them.

Grade	Cost vs flat	What to do
Flat (0%)	1.0x (baseline)	Your reference. Everything below is relative to this.
Gentle up (+5%)	~1.3x as costly	About a third harder per step. Still runnable for most, but it adds up over a long climb.
Moderate up (+10%)	~1.7x as costly	Near the line where hiking starts to make sense, especially late in a race.
Steep up (+15%)	~2.1x as costly	Running this is rarely worth it in an ultra. Power-hike it and save the legs.
Gentle down (-5%)	~0.9x (a little easier)	Free speed. This is where you make up time without spending much.
Steep down (-15%+)	Rises again, and trashes quads	Braking is expensive and it shreds your quads. The cost curve is not a slide; past about -10% it climbs back up.

These are net cost-of-running figures and are approximate, but the shape is what matters: cost climbs fast as the grade steepens, and steep downhills get expensive again because braking is hard work that wrecks your quads.

The power-hike rule, in plain terms

Energetically, walking starts beating running somewhere around 15 to 16 degrees when you are fresh. But that crossover point drops as you get tired, so deep in an ultra most people are hiking anything over about 8 to 10%, even the pros. Kilian, Courtney, Walmsley, they all flip to a hike when the grade hits double digits or the climb is long enough to matter. Hiking the steep stuff is not weakness, it is the smart play.

My field rule needs no math: if your "run" has shrunk to a shuffle that is barely faster than a strong hike, or your heart rate spikes and you start tasting pennies, drop to a power-hike with your hands driving on your thighs. You will lose almost no real time, you will keep your effort aerobic so you are not torching glycogen, and you will save your legs for the runnable miles where speed is actually cheap. Plan your hikes on the profile in advance: mark the climbs you intend to walk so you are not making that call with a fried brain at mile 70.

To put real numbers on your climbs and descents, run them through our grade-adjusted pace calculator so you can see how much each grade actually slows you, and read how to pace an ultra by effort for the heart-rate and power-hike side of it.

Step 5: Build the segment-by-segment plan

Now you turn all of this into one usable thing. Chop the course at the aid stations, because that is how you will actually live the race, not in even mile splits. For each leg between aid stations, write the terrain, the tactic, and a realistic time budget. Here is a worked example for a hilly 50K with about 6,000 feet of gain, so you can see the shape of it.

Leg	Terrain	Tactic	Time budget
Start to AS1 (mi 0 to 7)	Rolling, gentle net climb	Go EASY. This feels too slow on purpose. Bank patience, not time.	~1:15 (target), cutoff ~2:00
AS1 to AS2 (mi 7 to 14)	The big climb, ~1,800 ft over 4 mi	Power-hike anything over ~10%. Settle into a rhythm. Eat on the climb.	~1:45 (target), cutoff ~4:00
AS2 to AS3 (mi 14 to 22)	High rolling traverse, runnable	This is your money section. Run the flats and gentle downs steady.	~1:40 (target), cutoff ~6:15
AS3 to AS4 (mi 22 to 27)	Long sustained descent, ~2,200 ft	Quick feet, light steps, do NOT hammer it. Protect the quads.	~0:55 (target), cutoff ~7:45
AS4 to finish (mi 27 to 31)	Rolling with one nasty late kicker	Hang on. Expect to fade 5 to 10%. Empty the tank on the last mile.	~0:55 (target), cutoff ~9:00

The numbers here are an illustration, not your race. The method is what travels: every leg gets a terrain read, a tactic, and a time you expect to arrive, with the cutoff sitting next to it so you always know your margin.

Make it a card you can read at mile 50

Once the legs are mapped, boil it down to something you can actually use when your brain has turned to oatmeal. I write a tiny card (or tape it to my bottle, or load it on my watch): at THIS aid station, target arrival is THIS time, do THESE things (refill, grab gels for the next carry, take a salt cap, eat before the climb). The plan should make decisions FOR you so you are not problem-solving on dead legs.

Tie your fueling to the same legs, not to the clock. Every carry between aid stations needs enough carbohydrate and sodium to get you to the next stop at your hourly target, with a buffer if that leg is a long climb. Plan the eating per leg, build the carries off the aid-station chart, and you will not run dry two miles short of help. That is exactly the method in the fueling guide below.

Build the eating side of each leg with how to build an ultramarathon fueling plan and the free ultra fueling calculator, which maps your carbs and sodium per hour onto the carries.

Pace the plan: split strategy and cutoff buffer

The last piece is the time budget itself. A profile-aware plan is only as good as the effort you run it at, and the two things that ruin good plans are going out too hot and not respecting the cutoffs.

Plan to fade, and start slower than your ego wants

On a flat road you can chase a negative split. On a real trail ultra, forget it. Terrain, fatigue, heat, and altitude make a positive split nearly inevitable for almost everyone, so plan for it instead of fighting it. A conservative first half is money in the bank: it spares your glycogen and keeps fatigue down for when the race actually gets hard in the final quarter.

A clean framework is to split the race into four quarters, run even-to-slightly-positive effort for the first three, and accept a 5 to 10% fade on the fourth. The classic blowup is a first quarter that felt easy but was never sustainable. Real talk: if your first big climb has you breathing hard and pushing, you already went out too fast. Back off. The race starts at the halfway point.

Treat cutoffs as a hard wall, with a real buffer

Aid-station cutoffs are usually loose early and tighten as the race goes on. They are a safety net, not a pacing guide, and if you are running anywhere near the early cutoffs you are already in deep trouble. So plan to your goal finish, then check that every single leg leaves comfortable margin to its posted cutoff, and stack a 3 to 5% cushion on top for the stuff that always happens: a rough patch, a long stop, a missed turn.

That buffer matters most at altitude and in the heat, where your late-race pace can fall off a cliff. Write the cutoff next to your target arrival for every aid station so you always know your margin at a glance. The day will rarely go faster than you hoped, so build the plan around the slower version of yourself and be pleasantly surprised.

Pressure-test your finish time and your aid-station splits with the race time calculator, which factors in the vert so the hours in your plan are honest.

⏵ Stop eyeballing a static profile

Reading the chart by hand is a great skill, but it is slow and easy to get wrong. Summit Line takes your actual course and your real fitness and builds the segment plan for you: grade-by-grade pacing, where to power-hike, aid-station splits with cutoff margin, and a fueling schedule mapped onto every carry. You study the course once, then race off a plan dialed to you instead of a guess.

Get started free →See it on a real race

⏵ Free calculators, no signup

Studying the profile gives you the shape of the day. These free tools put real numbers on it, so your segment plan and time budget are based on math, not vibes.

See all free running tools →

Keep going: related guides

Studying a course FAQ

How do I read an elevation profile?

Start with the axes. The bottom is distance, the side is elevation, and the line is the terrain you will run. First find the total gain and the distance, then divide to get feet of vert per mile, which tells you how hard the course really is. Next walk the line left to right and mark the big features: where the long climbs sit, how steep they are, where the quad-wrecking descents are, and which sections are runnable. The single most important thing is WHERE each climb falls in the race, because a 2,000 foot climb at mile 4 is a totally different problem than the same climb at mile 80. Read the profile as a story of where you will be strong and where you will be hurting, not just as a pile of total gain.

Does the elevation profile lie to me?

Sometimes, yes, and you have to know how. Race directors almost always exaggerate the vertical scale so a climb that is a 6% grade looks like a cliff on the chart, which makes gentle-but-relentless grades look scarier than they are and hides short steep punches inside a "flat" looking stretch. The total gain number can also be off, because GPS is poor in the vertical and noisy tracks can inflate gain by hundreds or thousands of feet, while heavy smoothing can sand real climbs away. So treat the profile as a rough map, not gospel. Check the gain against a couple of sources (the RD number, Strava, a mapping tool), and where you can, look at a real map or other runners reports to confirm the grades and the footing, which a profile never shows.

How do I know when to power-hike instead of run?

It comes down to the grade, the length of the climb, and how deep you are into the race. Energetically, running stops being worth it somewhere around 15 to 16 degrees when you are fresh, but that crossover drops as you tire, so in long ultras most people are hiking anything over about 8 to 10% in the back half. The real cost numbers back this up: a 10% climb costs roughly 1.7 times flat running and a 15% climb about 2.1 times, so you burn a ton of energy for very little speed. The rule I use is simple: if your run turns into a shuffle that is barely faster than a strong hike, or your heart rate spikes and you start tasting pennies, switch to a power-hike with hands on your thighs. You almost never lose real time hiking the steep stuff, and you save your legs for the runnable miles where speed is actually cheap.

How do I turn a course into a segment-by-segment race plan?

Use the aid stations to chop the course into legs, because that is how you will actually experience it. For each leg, write down the distance, the terrain (climb, descent, runnable, technical), the tactic (run, hike, hold back, push), and a realistic time budget for that section at the effort you want. Add them up to get your projected finish, then sanity-check it against a vert-aware finish calculator and the official cutoffs. The goal is a little card you can read at mile 50 when your brain is mush: at THIS aid station, you should arrive around THIS time, then do THESE things. Plan the effort and the fueling per leg, not per mile, because miles lie on a mountain and aid-station-to-aid-station is the unit that matters.

Should I plan even splits, or expect to slow down?

On a flat road you might chase even or negative splits, but on a real trail ultra you should plan to slow down a bit, and that is normal. Terrain, fatigue, heat, and altitude make a positive split nearly inevitable for most runners, so the smart play is a conservative first half that banks patience, then an honest expectation of fading 5 to 10% over the final quarter. A common framework splits the race into four quarters and targets even-to-slightly-positive efforts for the first three, then accepts the fade on the fourth. The mistake that ends races is going out at a pace that feels easy early but was never sustainable. If your first big climb has you breathing hard, you are already overcooked. Start slower than your ego wants.

How much buffer should I leave on the cutoffs?

Plenty, and you should plan to your goal time, not to the cutoffs. Aid-station cutoffs are usually generous early and tighten late, so running near the early cutoffs means you are already in trouble. Build your segment plan around a realistic target finish, then check that every leg leaves a comfortable margin to the posted cutoff, and add a 3 to 5% cushion on top for the unexpected (a bad patch, a long aid stop, a wrong turn). The buffer matters most at altitude and in heat, where your pace can fall off a cliff late. Know the cutoff at every station, know your planned arrival, and keep the gap between them honest, because the cutoff is a hard wall and the day will rarely go faster than you hoped.

This guide is for training and race-planning purposes and reflects general exercise-physiology research (including the classic Minetti cost-of-running work) and reputable trail and ultra coaching practice. It is not medical advice. The energy-cost figures, walk/run crossover, and vert-per-mile bands are approximate and vary with footing, fatigue, altitude, and the individual. Test your own pacing and fueling in training, confirm course details against official sources, and talk to a qualified professional before any big changes, especially if you have a medical condition.