A timing session is the unit of timing work for race day. One session covers one timing setup — typically one race, or for brackets, all rounds of one bracket.Documentation Index
Fetch the complete documentation index at: https://docs.time2.bike/llms.txt
Use this file to discover all available pages before exploring further.
Hierarchy
raceIds. Operators record finishes scoped to a specific race (via the race tab at the top of the operator screen), so the same session timer can serve multiple categories that race together.
Why multiple races in one session
In practice many disciplines run multiple categories on one clock:- A criterium where Cat 1/2/3 start together.
- An XC race with three category waves but the same finish line.
- A dual-slalom bracket whose “races” are seeding + bracket rounds.
Session types
standard— one operator, plate-input or tap-to-finish driven. 95% of races.dualSlalom— multi-device, lane-driven. See Dual slalom.
Session lifecycle
- idle — created, nothing recorded yet.
- running — the clock is alive; operators are recording.
- paused — see pauseSemantics below.
- stopped — the clock is stopped but the session is still editable.
- finalized — locked. No more events accepted.
- published — visible on the public results page.

Pause semantics
Set per session at creation:- frozenClock — pause stops elapsed time for everyone. Best for slalom and “we have a course hold” pauses.
- softPause — wall clock keeps going; pause just hides controls. Best for “I’m pausing because the volunteer is on a snack break”.