Pipeline ›››

How it works

One path from schedule to standings. This slice proves the UI with sample data. Next: persistence, then an admin-only Windows companion so results leave the pit box PC without a manual file hunt.

1. 01

   Stand up a season

   Series → season → classes → roster. Copy last year’s points preset or tune finish, stage, and drop rules.

2. 02

   Publish the schedule

   Rounds with tracks, stage counts, and session status. Next-event signal shows on the overview HUD.

3. 03

   Results land automatically

   Primary path (coming): league owners/admins run a Windows companion on their pit box PC during the race — local iRacing SDK → auto-upload when the session ends. Optional second admin PC supported. Drivers never install it (website only). Fallback: import the saved results file (v1 stub).

4. 04

   Apply race ops

   Penalties adjust points or grid. Liveries go through an approval queue. Race control mirrors the live field and incident list.

5. 05

   Read the championship

   Driver and team standings with multi-class filters, drop toggles, and playoff cutoff markers.