Cutoffs Don't Care How Fit You Are

Most people who don't finish an ultra were fit enough to finish it. They just ran out of a resource nobody trained them to manage: time.

Fitness gets talked about endlessly. Cutoffs barely get talked about at all. Then somebody gets pulled at mile 60 with legs that still work, and everyone calls it a bad day.

It usually wasn't. It was arithmetic, done too late.

A cutoff is not a finish time

This is the misunderstanding that ends the most races.

You sign up for a 100-miler with a 30-hour limit. You do the division: 18 minutes per mile. You've walked faster than that. You stop worrying.

But the 30-hour limit is the last cutoff, not the only one. In between sit six, eight, sometimes twelve intermediate checkpoints, and they are not spaced to match your 18-minute average. They're spaced around road access, aid logistics, and the volunteers who have to go home. Some of them are tighter than the finish. The early ones often are.

The runner who plans for 18-minute miles and hits a checkpoint at mile 30 that quietly required 15s has already lost the race. They just don't find out for another twenty miles.

The number that matters is buffer, not pace

Pace is the wrong unit for this problem. Pace changes every mile. It changes with grade, heat, altitude, whether you can still eat.

Buffer is the number you can actually act on: how many minutes are you ahead of the next cutoff, right now.

Buffer behaves differently from pace. Pace is instantaneous and noisy. Buffer accumulates and drains. You can bank it on a runnable descent and spend it on a climb, and at any moment there's exactly one number that tells you whether you're in trouble.

Runners who track buffer make different decisions than runners who track pace. They know the difference between a slow mile and an expensive one.

Work an example

Say a checkpoint sits at mile 40 with a 12-hour cutoff. That's an 18:00/mile requirement, same as the race average. Comfortable.

Now add what actually happens. You spend eight minutes at each of the four aid stations before it. That's 32 minutes gone, and it doesn't feel like anything at the time. Your real running requirement is no longer 18:00/mile. It's 17:12.

Still fine. But you were planning to spend longer at the mile-40 stop, because that's where your drop bag is. And the section after it climbs. And it'll be dark.

None of those is a mistake. Together they're a DNF, and the only place you could have seen it coming was on paper, three weeks earlier.

Aid stations are where races die

Nobody plans to spend 45 minutes in a chair. It happens in eight-minute increments, twelve times, and it never once feels like the thing that ended your race.

Ten aid stations at ten minutes each is one hour and forty minutes. In a 30-hour race that's most of your margin, spent standing still, usually on things that could have taken ninety seconds if somebody had handed them to you.

This is the strongest argument for a crew that knows the plan, and the strongest argument for writing the plan down. A crew that has your bottles filled and your food in your hand turns a ten-minute stop into a two-minute one. Do that eight times and you've bought back an hour you'd otherwise have to run for.

The back half is slower. Plan for it.

Almost everyone runs a positive split in an ultra. The second half takes longer than the first. This is normal, and it's not a failure of discipline.

What is a failure is planning as if it won't happen. If you build your cutoff plan on your first-half pace, you've built it on a number you will not see again.

Three things stack up in the back half. The climbs cost more than they did fresh. Your stomach gets less cooperative, so fueling slows down. And the sun goes down.

Night is the one people underestimate. Your world shrinks to a headlamp beam, technical footing gets slower and more careful, and the hours between 2am and dawn are where most people give back whatever buffer they had. Plan to be slowest exactly when the cutoffs stop being generous.

Build the chart before race day

This takes about twenty minutes and it is the highest-leverage twenty minutes in your whole build.

Get the official cutoff list from the race. Not a forum post, not last year's numbers. The race's own current documents, because directors change these.

Then, for each checkpoint, write down four things:

• The mile marker and the hard cutoff time
• The pace required to reach it from the previous checkpoint, not from the start
• The time you intend to arrive, with buffer built in
• How long you plan to stop there

That third column is the one people skip, and it's the one that matters. A plan that arrives exactly at each cutoff is not a plan. It's a coin flip with no margin for a rolled ankle, a bad stomach, or a wrong turn.

Segment-to-segment pace is what exposes the tight spots. Averaged from the start, every checkpoint looks survivable. Computed segment by segment, the hard ones announce themselves, and you can decide in advance where you're going to spend and where you're going to bank.

Race day: reading the number

Once you're moving, the chart collapses into one question, asked over and over. How much buffer do I have at the next checkpoint, and is it growing or shrinking?

Growing means you can afford the long stop, the shoe change, the extra few minutes with your crew.

Shrinking means something has to change now, while changing it is still cheap. Shorten the stops first. It's almost always the least painful place to find ten minutes, and almost always where the ten minutes went.

The mistake is waiting for the buffer to hit zero before responding. By then your options are gone and the only move left is running harder than you can sustain, at the exact point in the race where that's most likely to end you.

This is the part we built into HARDN. The cutoff tracker holds your chart, and as you update your position it shows buffer at the next checkpoint, flags close calls before they're emergencies, and projects your arrival three ways: at your current pace, if you slow 10 percent, and if you speed up 10 percent. That middle projection is the honest one. It's what happens when the sun goes down and the climbs start costing more, and seeing it at mile 45 instead of mile 70 is the entire difference.

Knowing when it's over

Sometimes the math is just the math.

If the required pace to make the next cutoff is faster than anything you've run in the last twenty miles, and the terrain ahead is harder than the terrain behind, the answer isn't grit. Runners hurt themselves badly chasing a checkpoint that stopped being reachable an hour ago.

There's a difference between a race you lost and a race that was over before you admitted it. Knowing which one you're in is its own kind of strength, and it's the kind that gets you to a start line again.

The short version

Cutoffs aren't a formality at the end of the race. They're a series of gates, unevenly spaced, and the early ones are frequently the hard ones.

Do the arithmetic before you toe the line. Track buffer, not pace. Get out of the chair.

Most people who get pulled were fit enough to finish. Don't be one of them for a reason a spreadsheet could have caught.