Every finish you record belongs to the runner, not to the race.
Every finish you record belongs to the runner, not to the race.
What's included
Runner-owned race record — every finish, split and PR accrues to their own account, across orgs and across years
A race that changes platforms cannot take a runner's history with it, because it was never the race's to hold
Entries with a real date ladder: early-bird, standard, late, each a moment in the RACE's timezone
Waivers recorded by VERSION and timestamp, never a checkbox — so you can show what a February entrant actually accepted
Bib ranges per distance, issued in a transaction: no duplicates, no spilling a marathoner into the half's results
Chip time for records, gun time for placings — kept apart, so a PR table is never inflated by corral position
Timing-partner ingest: live splits and finishes posted as runners cross, published as they land
Peer-to-peer fundraising on the grants engine the platform already runs, not a bolted-on donation form
Volunteer shifts, packet pickup and race-day desk entries on the same workforce and scheduling the org already uses
The race website is a real Builder site on the org's own domain — not a templated page on someone else's
About this module
Registration platforms keep results in a silo per event. Your 2024 marathon lives in that race's account; next year's different race is a different silo, and runners end up keeping their own PRs in a spreadsheet because nobody else will. Races inverts that: every finish accrues to the runner's own Turtini account, across organizations and across years. A race that changes platforms cannot take a runner's history with it, because it was never the race's to hold.
For the organizer it is the whole event: entries on a real date ladder (early-bird, standard, late, each resolved in the race's own timezone), waivers recorded by version and timestamp rather than a checkbox, bib ranges issued per distance inside a transaction so no two runners can wear the same number, and chip and gun time kept apart — chip for records, gun for placings. Timing partners post splits and finishes as runners cross, and results publish as they land.
The rest is machinery the platform already runs. Fundraising uses the grants engine, not a bolted-on donation form. Volunteer shifts and the race-day desk use the same scheduling and workforce the org already has. The race website is a real Builder site on the org's own domain. And because a runner already has an account, entering a race puts it on their calendar without anyone being asked to "add to calendar".
What you can do with it
A 5K series runs eight events a year and every runner's season accrues to their own record
A marathon issues bibs by distance with no duplicates and publishes live results as runners finish
A charity run raises through personal fundraising pages tied to the entry itself
A tri club hands packet pickup and volunteer shifts to the same scheduling it already uses
Get this module
Free for all Turtini organizations.
Who it's for
- Road race, trail and triathlon organizers
- Charity events and the nonprofits behind them
- Clubs and schools running a recurring series
Details
- Category
- Operations
- Pricing
- Free
- Built by
- Badge
- New