How to Analyze xG in Match Reports: A Tactical Guide for Smarter Football Analysis

You’ve just finished watching a match where the underdog created three clear chances but lost 1-0, while the dominant side had twenty shots but only scored from a deflected free kick. The scoreline says one thing, but your gut tells you something else entirely. That’s where Expected Goals (xG) comes in—not as a magic number that predicts the future, but as a tool to separate process from outcome. In this how-to guide, you’ll learn how to read xG data in match reports, combine it with tactical context, and avoid the common pitfalls that lead to misleading conclusions. Whether you’re writing for a blog, analyzing for a podcast, or just trying to understand the game deeper, these steps will make your match analysis sharper.

Step 1: Understand What xG Measures—and What It Doesn’t

Before you dive into any match report, you need to know the basics of the Expected Goals model. xG assigns a probability score (from 0 to 1) to every shot based on factors like distance to goal, angle, body part used, type of assist, and defensive pressure. A shot from six yards out with the goalkeeper off balance might have an xG of 0.8, meaning it would be scored 80% of the time by an average player in that situation. A long-range effort from 30 yards with defenders closing down might have an xG of 0.02.

What xG does well:

• It quantifies chance quality, not just quantity.
• It smooths out short-term variance (like a goalkeeper having a world-class game).
• It helps identify teams that are creating high-quality chances consistently.

What xG doesn’t do:

• It doesn’t account for shot placement or goalkeeper skill perfectly (though advanced models adjust for this).
• It doesn’t measure defensive blocks, last-ditch tackles, or tactical fouls.
• It doesn’t predict the exact score—it only describes the likelihood of scoring from the chances created.

When you read a match report that says “Team A had 2.1 xG to Team B’s 0.8,” you know Team A created better chances. But if the final score is 1-1, you need to ask: did Team B’s goalkeeper make exceptional saves? Did Team A miss clear-cut opportunities? Was there a penalty that boosted xG? Context is everything.

Step 2: Pair xG with Shot Maps and Shot-on-Target Data xG alone is a number. To make it useful, you need to see where the shots came from. Most modern match reports include a shot map—a visual representation of every shot with its xG value. Combine this with shots on target (SoT) data to understand finishing efficiency.

In this example, Team A outperformed their xG by a small margin (+0.2) but Team B underperformed significantly (-1.1). The shot map might show that Team A’s chances came from central areas inside the box, while Team B’s came from tight angles or long range. The 1-1 scoreline flatters Team B—they were outplayed in chance creation but scored from a low-probability situation. For a match report, this is gold: you can argue that Team A’s process was better, even if the result didn’t reflect it.

Action step: When writing a match report, always include xG per shot (average quality per attempt). A high total xG with low xG per shot means volume over quality—think twenty long-range efforts versus five high-quality chances.

Step 3: Contextualize xG with Tactical Factors xG doesn’t exist in a vacuum. A team that plays a 4-3-3 Formation with high pressing might generate high xG from counter-pressing turnovers, while a 4-2-3-1 Formation might rely on set pieces and crosses. A 3-5-2 Formation often creates chances from wing-back crosses and second balls. The tactical setup directly influences the types of chances a team creates.

Key contextual questions:

• Was there a red card? If a team plays with ten men for 60 minutes, their xG will be suppressed. Compare per-minute xG instead.
• Was the match played in poor weather? Rain, wind, or snow reduces shot accuracy and xG values.
• Was it a cup final or a league game? Teams often play more conservatively in high-stakes matches, lowering xG totals for both sides.
• Did the game state change early? An early goal alters the tactical approach—the leading team may sit back, inflating the opponent’s xG from low-quality chances.

For example, in a recent Premier League match, a team playing a 4-3-3 Formation had 1.8 xG in the first half while pressing high and winning the ball in advanced areas. After going 2-0 up, they dropped into a mid-block, and their second-half xG dropped to 0.4. The final xG of 2.2 looks impressive, but the tactical context reveals a team that dominated early and managed the game late. A smart match report would highlight this split.

Step 4: Compare xG with Possession and PPDA to Find Patterns

Possession percentage can be misleading. A team with 65% possession might have 1.2 xG, while a counter-attacking team with 35% possession might have 1.5 xG. This is where PPDA (Passes Per Defensive Action) becomes useful. PPDA measures how many passes a team allows the opponent to make before making a defensive action (tackle, interception, foul). A low PPDA (like 6-8) indicates high pressing intensity; a high PPDA (like 15-18) suggests a deeper defensive block.

