Chip Time vs Gun Time for a Pace Band
Match your pace band to the correct race clock. Convert a start-line delay into cumulative clock readings and keep cutoff rules separate.
Choose the start that your plan measures from
Chip time, also called net time, usually measures your time from crossing the start timing point to crossing the finish timing point. Gun time measures from a designated race start signal. In a large field you may spend several minutes reaching the start line. A pace band shows elapsed durations; it does not know your personal start-line delay or which wave a roadside clock uses.
For a plan measured from your start-line crossing, compare with a stopwatch you start at that crossing and leave running through stops. Chicago’s official pace-team page says its pacers start their watches at the chip mats. The B.A.A. 10K athlete page likewise describes timing from the start line and identifies net time as that event’s official time. These examples do not determine every other event’s scoring rules.
Add a known delay to read the roadside clock
Imagine a 10K with a 50:00 net target. You cross the start line 3:20 after the start signal used by the course clock. An even plan reaches 5 km after 25:00 of running, when that same clock would read 28:20. The finish would read 53:20 while your net duration is 50:00. The 3:20 is an offset between clock origins; it is not extra moving time you need to recover.
| Point | Band / net elapsed | Clock from the same start signal |
|---|---|---|
| Start line | 0:00:00 | 0:03:20 |
| 5 km | 0:25:00 | 0:28:20 |
| 10 km finish | 0:50:00 | 0:53:20 |
If a clock shows 28:35 at that same 5 km point, subtract the known 3:20 delay to get 25:15 net elapsed, then compare with the 25:00 band target. You are 15 seconds behind that arithmetic reference. Do not compare 28:35 directly with 25:00 and conclude you need to make up three minutes. First verify the clock really uses the start signal assumed in your offset.
Waves and pauses can change the comparison
A clock may show time from an earlier wave, the first race start, your wave, or a separate event. A watch started while waiting in a corral adds a different delay. Read the organizer’s explanation and label your reference before race day. If the relationship is uncertain, your own continuously running elapsed timer at physical course markers is a clearer personal comparison.
Auto-pause can make a watch show moving time while net race time continues through an aid-station stop. A 30-second stationary stop remains part of elapsed race time. If you build a moving-time budget, add the stops when interpreting total finish time. The run-walk calculator reports both quantities, and clearly excludes unspecified stops from intermediate checkpoints.
A target time does not settle awards or cutoffs
Check the current participant guide for the clock used for awards, qualification, intermediate closures and finish-line closing. Those can use different rules, including fixed times of day. Never infer extra time on course just because you start later. A personal arithmetic plan cannot decide an official result, entitlement or race rule.
Keep the band and notes unambiguous
Create the band with your intended net elapsed target and the exact race distance. Keep any known clock offset as a separate clearly labelled reference; adding the delay to the target inside the band maker would slow every displayed split. Check the final line, checkpoint units and print scale. For a run-walk pattern, use its own checkpoint table because an even-pace band has different intermediate times.