Skip to main content

Race Roster setup

Do this before or in parallel with RunScore. If the results race already has Live Predictive Tracking (LPT) enabled and segments defined, skip this page.

Each step below is a summary. Use the linked Race Roster article for the exact UI.

Splits must match

The listing Field Header must equal the Race Roster segment name. The event distance must match that segment, including at the mat/decoder. Event names can differ. One mismatch and that checkpoint does not drive tracking.

Steps​

  1. Create a structured results race — result type Structured, with the correct distance. Details: How to Set Up Predictive Tracking For My Event.
  2. Add segments — one per timing checkpoint. Road races: cumulative (start line → split). Duathlon or laps: interval. Each segment is clock time of day or elapsed — RunScore must send that same kind of value. Name, distance, and time type here are what RunScore must match.
  3. Enable Live Predictive Tracking on that results race — gun start, cutoff, pace type (average vs last segment). Same article as step 1.
  4. Upload a course route (GPX or KML) if you want the map. Optional but recommended. Same article as step 1.
  5. Estimated finish time (optional) — a registration question, then a results column. Helps pace from start to the first split. Only if you will also send that column from RunScore. Details: How to Set Up Predictive Tracking Using Estimated Finish Times.

Copy the numeric results race ID. It goes in the listing header as ##id##.

Next: RunScore setup.