How to read Progressive Passes without overclaiming

What the metric measures

A Progressive Pass moves the ball meaningfully toward the opponent’s goal. The rule needs a stated distance threshold. Analysts and tools can differ. In StarkPitch maps, the working definition is roughly twelve metres or more.

The metric has a practical use. Possession that advances territory is different from possession that moves sideways. Progressive counts help separate those patterns in event data.

What it does not prove

High progressive volume is not proof of better football. A team can progress into low-value areas. It can also progress often because the opponent sits deep. The passes may still fail to create shots.

Low progressive volume is not proof of failure. A side may progress less often and still create better chances. It may rely on transitions or set pieces instead of long circulation.

Progressive Passes do not encode intent, coach instructions, or off-ball structure. They summarise observed on-ball advances.

How to read a progressive-pass map

Start with start zones and end zones. Advancement into half-spaces or the box matters more than sideways progress near halfway.

Compare progressive share as well as raw counts. Progressive share means Progressive Passes as a percentage of completed passes. Raw volume mixes style, match length, and possession share.

Then pair the map with a Shot Map. Progression without shots can be sterile control. Shots without progression may come from transitions or set pieces. Both patterns are real. They answer different questions.

A careful claim

In the Argentina against France final sample, Argentina’s progressive share is much higher across the open-data file. A careful claim stops at process difference and timing. When did France’s dangerous moments arrive? Did they need the same progressive structure?

An overclaim would be: “Argentina controlled the final because they progressed more.” Control, threat, and result are related. They are not identical.