Race Operations
Race Builder And Class Rules
Build motos, heats, LCQs, and mains from real entries.

The Race Order Problem
Race order looks simple until classes start changing, riders enter multiple classes, and the gate count no longer fits the plan.
MX days need motos. AX and SX events may need heats, LCQs, mains, transfer rules, and tighter show timing. Paper and spreadsheets can fall apart fast.
What FlaggerAI Does
FlaggerAI helps build race order from entries while keeping classes, rider counts, gate size, grouped scoring, and results in the same race-day system.
Staff can preview the build before saving it, which helps catch problems before riders are staged.
MX Mode
For motocross, the race builder can organize Moto 1, Moto 2, and Moto 3 style event flow. Classes can be grouped while keeping scoring separate where needed.
AX/SX Mode
For arenacross and supercross-style events, the system can support heats, LCQ, and main formats. Promoters can review class groups, heat counts, transfer rules, and warnings before the race order is final.
What Promoters Get
Promoters get a cleaner way to build the show and reduce last-minute chaos. Riders get clearer race order. Staff get fewer surprises at the gate.
That is the real win: less guessing once the night is moving.
Best For
- local MX race days
- arenacross events
- supercross-style formats
- promoters with changing class counts
- tracks that want timing, results, and scoreboards tied to the race order
FAQ
Is this only for race days?
No. Race builder is most important on race day, but the same data can support entries, check-in, scoreboards, results, and post-event review.
App views and hardware
See the screens and race-day gear


Want to see it on your track?
