Read match-day load
The Load tab on every completed GPS match: the team’s output against its season, each player against their own baseline, and the top-up list for Monday’s session.
The match is the biggest load of any player's week, and the one you didn't design. The Load tab on each completed match shows what the weekend actually asked of the squad, and who it short-changed. Read it before you write Monday's session.
- The tab appears on a completed match that was run through Clubhouse, for a squad with GPS switched on. Families and players never see it.
- There's nothing to enter. GPS data arrives from the club's Catapult connection on its own, so this tab is for reading.
- If a completed match shows No GPS data for this match, the units weren't synced for that fixture or the data hasn't arrived yet.
Open Matches in your sidebar, tap a completed fixture, and choose the Load tab.
Team Load answers "what kind of match was that?" in three numbers, each averaged across the players who wore a unit: Distance / player, HSR / player and m/min. Each is compared with the squad's season average from its other tracked matches. A long, low-intensity away game and a short, frantic derby can look the same on the calendar. They look nothing alike here, and next week's training should reflect the difference.
In the example above, 13 players were tracked against Sandpiper Bay, averaging 5.9 km and 385 m of high-speed running each.
Every tracked player gets a row with Mins, Dist, HSR, HSR/min and Top speed. Where it isn't obvious from the minutes, the row says Did not play, or Also played with the other squad's name for a player who turned out in two grades that weekend.
Two markers compare each player with their own recent matches rather than with the squad:
- HSR down. Their high-speed running was well below their usual for the minutes they played.
- Top speed down. They never got near their usual peak.
Both appear when a player falls under 85% of their own average over recent matches. On a full match, either one is a conversation on Monday: fatigue building up, a knock nobody mentioned, or a role that genuinely asked less. The marker can't tell which. The player can.
Top-up candidates lists everyone who played under 60 tracked minutes, with the high-speed running each one is short of against their own full-match baseline, shown against each name as, for example, 420 m HSR short. That's the work the weekend owed them and didn't deliver: the substitute who got 20 minutes, the starter who came off early.
Left alone, those players arrive at the next match undertrained in exactly the quality that protects them from injury. The list is your evidence for who does extra work early in the week. Players who didn't get on at all aren't on it, because there's no match data to measure them against, so remember the unused substitutes yourself.
This tab is objective data only. How hard players felt their sessions were sits with training, on each session's load card, and the whole week (readiness, the MD−2 top-speed check and the HSR trends) is on the Player Load dashboard. If a player's match ended early through injury, you'll see the short minutes here and the reason in the medical team's records.
- Every completed GPS match has a filled Load tab. A run of No GPS data matches is a sync problem worth chasing with whoever manages the units.
- Every HSR down or Top speed down on a full match got a conversation before the next session.
- The top-up list, plus the unused substitutes, shaped Monday's session.
Last reviewed 24 Sept 2026
Was this page helpful?