Course Recon: Learn the Race Course Before Race Day

Two runners in identical shape can finish ten minutes apart on the same day — simply because one knows that at kilometre 32 the road turns and the wind flips, and the other does not. Course recon has the best ratio of time invested to outcome gained in the entire sport: one or two hours, no fitness lost, and afterwards a good part of the uncertainty that makes races slow is simply gone.

Why knowing the course saves race time

The mechanism is well described and distinctly unglamorous. If you know the course, you spread your effort more evenly. A climb you anticipate does not get answered with a surprised sprint; a long descent you expect does not get paid for at the top. Those unnecessary spikes are exactly what is missing in the final third — a 30-second surge on a hill costs more than it gains, because the energy burned there comes back later as a loss of pace.

The second effect is psychological and measurable: expectation reduces perceived effort. A section you have already run in your head feels shorter than one that surprises you. It is the same effect that makes RPE the deciding variable in pacing — "how hard does this feel" is relative, not absolute.

The third effect is logistics: aid stations, toilets, transition zones, parking, start area. Standing in traffic for 20 minutes on race morning because you did not know the access road costs more than any single training session of the last week.

First digital: what the elevation profile really tells you

Preparation starts at home, with a file. Download the official profile or the GPX and read it in three passes — not as a picture, as information:

• First pass, the shape: Where is the longest climb, where does the course drop hardest, is the second half harder than the first? A marathon with its main climb between 25 and 35 km is a completely different race from one with an even distribution.
• Second pass, gradient in percent: A kilometre at 2 percent is flat, at 5 percent it is a climb, at 8 percent you walk or shift hard. Translate the sections into concrete expectations: at 5 percent, a runner typically loses 15 to 25 seconds per kilometre against flat pace at the same effort.
• Third pass, the descents: Long downhills are not recovery, they are load on the quads and knees. Anyone without descents in training pays for it between kilometres 30 and 40. Details in downhill running technique.

Be sceptical of auto-generated profiles: smoothing algorithms hide short ramps, and elevation models differ by several metres depending on the data source. When two sources disagree, trust the organiser's official course description — and verify the critical sections on site.

The three key sections that actually matter

Nobody needs to memorise a marathon course. What counts are three to five places where the race is decided. Pick them out the evening before your recon, then drive or run straight to those spots:

• The main climb: This is where it is decided whether you reach the top with reserves or with an oxygen debt. Measure the length, check the gradient on the steepest ramp, and settle whether you run or walk it. Above 8 percent and over 300 metres, walking is often the faster strategy — not the weaker one.
• The fastest descent: It gives time back, but only if you can handle it technically. Check corner radius, surface and whether the corners are sighted. In tight, blind corners the winner is whoever brakes early.
• The critical kilometre in the final third: Usually a combination of headwind, a slight rise and fading concentration. That is the section that belongs in your preparation — not the start everyone knows.
• The aid stations: The number matters less than their position relative to your gels. If the first station only comes at kilometre 8 but you eat every 30 minutes, you need your own supply — or you shift your schedule.

Those four points fit on half a page. Anything beyond that is ballast for your head on race day.

The recon itself: when, how, how much

Timing is a compromise. Two days before the race is ideal, because the legs are still fresh enough for a short stimulus and the information stays in your head. The day before works too, but short and without load. On race day itself you only check the start area, the transition zone and the first kilometre.

The mode depends on the distance:

• 10 km to half marathon: The whole course, once, easy. 20 to 30 minutes at goal pace over the final two kilometres is a legitimate stimulus and a form check at the same time.
• Marathon: In sections. The first three kilometres on foot, then drive to the two key sections and run 10 to 15 minutes at race intensity there. Running an entire marathon course two days out costs more than it gives.
• Cycling and gran fondo: Ride the climbs and the descents, drive the flat parts. In cycling, descents are the most frequently underestimated factor.
• Triathlon: Swim the course once if possible, or at least inspect the entry and exit zone. Walk the transition area, ride the bike loop in sections, run the run loop in full. What happens in transition is covered in T1 and T2.

One hard rule: no recon that behaves like a training session. Anyone running 15 kilometres with three intervals two days before a marathon has not done recon, they have trained — at the worst moment of the cycle.

What is genuinely different on site

Five things sit between the elevation profile and reality, and no portal shows them:

• The surface: Asphalt, concrete, gravel, forest track, cobbles. A 400-metre cobbled section costs real pace at the same effort and hammers the calves. When wet, "slow" becomes "risky".
• The corners: Ninety-degree turns between buildings, switchbacks, U-turns onto the opposite carriageway. Every tight corner is a pace break, every turnaround a braking and accelerating event.
• The wind: You know the prevailing direction from the forecast, the local channelling only on site. Street canyons, woodland and valley floors create wind tunnels that appear on no map. Note where you turn into the wind — that is where the group will split.
• The sun: Where is it at start time? A shadeless section at 11 a.m. is a different section than at 8 a.m. In heat, the position of those kilometres is a pacing argument, see heat training.
• The aid stations in reality: Is the table on the left or the right? Cups or bottles? Gels or water only? That decides which side you approach from — and whether you reach the table at all in a crowd.

The recon note: half a page that makes the difference

After the recon you do not write a description, you write instructions. The difference: "km 32: headwind, slight rise" is an observation. "km 32: turn into the wind, pace minus 5 s/km, take the gel at km 30" is a plan. Only the second one helps during the race, because it takes the decision in advance.

A five-column grid has proven itself: kilometre, what is coming, what I do, what I feel, what I eat or drink. The "what I feel" column sounds soft but is the most practical part — it links the place to the expected physical state and makes the scene retrievable later. Combine that with visualisation and you carry a scene in your head on race day instead of a surprise.

For a marathon, a second note has proven useful: an index card with seven lines that fits in a jersey pocket. Not the splits — those are on the watch — but the seven sentences you need out there: "km 5: don't go faster", "km 21: check", "km 30: cadence up".

Course knowledge as a training argument

If you know the course, you can train more specifically — and that is the point most often missed in practice. A race with 600 metres of climbing demands different preparation than one with 200; a course with long descents needs eccentric load tolerance, not another set of intervals. Once you know the profile, you plan the final six weeks accordingly: more climbing at tempo, longer descents, one or two sessions on similar terrain.

For the structure of those weeks, see the marathon training overview — it describes how base, build and peak phases stack up and where course-specific sessions fit. Road racing follows the same logic in reverse: climbs are trained on climbs, not on the flat, see gran fondo training.

Common mistakes in course recon

• Running too much. Recon turns into a session, and two days before a race every unnecessary bit of fatigue is a deficit with no return.
• Trying to remember everything. Twenty notes are not preparation, they are a list nobody recalls mid-race. Three to five points are enough.
• Only looking at the climb. The climb is rarely the problem. The descent after it, the headwind on the plateau and the aid station before it decide the result more often.
• Forgetting the start area. Start corral, toilets, bag drop, access road: every search on race morning costs nerves you need later.
• Not writing the recon down. Four hours later the details are gone. Without a note you come back with a feeling, not information.

The process in short form

Six steps, in this order: first read the profile and the official course description, second mark three to five key sections, third inspect access, start and transition zone, fourth run or ride the key sections, fifth note the aid stations and which side they are on, sixth write it all down as instructions on half a page. Time required: 60 to 120 minutes depending on distance and travel. Return: fewer surprises, more even pacing, better logistics — and a head that is free on race day for what actually happens.

Frequently asked questions about course recon