Race-Day Timing

5KClock keeps split capture fast, readable, and local-first.

Built for coaches who need a dependable race clock, live split capture, workout timing, saved sessions, and optional Copley Running sync without dragging a laptop onto the course.

3 clocks 5K, 2 Mile, and Meters timing modes for race-day capture.
Local-first Sessions, CSV exports, and recordings stay on the device by default.
Coach-ready Hardware controls, athlete assignment, and workflow built around course use.
5KClock live race clock home screen

Live Race Clock

Start the clock at the gun and keep the operator view large enough to use under pressure.

5KClock one-mile split entry and projection

1 Mile Splits

Capture one-mile splits quickly and convert them into projections and assigned athletes.

5KClock two-mile split projection

2 Mile Updates

Track later-race position with updated projections, tap history, and order counts.

Documentation Hub

The public docs are now organized as part of the site and rewritten from the imported files so they follow the site chrome and only publish safe, user-facing documentation.

Race Clocks

5K, 2 Mile, and Meters timing, split capture, projections, tap history, and hardware controls.

Open Race Clocks

Workout Clocks

Interval workout groups, athlete assignments, host/follow sync, and live segment displays.

Open Workout Clocks

Video & Voice

Camera, microphone, voice notes, video overlays, and how recordings are attached to sessions.

Open Video & Voice

Athletes & Sessions

Roster imports, meets, saved CSV sessions, recording files, and session recall after the race.

Open Athletes & Sessions

Settings & Sync

Save location, multi-device roles, lock screen behavior, and optional Copley Running sync.

Open Settings & Sync

Privacy & Security

Local-first storage, device permissions, keychain usage, encryption notes, and logging guidance.

Open Privacy & Security

Security posture

The imported ZIP was rebuilt as server-rendered pages instead of shipping its raw HTML directly. The public documentation excludes the workout API contract so bearer-token flow and endpoint details are not exposed on the public site.