Yellow Cards, Red Cards, and Penalties: RubiScore's Match Discipline Data

Match discipline data is the structured record of every booking, sending-off, and spot kick that occurs during a football match — the timestamped sequence of yellow cards, red cards, and penalty awards that punctuates the run of play. RubiScore treats this stream as a distinct layer of the match model, separate from the goals and substitutions, so that the disciplinary shape of a fixture can be read on its own terms rather than inferred from a scoreline.

Why pull cards and penalties out into their own layer?

For most casual viewers, a yellow card is a flicker on the screen and a penalty is a goal in waiting. The discipline events are absorbed back into the broader story of the match as soon as they happen. Pull them out and arrange them by minute and by player, however, and the same set of events starts to read very differently.

The investigative case for separating the discipline layer is that the patterns inside it are routinely buried by aggregation. A match that ends 2–1 with one penalty and four bookings looks, in summary form, much like any other one-goal game. The discipline sequence reveals whether the first booking arrived inside ten minutes, whether both yellows landed on the same midfielder before half-time, whether the penalty came under VAR review or was called on the field. Those details shape the fixture far more than the final score conveys, and they are the kind of evidence that bettors, fantasy managers, and tactical analysts spend a lot of energy trying to reconstruct after the fact.

A discipline layer that is captured cleanly during the match removes most of that reconstruction work. The events are already there, in order, tagged to the players and the referee who authored them.

What counts as a discipline event in the data model?

The match discipline layer on the platform is built around four core event types, each captured as a structured record with a minute, a player, and an authoring official. The intent is to keep the event close to the form in which it was issued on the field, before any post-match interpretation is layered on top.

The events tracked include:

• Yellow cards. Every booking is logged with a timestamp, the player cautioned, the referee who issued it, and a flag for whether it was the player's first or second yellow of the match.
• Red cards. Straight reds and second-yellow dismissals are tagged separately, since the disciplinary weight of the two is different even though both end the player's match.
• Penalty awards. Each spot kick is recorded with the awarding minute, the player who took the penalty (or the player who would have taken it before a retake), the outcome (scored, saved, missed, retaken), and a flag for whether VAR was involved in the decision.
• VAR overturns and confirmations. Where a discipline event was reviewed by VAR, the original on-field call and the post-review outcome are both preserved, so the audit trail of the decision survives in the data.

The data dictionary on RubiScore is explicit about which of these fields appear for which competitions. The top European leagues and the major UEFA tournaments carry the full set, including the VAR audit fields. Competitions further down the pyramid carry the card and penalty events but may lack the VAR layer, depending on whether the governing body publishes a structured review feed.

How are discipline events captured during the match?

A booking is not a separate broadcast feed. It arrives inside the same live event stream that carries the goals, the substitutions, and the corners, but it is tagged differently so that the discipline layer can be filtered out and read on its own.

During the match, the live feed publishes each booking and penalty as a discrete event as soon as the on-field decision is made. The platform writes that event to the match page in real time, propagates the per-player and per-referee aggregates, and exposes the running totals on the live match view. If a decision is taken back to the touchline monitor for VAR review, the original event is held in a provisional state and resolved when the on-field referee returns with the final call. Both the provisional and the final state are preserved.

After the final whistle, a reconciliation pass cross-checks the live record against the official match report published by the competition. The official report is the source of truth for the season-long totals — a card later rescinded on appeal is removed from the player's running count, and a missed booking added by the league is inserted. The live event sequence is preserved as it was witnessed, however, because the timing of a card matters for any analysis of how the match actually unfolded, even if the card itself was eventually struck from the record.

What can a season of card data reveal?

A single match's bookings are too small a sample to mean much. Stretch the discipline layer across a full season and the patterns begin to firm up, particularly when the data is sliced by player, by team, and by the time window in which the cards land.

Three readings tend to be the most informative.

The first is the per-team card profile. A team that picks up most of its cards in the opening twenty minutes is playing a high-pressure defensive style that risks early bookings — a profile that often correlates with a tactical reliance on tactical fouls in the middle third. A team that accumulates cards late in matches is more often defending a result under pressure. The same total card count can mean very different things depending on when the cards arrive, and the timestamped event layer is what makes that distinction legible.

The second is the per-player booking rate, normalised to minutes played. A central midfielder who averages a yellow every two matches is a different proposition from one who picks up the same total over twice as many minutes. The platform's per-player view expresses the booking rate per ninety minutes alongside the raw total, so the comparison can be made on equivalent ground.

The third is the penalty distribution. Penalty awards are rare enough that any single-season sample carries a lot of noise, but across multiple seasons the home-away split, the share of penalties given inside the final fifteen minutes, and the proportion involving a VAR review all settle into reasonably stable patterns at the league level. A team whose penalty profile deviates sharply from the league baseline — far more awarded to them than against them, for instance — is the kind of signal that rewards a closer look at the underlying events.

Where VAR has reshaped the discipline record

The video assistant referee protocol has been the single largest structural change to the discipline layer in the last decade. Cards and penalties that previously stood as final on-field decisions are now subject to a parallel review process, and the data model has had to track both the original call and the post-review outcome to keep the historical record honest.

Three effects show up consistently in the data once VAR is layered in.

Penalty rates have risen in most top leagues since the protocol was introduced, because clear-and-obvious errors of omission — penalties that should have been given and were not — are now caught more often than they were under the on-field-only regime. Red card rates have followed a similar but smaller upward shift for the same reason, particularly for serious foul play and denial-of-goal-scoring-opportunity calls. Yellow cards, by contrast, are largely outside the VAR scope and have moved much less.

The platform keeps the pre-review and post-review states of each affected event so that year-on-year comparisons remain coherent across the protocol's introduction and subsequent refinements. Rubi Score's audit fields make it possible to ask a question as specific as "how many penalties in this competition were awarded only after VAR review last season" without reconstructing the data from broadcast footage, which would otherwise be the only way to recover that breakdown.

Where the discipline data stops short

A clean event record is a powerful tool, but it has firm limits that are worth stating plainly. The data records that a booking was issued, not whether the challenge deserved it. It records that a penalty was awarded, not whether the contact in the box was sufficient. Those judgements belong to the league's disciplinary panels and to the post-match analysis, and the role of the live data layer is to make sure the event record itself is complete and accurate enough that the argument can take place on shared ground.

The same caution applies when the discipline layer is read across competitions. A booking rate in the Premier League is not directly comparable to one in Serie A, because the leagues play to different physical rhythms and the population of fouls they generate differs. Useful comparison is made within a single competition, against the same season's baseline, and across a sample large enough to outlast the noise of any single weekend.

Read with those caveats in mind, the match discipline layer becomes one of the more analytically rewarding entities in the live football model. Cards and penalties are rare enough to feel discrete, frequent enough to carry signal across a season, and consequential enough to shape the betting and tactical markets that build on top of them. The full per-match record — yellows, reds, penalties, and VAR-reviewed decisions, for every match in the covered competitions — is published on rubiscore.com alongside the rest of the football data, so the discipline sequence can be examined match by match rather than waited out until the end of the season.