How to Read a Football Data Report Without a Statistics Degree

Open a modern match report from a data provider and the uninitiated see a cockpit: an xG timeline climbing in steps, a pass network webbed with lines, shot maps scattered with dots, momentum charts rolling like an electrocardiogram. It looks like homework. In reality each element answers one plain question, and learning the four or five that matter takes less time than the first half of any match.

This is a fan's guide to the standard match data pack — what each visual is for, what a healthy version looks like, and the one mistake people make with every single one.

The xG timeline: the match as a story

The xG timeline plots each team's cumulative expected goals as the match progresses, stepping upward every time a chance is created. Read it like a plot. Long flat stretches are stalemate; steep jumps are periods of real danger. A team that climbs steadily all match was turning the screw; a team flatlining for an hour before one giant spike was hanging on and nearly stole it at the end.

The classic mistake is treating the final totals as the whole story. Two sides can finish level on xG with completely different matches behind them — one trading blows throughout, the other dominated for eighty minutes before a late flurry. The shape of the line matters as much as where it ends.

The four questions a data pack answers

• xG timeline: when were the chances, and whose?
• Shot map: from where did each team shoot?
• Pass network: who connected with whom, and where?
• Momentum or field tilt: who played where, and when?

Shot maps and pass networks

The shot map places every attempt on a pitch diagram, usually sized or coloured by its xG value. A good attacking map shows a cluster of big dots inside the box; a worrying one shows a spray of small dots from range. When a striker is criticised for a quiet game, the shot map is the first appeal: no dots at all means the service failed him, while several big dots missed means he failed the service.

The pass network looks abstract but answers a concrete question: how did the team actually connect? Each player is a node placed at his average position, each line a passing link, thicker for more passes. Networks reveal the truth about roles — the full-back who played as an extra midfielder shows up parked in the centre circle, and the winger who spent the match isolated stands alone with one thin line to his name. Lopsided networks, where everything flows down one flank, often explain why that side's attacks became predictable.

Momentum charts and the context layer

Momentum graphics — whether proprietary models or simple field-tilt windows — compress the flow of the match into a wave. They are the best tool for finding the moments worth rewatching: the ten-minute surge before half-time, the collapse after the substitution. But they are descriptors, not explanations, and they routinely make losing teams look competitive because trailing sides attack more by default.

That is the meta-lesson of the whole pack: every chart needs the scoreline and the clock beside it. Game state bends every number. A team two goals up stops attacking by choice, and its second-half data will look like decline when it is actually management.

Building a five-minute routine

The practical way into match data is a fixed order, repeated until it is automatic. Start with the score and the xG timeline together to learn what happened and when. Move to the shot map to see whether the chances matched the story. Glance at the pass network for anything structurally strange — a lopsided flank, an isolated striker. Finish with the momentum chart to locate the two or three passages worth rewatching on video. Five minutes, four charts, one much clearer picture.

The routine works because each step checks the previous one. The timeline says a team dominated; the shot map confirms the chances were real; the network shows how; the momentum chart says when. When one step contradicts the others, you have found the interesting part of the match — and that, more than any single number, is what the data pack is for.

None of this replaces watching the match; it sharpens it. The fan who checks the timeline at full time knows whether to be angry at the finishing or the creation, whether the draw was a robbery or an escape. That is the entire point of the numbers — not to settle arguments, but to make them better informed.