Calculator

Planning guide

Ultramarathon Cutoff Times: How Checkpoint Cutoffs Work

An overall cutoff is the time limit for the whole race. Checkpoint cutoffs are the deadlines in between, written as leave-by or arrive-by times. This guide covers the moving pace those limits require after planned stops, and a per-checkpoint buffer worksheet for a fictional 50-mile course.

Last updated November 16, 2026

Quick answer

In this guide's illustrative 50-mile example, an example overall cutoff of 13:30 with 50 minutes of planned stops requires a 15:12 per mile moving pace to finish exactly on the cutoff. The same course with a 12:30 finish goal needs a 14:00 per mile moving pace and shows a 1:00 overall buffer, but the tightest checkpoint buffer in the worksheet is 19 minutes at High Meadow.

A cutoff is a deadline on the race clock. It can apply to the finish, to a checkpoint along the way, or to both, and the wording in your runner guide tells you which time to compare.

If the rule is a leave-by, compare it with your planned departure. If it's an arrive-by, compare it with planned arrival. The 100-mile aid-station plan walks through that check on a worked overnight card.

What types of cutoffs do ultras use?

An overall cutoff is the time limit for the whole race. Checkpoint cutoffs are intermediate deadlines at aid stations, and a runner guide may list them as clock time or as elapsed time from the start.

A clock time looks like 2:00 PM. Elapsed time looks like 8 hours. The printed card puts a day label on every clock (Day 1, Day 2), so times after midnight stay in order; the 100-mile aid-station plan shows how those labels work. In wave starts, some races time every cutoff from the last wave's start, so check which start your guide uses.

Some races set checkpoint cutoffs as the time you have to leave the aid station by. Others use the time you have to arrive or pass through by. One race can even use both, so read the wording for each checkpoint. If the runner guide lists only a time, ask the race which one it means.

The ultramarathon aid-station plan covers how to copy official distances, start times, and cutoff language from the current runner guide onto a card.

What pace does a cutoff require?

Direct answer: The moving pace that just makes a cutoff is the cutoff's elapsed time minus your planned stops, then divided by the race distance. That's what the planner does in Goal mode when your finish goal equals the overall cutoff.

pace that just makes the cutoff = (cutoff elapsed - planned stops) ÷ distance

Overall time limits vary a lot, even between races of the same distance, so start from your race's published limit. The figures below are labeled examples.

Here's an illustrative 50-mile course with a 6:00 AM start, 50 minutes of planned stops, and an example overall cutoff of 13:30, which is 7:30 PM on the clock. Every clock in this example falls on Day 1.

PlanGoal elapsedStopsMoving timeRequired moving paceOverall paceProjected finishCutoff buffer
PlanJust makes the example 13:30 cutoffGoal elapsed13:30Stops50 minMoving time12:40Required moving pace15:12 per mile (9:27 per kilometre)Overall pace16:12 per mileProjected finish7:30 PMCutoff bufferon the cutoff (0:00)
PlanSame course, 1:00 overall bufferGoal elapsed12:30Stops50 minMoving time11:40Required moving pace14:00 per mile (8:42 per kilometre)Overall pace15:00 per mileProjected finish6:30 PMCutoff buffer1:00 ahead

Set the goal to that example 13:30 cutoff and the required moving pace is 15:12 per mile. You finish at 7:30 PM, on the cutoff, and the planner's cutoff-buffer chip reads 00:00:00 ahead, which means no margin at all.

Give the same course a 12:30 finish goal, one hour under that example cutoff, and the required moving pace becomes 14:00 per mile. You finish at 6:30 PM, 1:00 ahead of the example 13:30 cutoff. That 14:00 pace is faster than 15:12 because the same 50 minutes of stops now have to come out of a shorter goal.

The same just-makes math, with other labeled example cutoffs and stop budgets:

DistanceExample overall cutoffExample stop budgetMoving timeMoving pace that just makes the cutoffOverall pace (cutoff ÷ distance)
Distance50 kmExample overall cutoff8:30 elapsedExample stop budget30 minMoving time8:00Moving pace that just makes the cutoff9:36 per kilometre (15:27 per mile)Overall pace (cutoff ÷ distance)10:12 per kilometre (16:25 per mile)
Distance50 miExample overall cutoff13:30 elapsedExample stop budget50 minMoving time12:40Moving pace that just makes the cutoff15:12 per mile (9:27 per kilometre)Overall pace (cutoff ÷ distance)16:12 per mile (10:04 per kilometre)
Distance100 kmExample overall cutoff16:00 elapsedExample stop budget1:00Moving time15:00Moving pace that just makes the cutoff9:00 per kilometre (14:29 per mile)Overall pace (cutoff ÷ distance)9:36 per kilometre (15:27 per mile)

For 100-mile finish times after a stop budget, use the 100-mile pace chart. The same Goal-mode math applies if you set the finish goal to your race's overall cutoff.

Want the pace and overall buffer for your own stations? Open the planner, enter the distance, stops, start time, and overall cutoff, and print the card.

Which checkpoint is the tightest?

In this example, the tightest checkpoint is High Meadow at mile 27, not the finish.

The worksheet uses the 12:30 plan above: 50 miles, a 14:00 per mile moving pace, 50 minutes of stops, a 6:00 AM start, and the example 13:30 overall cutoff. The leave-by times are labeled examples written beside the departure column, because the planner can't store them. The finish is compared with the overall cutoff as an arrive-by, since the finish row has an arrival and no departure. All clocks below are Day 1.

