No Scorecard, No Claim: The Real Risk in Cricket Analysis Is the Information Gap

In the 34th over of a match last season, a colleague sitting beside me said the momentum had shifted. I asked which over, which bowler's run-up, which corner of the field had moved. No answer came. That silence is the subject of this piece. A large share of the technical claims we make about cricket every day rests on memory and instinct rather than clips and timestamps. Since my days on the coaching staff at Liverpool I have kept one rule: every tactical claim must carry two film clips and one number. In cricket that rule is harder to keep, because every ball builds a small match of its own, and behind every decision sit a bowler's fatigue, a captain's hesitation and a pitch's mood. Still, without the rule, analysis collapses into a pile of commentary.

Context: the clock of the format

The first condition of cricket analysis is knowing the format. Test, ODI, T20 and The Hundred are all cricket, but their clocks differ. In Test cricket time is an ally against the opposition; in ODIs time must be spent in stages; in T20 time is the opponent. A strike rate of 130 was outstanding in a 2026 ODI, is middling in a 2026 T20, and is close to meaningless in a Test. A bowler's economy of 8 is acceptable in T20 and ruinous in a Test. The Hundred changes the arithmetic again: a 100-ball innings, a maximum of 20 balls per bowler, five-ball sets. In that structure the length of a spell and the distribution of the closing overs must be planned completely differently.

A technical decision made without knowing the format is a set of directions on the wrong map. Take one example. A batter who makes 60 from 70 balls to chase 350 in an ODI has won his side the game. Put him in the same role in a T20 and the side loses, because 70 balls is nearly half the innings when the requirement was 45 from 25. The same innings, read in two formats, gives two results. This is why I never carry a number from one format into another; the first boundary of transfer-fit sits here.

Venue is the second variable. A venue is not a backdrop; it is an active variable. In October 2026 at Mirpur, Bangladesh beat England by 108 runs, and Mehidy Hasan Miraz, on debut, took 6/80 in the first innings and 6/77 in the second for 12 wickets in the match. Exactly one year later, in August 2026 at the same Mirpur ground, Bangladesh beat Australia by 20 runs, with Shakib Al Hasan making 84 in the first innings and taking 10 wickets in the match. Both results were historic; both came at the same ground. But if those two results are used to argue that Bangladesh's spin attack is equally sharp in all conditions, the analysis goes wrong. The bounce and drift Mirpur gives a left-arm spinner do not exist in Perth or Leeds. Home data very often hides away weaknesses; it is the most common trap I see.

Core analysis: sample, luck and the geometry of role

You cannot draw a career conclusion from 42 balls in one innings. Five wickets in one spell means the bowler was outstanding; that simple reading has done more damage in cricket than almost any other. Two of those five may be tailenders, one may follow a dropped catch, and one may be the product of haste in a rain-shortened game. I look instead at three different things: the spread of lengths, the repeatability of the release point, and the distance created in the batter's footwork. Together they tell you whether the bowler was in control or the scorecard was simply on his side.

Without a separation between result and process, analysis becomes a translation of the scoreboard. At Edgbaston in 2026, England beat Australia by two runs in one of the great Tests. But that two-run margin says more about luck than process: an edge, a no-ball, a review. At the 2026 World Cup final the match was tied and the winner was decided by a boundary count; the rule has since changed, but the analysis of that night is still written in the language of the scoreboard. DLS is a larger example. The method introduced in 2026 was revised in 2026, yet statistics from rain-shortened matches are still routinely judged against full-match benchmarks. The toss is the same trap: a side that wins four Tests after losing the toss cannot be assessed properly unless the toss effect is stripped out.

In player evaluation I separate three layers. The first is the age curve: a fast bowler's pace peaks between 28 and 32 and then declines, while a spinner's control improves after 30. The second is workload: Shakib Al Hasan has played three formats for nearly two decades, which is proof of his ability and at the same time a ledger of debt accumulated in his body. The third is format specialisation: a batter who is excellent in Tests is not automatically a T20 finisher.

A player's role does not determine his statistics; the context of his statistics determines his role. Here I borrow an idea from football, but with limits. In July 2026 in Kazan I sat with a stopwatch measuring how far Argentina's defensive line dropped during France's 4-3 win; Kylian Mbappe did not outrun Argentina, he redrew the distance between the lines. The cricket equivalent is the ring of the field: the real way to dismiss a batter is often not his shot but the size of the empty space around him. The equivalence ends there, because cricket produces a new decision every ball while football produces one in a passing sequence. Ignore that difference and the analogy becomes decoration.

In the world of leagues and commerce, this role map is lost even more often. A franchise buys a batter at a premium at auction, yet that batter has never batted at number three, the role he was bought for. The price is built from a narrative, not from a role map. This narrative, manufactured by agents, is cricket's most invisible cost: it sets the market price while its relationship to the team's need is often zero. I do not judge a player by his auction price; I look at how many balls he has actually played in that specific role, on which fields, against which bowlers.

Governance follows the same logic. Since being appointed in 2026 as one of three advisors to the Bangladesh Cricket Board, overseeing digital and media affairs, I have seen more clearly that scheduling, central contracts and the league-versus-national-team conflict cannot be read separately from performance. Why a bowler suddenly loses two kph may have a simple answer: six matches in four formats across three weeks. DRS controversies need the same treatment. Introduced in 2026, the system has improved the transparency of decisions while moving umpiring debate to the centre of the post-match narrative.

Contrarian: more data has not made analysis better

The intuitive view is that more information means better analysis. My experience says the opposite. More data has made bad analysis faster. Anyone can now join three graphs into a narrative, and that narrative needs no clip. Our real blind spot is that we treat missing information as neutral, as though no information means no risk. Missing information means the risk is unknown, not zero. Without an injury record we assume everyone is fit; without a pitch report we assume a neutral surface.

The second blind spot is executive. We prepare for the clip we expect, and the match usually turns on a different one. As coaching staff I have watched plans built at the interval around the opposition's main weapon, only for the decisive moment to arrive from a small habit at the third level: consistency on leg stump instead of a wide yorker. The press is not a sprint; it is a conversation held in five-yard increments — and the first sentence of that conversation is often unheard, because we have the camera ready for the second.

Takeaway

In the next match, watch one thing and not the scorecard. See where the dot balls cluster between overs 20 and 30, and which ring of the field is moved in the very next over. If the dot-ball cluster and the field change do not connect, the pressure everyone is describing is probably imagined. I have seen this cycle before; it just wears different boots. So the question is simple: are you explaining the result, or the process?

Sidebar: what the analysis file must contain

My own template has four boxes, and if any one is empty I do not write a conclusion. The first is format and competition; the second is venue and weather, including the DLS possibility; the third is sample size — how many innings, how many balls, over what period; the fourth is the luck component — toss, dropped catches, reviews. Without those four boxes filled, what gets written is not analysis but guesswork. A report written over empty boxes reaches readers quickly but loses their trust over time. In cricket, trust once broken takes many seasons to return.

Sidebar: three numbers I always read together

First, dot-ball percentage, which tells you whether the bowler was in control. Second, strike rotation, which tells you whether the batter could get off strike. Third, the number of field changes, which tells you how quickly the captain was reading the situation. Read alone, any single statistic usually tells a false story.