Miss one cutoff by 90 seconds and your entire race is over, no matter how strong your legs feel. That is why a solid 100 mile cutoff plan example matters. Not as a spreadsheet exercise, but as race protection. If you are running a hundred, cutoff planning is not separate from pacing, fueling, or terrain strategy. It is the frame holding all of it together.
Most runners make the same mistake. They look at the official cutoff chart, divide total race time by 100 miles, and assume they just need to hold an average pace. That works on paper and falls apart on trail. A 14-minute average sounds manageable until the course stacks a hot canyon climb, a technical descent in the dark, and a long aid station reset into the same stretch.
A good cutoff plan is built around where time is actually won and lost. It accounts for vertical gain, footing, altitude, weather, aid station behavior, and the fact that mile 78 does not feel like mile 18. If you know where the race slows down, you can decide where you need margin.
What a 100 mile cutoff plan example should actually show
A useful cutoff plan does more than repeat race rules. It gives you target arrival times at key aid stations, a realistic moving pace for each segment, and a buffer you can protect when the day starts slipping. The goal is simple: stay ahead of mandatory cutoffs without burning yourself early.
That means your plan should be aid-station-based, not just mile-based. Most hundred-mile races are managed through aid stations anyway. They are where cutoffs happen, where crews meet you, and where time quietly disappears. If your plan ignores station time, it is incomplete.
You also need to separate moving time from total elapsed time. Many runners think they are pacing well because their trail pace looks right between stations, then lose 25 minutes at an aid stop and wonder why the cutoff cushion is gone. Cutoff math does not care whether that time was spent climbing, filling bottles, changing socks, or staring at soup.
A practical 100 mile cutoff plan example
Let us use a simplified example for a 100-mile mountain race with a 30-hour overall cutoff. This is not tied to one event, but it reflects how real races behave.
The course has 16,500 feet of climbing, several long sustained ascents, moderate technical terrain, and 12 major aid stations. The official cutoff chart looks manageable at first glance. The trap is that the back half gets slower, and the final quarter includes darkness, fatigue, and reduced downhill speed.
Here is the structure of a workable plan.
Segment 1: Start to mile 18
Suppose the first major aid station is at mile 18 with a cutoff of 5 hours 30 minutes. A lot of runners see that and think, I just need to average around 18-minute miles. That can be dangerous if the first climb is runnable and the field energy is high. This is where people either waste matches by pushing too hard or lose free time by moving too casually.
A smart target might be 4 hours 30 minutes, giving you a 60-minute buffer. That does not mean racing the first section. It means using your freshest legs on the most efficient terrain while keeping effort under control. If the section is runnable, this is the place to bank time safely.
Segment 2: Mile 18 to mile 42
Now the course turns slower. Say there are two aid stations in this stretch, at mile 30 and mile 42, with progressively tighter windows because of climbing and heat exposure. Your target might be 7 hours 40 minutes to mile 42 on elapsed time, while the official cutoff is 9 hours.
Notice what this does. You are not trying to run aggressively. You are trying to leave the early race with enough daylight and enough margin to survive the inevitable slow patch later. The buffer is there because the race will ask for it.
Segment 3: Mile 42 to mile 62
This is where many hundred-milers start bleeding time. The effort is no longer cheap. Aid station stops get longer. Nutrition gets less automatic. If mile 62 has a cutoff at 18 hours, your plan might target arrival at 16 hours 15 minutes.
That 1 hour 45 minute cushion is not luxury. It covers normal slowdown, not disaster. Maybe the temperature rises. Maybe a descent trashes your quads. Maybe you need 10 extra minutes to settle your stomach. You want that room before night arrives.
Segment 4: Mile 62 to mile 80
This is often the hinge point in a 100 mile cutoff plan example. If your race starts to come apart, it usually shows here first. Say mile 80 has a cutoff of 24 hours. A smart target might be 21 hours 45 minutes.
Why such a large gap? Because the final 20 miles are rarely your fastest. Darkness, navigation errors, reduced appetite, and muscular damage all push pace down. If you arrive at mile 80 with only 30 minutes to spare, you are not in control. You are reacting.
Segment 5: Mile 80 to finish
With a 30-hour race cutoff, arriving at mile 80 in 21 hours 45 minutes gives you 8 hours 15 minutes for the final 20. That may sound generous, but on a hard course it can disappear quickly. If the last section includes one more major climb and technical singletrack, you may be moving at survival pace. Your earlier margin is what keeps the race alive.
How to build your own plan without guessing
Start with the race cutoff chart, then map every official aid station and note the distance between them. After that, stop thinking in averages. Think in segments.
Ask what each section demands. Is it steep hiking terrain? Smooth jeep road? Rocky descent? Exposed ridge that gets hammered by sun or wind? You should expect a different pace in each of those environments. That is the core difference between a real plan and a hopeful one.
Then estimate moving time for each segment based on terrain, elevation, and your likely race-state at that point. Early segments should reflect controlled efficiency. Mid-race segments should include some slowdown. Late segments should assume meaningful fatigue. If your pace chart suggests you will run mile 88 as efficiently as mile 12, the chart is lying to you.
Next, add aid station time on purpose. Not as a vague guess. Put a number on it. Maybe 3 to 5 minutes for a bottle refill and quick move-through. Maybe 8 to 12 minutes at major crew access stations. Maybe longer if you expect clothing changes after dark. The point is to make those minutes visible before race day.
This is where race-specific planning tools matter. When you can inspect the course by aid station, review elevation per segment, and compare terrain transitions instead of just total mileage, your cutoff plan gets sharper fast. One mention is enough: TrailSight is built for exactly this kind of prep.
Where runners usually get cutoff planning wrong
The first error is building around best-case pacing. A cutoff plan should survive an average day, not require a perfect one. If your model only works when fueling is flawless and every descent goes smoothly, it is too fragile.
The second is treating all buffers equally. You do not need identical time cushions at every aid station. On runnable early terrain, 30 to 60 minutes of spare time might be realistic. On a brutal back-half climb, protecting even 20 minutes may take discipline. Place your biggest margin before the race gets expensive.
The third is ignoring aid station drift. Five extra minutes here, seven there, another six after sunset - suddenly your moving pace is fine and your race clock is not. This is why elapsed-time planning matters more than pace bragging.
The fourth is failing to update the plan during the race. A cutoff strategy is not static. If you lose 18 minutes to stomach issues at mile 35, you need to know exactly where you can realistically get some of that back and where you cannot. Not every segment is a recovery segment.
A better rule for race day
Think of your cutoff plan as a live control system, not a prediction. At each aid station, compare your actual arrival to your target, not just the official deadline. If you are still on your target schedule, keep executing. If you are behind target but ahead of cutoff, tighten transitions and protect effort. If you are close to the official limit, stop making emotional decisions and start making efficient ones.
That might mean shorter station time, faster hiking on climbs, or more deliberate fueling so a small problem does not become a race-ending one. It does not mean panic. Panic burns time and energy at the same time.
A hundred rarely falls apart all at once. More often it leaks away in small, preventable losses - an overcooked opening climb, a sloppy crew stop, a missed calorie window, a late realization that the next segment is slower than expected. The runners who stay ahead of cutoffs are usually the ones who saw those losses coming.
Build your plan by aid station. Respect the terrain. Give the back half more weight than your ego wants to. Then when the race gets narrow and the clock starts looking louder than the trail, you will still have room to run your race instead of the cutoff’s.