Build the course on a timeline, then wire it to your hardware.
The course is the backbone of every result. You lay out timing points on a visual timeline, then tell each one how to behave - which readers feed it, in what priority, which points it depends on, and the rules that turn raw reads into clean splits. Multi-stage events like triathlon and duathlon are first-class, not a workaround.
1 · Lay out the timeline
Drop start, splits, laps and finish onto a visual timeline. Drag to reorder, set distances, and see the whole course at a glance before a single read arrives.
2 · Wire each point
Assign the hardware that feeds a point, set reader priorities for when several see the same chip, add dependencies, and choose the timing rules that decide which read counts.
3 · Add stages
Triathlon, duathlon, swim-run - chain stages together with their own distances and transitions, and the engine scores each leg and the overall in one pass.
Every checkpoint has its own public face.
Open any timing point and set how it appears to the world - a public title and short code, its distance, and how times are rounded. The internal plumbing stays internal; participants only ever see the clean, named checkpoint.
.png)
