Training ScienceCoaches12 min read
Team Match Insight explained: whole-team match analysis, end to end
MicroPulse·
A detailed guide for coaches on what Team Match Insight shows, where the data comes from (Wyscout General, Defending and Indexes plus GPS/IMA), how to read each panel, how data gets in without overwriting — and what comes next.
What is Team Match Insight?
Most clubs already own the data but use it poorly: the match stats live in Wyscout, the physical data in Catapult, and the results in the coach's head. Team Match Insight brings these three worlds onto one page and answers the question coaches actually ask: how does the way we play connect to whether we win?
The key is that the answer is never in a single match. One match is noise — a team can run a lot and lose, or play poorly and win. Team Match Insight gathers every match of the season, reads each one against the result, and surfaces the patterns that only appear once enough matches stack up. It is a descriptive context layer — it helps you understand how the team plays, without ever touching the daily decision of who is green, amber or red.
The data: General, Defending and Indexes — plus GPS/IMA
Team Match Insight is built on three Wyscout exports (Team → Stats, with "Show opponents" ON, one per DISPLAY preset) and movement from Catapult:
General — the core, and the only required file. It gives goals, xG, shots (and on target), passes (and accuracy), possession, duels won, and losses/recoveries by pitch zone. Because the opponent is included, it also yields xG against, shots against and goals against.
Defending — adds defensive duels won (%), showing whether the team wins its one-on-one battles.
Indexes — adds PPDA (passes allowed per defensive action; lower = more intense pressing) plus style indices like match tempo, passes per possession and long-pass share.
On top of this sits movement: GPS and IMA from Catapult (running, sprints, high-speed running, accelerations/decelerations), which syncs automatically. The results themselves come from the fixture list. So every match carries both a tactical and a physical side, each with its own provenance.
The four panels
The page reads top to bottom, each panel with a one-line summary and a "How to read this" button.
The read — an auto-generated, plain-language summary of the season so far (a headline plus a few facts), labelled as auto-generated. Built from your data by rules, not guesswork.
First half vs second half (last match) — for your most recent game, how each movement metric changed between halves, per minute, with a per-player breakdown. Green = held up, amber = faded. Shows fatigue and how the team holds up after the break.
Wins vs losses — in two parts. First the movement (GPS/IMA) in wins versus losses, then the match stats (xG, xG against, shots, possession, PPDA, duels) — each with an effect-size chip showing which metrics actually separate the two, plus a match-by-match table. This is the heart of it: what characterises the games you win versus the ones you lose.
What tracks the result? — correlations between movement, match stats and results, with honest warnings whenever the sample is too small to read into.
Plain language and explainability
The page is designed for coaches, not analysts. Every panel follows the same layered read: a one-line verdict at the top, then 2–3 plain facts (the "why"), and finally the raw tables behind a "Show details" toggle. Sport-science terms (PPDA, xG, IMA, effect size) live behind explainers, never in the foreground.
Everything is bilingual (English/Icelandic). Where the system uses an auto-generated summary it is labelled as such and cites the underlying numbers. And when the sample is small — fewer than about ten matches, or fewer than three wins and three losses — the page says so and asks you to treat strong-looking links as tentative. Honesty about uncertainty is part of the product.
How the data gets in (without overwriting)
Match stats are uploaded right on the page: open "Import Wyscout stats", drop in the General file (and Indexes/Defending if you want), Preview — which shows exactly what will change without saving — then Import. Matches are matched by date, so re-importing updates the matches already saved and adds new ones, never duplicating. You can import the whole season or just the new matches.
Movement (Catapult) syncs automatically through the OpenField connection — nothing to upload there. And so the system can tell wins from losses, enter each match result on the fixtures page (otherwise results are inferred from the Wyscout goals).
What it is not
Team Match Insight follows the same rule as everything else in MicroPulse: one system, one verdict, visible everywhere. This page is a context layer — it never touches the readiness colour, the daily decision, or the training recommendation. Green, amber and red still come from the personal norm (how today compares to each player's usual), not from whether the team won its last match.
It also shows association, never causation and never prediction. "Run more" does not make you a better team; metrics simply coincide sometimes. The page shows those links honestly rather than selling them as a recipe.
What's next: passing and attacking
Today the system reads three Wyscout presets — General, Defending and Indexes. But the architecture is preset-agnostic: it detects automatically which file supplies what, so adding two more is a direct extension.
Passing would deepen the attacking picture most: forward passes, passes to the final third and into the box, progressive passes, crosses and line-breaking "smart passes" — that is, how the team builds up and breaks through, not just how much xG it creates. Attacking adds box presence, attack types (build-up, counters, set pieces) and offensive duels.
Both are per match and include the opponent, so they would slot straight into the wins-vs-losses and correlation panels with no new design. The result: an even richer read of how the team attacks — whether the wins are about creating more, breaking lines more often, or getting into the box more.