GPS — speed bands and external load

When the GPS module is enabled, a GPS tab appears on the Team load page. For each player it shows the latest-session value per speed band, the external (GPS) load against the internal (sRPE) load, and the ACWR. The values come from your GPS export (Catapult, STATSports…): strivn displays what the provider already computed — it does not recompute anything.

Note

The GPS tab only appears when the GPS module is enabled for the team and GPS data has been imported. Reading it requires the view GPS permission.

Your speed bands

A GPS export has no “aerobic” column. It has numbered zones (Zone 1, Zone 2…), often in distance and in time. So you decide how to group them: a band is a name you give to a sum of zones.

For example: Aerobic = Zone 1 + Zone 2 + Zone 3.

Your bands drive everything else — the table columns, the player charts, and the individual targets.

Mapping zones to columns

In the team Settings, the Speed zones and bands section requires the manage GPS permission.

The first block, Columns per zone, maps each zone to its columns: one for Distance, one for Time. Leave empty whatever your export does not provide — a zone with no column appears nowhere.

Tip

Fill in both columns when you have them. That is what makes the Measure selector useful: the same zone then reads in metres or in seconds without redefining anything.

Defining bands

The second block, Bands, lists your bands. For each one: a Band name, and the zones it sums. Add a speed band creates one, Remove takes it away. Finish with Save zones and bands.

Three useful rules:

• One zone can belong to several bands. Nothing stops you having Aerobic = Z1+Z2+Z3 and Total volume = Z1+…+Z6 side by side.
• Renaming a band loses nothing. Its targets and your saved columns follow the new name.
• A removed band is not deleted: it is archived, and its targets are kept in case it comes back.

If you configure nothing, the team starts with four classic bands — Aerobic, High intensity, High-speed running, Sprint — already mapped to the columns strivn recognised in your export.

The squad status

The GPS — squad status table lists the players furthest from their target first. For each player, the latest session’s value per band is coloured against their individual target:

• amber = under the target (under-loaded);
• green = on target;
• red = over the target.

Players with too few sessions carry an Insufficient data badge instead of a misleading number.

A band whose zones are not all mapped in the displayed measure stays empty (—). strivn never adds up part of the zones: an incomplete sum would be a wrong number, not an approximate one.

Choosing columns

The Columns button opens the picker. You choose which columns show and in what order: your bands, the Ext/Int ratio, the ACWR, the number of Sessions, and any additional metric you have added. Your personal choice wins; a head coach can also set the team default.

The three selectors

Above the table, three selectors change what you are looking at.

Selector	Options	Effect
Measure	Distance · Time	Reads your bands in metres or in seconds
Sessions	All · Trainings · Matches	Narrows the sessions taken into account
Period	7 days · 4 weeks · 12 weeks · Season	Narrows the window shown

Measure

Distance and Time show the same bands in the other unit. Each band has a target per measure: you can aim for 4,200 m of aerobic and 15 minutes, independently.

If your zones have no column in the chosen measure, strivn says so and points you at the settings rather than emptying the table without explanation.

Sessions and Period — two different reaches

This is the thing to remember on this page.

Sessions is a comparability filter. A match and a training do not compare: a match’s external load is structurally higher. So this filter changes everything that is computed — the session shown, the values, the suggested target, the ratio and its baseline.

Period is simply a display window. It changes what is listed and charted, and nothing else. The ratio baseline stays on 28 days whichever period you choose.

Caution

These two selectors do not have the same reach, and that is deliberate. Choosing “7 days” does not make a player short of data: strivn counts their real history, not the window shown. Choosing “Matches”, on the other hand, recomputes their target on their matches — otherwise you would be comparing a match against a training average.

A player’s detail

Click a row to open the player’s detail panel without leaving the page. It inherits the table’s measure and filters: you will never see two different populations on the two sides.

Speed bands

