Built for timing, scoring & event admin
Race day, handled.
The software your timing & scoring team and event admin use to run race day — with race formats you define, scoring you control, and public pages your racers can share.
The software your timing & scoring team and event admin use to run race day — with race formats you define, scoring you control, and public pages your racers can share.
EventDay is the workflow between registration and timing. Pull entries in. Build heats and finals the way your rulebook actually works. Score them as the day unfolds. Push results, lineups, and season points to public pages your racers can find on their phones.
It doesn't replace your registration platform or your timing system. It connects to them and gives your timing-and-scoring team and event admin staff the operational layer that booths usually patch together with spreadsheets, group texts, and a printer that's always out of toner.
Six pieces that work together. Configure once, use every weekend.
Define your own classes, heat structures, LCQs, and finals. Configure point tables per class. Triple-Crown overall scoring. Drop-rounds. Whatever your rulebook calls for — you build it once, it runs every race.
Pull from CSV exports, Orbits files, or auto-sync with SpeedRegPro. Maintain a season-long member roster. Bib conflicts caught on import. Class names mapped once and remembered.
Score-a-race UI built for the booth, not for a database admin. Heat results flow into LCQ qualifiers and main lineups automatically. Recompute standings with one click after a protest reverses a finish.
Multi-event championships with configurable point structures. Tiebreakers handled. Triple-Crown rounds tracked separately. Drop-round logic if your series uses it.
Branded pages your racers can pull up on their phones during the weekend. Lineups by class. Results by round. Season points table. One link, always current.
Fullscreen big-screen view designed for the announcer's monitor. Pin a class. Walk through finishes one rider at a time. Shareable URL the production crew can put up on their feed.
Setup is a one-time investment. After that, race day is a series of clicks.
Set up your series, classes, point tables, and heat structure. Once. The setup tracks your sanctioning body's rulebook however you read it.
Pull entries from your registration platform — auto-sync from SpeedRegPro or upload a CSV/Orbits export. Roster matched, bib conflicts surfaced.
Build heats, run qualifying, fill LCQs, set finals. Score each race as it ends. Print or PDF heat sheets and results to whatever your timing crew needs.
Public lineups, results, and season standings live on your domain. Announcer page goes to the booth. Done — on to the next weekend.
EventDay is the operational layer between systems you already trust. We don't replace what works.
Auto-sync entries every minute. Map remote class names once and EventDay remembers. Manual import-once is also available if you'd rather hold the trigger.
Visit speedregpro.com →Drop the .txt export from MyLaps Orbits or a similar transponder system. EventDay parses entries and feeds them straight into your event roster.
If your registration system can produce a CSV with name, class, and bib number, EventDay can import it. No proprietary format required.
Things people ask before they decide to look at this seriously.
Anything with classes, heats, and a season points championship. The race-format engine is configurable, so it doesn't assume a particular sanctioning body or rulebook. If you've got rounds, classes, and qualifying-into-mains, it'll work — sleds, karts, motocross, dirt-track-style series, all the same shape underneath.
No, and we wouldn't want it to. Registration platforms handle waivers, payments, and rider profiles. Timing systems handle transponders. EventDay handles the part in the middle — entries become heats, heats become results, results become season points. Plug it into whatever you're already using.
Self-hosted on Fly.io with persistent SQLite. One small VM. We can deploy it for you or hand you the deploy and walk you through it. Your data, your domain, your control. We don't run a multi-tenant cloud you have to trust with your roster.
Yes. The database is plain SQLite. Pull a copy any time. CSV exports for entries and results are part of the printout system. Nothing about your data is locked in.
Class definitions, heat counts, qualifying structure, LCQ logic, final size, point tables, drop-rounds, Triple-Crown overall scoring — all configurable per series and per season. If your rulebook says it, we can usually make it run. If it can't, we'll build it.
We're in early access. Talk to us about your series — how many events, how many racers, what you're using today — and we'll work out something that makes sense. Send us a note.
Fifteen-minute walkthrough. Tell us about your series — how many events, how big the entry list, what your booth uses today — and we'll show you the parts that matter.