Three file shapes work.

  • An Orbits results export carries one row per rider, with the approved order, explicit outcomes, and available times.
  • A Speedhive 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 passing log collapses to each rider best lap. A race passing log also needs lap counts, elapsed times, and a finish marker, and produces a finishing order.

Read imported results

An approved results import uses the supplied order, outcomes, and available times. Class results do not establish an overall road order. For repeated numbers in one source class, Race Control matches a unique registered motorcycle when possible. Unresolved motorcycle conflicts are held for review.

Source rows without a matching registration stay as imported results and do not create eligibility. It does not recalculate the order from lap counts. A last-lap time does not supply a best lap or total time. Qualifying results need a best lap to supply a qualifying time. An omitted rider is not treated as DNS.

A qualifying export can repeat a timed competitor as an extra row with no time or laps. Race Control ignores that extra row when its number, name and class exactly match one timed row. It keeps the original CSV and all other competitors with no time. Other duplicate rows still need corrected results.

A qualifying row without a usable best lap raises no timing alert, even if its rider is unknown or its registration differs. The source row stays available. A corrected upload with a best lap can raise an alert for staff to review. Race finishes, DNF and disqualifications can need review without any lap times. A missing best lap alone does not make a race result unusable.

The Bridge also ignores practice rows without a usable best lap for timing review. These empty rows cannot block a separate timed row for the same rider. Two positively identified registered bikes can keep separate practice timing rows for one rider. Qualifying and race motorcycle restrictions still apply.

A DNS row for an unknown rider or a rider outside that class raises no alert without laps, times or a finishing position. Race Control keeps that imported row without adding registration or participation. A registered rider's valid DNS remains in the applied results. DNS rows with laps, times or a finishing position can still raise identity or participation alerts. An identity conflict or a stale timing decision still needs review.

Orbits can list an unidentified transponder with number -??-, a name such as - 7241736 -, and no class. Race Control checks current event registration records to identify the rider. A unique transponder, number or name can match when the registration records agree. Historical transponder ownership alone supplies a suggestion. Other riders' results can still be imported while uncertain rows wait for review.

A practice product's number applies to its reviewed session. A Friday practice number does not become a Saturday qualifying or racing number for that rider.

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.

Different riders can share a transponder in separate reviewed runs. Race Control uses the current run's registration assignments to identify its rider. An old organization transponder link does not replace those registration assignments. Claims from different riders in one run, or claims without a known run, need review.