CheckpointMilePlanned time to compareExample official timeRule in this exampleBufferNote
CheckpointOak HollowMile8 miPlanned time to compareleave 7:57 AMExample official timeleave-by 8:45 AMRule in this exampleleave-byBuffer48 minNote
CheckpointMill RoadMile16 miPlanned time to compareleave 9:57 AMExample official timeleave-by 10:45 AMRule in this exampleleave-byBuffer48 minNote
CheckpointHigh MeadowMile27 miPlanned time to compareleave 12:46 PMExample official timeleave-by 1:05 PMRule in this exampleleave-byBuffer19 minNotetightest in this example
CheckpointStone BridgeMile37 miPlanned time to compareleave 3:16 PMExample official timeleave-by 4:00 PMRule in this exampleleave-byBuffer44 minNote
CheckpointWest PondMile44 miPlanned time to compareleave 5:06 PMExample official timeleave-by 5:50 PMRule in this exampleleave-byBuffer44 minNote
CheckpointFinishMile50 miPlanned time to comparearrive 6:30 PMExample official timearrive-by 7:30 PMRule in this examplearrive-byBuffer60 minNoteoverall cutoff

The overall buffer is 60 minutes, but High Meadow's leave-by buffer is 19 minutes, the smallest of the five checkpoints in this example.

If the finish margin is the only number you watch, you're putting all your eggs in one basket case.

How much buffer should you plan?

There isn't one standard buffer for every race. Decide what you want room for, then check the tightest checkpoint against its own official time.

A pacing study of a 100 km race found that runners slowed as the race went on, and slower finishers slowed more. The planner and this worksheet use one constant moving pace, so they don't model that slowdown. A long stop, a slow climb, or night sections are things you might want room for. The example below is a stop that runs long.

To see what happens if that stop runs long and you don't make the time up, keep the moving pace at 14:00 per mile (Pace mode, so the finish can slip) and raise the High Meadow stop from 15 minutes to 30 minutes.

PlanStopsProjected finishFinish clockOverall bufferHigh Meadow departureHigh Meadow leave-by buffer
Plan12:30 planStops50 minProjected finish12:30Finish clock6:30 PMOverall buffer1:00 aheadHigh Meadow departure12:46 PMHigh Meadow leave-by buffer19 min
PlanHigh Meadow stop runs 15 min longStops65 minProjected finish12:45Finish clock6:45 PMOverall buffer45 min aheadHigh Meadow departure1:01 PMHigh Meadow leave-by buffer4 min

Stone Bridge's departure moves from 3:16 PM to 3:31 PM, and West Pond's from 5:06 PM to 5:21 PM, each buffer falling from 44 minutes to 29 minutes. The finish moves from 6:30 PM to 6:45 PM, and the overall buffer falls from 60 minutes to 45 minutes. High Meadow's leave-by buffer falls from 19 minutes to 4 minutes, which is still shorter than that 45-minute overall margin.

Those 19-, 4-, 60- and 45-minute figures belong to this example only. When you change a stop, rebuild the minutes from the jobs at that station with the aid-station stop-time guide, then rerun the card.

How do you use Aid Station Planner with checkpoint cutoffs?

Enter the overall cutoff in the planner. It doesn't store per-checkpoint cutoffs, so write each official leave-by or arrive-by beside the matching departure or arrival on the printed card, and rerun the plan when your stops change.

The optional overall-cutoff field is the one that produces the cutoff-buffer chip: time ahead of the overall limit, time over it, or Not set. The calculation methodology uses cutoff buffer = overall race cutoff - projected finish.

Print the card, or save it as a PDF, from your browser. The planner doesn't save your plan, and the sheet doesn't compare departures to checkpoint cutoffs for you. The finish row shows arrival only, so an overall finish limit is an arrive-by comparison.

The printed card also carries this footnote: "Planning math only. Confirm the current runner guide; checkpoint cutoffs often apply to departure, not arrival."

When you have your official distances, stops, and overall cutoff, open the planner, build the card, and write the checkpoint times beside it. It takes about 60 seconds, and it's free.

More planning guides live on the guides hub, including the 100-mile pace chart.

FAQ

What happens if you miss a cutoff?

Miss a checkpoint cutoff and you're usually out of the race: you can't continue on the course. What happens next depends on the race. Some cut or take your bib, some drive you back, and a finish after the overall limit may not get an official time. Your runner guide has the exact rule.

Do cutoffs apply to arrival or departure?

Some races set checkpoint cutoffs as the time you have to leave the aid station by. Others use the time you have to arrive or pass through by. One race can even use both, so read the wording for each checkpoint. If the runner guide lists only a time, ask the race which one it means. The 100-mile aid-station plan walks through a leave-by check on a worked overnight card.

Can I enter checkpoint cutoffs in the planner?

No. You can enter the overall race cutoff and compare official checkpoint rules with the arrival and departure card. Write each official leave-by or arrive-by beside the matching column on the printed card, and rerun the plan when your stops change.

What's a good cutoff buffer?

There isn't one standard buffer for every race. Decide what you want room for (a long stop, a slow climb, a late slowdown), then check the tightest checkpoint, not only the finish. In this guide's 50-mile example, the overall buffer is 1 hour but High Meadow has only 19 minutes, and a 15-minute longer stop there cuts it to 4 minutes.