Matchweek Load
GPS & session output · 13‑week season block
ⓘ
Connecting…
Upload your data
This saves straight to your club’s database — nobody at another club can see it. Upload any combination of GPS/Wellness/Strength testing/Testing below — none of them is required on its own. GPS and Strength testing are your provider’s own raw export files, auto-detected; Wellness and Testing use the templates below. Every one of them shows a review screen first — rows already saved for that player/date are flagged and unchecked by default, and nothing commits until you confirm.
GPS sessions optional
Your GPS provider’s own export file, as-is — format auto-detected. Two common export formats are supported so far, with more added as needed.
or drag & drop a .csv file here
Wellness optional
or drag & drop a .csv file here
Strength testing (isometric) optional
An isometric strength-testing repetitions export, as-is — hip, knee, etc., not the jump/sprint Testing field alongside it. Reps are reduced to the single best (highest peak force) rep per player/date/test/side, and left/right are paired up to calculate limb symmetry.
or drag & drop a .csv file here
Testing optional
Jump/sprint testing (CMJ height, 10m/30m sprint, RSI) — log as many sessions as you like under any label (Baseline, Retest, a date, whatever suits), not just a fixed pair; each new one is compared against the player's previous test. A separate data type from the isometric strength testing alongside it (that's isometric strength; this is jump/sprint power and speed) — just a different battery and still its own template.
or drag & drop a .csv file here
sRPE (session load) optional
Session RPE × minutes — whole-session training load. A row for a player/date/session type that already has a GPS session logged updates that row's sRPE; a row with no matching session (e.g. gym, pool) creates a new one if minutes is included.
or drag & drop a .csv file here
Column guide
Review GPS import
| Incl. | Original name | Matched player | Date | Type | Min | Dist (m) | HSR (m) | Sprint (m) | Sprints | Top spd | Load 3D | Load 2D | Flags |
|---|
Review strength testing import
| Incl. | Original name | Matched player | Date | Test | Side | Peak force (N) | Peak force/kg | Max RFD | Reps seen | Flags |
|---|
Review wellness import
Check each question's direction in this file — this app always stores 5 = best/freshest. If your questionnaire scores the other way for any of these, switch it below; the preview table updates to show the transformed values that will actually be saved.
| Incl. | Player | Date | Sleep | Soreness | Fatigue | Mood/stress | Readiness | Flags |
|---|
Review testing import
| Incl. | Player | Date | Phase | CMJ height | Sprint 10m | Sprint 30m | RSI | RSI method | Flags |
|---|
Review sRPE import
| Incl. | Player | Date | Session type | Minutes | sRPE | Action |
|---|
Players to review this weekThis session
Ranked by what’s most likely to affect training or selection decisionsTotal distance — selected sessionThis session
Squad
Flagged this week
Squad average
High-speed running & sprint distanceThis session
HSR distance (>19.8 km/h)
Sprint distance (>25.2 km/h)
Weekly high-speed output — squad medianFull season
HSR, m/min
Sprint, m/min
Output by position group — selected sessionThis session
Avg HSR distance
Avg sprint distance
Training Considerations This Week
GPS, wellness, testing and data-quality signals together, including the lower-priority items Squad Overview only counts — a starting point for planning, not a prescriptionNothing stands out this week — no notable exposure, load, wellness, testing or availability signals across the active squad.
Weekly Speed Exposure
Training volume and maximum-speed exposureTraining HSR vs own match benchmark · training sessions only
Top speed touched this week vs own season best
Training, match, weekly total and top-up HSR for every eligible player, with the figures behind each percentage. Sprint distance sits inside HSR.
Weekly planning
Pick a day in the microcycle to bring the most relevant considerations to the top — nothing is hidden, only reordered
Category
Considerations
Weekly schedule
Which calendar day each match-day label falls on for your squad — used only to label the planning-day picker (e.g. “MD‑3 · Wed”). This never changes how a session is classified — that always comes directly from the sessionType column in your data — and no single layout is assumed: edit any day, or leave a day blank if your week doesn't use it. Saved to your club's record — every login at this club sees the same schedule.
Cross-domain read
GPS, wellness and testing considered together — the interpretation, before the supporting charts belowSession-to-session volume
This session
Rolling average (own normal)
High-speed running & sprint exposure
HSR distance, m (>19.8 km/h)
Sprint distance, m (>25.2 km/h)
Chart display
Top speed — session-to-session
Reached ≥90% of season best
Below 90%
Season best
90% of season best
Most recent match — first half vs second half
Technical — most recent match
Wellness — block trend
Readiness score
Own early-block average
Physical testing — jump & sprint
Training load (sRPE)
Strength testing (isometric)
Individual benchmarks
Season, recent form and personal best — each against this player's OWN history, with sample-size rules applied before a figure is shownSpeed exposure
Top-end speed and genuine sprint touches — tracked separately from HSR volume aboveConsideration history
Current and previous training considerations for this player — whether each improved, persisted, recurred or resolvedTimeline
Sessions, wellness, testing and staff notes together, in one chronological viewStaff notes
Tactical role, planned loading modifications and other context, added by staff rather than derived from data. Saved to your club's record — visible to any staff member who signs in.Add a note
Full sleep/soreness/fatigue/mood breakdown visible here — Coach logins see composite readiness only.
Worth a look
Players whose reported wellness has genuinely dropped from their own normal — not just low in absolute termsSquad readiness — 5‑week trend
Squad average readiness
Block-start average
Readiness by player — selected session
Squad
Worth a look
Squad average
Individual wellness trends
Each dimension on its own, not just the composite — a drop in composite readiness can come from one factor alone (e.g. sleep) while the others stay normal, which the composite score hidesNotable testing changes
Test results that moved beyond normal test-retest noise versus that player's own previous test, across any metric — tap a flag's threshold badge for the reliability figure behind itPrevious vs latest test — by player
Previous
Latest
Previous vs latest test — by position group
Previous
Latest
Longitudinal trend & block comparison
Built to show every test on record, not just the two most recent — currently plots whichever phase labels exist in this datasetStrength testing (isometric)
Isometric strength (hip, knee, etc.) from your strength-testing provider — a separate data type from the jump/sprint testing above. Each test shows the single best (highest peak force) rep per side; Limb Symmetry Index (LSI) is the weaker side as a % of the stronger — 100% is fully symmetric.Notable strength findings
Low Limb Symmetry Index, or a meaningful drop in peak force versus a player's own last test — practical thresholds (85% LSI, 10%+ drop), not statistically-derived reliability bounds like the CMJ/sprint/RSI flags above (see the Metric Guide below).No strength testing logged yet — import a raw isometric strength-testing export from Upload your data to see results here.
Metric Guide & Reliability
- CV (between-day measurement noise)
- How much a retest can move on its own from normal day-to-day measurement noise. This squad only has one baseline+retest pair per player each — not enough to calculate its own test-retest CV — so each figure below is sourced from a published between-day reliability study in a comparable athlete population instead. On its own, exceeding this figure once is not treated as evidence of a real change on this page — see MDC95 below.
- Countermovement jump height
- CV ±5% — Lonergan et al. 2025, elite academy soccer players, 8-day inter-day reliability, International Journal of Strength and Conditioning.
- 10m sprint time
- CV ±3.1% — adolescent rugby union/league players, Leeds Beckett University reliability study.
- 30m sprint time
- CV ±2.0% — same reliability study.
- Reactive strength index
- CV ±7% — a conservative floor set above the 5.4–6.9% intraday CV reported from force-plate drop-jump testing (hurling players); between-day RSI reliability is sparsely reported in the literature, so treat this as the noisiest of the four. "RSI" also isn't one calculation — flight-time÷contact-time (dimensionless) and jump-height÷contact-time (m/s) aren't interchangeable, so no unit is shown. Each import can optionally declare which formula a reading used (the rsiMethod column), which gives any two RSI readings one of three comparability states: matched (both declared the same formula — compared normally, with the usual MDC95 screening caveat); conflicting (both declared, but different — flagged as a mismatch, no %-change calculated at all); or unverified (one or both left the formula blank — the values and the raw %-change are still shown as logged, but they're never run through MDC95 or colour-coded as a confirmed change, since nothing confirms they're the same quantity). It's on you to declare the formula for both readings if you want a confirmed comparison; leaving it blank doesn't hide the numbers, it just stops the app from vouching for them.
- MDC95 (minimal detectable change, 95% confidence)
- The bar a retest actually needs to clear before it's called "beyond measurement error" with 95% confidence — the standard Hopkins/Weir formula, MDC95 = CV × 1.96 × √2 (≈ CV × 2.77). This replaces an earlier, looser version of this page that flagged a change as soon as it passed the raw CV once, which overstated confidence — a single retest moving by "about the published CV" is still well within plausible measurement noise.
- Smallest worthwhile change (SWC)
- A separate, practical-importance bar — calculated from this squad's own data (0.2× the between-player spread at baseline), shown once at least 4 baselines are on file for that metric. SWC and MDC95 are independent: a change can clear one without the other. A flag needs to clear both SWC and MDC95 to reach the Testing tab; the hover note on each flag says whether it cleared SWC as well.
- Protocol & equipment
- Not captured in this dataset — only a date and phase label per test. A real deployment should log tester, equipment, exact protocol and trial number alongside each result, since comparing across different equipment or protocols isn't a reliable comparison regardless of how the CV/SWC/MDC95 figures are read.
- Isometric strength — best-rep aggregation
- Each test/side/date is reduced to its single best (highest peak force) rep from the raw import, never an average across reps — the standard convention for strength testing (the same logic as taking a 1RM or a best jump, not a mean of attempts). Rep count on file is kept alongside the result but not shown as a reliability figure in itself.
- Isometric strength — Limb Symmetry Index (LSI)
- LSI = (weaker side ÷ stronger side) × 100 — 100% is fully symmetric. 85–90% is a commonly cited reference range in return-to-play/ACL literature, not a cutoff validated against this squad's own data the way CMJ/sprint/RSI's CV figures above are — treat a low reading as worth a look alongside injury history and loading, not as a standalone diagnosis.
- Isometric strength — flag thresholds
- Both isometric-strength flags (asymmetry below 85% LSI; a 10%+ peak-force drop on one side versus that player's own previous reading for the same test) are practical magnitude thresholds, not MDC95-style statistically-derived reliability bounds — there's no published between-day CV for this kind of isometric strength testing in this dataset to calculate one from. They're a starting point for a closer look, not evidence of a real change with any stated confidence level.
Session load = RPE (0–10 Borg CR-10 scale) × session minutes, in arbitrary units (AU).
Worth a look
Players whose training load, ACWR or day-to-day variation has moved against their own normal — not just whoever has the highest absolute numberWeekly sRPE load by player — this week vs own recent average
This week
Own recent weekly average
Squad training-load status
Weekly load, monotony, strain and ACWR per player — ACWR/monotony need 7/28 days of a player's own tracked history before they show a numberIndividual load trend
Daily sRPE load across the block, with a 7-day rolling total overlaid — a gap in the line is a session logged with no sRPE entered yet, not a rest day; a true rest day (no session at all) plots as zero.Data quality overview
Session-by-session record of what's included, what's excluded and why — the audit trail behind every chart and flag in this appExclude session
Saves immediately.
Position for this match
Saves immediately.
Match result
–
Saves immediately.
Match opponent
Saves immediately.
Position Compare
First half vs second half, block totals and top speed — by position group. Single match by default, so read a swing alongside that player’s own multi-match pattern before calling it a trend. more ⓘ—
Selected player comparison
Distance — 1st vs 2nd half
HSR distance — 1st vs 2nd half
Top speed
HSR / min (block)
Sprint distance (block)
Flexible comparison
One metric at a time, against whichever baseline you pick — the table above audits a single match's half-split; this is for everything elsePosition groups
Every position starts in its own group — centre-backs are never automatically pooled with fullbacks, or defensive mids with central mids. Give two or more positions the SAME group name here only if you want them compared together (e.g. a small squad where CDM and CM should be pooled) — this never changes a player's own recorded position, only which players this comparison treats as the same group. Saved to your club's record — every login at this club sees the same groups.
Squad roster
Each player's own recorded position — this is what every chart, season benchmark and Position Compare group uses for them by default. Changing it here applies from now on across the app, including past sessions that don't have their own match-specific override set. To correct just one match (e.g. someone filled in out of position for a single game) use the Position action on that match's row in the Session Log instead — don't change their default position for a one-off. Saved straight to your club's roster.
| Player | Status | Sessions logged | Position |
|---|
Each change saves as soon as you pick a new position — no separate Save step.
Matchweek Load · ·
Average Match Demands
Typical match demands for players completing 75+ minutes — season benchmark for running volumeTotal distance by match · dashed line = season average · bar colour = competition type (League / Cup / Pre-season), inferred from each session's logged competition/opposition text
Season Physical Output
Match-by-match trend across the season, each against its own averageHSR Distance
>19.8 km/h
Sprint Distance
>25.2 km/h
Match physical output & results
Explore how total distance and high-speed running vary across match results. Each point represents one match, coloured by result.Match outcomes depend on many factors. These comparisons show associations, not causes.
- Total distance
- Distance covered during the match (m).
- HSR
- Distance above 19.8 km/h (m).
- Sprint
- Distance above 25.2 km/h (m), included in HSR.
- Inclusion
- Outfield players with ≥75 minutes played.
1st Half vs 2nd Half — Season Comparison
75+ minute matches only, per playerProjected Physical Output — Per 90 Minutes
What to expect from each player over a full match, based on their own logged rateSeason Trend Charts
Minutes Played
Match Distance
Match HSR
Peak Speed
Work Rate — Distance/Min
Work Rate — HSR/Min
Metric Guide & Reliability
- Half Split Reliability
- Reliable at 5+ matches with 75+ minutes played; below that, read as limited sample. Half-minutes are assumed even (45/45) since exact half-time minutes aren't separately logged.
- Projection Reliability
- Reliable at 5+ logged sessions with 25+ minutes; below that, treat the per-90 projection as indicative only.
Match Demands
Player Output
All appearances, including substitutes · sorted by total distanceMetric Guide
- Summary tiles
- Outfield players with 75+ minutes only. Player charts below include every appearance, subs included.
Match Intensity
Player Match Intensity
Sorted by distance/minTip. Per-minute values level the field between players on different minutes, but a short cameo can still produce a misleadingly high rate — always read it alongside minutes played, not on its own.
Metric Guide
- Distance/min, HSR/min
- Total figure divided by minutes played — a like-for-like intensity rate regardless of time on pitch.
- Players Included
- Outfield players with 75+ minutes, used for the summary tiles only.
First vs Second Half Work Rate
Individual Work-Rate Change
75+ minute players — half-minutes assumed even (45/45). 1H+2H figures are recorded independently in your export and occasionally won't sum to exactly the full-match total shown elsewhere (source-data/export rounding, not a calculation here) — Δ is computed from the unrounded rates, not the rounded m figures shown.Tip. A drop in raw second-half distance isn't necessarily fatigue if tempo or tactical shape changed — read the flag alongside the match context (scoreline, weather, opposition) before treating it as a physical decline.
Metric Guide
- Flag
- Large 2H drop: distance/min fell 15%+ from 1st to 2nd half. Moderate 2H drop: 8–15%. Stable: within ±8%. Increased: rose 8%+.
- Half split basis
- Half-minutes aren't separately logged, so each half is assumed 45 minutes for 75+ minute players; rate = half distance ÷ 45.
Squad Technical Snapshot
Metric Guide
- xG / xA
- Expected goals/assists — a model's estimate of chance quality, not a measurement. Stays visually distinct from the GPS-measured numbers elsewhere in this report for that reason.
- Actions successful
- Passes, duels, dribbles and shots combined — attempted vs successful, same shape as the rest of this table.
Each section below starts from an auto-generated summary of the data currently loaded — click into any section to edit the wording before you export, untick a section or an individual line to leave it out, and use "Print this report" above once you're happy with it. These edits are for this session only and aren’t saved between visits; the club name is the one setting that persists.
Role & permissions
What each viewing role sees across this app — and the limits of what a front-end switch like this can actually enforce
Three permission tiers, matched to how access actually needs to split. Coach: composite readiness, flags and scannable summaries — raw sleep/soreness/fatigue/mood scores and testing-change detail are hidden. Performance & Medical: sport science, S&C and medical staff — full wellness sub-scores and testing breakdowns by player and position. Admin: everything Performance & Medical sees, plus oversight access. This switch stays in sync with the "Viewing as" control in the header.
For Admin and Performance & Medical logins this is a preview only — your login already holds the full dataset, so switching just changes what's rendered. A Coach-tier login is different: the database withholds raw sleep/soreness/fatigue/mood scores and full testing breakdowns at source, so there's nothing for a switch to reveal.
Squad roster
Each player's own recorded position — used across every chart, average and comparison in this app unless a specific match sets its own (see the Position action on that match's row in the Session Log)Position groups
Which positions are compared together on the Flexible Comparison panel (Position Compare tab)Weekly training schedule
Which match-day-relative session type falls on each day of the week (used by Training Considerations)Speed thresholds
The speed definitions used for HSR and sprint distance across this dashboard
These relabel how HSR and sprint distance are described here — they don't recompute anything. Your GPS provider's own export already splits distance at fixed speed bands, so set these to match your provider's actual definitions rather than this app's defaults.
Club name
Shown in the header and on printed/exported Staff Reports. Saved to your club's record — changing it here renames your club for every login, not just this device.About this deployment
Sessions, wellness, testing, Training Considerations, staff notes and club settings all live in your club's own database behind a login — every coach who signs in sees the same up-to-date record, on any device, and no other club can access it. A Coach-tier login is further restricted at the database level: composite wellness readiness and flags only, no raw sub-scores, no full testing breakdowns, and sensitive staff notes withheld entirely. The only client-side-only data is a Staff Report's in-progress edits before export — a scratch pad, not a saved document. The "Viewing as" switcher above (Admin/PM logins only) is a display preview; it has no effect on what a Coach-tier login can actually access.
· Club-specific, access-controlled data · HSR >19.8 km/h · Sprint >25.2 km/h
A platform by EM Strength & Performance