Directory of ITIL® and ITSM services  
& software. A launch pad for the  
IT infrastructure library® (ITIL®) & ITSM  

 Directory of Software & Services for ITIL® and ITSM Contact Us Front Page
 

Progressive Passes, Carries, and Beyond: The RubiScore Approach to Advanced Metrics

Progressive metrics describe how a team moves the ball forward into dangerous territory — not by counting every pass and dribble, but by counting only the ones that meaningfully advance possession toward goal. RubiScore tracks this family of metrics alongside the headline figures on every covered match, so a reader can see who carried the ball into the final third, who threaded the pass that broke a defensive line, and which midfielders did the unglamorous work that turns possession into shots.

What is a progressive pass?

A progressive pass is a forward pass that moves the ball closer to the opposition goal by a defined distance, usually measured against a threshold that scales with the area of the pitch the ball is in. The common rule of thumb, used across most modern football data providers, is that a pass counts as progressive if it advances the ball at least a meaningful number of metres toward the goal-line, with a stricter threshold in the defensive third and a looser one inside the attacking third.

The intent is straightforward. Not every pass deserves equal weight. A goalkeeper rolling the ball to a centre-back covers ground, but it does not change the shape of the possession. A line-breaking ball from a deep midfielder into the half-space between centre-back and full-back can transform a slow build-up into a chance within seconds. Progressive pass counts try to separate the second kind of action from the first.

In practice the metric is computed event by event. The data feed records each pass with its start location, end location, and outcome. A short script applies the progression threshold, checks whether the pass moved the ball forward by at least the required amount toward the opposition goal, and tags it as progressive. The result is a per-player and per-team count that can be read alongside the more familiar pass total and pass accuracy figures.

What counts as a progressive carry?

A progressive carry is the same idea applied to dribbles and ball-carrying actions rather than passes. The player has the ball at his feet, moves it forward through space without losing it, and ends the carry closer to goal by at least the threshold distance. Like progressive passes, carries are filtered against zone-aware thresholds — the bar is highest in the defensive third, where a carry is usually risk-light, and lowest in the attacking third, where every metre is contested.

Carries matter because they capture a kind of progress that pass counts ignore. A winger who beats his marker and runs the ball into the box, a full-back who steps out of the line and drives into midfield, a centre-back who carries the ball across the halfway line because no opposition player closes him down — these actions are central to how modern teams build attacks, and they are invisible in possession percentages or simple pass totals.

RubiScore separates carries from dribbles deliberately. A successful dribble is defined narrowly as beating a defender; a carry is broader and includes any forward movement with the ball under control, with or without an opponent in the way. Both are tracked, but they answer different questions. Dribbles measure one-versus-one skill. Carries measure ball progression. Reading them together gives a much sharper picture than reading either on its own.

Why do progressive metrics matter?

Football's traditional stat sheet — possession, shots, shots on target, pass accuracy — was designed for a sport that, two decades ago, did not have the data infrastructure to ask more sophisticated questions. The headline numbers are still useful, but they are also famously misleading. A team can hold seventy percent of the ball and lose. A team can complete ninety percent of its passes and never threaten the goal. Possession quality, not possession quantity, is what wins football matches.

Progressive metrics close part of that gap. They reframe a familiar question — who is in control of the ball? — as a more useful one: who is moving the ball forward into territory where chances are created? Read across a full season, the progressive numbers tend to line up with the teams and players that everyone watching can see are dictating play, even when the basic possession figures do not.

There are a few specific reasons this family of metrics has become standard in modern football analysis:

How does Rubi Score collect progressive data?

The collection is event-driven rather than computed live in the same way the score is. Every covered match generates a stream of events: passes, carries, shots, fouls, throw-ins, set pieces, and so on. Each event carries its own metadata — player, timestamp, start and end coordinates, outcome. The progressive flag is applied as part of the data pipeline: when an event lands in the feed, the platform's processing layer checks the start and end coordinates against the zone-specific progression threshold and tags the event accordingly.

During the match, the live page shows a working count of progressive actions, derived from events as they arrive. After the final whistle, the data is reconciled against the richer post-match dataset, where any corrections to event coordinates or attributions are applied. The progressive totals are updated to reflect the cleaned numbers. As with xG, the post-match values are treated as authoritative — small shifts in the live count are an honest consequence of using fast data first and complete data second.

The depth of the breakdown depends on the competition. In the top European leagues, the major continental cup competitions, and international tournaments tracked at full depth, every progressive action is attributable to a named player, with the start and end coordinates available behind the headline number. In competitions covered at a lighter level, progressive totals may be reported per team rather than per player. The match page is transparent about which level of detail it is showing for a given fixture.

Progressive metrics by position

A useful way to read these numbers is by position, because the meaning of a high progressive count changes depending on where the player operates.

Reading the numbers without the position context tends to flatten them. Read with the position context, they describe what each player is being asked to do, and how well they are doing it.

What progressive numbers do and do not say

Progressive metrics are descriptive, not evaluative. A high count means the player is moving the ball forward often. It does not mean the team is creating better chances, that the progression is leading to shots, or that the player is making good decisions. A player can rack up progressive carries by running into traffic and losing the ball, or progressive passes by playing forward into pressure and conceding turnovers.

The honest way to read the numbers is in combination with outcomes. Progressive passes paired with key passes and xA show how often the progression is ending in a chance. Progressive carries paired with successful dribbles and touches in the opposition box show whether the carry is producing penetration or just kilometres. The data on RubiScore is structured to be read this way: the progressive figures sit alongside the related outcome metrics rather than being presented in isolation.

The team-level reading follows the same principle. A side with high progressive pass totals but low xG generated is moving the ball forward without producing chances — typically a sign that the final ball, not the build-up, is the problem. A side with low progressive totals but high xG is producing chances through routes that bypass the metric, often via transitions or set pieces.

Where does the data sit on RubiScore?

For every covered match in a fully tracked competition, the progressive figures appear on the match page alongside the standard event statistics, with team totals and per-player breakdowns. Player profile pages aggregate the season-long progressive numbers, so a midfielder's progression output can be read against the rest of the league at the same position. Historical data is preserved at the season level for tracked competitions, allowing reading across years rather than only the current campaign.

The methodology document for how progression thresholds are defined and applied is published on rubiscore.com alongside the rest of the live and post-match data, so a reader who wants to know exactly what counts as a progressive pass for a given zone of the pitch can find the answer in one place rather than reconstructing it from outside sources.


HOME ~ WEBLINKS ~ CONTACTS

==> SOFTWARE DOWNLOAD AREA <==



       ITIL® is a Registered Trade Mark of AXELOS Limited. IT Infrastructure Library® is a Registered Trade Mark of AXELOS Limited

       For other information see also ITIL Service Management; CCTA and BBB.Org
       Coming soon: Service Providers Directory

Copyright © 1993-2016 BC Associates WF2