Behind the Scoreboard: The Eight-Layer Framework of Cricket Analysis

Behind the Scoreboard: The Eight-Layer Framework of Cricket Analysis

The biggest lesson of my professional life came from a number that had nothing to do with cricket. On 6 December 2026, Liverpool beat Spartak Moscow 7-0 in the Champions League. That night, the scoreline was the only story in the media; Mohamed Salah scored twice. But the dashboard I built after the match told a different tale: Liverpool generated 5.1 xG and their passes-per-defensive-action stood at just 6.8 — meaning that after losing the ball, they won it back within roughly seven passes. That single number said what the 7-0 could not: this was the victory of a pressing system, not merely a display of individual skill. I built the xG/PPDA dashboard, and Liverpool used it to sharpen their pressing cycle the following season.

That thread reached 2.4 million impressions, and I realised that data storytelling had commercial value. As an ENTJ, I decided quickly: every piece would open with a decisive number, not an anecdote. But that is exactly where my real problem began. I came from cricket — I joined The Daily Star sports desk as a cricket reporter in 2026, then moved into the BCB media setup. Football dashboards were new to me; cricket was my mother tongue. Yet cricket analysis was still stuck in an old mould: runs, wickets, averages, strike rates. The question arose: can the controlled, layered analysis of football be applied to cricket?

From years of watching matches, sitting behind the camera, and scraping scorecards, I reached a conclusion: cricket analysis is not a matter of a single number, but a structure of eight layers, where each layer determines the meaning of the next. In this piece I will open up those eight layers. But a warning first: no framework replaces the truth; it only clears the path towards it.

Why the Scorecard Alone Is Not Enough

A scorecard is an aggregate outcome, the final image of a process. It tells you who won, but not how they won — and that "how" is the forecast for the next match. Two Test innings of 400 look identical, yet one rests on patient blocking and the other on aggressive counter-attack. In the next match, the two teams' risk profiles will be entirely different. To capture that difference, cricket must be divided into eight layers: format and match construction, player technique, team landscape, league and commercial ecosystem, rules and governance, risk, public narrative, and industry transmission. Each layer answers a different question, and together they form a decision.

I have built a translation layer between football's continuous-flow model and cricket's discrete-event logic. In football, pressure is measured by PPDA — the lower, the more intense. In cricket, the equivalent of that intensity is the density of the fielding ring, the speed of bowling changes in the powerplay, and the reliance on spinners in the middle overs. The logics of the two games are not identical, but the question is: is the team imposing its own will, or merely reacting to the opponent's decisions? I never make this translation mechanically — each time I state clearly which mechanism transfers and which does not.

My method has a specific discipline: first raw data collection, then format adjustment, then situational splits, and finally a confidence tier. At each step I ask myself — what can this number prove, and what can it not prove? Data analysts are now invading dressing rooms, and their conclusions often detach from the actual rhythm of the match. The only way to avoid that detachment is the habit of interrogating the framework.

One: Format and Match Construction

The first layer is the most neglected. Test, ODI and T20 — the statistics of these three formats are not directly comparable, because their time budgets and risk calculations differ. In a Test, an unbeaten 30 is valuable; in a T20, that same 30 may lose you the match. I have tried to build a format index in which each innings is measured against the median of its own format, not raw runs. Venue matters here too: 250 on a spin-friendly pitch is not the same as 250 on a flat deck. Dew, wind and the DLS-revised target — these environmental factors alter the result so much that the raw scorecard becomes almost meaningless. The toss is a special problem: many analysts dismiss it as "luck," yet at a dew-prone venue the toss nearly determines the second innings' batting conditions. To make a number meaningful, we must first know which box the number sits in.

Two: Player Technique and Data

In the second layer I put the individual at the centre. Here I look at four things together: raw average, situational splits (home/away, spin/pace), recent trend, and the age curve. I tracked Luka Modric across seven matches at the 2026 World Cup — he covered 63.2 km, completed 484 passes and created 17 chances. But the numbers alone say nothing unless we know against whom and in what match situation. A century when the team is 300 behind carries a different weight from one when the team is on the brink of victory. In cricket this situational adjustment is harder, because play stops every ball. A batter's strike rate must be read alongside his role: an opener's duty differs from a finisher's. For an all-rounder like Shakib Al Hasan, the value varies so much by format that a single average can never capture his true contribution. Recognising the inflection point of the age curve is the hardest task of this layer, because form and decline look alike.

Three: Team Landscape and Ranking

