Skip to content

What is a public event

A public event in Racecraft is a single track with a shared reference run and a public leaderboard. It's the right tool when you want every rider's time on the same track, in one place, visible to the world.

The pieces of an event

Every public event has:

  • a title (what the event is called)
  • a start time and end time (the window the event runs for)
  • a reference run that defines the track — where it starts, where it ends, and the splits everyone is measured against
  • a WhatsApp group invite link so riders can find each other and ask questions during the event
  • a public web page at a unique URL, with a QR code you can share on posters, social, and signage

When the event is published, anyone with the link or QR code can see the leaderboard and the reference run. When it's unpublished, the event is hidden.

What riders see

A rider lands on the event's page from a QR scan or a shared link. They see:

  • the event's title, dates, and location
  • the reference run, which they can watch
  • the live leaderboard
  • a path into the app to upload their own run onto the leaderboard

A rider with the app already installed jumps straight into the upload flow. A rider without the app is prompted to install it; their run will join the leaderboard once they upload.

What spectators see

Spectators don't need the app. They see the same event page in a browser — title, reference run, live leaderboard — and don't need an account. The page updates as new runs come in.

How an event is different from a team session

A team session and a public event both centre on a single track and a single reference run. The differences:

  • a team session is private to the team's members; a public event is on the open web
  • a team session is for internal coaching and analysis; a public event is for race-day visibility
  • a team session tags runs with the rider's identity within the team; a public event tags runs with the rider's name as it should appear publicly

A program that wants both — internal coaching across the season and a public race day at the end — uses both: team sessions through the season, a public event for the race.

The current scope

Public events today are admin-set-up. You request an event, we configure it, and you get a link and QR code to share. We're working toward operator-managed events; for now this guide reflects how it actually works.

If you want detail on individual moving parts: