A RubiScore Glossary of Attacking-Sequence Metrics: How Data Tracks a Team's Build-Up

A shot map or a pass count tells you what happened at the two ends of an attack. It says nothing about the attack itself — how it was built, how far it travelled, or how many players touched it before it either produced a chance or broke down. That gap is what sequence data is built to close, and RubiScore is among the platforms that structure match data around sequences rather than isolated events. This glossary works through the core terms, grouped by what question each one answers.

What Counts as a Sequence

A sequence is a period of continuous possession by one team, starting the moment they win the ball and ending when the other team regains it, the ball goes out of play, or a stoppage occurs. It is the basic unit that sequence-based analysis is built from, and everything else in this glossary is a way of describing or classifying sequences once they exist.

Open-play sequence: a sequence that begins from regular play — a regain, an interception, a loose ball — rather than from a dead-ball restart. Most sequence metrics are calculated on open-play sequences specifically, because set-piece possessions follow a different logic and would distort the averages if mixed in.
Sequence length: the number of passes, carries, and touches within a single sequence before it ends. A short sequence might be a single long ball into a striker; a long one might involve fifteen or more connected actions across the pitch.
Broken sequence: one that ends without reaching a meaningful attacking outcome — a misplaced pass, a failed take-on, an offside flag. Tracking how often sequences break, and where on the pitch they tend to break, is one of the more direct ways to read a team's technical reliability under pressure.

Classifying Sequences by Directness

Not all possessions attack the same way, and the direct-versus-possession distinction is the most common way of separating them.

A direct sequence covers ground quickly relative to the number of actions involved — the ball moves toward goal in long passing lines or fast carries, with few touches needed to reach a dangerous area. A possession-based sequence instead accumulates many short connections, patiently working the ball through zones rather than around them. Neither is inherently superior; they are different routes to the same destination, and the mix a team relies on is itself a style signature. A team's ratio of direct to possession-based sequences, tracked over a season, describes its attacking identity more precisely than possession percentage alone, since two teams can hold the ball for similar shares of a match while building their attacks in almost opposite ways.

The ratio also changes with game state in ways worth separating out before drawing conclusions. A team chasing a goal late in a match will naturally produce more direct sequences than its season average, simply because time pressure removes the option of patient buildup. Match data published on rubiscore.com is organized so that sequence figures can be filtered by period and scoreline, which matters here — a club's true directness profile is better read from first-half, level-score sequences than from a whole-match average that blends calm buildup with late desperation.

Where Sequences Start and Where They End

Location matters twice in sequence data: where the possession begins, and how far it travels before ending. RubiScore structures this pairing as two linked fields on every sequence record, rather than reporting a single distance-covered figure.

Sequence starting zone: the area of the pitch where a team won the ball that began the sequence. A team that starts most of its sequences in its own defensive third is playing a longer, more patient buildup game than one that regularly starts sequences already in the middle third after a high regain.
Box entry: a sequence outcome where the ball is passed or carried into the opposition penalty area, regardless of whether a shot follows. Counting box entries separately from shots reveals teams that reliably get into dangerous territory but fail to convert that access into attempts — a distinction a shot map alone cannot show.
Final-third entry: a broader marker than a box entry, recording any sequence that progresses the ball into the attacking third. Comparing final-third entries against box entries against actual shots creates a simple funnel, and the size of the drop-off at each stage points to where an attack is losing its threat.
Deep progression: any pass or carry that moves the ball a significant distance closer to goal from a deep starting position, independent of whether it happens inside a recognized sequence boundary. It is a companion metric to sequence tracking rather than a sequence-level statistic itself, useful for crediting individual passers.

Measuring Involvement Within a Sequence

Sequence involvement asks a narrower question than total touches: how many of a team's attacking sequences did a given player actually participate in, and at what point in the sequence did that participation happen. A player heavily involved early in sequences is functioning as a build-up outlet; one involved late is operating closer to the finishing end. The same player can show very different involvement profiles across two seasons without any change in raw touch count, if the team's overall sequence structure shifts around them — which is why involvement figures are read alongside sequence starting zone and sequence length rather than in isolation.

Involvement also separates two players who look identical on a passing chart. A deep-lying midfielder who touches the ball in nearly every sequence but almost always early, and a forward who touches it in far fewer sequences but almost always in the final action before a shot, can post similar total-touch numbers while performing entirely different jobs. Involvement data resolves that ambiguity by tagging where in the sequence — not just how often — a player's touches occur, which is the detail a simple touch count or heat map cannot supply on its own.

Common Misreadings of Sequence Data

Sequence numbers are easy to log incorrectly once they leave the raw dataset, and a handful of mistakes recur often enough to name directly.

Treating sequence count as a proxy for quality. A team can generate many sequences that all break down in the middle third; volume alone says nothing about whether those sequences threatened anything.
Comparing sequence length across leagues without adjusting for pace. Competitions with faster average tempo naturally produce shorter sequences league-wide, so a cross-league comparison of raw sequence length mostly measures the league, not the team.
Ignoring set-piece sequences when computing box-entry rates, or accidentally including them. The two need to be kept separate consistently, or the resulting rate mixes two different attacking mechanisms into one number.
Reading a single match's directness ratio as a stable trait. One game is a small sample; the ratio only becomes descriptive of a team's identity once it is averaged across enough matches to smooth out scoreline-driven noise.

How Sequence Data Relates to Other Advanced Metrics

Sequence metrics are descriptive counts — they record what happened without assigning a probability to it — which puts them in a different family from expected threat and other possession-value models that estimate how dangerous a passage of play was. Field tilt, by contrast, is closely related: it measures a team's share of final-third touches, which is effectively a summary statistic built from where sequences spend their time. PPDA sits on the defensive side of the same picture, describing how many opponent sequences are allowed to progress unchallenged. Reading sequence counts next to field tilt and PPDA gives a fuller account of a match than any one of the three alone, because sequence data shows the shape of the attacking effort while the other two show its territorial and defensive consequences.

Why the Distinction Matters in Practice

Two teams can finish a match with near-identical possession and shot totals while having built their attacks in completely different ways — one through a handful of long, direct sequences that each carried high risk and high reward, the other through dozens of short possession sequences that patiently wore down a defensive block. Aggregate totals erase that difference; sequence-level data preserves it. That is the practical case for tracking sequences as their own category rather than folding them into shot- or pass-based numbers, and it is why platforms such as RubiScore surface sequence and box-entry figures as their own entities within match data rather than as a footnote to the shot map.

Reading the Terms Together

A useful way to hold this glossary together is as three layered questions applied to any attack: where did the sequence start, how did it travel — direct or patient, long or short — and where did it end, whether that is a broken possession, a final-third entry, or a shot. Sequence length and directness describe the middle of that journey; starting zone and box entry describe its edges. None of these terms requires a fabricated statistic to be useful — they are counting and classification exercises applied consistently over many matches, which is exactly what makes them stable enough to compare across a season. Sequence and box-entry data for current matches is published on rubiscore.com alongside the more familiar shot and possession numbers.