Skip to main content

Finish area and scoring events

Race organization is how you structure the physical finish area and translate it into RunScore's data model. Regardless of setup, RunScore uses the same underlying model: each physical timing point maps to a scoring event in your race's Events.xml file.

For a step-by-step list of what to do before and on race day, see the Race-day checklist.

Chip timing​

Chip timing is the standard for road races. Each runner wears a chip — on a shoe or bib — that transmits an ID when the runner crosses a timing mat.

Bird's-eye view of a chip timing finish showing runners crossing a timing mat at the finish line with no chute or fencing required, an antenna/decoder at the mat edge, and a cable running to the computer

The timing mat and decoder capture each runner's chip ID and crossing time, then send the data directly to RunScore.

Setting up chip timing in RunScore​

  1. Define a finish-type event for each timing mat in Events.xml using Misc. → Edit list of Events.
  2. In the External Timer initialization, set each timer slot's Event field to the matching event name from the dropdown.
  3. The chip system sends bib-and-time pairs directly — no manual data entry is needed.

For full device setup, see the Chip/Bib Timing section.

Always have backup timing for the leaders

Place a second timing mat about 15 m behind the finish to catch missed chip reads. An assistant should also record the first few finishers (or award-relevant bibs): bib, sex, and time from the official clock. Use the backup mat to patch missed reads on the primary Finish event — do not merge the two mats with Combine Events.

Sample race reference​

The 5K sample race (C:\RunScore\SampleRaces\5k) is a typical chip-timed setup. Its Events.xml defines four events:

EventTypePurpose
GunStartstartGun-time start
ChipStartstartChip-mat start
AnnouncerdefaultAnnouncer feed
FinishfinishFinish line

Announcer uses the default type because it is not a start, split, or finish event. It is an auxiliary feed, not an input to your overall results — do not run Combine Events on this race, or its times would override the Finish times.

Finish lines and chutes​

Most chip-timed races use a single finish line, which maps to one finish event. Some races still need physical lines or a chute:

  • One scoring event per physical finish line. A single finish line is one event; a race with two lines is two events.
  • Cross-country, overflow, and men/women splits either funnel runners past one line or use separate lines. When lines are separate, each line is its own event.
  • Use Combine Events only when the lines are parallel finishes — that is, each runner crosses exactly one line. Never combine the primary finish mat with the backup mat.

Cross-country individual and team scoring is handled by the Team Score CC command, not by finish-area setup.

Setting up multiple finish lines​

  1. Define each finish line as a separate event in Events.xml using Misc. → Edit list of Events. For example: MEN and WOMEN, each with type finish.

  2. Assign each timing mat to its event. In the External Timer initialization, set each slot's Event field to the matching event name.

  3. Merge results in your listing file using the Combine Events command. Combine Events merges all non-select, non-start events that have a finish order and automatically sorts by time. You can add an explicit Sort command afterward as a defensive measure:

    Combine Events
    Sort

  4. Before publishing, patch any missed reads from the backup mat and check the leader and award bibs against the assistant's notes.

How RunScore models it​

Regardless of physical layout, every timing point maps to a scoring event in Events.xml. A backup mat is its own event used to patch misses — it is not merged with the finish. The leader check is a manual procedure, not an event.

Key concepts:

  • Event — a named container for timing data (also called a "scoring event" to distinguish it from a calendar event). Each event stores bib numbers and their associated times. Defined in Events.xml with a type: default, start, split, or finish. Most finish-line events use finish; leave an event as default when it does not need start/split/finish semantics. Note that a default event with a finish order is still pulled into Combine Events, so keep auxiliary events (checkpoints, announcer feeds) out of any listing that combines events.
  • Lane — the position an external timer or chip system routes data to, counted 1-based over the event list. Only select events are skipped; start and finish events both consume a lane. So for the 5K order above, ChipStart is lane 1 and Finish is lane 2.
  • Combine Events — a listing command that merges all non-select, non-start events that have a finish order, keeping the first time recorded for each bib. Use it only to merge parallel finish lines, where each runner appears on exactly one line. Do not use it on a race whose default events share bibs with the finish.

To define or edit your events, go to Misc. → Edit list of Events. For a full walkthrough of event configuration, see Race Configuration.

Related commands

These command pages cover scoring for specific race types: