Skip to content

GPS and training load monitoring

Every session, measured against the player who ran it.

AthleteIQ Labs turns your GPS units' data into a daily, weekly and season view of training load, built for performance staff. Every number is read against that player's own history on the same day of the microcycle, squad averages leave out anyone who did not train in full, and the week you planned is compared with what the units actually recorded.

Sign in

From the units to the right athlete

A coach syncs the club's GPS account from the platform, and each session arrives with its drill-by-drill periods and the participation tags your staff already add in the units' own software: Full, Part, Rehab and the rest. Every unit is resolved to one athlete record, the same record that holds their force-plate tests, gym logs and daily wellness. A device or a name that cannot be matched with certainty goes to a review queue with suggested candidates. It is never guessed.

Your staff mark which parts of a session were warm-up, main work or compensation top-ups, and the free-text period names typed on the units are matched to your own drill library. Trialists stay visible on attendance views but are kept out of squad averages, so they never shift the team's baseline.

  • Sync from your GPS provider's cloud account
  • Drill-level periods, not only session totals
  • One athlete record across every data source
  • Unmatched devices go to a review queue, never guessed

The daily report: each player against their own best

The daily table shows duration, total distance, high-speed running above 19.8 km/h, sprint distance above 25.2 km/h, sprint and high-speed efforts, accelerations and decelerations for every player. Each cell is coloured by its percentage of that player's own best on previous sessions of the same match-day slot this season: an MD-3 is compared with earlier MD-3s, never with a recovery day and never with the squad average. Top speed is read against the player's career best instead. Two more baselines are one click away: the player's best in a competitive match, or a target your staff set by position and match-day.

The colours run on six bands, from under 25 % to above 105 %. They describe magnitude rather than pass judgement, because 95 % of a match-day best is the plan on one day and a problem on another, and only your staff know which day they planned. Squad and positional averages count only full-participation players; partial and rehab sessions are still shown, they simply do not drag the average down.

The table sorts by any column, prints to a one-page landscape sheet, and goes into a PDF or Word report as a real table rather than a screenshot.

  • Same match-day slot, this season, past sessions only
  • Match best or coach target as alternative baselines
  • Six-band magnitude scale, not traffic lights
  • Full-participation squad averages

The week, the block and the season

The weekly view follows the microcycle from one match to the next: the load wave across the week's sessions, metabolic and mechanical output side by side, and the squad's historical volume by speed zone. The high-intensity acute:chronic workload ratio uses exponentially weighted averages, says when it is still building a baseline, and carries the published caveat about its limits, so it reads as context beside the absolute loads and never as an injury prediction.

The rotation and top-up tracker compares each player's high-intensity week with the benchmark your starters set in the last match, so you can see who needs a top-up before the next game. The season view lists each player's totals beside the sessions they attended out of those available. Compare mode puts any two sets of sessions side by side, whether two microcycles, two phases of the season or two training blocks, and the week your staff built in the training planner is compared with what the units recorded.

The hardest minutes, not the average

Session totals hide the moments that decide a match. From the raw 10 Hz data, the platform finds each player's most demanding 1-, 3-, 5- and 10-minute windows, in every session and every drill. A window never spans two recorded periods, so a half-time or a pause between drills never dilutes a peak. Each peak is read against the player's own match reference, the median of their best match peaks, and then against their position's, and the drill breakdown shows which drill produced it.

The same positional data shows where a session actually happened: the time spent in every 5-metre cell, drawn inside the ground's own outline. When a map cannot be built honestly, the platform withholds it and says why.

Into the match, and out of it

Every fixture has its own report. Before kick-off it shows the week that led into it: how the load tapered towards the match, who had their sprint exposure, and how monotonous the week was against the squad's own season. On match day each player's GPS load and minutes sit beside the positional match demand, built from competitive matches only, so a friendly never lowers the bar. The day after, the same report shows who is still recovering, from each player's jump test against their season best.

Every training day takes its match-day label from the fixture calendar, and your staff can override a single day when the week changes.

Goalkeepers, targets and the pitchside view

Goalkeepers are kept out of outfield averages and get reports of their own: every dive in a session, the weekly dive load, and the balance between dives to the left and to the right. Your staff set targets per metric and match-day, by position, and goalkeepers have targets of their own. During a session the live pitchside view puts every player on a card, refreshing every 15 to 60 seconds, with a running per-drill panel. A weekly squad leaderboard ranks top speed, percentage of personal top speed, high-speed distance and high-intensity efforts.

One load picture per athlete

External load is half the story. Athletes rate each session's effort on their phone, and the rating is multiplied by that session's GPS-measured duration, so internal load needs no minutes typed by hand. The GPS history lives in the same athlete record as wellness, jumps, the gym and medical availability, and it carries across seasons, so a career-best top speed is still the reference years later.

Frequently asked questions

Which GPS units does it work with?

Today the platform connects directly to the cloud account of one of the major GPS providers used in professional football, and reads sessions, drill periods, participation tags, goalkeeper dive events and raw 10 Hz data from it. If your club uses a different system, tell us on the demo call. We would rather tell you what is connected today than promise a connector that does not exist yet.

Do we need 10 Hz data?

Not for the daily, weekly, season and match reports, which use the session and drill totals your units already compute. The worst-case windows and the map of where a session happened need the raw 10 Hz data.

How is a player compared with their own best early in the season?

The baseline comes only from earlier sessions in the same match-day slot this season, and the table says when a slot has no baseline yet. Until it does, the same table can be read against the player's best in a competitive match or against a target your staff set.

Is the ACWR used to predict injuries?

No. The ratio is calculated with exponentially weighted averages, flagged while the baseline is still building, and shown with the published caveat that it is a poor injury predictor on its own. It is context beside the absolute loads, not a risk score.

Who can see the GPS report?

Coaches and analysts work in it. Club administrators get a read-only view of each team. Athletes never see the squad report.

See your own sessions in it

Book a demo. We will walk you through the demo club's GPS report, then show how your GPS account, your drill library and your squad map onto the platform.

Sign in
All features