How Ford Timing cut duplicate data entry and simplified race day with Movemint
Ford Timing
Timing partner · Northern California
A three-person timing company running more than 50 events a year across Northern California, with results syncing automatically instead of being carried between systems by hand.
- Race Result integration
- Bib and wave assignment
- race-day setup, down from 30
- 5–10 min
- events timed a year
- 50+
- Partner
- Ford Timing
- Discipline
- Race timing
- Region
- Northern California
Thirty minutes to set up, and a CSV in the middle of it
Ford Timing has spent more than 15 years timing races across Northern California, and with 50+ events a year run by a three person team, every minute on site counts. Aaron Ford and his team typically allow 30 minutes of setup before check-in opens, and in that window they have to set up computers, get the internet running, and train volunteers who in some cases have never used an event platform before. On top of that sat the manual work of moving results between systems, downloading and re-uploading CSVs by hand. That step was not just slow — any participant who registered after a CSV had been downloaded simply would not appear in it, leaving results incomplete until someone caught the mismatch.
The sync, and the bibs that assign themselves
Movemint syncs data automatically between the timing system and results, so the team no longer duplicates entry and late registrants are never left out. Results reach participants faster and with fewer chances for error, and Ford Timing can run races remotely rather than being on site for every part of the process. Bib and wave assignment saw a similar shift. At the Impala Stampede in San Francisco’s Golden Gate Park, the organizer had planned manual bib assignment with a multi-day packet pickup, printing and handing out labels in batches. Ford Timing and Movemint pushed for dynamic bib assignment instead, and once the client saw it in action, Aaron says they never wanted to go back. Even with volunteers seeing the interface for the first time, setup dropped from 30 minutes to 5–10.
A year and a half, and the events to show for it
Over a year and a half of partnership, Ford Timing has used Movemint across events including the Impala Stampede and the Renegade 5000 in LA and Oakland. The integration has saved the team time on race day while cutting errors from manual entry, and Aaron points to Movemint’s responsiveness as a reason the partnership has stuck: when he built his own workaround for a missing feature at a past Renegade race, the engineering team had an implementation in place within days.
It’s a game changer. I don’t have to reinvent the wheel with duplicate data entry anymore.
There was a feature on Movemint that I needed at a past event, and it was only a couple days later that Zack had a new implementation in place. One of the selling points on using Movemint is that I never feel alone. Not only are they there to answer support questions, they’re also willing to hear my feedback.
