Nineteen shots to six reads like a rout on paper. Put the same match’s shot map on screen and the story narrows considerably: fourteen of those nineteen came from outside the box, three were blocked before reaching the six-yard area, and the six shots from the other side included two clear one-on-ones.
Both numbers describe the same ninety minutes. Neither is wrong. They are simply answering different questions, and a recap that treats them as interchangeable evidence for the same claim is making a mistake that shows up constantly in match coverage.
What follows separates what a shot count can honestly support from what only a shot map can show, and lists the presentation choices that make a shot map say more than the data actually justifies.
What each number actually measures
- Shot count. Volume of attempts, nothing about location or quality.
- Shot map. Location and often quality, nothing about the shots that never happened.
- What both miss. Buildup quality, defensive pressure at the moment of the shot, goalkeeper positioning.
- The safest combined claim. Where a team generated its chances, not how dominant it was.
- The presentation trap. Dot size and bin choices that make a map look more decisive than the shots were.
- The honest caption. One that names what the visual leaves out, not just what it shows.
What a shot count can honestly support
A raw shot tally answers exactly one question well: how many times did a team attempt to score. That is a legitimate thing to know, and in matches where the gap is extreme, nineteen to three rather than nineteen to six, it does tell you something real about territorial control.
Where it fails is the moment a reader infers quality from quantity. A team can post a high shot count entirely through speculative efforts from distance, taken because a compact defense left no better option, and a low shot count entirely through a small number of clinically created chances. The count alone cannot distinguish between these two teams, and a recap that calls the high-volume team the more dangerous one without checking location has made a claim the number does not support.
The honest use of a shot count is territorial, not qualitative: it tells you who spent more of the match in a position to shoot, which is closer to possession than to threat.
What a shot map adds that the count cannot
A shot map plots every attempt by location, and frequently by outcome and estimated quality, converting a single number into a spatial pattern that a raw count erases entirely.
The immediate value is separating shots taken from good positions from shots taken because nothing better was available. A cluster of dots inside the six-yard box tells a completely different story from an identical number of dots scattered along the edge of the penalty area, and only the map makes that distinction visible.
The map also reveals patterns invisible in any single number: whether a team’s chances came predominantly from one flank, whether set pieces produced a disproportionate share of the good positions, or whether a team’s shots clustered in the closing minutes once an opponent had tired. None of this is recoverable from a shot count, however precisely it is reported.
A shot count and a shot map from the same match, side by side
| Metric | What it shows in this example | What it supports on its own |
|---|---|---|
| Shot count | 19 to 6 | Territorial dominance for the first team |
| Shots inside the box | 5 to 4 | A near-even split in higher-quality attempts |
| Shots from outside the box | 14 to 2 | A large share of low-quality volume for the first team |
| Big chances (clear one-on-ones) | 1 to 2 | An edge for the second team in the moments that matter most |
Read the shot count alone and the first team dominated. Read the full breakdown and the second team, with a third of the attempts, generated the better chances. Both statements are true, and only one of them survives contact with the map.
What neither number can tell you
Even a detailed shot map has a hard ceiling on what it can support, because it records outcomes rather than the process that created them.
Defensive pressure at the moment of the shot is invisible on a standard map. A shot taken from inside the six-yard box under a covering defender’s outstretched leg looks identical, as a dot, to the same shot taken completely unmarked. Some advanced models attempt to weight for this using tracking data, but the widely available public maps used in most recaps do not, and treating their quality estimates as a full account of difficulty overstates their precision.
Goalkeeper positioning carries the same blind spot. A shot map records where the ball was struck from, not where the goalkeeper stood, and a save from a well-set keeper looks the same on the map as a save that should have been a routine catch. The map is a record of attempts, not of goalkeeping quality, however tempting it is to read one into the other.
The presentation traps: bin size and dot scaling
Two design choices in how a shot map gets drawn change how decisive it looks, independent of the underlying data, and both are worth checking before quoting a visual as evidence.
Bin size matters when a map groups nearby shots into zones rather than plotting each one individually. A coarse bin can make a scattered handful of shots look like a concentrated cluster, simply because the zone boundaries happen to fall in a convenient place. The same data, binned differently, can produce a visibly different story.
Dot scaling matters even more, because most shot maps size each mark by estimated quality, and the visual difference between a small dot and a large one is often disproportionate to the actual difference in scoring probability. A shot valued at eighteen per cent and one valued at thirty per cent might carry dots that look several times different in area, exaggerating a gap that, in scoring terms, is closer than the picture suggests.
The symmetric map that looks meaningful and is not
A specific and seductive failure mode deserves its own mention: the map that shows both teams’ shots mirrored onto the same end of the pitch, so both clusters can be compared at a glance.
The visual is genuinely useful for comparison, and it is also easy to over-read, because mirroring implies the two teams were shooting at directly comparable moments and under comparable circumstances, which is rarely true. A team that built a two-goal lead by halftime and then defended a deep block for forty-five minutes will show a shot pattern shaped entirely by that game state, and mirroring its second-half shots against an opponent’s does not control for the fact that the two teams were playing completely different games by that point.
The fix is not to abandon the symmetric map, which remains a genuinely useful tool discussed elsewhere in coverage of how visual analytics are changing match coverage, but to caption it honestly: note the score state at each shot, or split the map by half, rather than presenting ninety minutes as a single undifferentiated picture.
Writing the honest version of the recap sentence
The discipline that fixes most of this is small and specific: name what the number measures in the sentence itself, rather than letting the number imply more than it does.
Instead of writing that a team dominated with nineteen shots to six, write that a team generated nineteen attempts, the majority from outside the box, while the opponent created fewer chances but two clear openings in front of goal. The second version takes one extra clause and survives a reader who checks the map, while the first collapses the moment anyone looks closer.
The same discipline applies to the map itself. A caption that says shots by location tells a reader less than one that says shots by location, sized by estimated quality, which does not account for defensive pressure. The extra clause costs nothing and prevents the single most common misreading of the visual.
How shot maps change the way a recap gets structured
Once a writer starts treating shot location as the primary evidence rather than the total count, the structure of a match report tends to shift with it. Instead of opening with the aggregate numbers, a report built around the map usually opens with where the game was actually won: a specific sequence of shots from a specific zone in a specific ten-minute window.
This produces a more specific piece of writing almost automatically, because the map forces a writer to name a location and a moment rather than reach for a season-long adjective like dominant or wasteful. A team did not simply create chances; it created them from the inside of the six-yard box in the final quarter of an hour, off two corners and a low cross. That level of specificity is available to any writer willing to look at the map before writing the sentence, and it reads as more credible precisely because it is checkable against the visual.
The tradeoff is length and pace. A recap built entirely around shot-by-shot detail can become dense quickly, and the better versions use the map to select two or three decisive sequences rather than narrating every attempt in the match.
Comparing shot maps across different data providers
Readers who follow more than one outlet’s coverage of the same match sometimes notice the shot maps do not quite agree, and the discrepancy is rarely an error on either side.
Different providers collect shot location data through different combinations of tracking cameras and manual logging, and small disagreements in exact coordinates are normal and usually inconsequential. The more consequential disagreement is in the underlying quality model: one provider’s estimate of a shot’s scoring probability might weight the angle of the shot more heavily, while another weights the speed of the buildup play that preceded it. Neither weighting is objectively correct, and both are reasonable modeling choices built on different assumptions about what predicts a goal.
The practical implication for a reader comparing two recaps of the same match is to treat the raw shot locations as broadly reliable and the quality scores attached to them as provider-specific estimates rather than as settled facts. A shot map is data plus a model, and the model half of that pairing varies more than most readers assume.
A short checklist before quoting either metric
Before citing a shot count in a recap, check whether the gap survives a look at shot location; a wide gap in total shots with a narrow gap inside the box is not the same story as a wide gap in both.
Before citing a shot map, check the bin size and the dot scaling against the raw numbers behind them, and note in the caption what the visual does not account for, particularly defensive pressure and goalkeeper positioning. Neither check takes long, and both prevent the recap from making a claim the data cannot actually carry.
Frequently Asked Questions
Is a high shot count ever a reliable sign of a dominant performance?
It correlates with territorial control, which is real information. It becomes unreliable the moment it is used as a stand-in for chance quality, since a high count built from long-range efforts describes a very different match than the same count built from good positions.
What does the size of a dot on a shot map actually represent?
Usually an estimated probability that the shot results in a goal, based on factors like distance, angle and sometimes the type of assist. It does not represent defensive pressure or goalkeeper positioning at the moment of the shot.
Why do two outlets sometimes publish different shot maps for the same match?
Different data providers use different underlying models to estimate shot quality, and different visualization tools make different choices about bin size and scaling. The shot locations themselves should agree; the quality estimates and their visual presentation frequently do not.
Should a recap avoid shot maps because they can mislead?
No. The map answers a real question the count cannot. The fix is captioning it honestly rather than avoiding it, since the alternative, a bare shot count, is more easily misread, not less.
What is the single most useful combined statistic?
Shots inside the box as a share of total shots, for both teams, read alongside the count of clear goal-scoring opportunities. It is not glamorous, but it survives scrutiny better than either number alone.
A shot count tells you who tried more often. A shot map tells you from where. Neither tells you who deserved to win, and a recap that asks either number to answer that question is asking for more than it was built to give.