Here, Team A had more possession and pressed harder (lower PPDA), but Team B created better chances (higher xG). Why? Team A’s high press might have been disorganized, allowing Team B to play through it and create high-quality chances from counter-attacks. Alternatively, Team A’s possession might have been sterile—passing sideways without penetration. The combination of xG, possession, and PPDA tells a story that possession alone cannot.

Action step: In your match report, create a small table like the one above. Then write a paragraph explaining the tactical narrative. For example: “Despite dominating possession and pressing aggressively, Team A’s low xG per shot (0.08) suggests their attacks lacked incision. Team B, sitting deeper and absorbing pressure, created three clear-cut chances from transitions, reflected in their higher xG per shot (0.18).”

Step 5: Use xG Accumulation Over a Season, Not Just One Match

One match is a sample size of one. Variance is high—a team can have 3.0 xG and lose 1-0, or have 0.5 xG and win 2-0. To make meaningful claims, look at xG over a longer period. A team that consistently outperforms their xG (scoring more than expected) might have elite finishers or a world-class goalkeeper. A team that underperforms might be due for regression.

Checklist for seasonal xG analysis:

• Compare xG difference (xG for minus xG against) to actual goal difference over 10+ matches.
• Look at xG per match trend: is the team improving or declining?
• Check xG against shot-on-target conversion rate: a team with high xG but low SoT% might be taking low-quality shots.
• Use /expected-goals-xg-season-review to see how xG correlates with final league position over multiple seasons.

For example, a La Liga team with an xG difference of +0.8 per match but a goal difference of +0.2 might be underperforming. If their shot-on-target accuracy is below league average, they might need better finishers or tactical adjustments. If their goalkeeper’s save percentage is unsustainably low, they might improve without changing anything.

Step 6: Avoid Common xG Misinterpretations

Even experienced analysts make mistakes with xG. Here are the most common traps:

• “xG predicts the score.” No, it describes the quality of chances created. A 2.5 xG team can lose 1-0.
• “Low xG means a team played badly.” Not always. A team might have a tactical plan to limit the opponent’s chances while creating few of their own (e.g., a 1-0 win with 0.5 xG).
• “xG is the same for all players.” No. Finishing ability varies. Erling Haaland converts chances at a higher rate than the average player, so his personal xG might understate his actual threat.
• “You can compare xG across different models.” Different providers (Opta, StatsBomb, Understat) use different models. Always note the source.

Action step: When citing xG in a match report, add a caveat: “Based on Opta’s xG model, which accounts for shot location, assist type, and defensive pressure. Individual finishing quality may vary.”

Step 7: Write the Match Report with xG as a Supporting Tool, Not the Star

The best match reports use xG to support tactical observations, not replace them. Start with the tactical narrative: “Team A’s 4-2-3-1 Formation struggled to break down Team B’s compact 5-3-2 block.” Then bring in xG to quantify: “Team A’s xG of 0.9 from open play reflects their inability to create central chances—most of their shots came from outside the box (0.05 xG per shot).” End with a conclusion that ties everything together: “The 1-0 scoreline flatters Team A, who were out-chanced 1.8 to 0.9 in xG. Team B’s counter-attacking approach, combined with a clinical finish, was the more effective strategy on the night.”

Final checklist for your match report:

• Include total xG and xG per shot for both teams.
• Add a shot map or describe shot locations.
• Contextualize with tactical factors (formation, game state, weather).
• Compare xG with possession and PPDA.
• Avoid overinterpreting one-match data.
• Use xG to support, not replace, tactical analysis.

Conclusion: xG Is a Lens, Not a Verdict

Expected Goals is one of the most powerful tools in modern football analysis, but it’s only as good as the context you bring to it. By pairing xG with shot maps, tactical formations, pressing metrics like PPDA, and seasonal trends, you can write match reports that go beyond the scoreline. Remember: the goal isn’t to prove that xG is “right” or “wrong”—it’s to understand why the game unfolded the way it did. Use the checklist above, stay skeptical of single-match data, and always ask “why” before “what.” Your readers—and your analysis—will be better for it.

For deeper dives into related metrics, check out our guides on /expected-assists-xa-in-tactical-context, /shots-on-target-accuracy, and /possession-percentage-and-outcome.