timingThe lap and finishing data for a session. Race Control reads timing from a file you upload or from a linked live provider. is what orders a grid. It reaches a session two ways, and both end in the same place.

Upload a file

Open Event → Schedule and upload the file against its session. Race Control reads the file name for a session code such as Q6 and proposes the matching session, and you confirm or change it. If two runs have the same code and name, use the scheduled start time in the target list to choose the right one. Two qualifying runs with that same code and name are a normal schedule when they have different start times. The Schedule shows no Duplicate warning for that case, but the file name alone still cannot choose between them.

Two file shapes work.

  • A classification export carries one row per rider. Each row holds a position, a number, a name, a class, and a best lap.
  • A raw passing log carries one row per crossing. Each row holds a lap number, a lap time, an elapsed time, and a transponder.

A practice or qualifying log collapses to each rider best lap. A race log also needs lap counts, elapsed times, and a finish marker, and produces a finishing order.

When you upload the same session again, the new file replaces what is there. There is no merge and no duplicate, so a corrected export is a straight re-upload.

Race Control accepts total times with missing leading zeros, such as 10:0.072, and displays them as 10:00.072. An invalid total time stops the import and leaves the previous timing intact. Correct the reported row, then upload the file again.

An organization can link one Speedhive live event to a Race Control event. Timing then arrives on its own while sessions run.

Live timing is explicit and never automatic across your whole club. You link one event at a time, and you can see and replay what it read. Speedhive covers the link and its limits.

What timing does not do

This is the single most useful thing to know about timing, and it surprises people.

Timing never creates a rider, a class, or an entry. It never grants anyone eligibility for a race. A rider who appears in a passing log but is not registered stays outside the event until you register them.

Timing does not say which class a rider races. A qualifying session that feeds five classes stores the same generic class on every row. Registration data answers this, which is why importing registrations comes first.

Note

A 0.000 lap time in an export means no time, not an instant lap. Race Control stores it as no time and leaves the space blank on a printed grid. A rider with no time still appears on the grid, ordered by the next criterion.

How a rider gets matched

A raw passing log compares its transponder, number, and name with your event roster. When those sources agree, it matches the rider. Identity conflicts wait for your decision.

One rider can hold several transponders, because one rider can race several bikes under one race number. A matched transponder is a claim with a record behind it, and it never merges two riders on its own.

Check what landed

Open the session and read its stored classification back. Position, number, rider, and best lap are all there, and that is exactly what the grid engine will use.

After you close the import results, View is unavailable while the Schedule refreshes. When it becomes available, open it to check the imported rows.

Resolve a timing identity conflict

Open the session's View action. Under Review timing identity, compare the CSV number, name, and transponder with the listed registered riders. Use Find another rider to search by name or number when the suggestions do not include the right person. Select who made the crossings, enter a Reason, then select Save timing decision. If you cannot assign them, select Exclude these crossings and explain why.

Until you decide, these crossings supply no qualifying lap or event number. Grids that require this session show Needs review and cannot be generated or published. Grids that use other sessions can continue.

The decision applies to the same claim in this session and survives a re-upload. It rebuilds timing from the retained original CSV and leaves registration names and transponder records intact. Check the affected grids and publish any revised grids through the normal review flow.

For an older import, select Recheck original file to check its retained CSV again. If that import had already assigned someone the wrong event number, open Entries and review the number difference there; choose the registration number for that rider. The timing decision does not remove a previously stored number choice.

For race results, every timing identity conflict must be assigned or excluded before the classification is shown. A disputed crossing can change the finish order or whether someone started. Qualifying keeps the uncontested laps while you review the remaining crossings.