Reviewing an athlete¶

Once a team has a shared track session with a confirmed reference run, reviewing an athlete is straightforward. This page covers how to find their runs, how to read what you're seeing, and how to give feedback that lands.

Finding an athlete's runs¶

In a team's session, every run is tagged with the athlete name of the rider in the video. The leaderboard groups runs by athlete; the session's run list shows each run with the athlete's name on it.

If you uploaded a run on the athlete's behalf and didn't tag the athlete, the run will show under your name instead. Re-tag the run to fix it — the leaderboard updates immediately.

Comparing athletes against the reference¶

Open any run to see:

its splits and per-section deltas relative to the reference
the continuous time-delta curve through the run
where exactly it lost or gained time

This is the same comparison view a solo rider would see — see Reading the comparison for how to read it. The team context just means you're looking at multiple athletes' runs all measured against the same reference.

Comparing one athlete against another¶

The leaderboard ranks every run in the session against the reference, so two athletes' runs sit side by side at their respective ranks. To compare two specific runs directly:

open one run's comparison view
the per-split deltas tell you where the time changed hands

Because every run is anchored to the same reference, "athlete A is 0.4s up at split 2 and athlete B is 0.1s down at split 2" is the same thing as "athlete A is 0.5s ahead of athlete B at split 2." The reference acts as a common ruler.

Giving feedback that uses the data¶

The most useful coaching pattern we see:

Find a section where the athlete's continuous delta climbs sharply — they lost time fast in a small region.
Watch that region on their run alongside the reference at the same point.
Identify what was different — line, body position, braking, gearing.
Set a target: "next session, hold the reference's line through that section and we'll see if the delta flattens."

This works because the data narrows down where before you have to explain why. Without splits and continuous delta, it's easy to spend the whole review watching the wrong part of the run.

When the comparison looks wrong¶

Two common causes when an athlete's comparison doesn't make sense:

the athlete's run was tagged with the wrong name — fix the athlete tag and the leaderboard updates
the predicted splits on the athlete's run drifted — the reference splits weren't anchored on distinctive enough frames. Move the reference splits to clearer frames and re-confirm; the athlete's run will be re-predicted

If neither is the issue, see the Rider FAQ for more diagnosis or contact support.