Race Link Live

Series & race organizers

Run the race from setup to final results.

Race Link Live connects course setup, checkpoint timing, field position, team access, incidents, results and publishing without forcing race control to reconcile separate systems.

Event workflow

Race control keeps course, timing, incidents and results in one operating view.

  1. Preflight

    Configure the course and field.

    Import course geometry, define timing points, assign vehicles, check source health and confirm who can see what.

  2. Start

    Open the event with known sources.

    Verify timing, position and publishing states before race control treats them as current.

  3. Race

    Handle exceptions with context.

    Review field position, checkpoint evidence, penalties, incidents and delivery status without leaving the event timeline.

  4. Finish

    Publish and retain the record.

    Finalize results, preserve timing and media evidence, and give authorized teams and audiences the outputs they need.

Race operations

See the active event, fleet and system health together.

The operating view keeps event controls, source health and recurring race-day work attached to the event instead of scattering them across separate tools.

illustrative example

Current Race Link Live interface. Event names and values are illustrative.

First-event scope

Define the first event before expanding the program.

We agree on the course, field, race-day responsibilities and outputs before the first event.

Scope itemYou provideRace Link Live defines

Course and field

Course file, checkpoint approach, vehicle count, classes and public-access rules.

Course configuration, timing approach, source package and operating boundaries.

Race-day coverage

Decision authority, race-day contacts and the support window required.

Preflight, source-health process, exception workflow, publishing path and support responsibility.

Outputs and sign-off

The results, evidence and viewer outputs that must be delivered after the event.

Retained record, authorized outputs, handoff format and the post-event review.

Discuss a series pilot →

Connected outputs

Race control remains the source of authority.

Teams

Receive the course, event state and authorized race information without operating the event.

Production

Receives timing, position, source health and approved race context for the program.

Fans

See published timing, maps and available race views after the organizer decides what is public.

Bring your course file

Review the event before choosing the deployment.

We will map course length, checkpoint strategy, vehicle count, operating roles, publishing needs and support coverage.

Book a series walkthrough ↗