Alpha Progress update: track & field field input has come a long way, with race-day polish now driving the path to beta.

Introducing 2T. I hope you like it!

I’m Jason Byrne. Years ago I founded MileSplit and built RaceTab. While my career has taken me other directions, I'm still passionate about the running industry and the community. And I am still a race director!

2Timer is designed to be the Swiss Army Knife for timing professionals. It is offline-first but cloud-ready, and it now has real track & field depth: seeding, multi-events, field-series input, results, reports, publishing, and FinishLynx exchange are all in place. What remains before beta is less about foundation and more about making a few key operator workflows faster, tighter, and more battle-tested.

Why does independent product matter? Because I'm not trying to convince you to use a specific registration system or turn your data into a product I can sell. I'll gladly integrate with every vendor out there or make it easy to push and pull data from your own website.

Track & field foundation is here

The core pieces are now connected well enough to show what 2Timer is becoming, not just what it might become.

  • Seeding and advancement workspace for rounds, heats, lanes, and flights
  • Multi-events, relays, event-level field input, team scoring, and sessions
  • Results, reports, publishing paths, and FinishLynx exchange/import workflows

Why it still says alpha

Beta means ready to test in a real meet. We are close, but not there yet.

  • Field input is shipped, but keyboard speed and wind-specific flow still need polish
  • Some finals scoring and athlete numbering workflows still need a smoother race-day flow
  • Reports and race-day workflow coverage are improving, but still being hardened

Progress right now

As of April 12, 2026, the roadmap has shifted from big missing foundation work to a much shorter list of in-flight refinements.

Roadmap reviewed 2026-04-12

Recently solidified

  • Track & field seeding and advancement workspace is established
  • Field-event flight input is now available from the Entries workflow
  • Reports, publishing paths, and FinishLynx exchange are working end to end
  • Workflow E2E coverage now includes start-list and saved-template report flows

Main work in flight

  • Wind-reading flow and validation
  • Field-input keyboard polish and operator speed follow-through
  • Finals scoring setup and more consistent athlete numbering across sections

Near-next follow-through

  • Priority report additions like awards and XC team finisher outputs
  • More real operator workflow tests beyond current report coverage
  • Domain migration follow-through where it materially helps future features

What is already in place

The story now is less "someday" and more "here’s what the product can already do." Highlights below — see help docs for depth.

Track & field foundation

Indoor and outdoor meets now have serious coverage: event setup, rounds, seeding, advancement, field-event input, relays, sessions, multi-events, team scoring, and track/field-specific reporting paths.

Track & field overview

Seeding workspace

The T&F seeding workflow is real now: queue-driven event review, per-round rules, preview/apply flow, manual placement editing, and advancement configuration in the same workspace.

Seeding & advancement

Results & publishing

Live results, canned reports, custom reports, and outbound publishing are built in, including local folders, FTP/SFTP, and S3/R2 paths for getting results out of the app.

Results & reports

FinishLynx race-day flow

2Timer can push PPL, SCH, and EVT files out to FinishLynx and pull LIF/LFF results back in, including track and field workflows that depend on the exchange folder.

FinishLynx for T&F

AI assistant

You can ask questions — but the real value is that it can do things for you: complicated, multi-step meet work that would have taken a long time to do manually. Describe what you want, get concrete proposed changes back, then review and approve before anything is applied. The first meet management system to ship with an assistant like this built in — not a side chat, but wired to the app’s meet tools and review flow.

How the assistant works

Offline-first, installable

Use the meet on shaky venue Wi‑Fi. Install as a PWA, keep working when the connection drops, sync when you’re back.

PWA & offline

Connectors & imports

Work with registration flows, timing hardware, and file formats timers already use — RunSignUp, Feibot, FinishLynx, RFID, HY-TEK‑style data, and more paths over time.

What this foundation opens up next

The roadmap is not just about polishing what exists. This same architecture gives 2Timer room to grow into nearby workflows that fit timers well.

Adjacent "cousin" sports

I’m actively thinking about sports that fit the same timing model without forcing a full rebuild. The strongest candidates right now are multisport, snowshoe racing, and some cycling formats that still map cleanly to events, markers, reads, splits, and results.

A wider variety of multis

The current multi-event work is a base, not the ceiling. There is room to grow into more masters, youth, and governing-body-specific combined-event formats instead of stopping at the standard presets.

Age grading

Age grading is also on the horizon, especially where there are strong standards behind it: road running first, then track & field once the event-mapping layer is fully nailed down.

Contact if something’s confusing or broken.