GPS sessions
Every session your athletes wear units for shows up here, with the data already crunched. This is where you review what a training or match actually demanded.
Who can use it: admins and coaches.
Browsing sessions
The GPS landing page lists tracked sessions from the last 90 days, newest first.
- Kind filter — All, Matches, Training, Adhoc.
- List ↔ Calendar — switch to a month grid (current month plus the two before) to see sessions in calendar context.
- Each row shows the date, kind, number of participants and duration. Match rows also carry their fixture: the opponent, the competition or fixture name, and a ★ Key game marker for fixtures starred as key on the Season page. A match with no name yet reads Opponent not set. Click a row to open the session in detail.
If a session looks short on participants — a unit that synced late, a player added partway through — use Backfill on the row. It re-pulls your GPS provider for the session window plus a margin and folds in anything new, telling you how many records it re-pulled. Backfill is only available for API-connected vendors (StatSports, PlayerData); summary-only uploads (SPT) can't be re-pulled.
Session detail
Opening a session gives you four layers:
Match details (for matches) — who you played, the competition or fixture name, the scheduled throw-in against what the GPS units actually recorded, any fixture notes, and a ★ marker if it was a key game. The opponent comes from the scheduled fixture when the session is linked to one; for a match that was never put on the schedule, a coach or admin can set the name here with Set opponent (it applies to every player's row in the session). If the session isn't linked to a fixture at all, use Move to… further down the page to attach it to one — that also pulls in the competition and throw-in time.
Headlines — a grid of "who topped what" cards: top speed reached, highest sustained speed (P95), best high-speed-running block, most sprints, repeat-effort bouts, hardest acceleration and deceleration, and more. Each names the leading athlete and their position.
Game-period charts (for matches) — first half versus second half across the key metrics: total and high-speed distance, sprints, distance per minute, repeat-effort bouts, peak speed and mean heart rate. Toggle between absolute values and % of demands (each period relative to the session mean) to see whether output held up or fell away after the break.
Participants table — every athlete with their per-session metrics (high-speed distance, sprints, repeat-effort bouts, heart-rate recovery where monitors were worn), sortable, each name linking to the athlete page.
Use the position filter to narrow the headlines and charts to a unit — for example Middle Third for the midfield block.
You can also download a PDF report of the session from here — see Reports.
Merging & splitting sessions
If one session shows up as two cards — usually a unit that synced late and fell outside the auto-grouping window — tick both on the list and use Merge sessions to fold them into one. On a session drill-down, Split players out pulls mis-attributed players into their own session, and Revert to automatic undoes any manual merge or split so the session groups itself again.
Reading the numbers
The headline metrics — MSS, HSR, sprints, RHIE bouts, HRR60, P95/P99 — are all defined in the Metrics reference. In short: high-speed distance and sprint counts tell you the volume of fast running, repeat-effort bouts and heart-rate recovery tell you about repeat-sprint capacity and fatigue, and the P95–P99 gap hints at session shape (intervals versus steady state).
Related
- Runs explorer — drill into individual sprints across sessions.
- Speed Progress — how speed develops over weeks.
- Data review — fix sessions the importer couldn't place.
- Metrics reference.