How to Read a Pass Network Map Without Mistaking It for a Formation

A pass network map plots each player as a node placed at the average location of their passing actions, and joins pairs of players with lines whose thickness reflects how often the ball travelled between them. It is one of the most widely shared graphics in football analysis and one of the most consistently misread, because at a glance it looks like a formation diagram and it is not one.

The difference matters. A formation describes an intended arrangement. A pass network describes where the ball actually went and who moved it, which is a record of behaviour rather than instruction. Reading one as the other produces confident conclusions about shape that the graphic cannot support.

What the graphic is actually made of

Before reading anything into a network, identify its components. Most versions carry four, and each encodes a different thing.

• Node position. The average location of a player's involvement in passing, computed from event coordinates. It is an average, not a place the player stood.
• Node size. Usually total passes made or received, so a large node means high involvement rather than good involvement.
• Edge thickness. The number of passes between that specific pair, almost always with a minimum threshold so that the map is not a spider's web of single passes.
• Edge direction. Present in some versions as an arrow or as a split line, absent in many. Without it, a thick line tells you two players exchanged the ball often, but not which of them was feeding the other.

Step one: read the build rules before the picture

Every pass network is built from choices, and the choices are usually printed in small text nobody reads. Three of them change the picture materially.

The first is the time window. Most networks are drawn from kick-off until the first substitution, because a substitution replaces a node and the average position of a partially played role becomes meaningless. A network drawn across ninety minutes with five substitutions is a different object from one drawn across the first hour with eleven stable players.

The second is which passes count. Networks are normally built from completed passes only, which quietly removes the failed attempts — often the most ambitious ones. A team that repeatedly tried and failed to reach its striker will show no connection to the striker at all, and the map will look like a team that never tried.

The third is the threshold. If pairs need a minimum number of passes to earn a line, raising the threshold thins the network and lowers it thickens it. Two maps of the same match with different thresholds tell visibly different stories, which is why comparing networks from different sources is unreliable unless the build rules match.

Step two: fix the reference frame

Check the attacking direction and whether both teams have been drawn attacking the same way. Many published comparisons flip one side so the two networks face each other, which is intuitive for viewing and confusing when reading numbers off the axes. Confirm also whether the pitch is drawn to scale, since a compressed vertical axis exaggerates how compact a side looks.

Step three: read the shape without calling it a formation

Now the map can be read, and the first discipline is to stop naming shapes. Average positions do not correspond to occupied positions. A full-back who spends the first half overlapping the touchline and the second half tucking inside will appear in a midfield location that they occupied at no point in the match. The node is the midpoint of two behaviours, not a description of either.

What the shape does support is a set of relational judgements:

• Vertical spread. The distance between the deepest and highest nodes indicates how stretched the team was in possession.
• Horizontal spread. Narrow networks suggest central circulation; wide ones suggest the ball was worked through the flanks.
• The gap between blocks. A visible empty band between defence and attack usually means the ball was bypassing midfield rather than being played through it.
• Isolation. A node sitting apart from every other node, with thin edges, indicates a player the team could not reach.

Step four: read the edges, including the missing ones

Edges carry more information than node placement, and the absent ones carry the most.

Look first for the hub — the node with the most and thickest connections, usually a pivot or a ball-playing centre-back. That player is the team's circulation point, and networks with a single dominant hub are structurally fragile, since removing one player from the game removes the route.

Then look at the backline ring. A thick chain of edges across the defenders with thin connections forward is the signature of possession that never progressed, and it is the clearest thing a pass network shows that a possession percentage hides.

Then look for asymmetry. Almost every team is heavier on one side. When one flank carries visibly more of the network, that is a real pattern, and it usually reflects who the progressive passers are rather than a tactical instruction.

Finally, look for the connection that should exist and does not. Two forwards with no edge between them, or a midfielder with no edge to the winger ahead, are the interesting findings on most maps, because they identify a relationship the team could not establish.

One caution belongs with the edges. A pass network only records completed connections between players who were both on the pitch at the time, so it cannot show the run that was made and ignored, the option that was available and refused, or the pass that was attempted and intercepted. Everything invisible on the map is invisible for the same reason: the ball did not arrive. That makes the network an excellent description of what a team managed and a poor description of what it attempted.

Step five: remember the opponent drew half of this

A pass network is co-produced. A compressed, backline-heavy network can mean a team chose to circulate safely, or it can mean the opponent's pressing structure denied every forward option. The map cannot distinguish between those, and it is why a network should be read next to the opponent's network rather than alone. When one side's map is stretched and progressive and the other's is flat and lateral, the honest reading is usually about the interaction rather than about either team's philosophy.

Step six: know what the neighbouring graphics do instead

Three visualisations get confused with each other, and separating them prevents most misreadings.

• The average position map places players at their average location for all actions, not just passes, and carries no edges. It answers where players were, and nothing about who they played with.
• The heat map shows the density of one player's activity across the whole pitch, which preserves the range that an average destroys. If you want to know whether a full-back actually occupied that central node, the heat map is the check.
• The pass network is the only one of the three that describes relationships between players, which is its unique contribution and the reason to use it at all.

Used together, the three cover each other's blind spots. Used alone, the network is the one most likely to mislead, because it is the one that most resembles a diagram people already think they understand.

There is a fourth check that costs nothing and settles most arguments: the underlying match statistics. If a network suggests a team never reached its forwards, the pass counts, touch totals and shot record should agree, and platforms such as RubiScore publish those per player for the same fixture. When the graphic and the counts disagree, the counts are the more literal record and the graphic is the interpretation.

Common mistakes worth avoiding

• Naming a formation from node positions, when the nodes are averages of movement.
• Comparing networks from different providers without checking thresholds and time windows.
• Reading a network from a match with an early red card or an early forced substitution, where the sample behind each node is small and the structure changed.
• Treating thick edges as evidence of quality. A thick line between two centre-backs is a high volume of low-value passes.
• Drawing conclusions from a single match. Networks vary hugely with game state, opponent and venue, and a pattern needs several matches before it describes a team.

A short checklist

Confirm the time window and whether substitutions are included. Confirm completed passes only. Check the threshold and the attacking direction. Identify the hub, the backline ring, the asymmetry and the missing edges. Compare against the opponent's network. Cross-check any surprising node against a heat map. Then, and only then, say something about how the team played.

Match event data of the kind that these maps are built from — pass counts, pass directions, average positions and player involvement across a season rather than a single afternoon — is published on rubiscore.com, and multi-match reading is what turns a striking graphic into a defensible statement about a team.