How to Plan Your Race Day for a 100K or 100 Mile Ultramarathon

A 100K or 100 mile ultramarathon is a bloody long time and creating your race plan is more than calculating distance divided by a target finish time. The course changes, the terrain changes, the cost of stopping adds up, cutoffs matter, and the way you use the first few hours can determine what is still possible much later in the race.

A useful race day plan needs to do more than produce an average pace, it needs to help you understand what the course is asking, where the constraints are, how much time is really available for movement, how you want to approach the race and what information will still be useful when you are tired to think of more than next next step.

A race plan is more than a pacing target

It is easy to begin with a finish goal. Maybe you want to run a 100K in 16 hours or a 100 miler in 30 hours. That target matters, but by itself it tells you very little about how the race should unfold.

Two races of the same distance can have completely different planning problems. One might climb hard early and become runnable later, another might save its biggest climb for deep into the race, one might have aid stations every 8 kilometres, another might leave you alone for 20 kilometres at a time. A generous overall finish cutoff can still contain one checkpoint cutoff that becomes the real constraint.

Start with the course, not the average pace

The first job is understanding the whole race before trying to decide how fast to move through it.

Look at the route, total distance, climbing, descending and where those changes occur. The location of the terrain matters just as much as the totals.

A major climb in the first 20 kilometres is a different planning problem from the same climb at 130 kilometres.

A long descent when you are fresh is not necessarily the same descent after a night on your feet.

Checkpoint spacing matters too. A 12 kilometre section might be a short, runnable connection between aid stations or a slow mountain leg that takes several hours. Distance alone cannot tell you that.

Put checkpoints and cutoffs into the plan before you worry about perfect pacing

An ultra is not only a start line and a finish line. Checkpoints divide the race into operational sections, and cutoffs can change what a sensible plan looks like.

Record the official checkpoint distances and cutoffs from the current race information. If a checkpoint has a cutoff, look at the buffer your target plan creates there rather than only checking whether your final finish is under the overall cutoff.

This becomes especially important when the race has an early cutoff that is relatively tight compared with later parts of the course. A pacing plan can look comfortable at the finish and still fail much earlier because it did not account for the way the cutoffs are distributed.

Also note the practical constraints that affect race day:

Which checkpoints allow crew, where drop bags are available, whether pacers are permitted, what the aid station provides and where a long gap between services changes what you need to carry.

Separate race time from moving time

This is one of the easiest mistakes to make when planning a long race.

If your 100 mile target is 30 hours, you do not necessarily have 30 hours available for movement.

Time spent filling bottles, changing shoes, eating, using the toilet, dealing with feet or sitting at an aid station is still part of the race clock.

Those examples are not recommendations, they show why stop time has to be planned explicitly. If ten checkpoints average six minutes each, an hour has disappeared before you account for a single longer stop.

Once planned stops are separated from movement, the useful question becomes:

where should the remaining moving time be spent?

Equal kilometres are not equal

Average pace is convenient because it reduces the whole race to one number. On a hilly ultra, that simplicity can be misleading.

A kilometre of sustained climbing can cost several times as much as a runnable flat kilometre.

Descending may be faster early, then become slower once the legs are damaged.

Altitude, surface and technicality can change the cost again.

That does not mean every hill needs its own complicated equation, It means the plan should recognise that the course has shape.

When I look at an ultra, I am interested in where the hard sections occur and what I am likely to be carrying into them.

A difficult section at 20 kilometres is mainly a terrain problem. The same section at 140 kilometres is terrain plus everything that has happened before it.

Should you bank time early?

This is one of the questions that comes up repeatedly in long ultras.

Being ahead of plan early is not automatically a problem, the important question is how you got there.

If you are moving slightly quicker than planned because the terrain is easy, conditions are good and the effort is genuinely controlled, that is very different from pushing the first climb because you want to build a large buffer before the race gets hard.

The danger with deliberately banking time is that the cost can arrive much later. A few minutes gained early can be insignificant compared with what is lost if the pace contributes to muscular damage, nutrition problems or an effort level that cannot be sustained.

That is why a race plan should include a strategy for how the target time is distributed, not just a target finish.

Some runners want to be more restrained early, Others prefer a balanced approach.

Some deliberately accept a somewhat faster early race. The important part is that it is intentional and visible in the plan.

What changes when you go from 100K to 100 miles?

A 100K is a serious endurance race in its own right, the point is not that 100K is easy, the point is that the planning problem changes when 100K becomes an intermediate point rather than the finish.

A good 100 mile plan therefore has to care about the state in which you arrive at 100K, not just the time displayed on the clock when you get there.

Plan checkpoint decisions before you are tired

Deep into an ultra, decision making becomes expensive. The more decisions you can make when rested, the fewer you have to make when you are cold, hungry, sleep deprived or trying to get out of a chair.

For each important checkpoint, think about the likely purpose of the stop. Food, Bottles, Clothing, Lighting, Shoes, Poles, Drop bag, Crew instructions, Medication. Anything that matters should be in the plan.

The aim is not to make a rigid script that must be followed regardless of circumstances. The aim is to reduce unnecessary thinking.

If conditions change, you can change the plan because you understand what the original decision was trying to achieve.

Turn the plan into something you can actually use on race day

A perfect plan that stays on a laptop is not much help at 2 am.

A runner normally needs less information than the full planning process produces.

The next checkpoint, distance, expected timing, cutoff and one or two useful notes may be enough in the moment.

The crew may need more, checkpoint location, expected arrival, cutoff buffer, food requests, clothing, gear and what needs to happen before the runner leaves again.

This is where the race plan should become a set of useful race day views rather than one giant document.

A full plan can remain the reference, a compact runner summary can reduce the information load, Garmin Course Points can carry checkpoint information onto a compatible watch, and a live crew system can compare the plan with what is actually happening.

A race plan is a framework, not mandatory

No race planner knows exactly what will happen on race day.

Weather can move, trails can deteriorate, your stomach can stop cooperating, a planned food can suddenly become impossible to look at, a descent can take more out of your legs than expected, you can be fitter than the target or discover that the target was too ambitious.

A calculated schedule also does not prove that you are physiologically capable of the finish time you selected.

That does not make planning pointless, it makes the purpose of planning clearer.

The best ultra plans are therefore detailed enough to be useful and flexible enough to survive first contact with the actual race.

Where Track3D Race Planner fits

The Track3D Race Planner was built specifically for this.

You start with the actual course GPX ot FIT file rather than an abstract distance, then add checkpoints, cutoffs, planned stops and timing into the plan.

Once setup you choose the finish target and then Course-Aware Pacing will distribute the required moving time using distance, elevation and cutoffs rather than assuming every kilometer is equal.

Race Strategy can then reshape how that plan approaches the early and later race by allowing you to choose wether you want to start easier or harder while keeping the overall target aligned.

The result can then be output as a Full Race Plan or compact Runner Summary, and the same checkpoint structure can be carried into Garmin Course Points to be displayed on your watch.

If you use Track3D Crew, the plan then becomes the race day context for live progress, upcoming checkpoints and ETAs for your crew to plan their day.

The important part is not that Track3D gives you another pace number, It is that the different planning decisions stay connected to the same race.

Common 100K and 100 mile race planning questions