The panel plots the value per band session after session. The muted background bars are each session’s internal load (sRPE). A dashed target line marks the band’s target.

The Player zone targets block adjusts the expected dose, in the displayed measure: in Distance you type metres, in Time seconds. Saving touches only that measure — your time target survives a change to the distance target. Reset to team target clears the individual targets and drops the player back to the team default (or the value suggested by their season average).

Additional metrics

If you have promoted export columns into tracking metrics, they appear under Additional metrics: one trend per session, no target (raw value).

Internal / external load

The Internal / external load block overlays two trends on one chart, each on its own scale:

• Internal (sRPE) — the perceived cost: RPE × duration, recomputed even on a GPS-covered session;
• External (GPS) — the mechanical work: the team’s GPS load (formula), or the imported total distance as a fallback.

The headline number is the latest session’s external ÷ internal Ratio, compared to the player’s 28-day base. The ratio has no absolute meaning (the two measures use different units): the only reference is the gap to the player’s own base.

Tip

A ratio that drops well below the base signals decoupling: the player is doing less mechanical work for the same perceived effort — a sign of hidden fatigue. The block header then turns red.

When one side is missing (no RPE logged, or no GPS data) the ratio stays empty (—). While the history is too short, the block shows Not enough data rather than a misleading number.

ACWR and adjustment

Lower down, the panel repeats the player’s weekly ACWR (like the Trends tab), then Adjust planned load lets you scale the player’s load for an upcoming week — without touching the team plan or the call-ups.

Importing by half or by block

A GPS export does not always cover the whole session. Many coaches export one file per half for a match, or one file per drill for a training session.

Once your files are uploaded, the matching screen shows a File scope card above the player matching. One menu per file:

Choice	Effect
Whole session (default)	The file sets the session values directly. This is the historical behaviour.
A sub-element	The file fills in that sub-element only. The session value is rebuilt from the sub-elements.

For a match, the sub-elements offered are the sport’s vocabulary: first half, second half, extra time, added time, warm-up. For a training session, they are the blocks already in the plan, plus New block… which opens a free text field.

Note

If a single file contains several periods (a “Period” column with “Half 1”, “Half 2”…), strivn detects them: the card shows one row per period, each with its own menu.

How the session value is rebuilt

When no file covers the whole session, each player’s session value is computed from their sub-elements, metric by metric, using the mode set for that metric:

Mode	For which kind of metric
Sum	Distances, loads, durations, counts (sprints, accelerations)
Maximum	Top speed, max HR
Minimum	Rarely used
Weighted average (by duration)	Average speed, average HR, per-minute ratios

Caution

A metric with no aggregation mode produces no session value. It stays readable in the Detail by sub-element table, but disappears from the session columns. This is deliberate: adding two top speeds together would produce a wrong number that looks right.

If a file covering the whole session also exists, it takes precedence: the session value comes from it, and sub-element files only add the detail.

Setting the modes

In the team Settings, section GPS metric aggregation (manage GPS permission). One row per metric your team actually imports, with a badge telling you where the effective mode comes from:

• Chosen by you — you set it explicitly.
• Default value — strivn inferred it from the column name.
• No mode — nothing resolved, the metric produces no session value.

Saving triggers a background recompute of the affected sessions.

The other GPS settings

In the team Settings, next to the bands (manage GPS permission):

• GPS metric mapping — map the metrics that are not zones (total distance, top speed, player load) to the right column in your export. strivn auto-detects; correct it here if a column is not recognised.
• Additional metrics to display — tick other export columns (accelerations, player load…) to track them as display columns, without a target.
• GPS metric aggregation — how each metric is recombined when the session is imported by sub-element (see above).

What next?

The GPS tab complements the training load (sRPE) and its Trends tab (ACWR). A load spike is surfaced automatically in signals & alerts.

On each metric tile, the estimated label recalls what the timeline stated, with the gap as a percentage — green under 10 %, amber above. See Exercise metrics.