Built by someone who still cares about the timing tent.

Why This Exists

Meet and race operations are full of exceptions: unusual formats, inherited files, last-minute corrections, venue internet problems, and customers who need a very specific output at the end of the day. The best software in this space has to be both dependable and flexible.

That is the lane for 2Timer. It is independent, local-first software for track and field, cross country, and road racing, built around flexible control, practical imports and exports, clean screens, and broad compatibility with the tools timers already use.

A Bit Of History

Years ago, I built RaceTab as a desktop meet manager for real scholastic and grassroots meet workflows. Even though it has not been actively updated in a long time, some operators still keep it around because it can handle a wide range of race flows, files, reports, and timing-table edge cases.

2Timer is not a RaceTab port. It is a modern browser app with local data, cleaner architecture, and a more maintainable foundation. But it is intentionally carrying forward the same practical reputation: a meet-operations tool that can adapt to the race you actually have.

Why The Name?

"2Timer" is a little tongue-in-cheek, which feels right for a project that is serious about race day without trying to sound too precious about itself.

First, it treats "timer" as a slightly wrong verb: this is the software race directors and timing crews use to timer. Second, this is my second time building race-management software after RaceTab, so I am a two-time developer in this very specific corner of the world.

And third, I sold MileSplit and no longer work at FloSports, but I still feel a strong connection to what I built there, to FloSports as an important part of my professional life, and to the many friends still doing good work there. So yes, there is a little "two-timing" joke in the name too, but with gratitude rather than distance.

What Makes It Different

2Timer is not trying to become a registration marketplace, payment network, parent app, or federation data platform. Those products can be useful, but they optimize for a different business.

This product is focused on the operator: setup, entries, seeding, timing workflows, field input, reports, publishing, recovery, imports, exports, and the race-day decisions that have to happen quickly and correctly.