The third layer looks at the team. The ICC ranking is a beginning, not an end. Ranking tells you who is consistent, but not who collapses under which conditions. I divide team structure into four parts: batting depth, bowling combination, bench depth, and age structure. A team's true strength shows in the average of its sixth or seventh batter, not in the names of its top three. Matchup history is decisive here — who gains a stylistic advantage over whom. England's aggressive batting philosophy works against Australia, but on a slow pitch against a spin-heavy side that same philosophy becomes a trap. Bench depth makes the biggest difference in a long tournament; anyone who thinks only the first XI wins matches will understand the error in the third week of a six-week tournament. I have also learned from the model of how home advantage drops in empty stadiums that part of a team's strength actually hides in the crowd-pressure equation.

Four: League and Commercial Ecosystem

In the fourth layer I step outside the game. IPL broadcast rights, franchise valuations and player salaries now shape the course of the game. The price at an auction reflects not just a player's recent form but his market utility — jersey sales, tickets, digital assets. It is here that blockchain-based fan tokens, fantasy leagues and sports digital assets have added a new layer: spectators are becoming direct economic stakeholders. I do not treat this as a sideshow. When a franchise's broadcast value exceeds the annual budget of a small national board, tension between league and national team is inevitable, and that tension reshapes selection policy. Player agents are the least-discussed but most influential force in this market; the rumours they spread distort price-setting, and that distortion ultimately decides a franchise's fate.

Five: Rules and Governance

The fifth layer is a question of power. Who gets the revenue, who takes the decisions, and whose interests do the rules serve? DLS revisions, DRS, the impact player, and the mega-auction RTM card — behind every rule sits a political compromise. In governance analysis I look at five things: power distribution, rule controversies, integrity and corruption risk, eligibility and selection, and geopolitics. Cricket today is no longer just a game on 22 yards; board politics, broadcast auctions and boycott controversies also influence match results. A rule change is never neutral — it always benefits someone, and that beneficiary is usually the party with the greatest hand in rule-making.

Six: Risk Calculation

The sixth layer looks forward. Risk comes in six types: sporting (form slump, injury), personnel (coach change, dressing-room discord), commercial (sponsor withdrawal), rules-related (sanctions, bans), public opinion (media pressure), and systemic (schedule overload). To gauge a team's true potential, I place each risk on two axes — likelihood and impact. For Bangladesh, the long-standing systemic risk was schedule pressure and bowling injuries; overcoming it was their biggest strategic achievement. The real job of risk analysis is not to scare, but to draw the line between which risks are controllable and which are not.

Seven: Public Narrative and Expectation

In the seventh layer I measure the market's belief. The gap between expectation and reality is the biggest opportunity. When the media declares a team "invincible," how much does that narrative rest on fundamental data? I look at how many matches' data support the narrative, and how far expectation has inflated. In cricket this gap is often dangerous: a new star is turned into "the next great batter" after two or three innings, while small samples are dangerously deceptive. The hotter the expectation, the harder the correction. In this layer I also watch sentiment indicators: when the distance between fan excitement and fundamental statistics grows, the risk of a crash grows with it.

Eight: Industry Transmission

The eighth layer views the whole industry as a supply chain: upstream, youth development and talent supply; midstream, national teams and leagues; downstream, broadcast, commercial and derivative markets. A rule change or a corruption scandal sends ripples from one end of this chain to the other. The South Asian heartland is the most sensitive part of this chain; there, a star's form slump shakes broadcast ratings, ticket sales and fantasy-platform activity alike. Without understanding this layer, no one can ever explain why a team depends more on what happens in the boardroom than on what it does on the field.

Where the Model Goes Wrong

So far I have spoken of eight layers as if the framework were complete. But honesty demands this: correlation is never causation. A team's win and its high intensity may be related, but that does not mean intensity is the cause of the win. A team can win through the opponent's error, the toss, the dew, or the mathematical kindness of DLS. I fell into this trap once — after a match, reading the tracking data, I concluded that a particular bowling change had turned the game, yet over the next five matches that same change made no difference. That was my biggest warning.

Small samples are data analysis's greatest enemy. One century or one five-wicket haul is never proof. I now write a confidence tier beside every conclusion — high, medium, low — and note the condition under which it would be falsified. To believe raw numbers without stripping out venue bias and luck factors is to deceive yourself. I built the xG/PPDA dashboard, and Liverpool — but I admit every time that the dashboard is a snapshot of football at a particular moment, not eternal truth. An analyst who does not know a model's limits becomes its slave, and that is exactly when analysis detaches from the rhythm of the match.

What You Will Watch in the Next Match

Before you read the scorecard in the next match, ask one question: in which format, in what conditions, at what stage of the match did these runs or wickets come? If you do not know the answer, your analysis has not yet begun. The next chapter of cricket will be written by the team that learns to read all eight of its layers together — not just the scoreboard, but what lies behind it. The question remains for you: are you watching the game, or merely reading the result?