Checkpoint and cutoff planning
Turn official checkpoint distances and elapsed-time cutoffs into arrival estimates, stop-adjusted buffers, and an ink-friendly pace band.
Enter official checkpoint distances and elapsed-time cutoffs from the current race guide.
Printable checkpoint plan
Constant moving pace: 9.0 min/km
100.0 km
Across entered checkpoints
All checkpoint stops combined
Under this arithmetic scenario
| Checkpoint | Distance | Planned arrival | Departure | Official cutoff | Buffer | Latest segment pace |
|---|---|---|---|---|---|---|
| Aid 1 | 25.0 km | 09:45 | 09:50 | 10:30 | +45m | 10:48/km |
| Aid 2 | 50.0 km | 13:35 | 13:45 | 15:00 | +1h 25m | 10:36/km |
| Finish | 100.0 km | 21:15 | 21:15 | Day 2 · 00:00 | +2h 45m | 10:36/km |
“Latest segment pace” assumes arrival at the preceding cutoff and includes that checkpoint's planned stop before the next segment. Real terrain and conditions are not modeled. Verify every cutoff against the current official race guide.
Copy checkpoint distances and cutoff times from the current organizer guide. Do not reuse last year's spreadsheet without checking for course and schedule changes. Enter every cutoff as elapsed time from the start. This model compares arrivals: if the race requires departure by the cutoff, first subtract your planned stop from that deadline to obtain the arrival deadline.
The planner applies one moving pace across the course, then adds each stop to later arrivals. That makes the arithmetic transparent, but not terrain-aware. Compare several conservative scenarios and use the aid-station strategy guide to define what actually needs to happen at each stop. For a wristband with a mark every few kilometres or miles and a planned fade, use the pace band generator.
It is the time between a calculated arrival and the entered arrival deadline. If the official cutoff is a departure deadline, subtract your planned stop from that deadline before entering it; otherwise the displayed buffer overstates usable time. A positive buffer is not a guarantee: climbs, weather, navigation, queues and physical problems can consume it.
Enter elapsed hours from the race start. The planner combines those values with the start clock to display local cutoff times, including later days.
A stop is added after arrival at its checkpoint and therefore delays every later arrival. The finish stop has no effect unless another checkpoint follows it.
No. It uses a constant moving pace. Build conservative scenarios from course-specific training and use official route information rather than treating the output as a prediction.