How to Review a Football Match After Full Time on RubiScore: A Step-by-Step Post-Match Workflow From the Timeline to xG, Lineups and the Table

A post-match review is a short, structured look at a finished game that asks whether the result reflected the performance and what changed the match. On RubiScore, every finished match keeps its timeline, statistics and lineups in one place, which makes a ten-minute review possible without watching the whole game again.

This guide sets out a step-by-step workflow, from confirming the final result to placing it in the league table, followed by common mistakes and a checklist. Match pages, results and standings are available at https://rubiscore.com. The workflow uses only data the RubiScore match page already shows, and it works for a match you watched as well as one you only followed through the score.

What You Need Before You Start

• The match page. The timeline, the statistics and the lineups for both teams.
• The competition table. To place the result in context afterwards.
• A rough pre-match expectation. Which team was favoured, and why. Even a one-line note helps, because a review compares what happened with what was expected.

It also helps to know the competition rules, such as whether extra time and penalties apply, so the final status is read correctly.

Step 1: Confirm the Result Is Final

Check the match status first. "FT" means the match finished after normal time; "AET" means after extra time; a penalty shoot-out result is shown separately and does not change the match score. RubiScore labels these statuses on the match page, so the score you review is the one that counts.

Some statistics are provisional at the final whistle. Data providers often review events after a match, and details such as the scorer of a deflected goal or a shot's classification can be corrected later. A review done the next day is based on more settled figures.

Step 2: Read the Timeline for Turning Points

The timeline lists goals, cards, substitutions and, where used, VAR reviews in order. Read it before any statistics, and mark the moments that changed the match:

• The first goal. It changes how both teams play for the rest of the game.
• Red cards. A team with ten players usually concedes possession and territory.
• Substitutions in clusters. Several changes at once often signal a change of plan.
• Late goals. They can turn a performance-based result into a misleading score.

Dividing the match into phases at these moments makes every later step easier.

Step 3: Read Possession and Territory in Context

Possession and territory figures describe the whole match, but they are shaped by the score. A team that led early may have handed the ball to its opponent deliberately. A team that chased the game will usually show high possession and many touches in the final third.

Ask which team had the ball during each phase you marked in Step 2, not only across the 90 minutes. A 60-40 possession split means something different if the team with 60% was trailing for most of the match.

Step 4: Compare Shots and Expected Goals With the Score

This step answers the central question: did the result reflect the chances?

• Shot totals show volume.
• Shots on target show how often the goalkeeper was tested.
• Expected goals (xG), where available, show the quality of chances.

A team that won 1-0 with lower xG than its opponent may have been efficient, lucky or defended well when it mattered. A team that lost while creating more and better chances has more reason for optimism than the result suggests. One match is a small sample, so treat the comparison as a signal, not a verdict.

Step 5: Look at Where the Chances Came From

Totals hide the shape of the chances. Check whether shots came from inside the box or from distance, from open play or from set pieces, and whether one or two big chances made up most of a team's xG. A team with many long-range shots and low xG struggled to break the opponent down. A team whose xG came mainly from a penalty and one set piece may not have created much in open play.

Step 6: Check Lineups and Changes

Compare the starting lineups with expectations. A rotated side, a missing key player or an unusual formation can explain much of a result. Then link the substitutions to the phases from Step 2. If a team's chances improved after a change, the change probably mattered; if nothing changed, it may have been routine. A substitution made because of an injury, rather than for tactical reasons, deserves a separate note, because it was forced rather than chosen.

Step 7: Note Discipline and Officiating

Cards and fouls tell part of the story. A team that committed many fouls may have been under pressure or deliberately breaking up play. A red card or a penalty decision can shape the rest of the match, so note whether such moments came before or after the decisive goals.

Step 8: Place the Result in the Table

Finally, check what the result means. Did it change the order at the top or bottom? Did it extend a run, or end one? A draw away from home against a strong opponent can be a good result in the table even if the performance data looked unfavourable.

Separating Performance From Result

The most useful output of a review is a short sentence that separates two things: how well each team played and what the score was. They often agree, but not always.

A useful frame is to place the match in one of four boxes. A team can play well and win, which needs little explanation. It can play well and lose, which usually points to finishing, goalkeeping or a single decisive moment. It can play poorly and win, which often comes from an early goal, a set piece or an opponent's error. Or it can play poorly and lose. The second and third boxes are where reviews add the most value, because they are where the scoreline alone is most misleading.

Adapting the Review to Different Matches

The same workflow works for most games, but some matches need an extra question.

• Cup ties with extra time. Split the review into normal time and extra time, because fatigue and substitutions change both teams in the extra period.
• Two-legged ties. Read the match in light of the aggregate score. A team protecting a first-leg lead may have been content to defend, which shapes every statistic.
• Derbies and rivalry matches. Expect more fouls and cards, and be careful about reading discipline figures as a sign of poor control.
• Early-season matches. New signings, new coaches and incomplete fitness make single results especially noisy.
• Matches with a red card. Review the periods before and after the dismissal separately, because they are effectively two different matches.

A Worked Example

Imagine a league match that ends 2-1. The timeline shows the home team scoring early, the away team equalising before half-time and the home team winning it with a goal in added time. The away team had more possession and slightly more shots, but the home team's xG was higher, built mainly on two clear chances inside the box.

The review reads: the home team created the better chances, the away team controlled more of the ball without opening the defence, and the late winner, though dramatic, matched the balance of chance quality. On RubiScore, the timeline, the shot statistics and the table update together, so this reading takes minutes rather than a full rewatch.

Common Mistakes

• Reading statistics before the timeline. Without the turning points, the numbers have no context.
• Treating possession as dominance. It often reflects the score.
• Over-reading one match of xG. Chance quality varies a lot from match to match.
• Ignoring set pieces and penalties. They can make up a large share of a team's xG.
• Reviewing too early. Some data changes after the final whistle.

A Ten-Minute Checklist

1. Confirm the final status: FT, AET or penalties.
2. Mark the turning points on the timeline.
3. Read possession by phase, not only overall.
4. Compare shots, shots on target and xG with the score.
5. Check where the chances came from.
6. Link substitutions and lineups to changes in the match.
7. Note cards, penalties and key decisions.
8. Place the result in the table.

Used in this order, the workflow turns a scoreline into an explanation. The match page on RubiScore holds every piece of data the checklist needs, and the order matters more than any single number: context first, statistics second, conclusions last.