The Scoreboard Stops; the Spreadsheet Doesn't

September 28, 2026. Dubai International Stadium. The Asia Cup final. India 223 all out, Bangladesh 222 — India champions by three runs. The television camera froze on the final ball, Mustafizur Rahman run out going for the second. The stadium scoreboard stopped on that single number, and the highlights package spent the following week replaying it.

On my laptop a file stayed open. Liton Das's 121 sat there not as one row but ball by ball. Bangladesh's run rate across the last ten overs in its own column, Kedar Jadhav's final-over length map on a separate tab, Liton's shot map as a wagon wheel. The broadcast stopped because the cameras were done. The spreadsheet didn't, because the question wasn't.

Seven years on I still open that file. Those three runs say less about Bangladesh's batting than about a quiet gap in Asian cricket analysis — where data is plentiful and the habit of reading it is thinnest.

Context: Collection Complete, Interpretation Missing

Bangladesh cricket does not lack data. The BCB performance unit has kept ball-by-ball logs for years; Hawk-Eye sits in domestic venues; GPS vests feed back from Under-19 and A-team series. The files accumulate. Reading them does not.

The simplest evidence is verbal. Television panels say almost every series that "Bangladesh's powerplay is weak." True, and half the story. A low powerplay run rate has at least two different causes — wickets lost, or a deliberately cautious start. The first is solved by batting order, the second by intent. The scorecard shows both identically, and so the decision usually goes the wrong way.

In September 2026 I stumbled into exactly this in Manchester. On the 9th, Manchester City beat Liverpool 5-0 — the match after Sadio Mané's 37th-minute red card. I was hand-logging a pressing sheet for all 20 Premier League clubs, every match, every pass-allowed-per-defensive-action. In that single fixture it showed City at 12.4 before the card and 6.8 after. The scoreline cannot be explained by City's strength alone, because half the story of that scoreline was the card.

That sheet changed my working language. Match-ball data is not the story of a match; it is the raw material of one. Turning raw material into a story needs context — the pitch, the weather, the state of the innings, the bowler's age, the travel fatigue. In Asian cricket that context changes fastest, which is exactly why interpretation carries the most weight here. And it is exactly what gets ignored.

Core: What Phases Say and Heatmaps Hide

I read a limited-overs innings in four blocks — powerplay (1-10), middle (11-30), acceleration (31-40), death (41-50). Two separate questions per block: what was the run rate, and what share of runs came in boundaries. Run rate tells you how fast the innings moved; it does not tell you whether it was controlled. Boundary share fills that gap.

In Asian conditions this split matters more, because spin's over-share is far higher than in Europe. So a batter's single "middle-overs run rate" figure is not merely unhelpful — it is unhelpful for a structural reason: it does not say how many spinners were bowling, how much the ball turned, or how deep the field was. The same strike rate of 70 is two entirely different jobs in Chattogram and Manchester.

This is where the heatmap cheats. On a television screen a batter's shot map glitters, but the map does not say which ball came in the death overs and which in the powerplay, which in a won match and which in a lost one. The map hides a player's role and shows only his imprint. It is the new version of an old error — reading tea leaves; what is visible is not an explanation.

While watching, I keep two columns in my notebook: ball-by-ball log on the left, and on the right the context of that ball — match state, required rate, who is bowling at the death. Years of watching build one habit: statistics tell me where to look, never why.

In franchise cricket this distinction lands directly on money. Asian league auctions are often priced on highlights — one good innings, one spectacular catch, one viral strike rate. Put the same player's three-year phase data alongside and the picture changes. Someone may be excellent in the powerplay and slow at the death: gold as an opener, a poor investment as a finisher. Auction tables sell those two roles at one price every season.

Asian conditions add another layer: the gap between domestic and international data. A bowler with a 6.8 economy in the Dhaka Premier League can concede 9.4 in international T20 — because the standard of the batter in front, the fielding, and the pressure all jump at once. The auction model has no room for that jump, and franchises carry the error for years.

Bangladesh's bowling workload is read the same way. For a left-arm pacer like Mustafizur Rahman, a continuous franchise season, then a home bilateral series, then another league — the fatigue of that cycle never shows in a single series economy. It shows in a six-month average. For multi-format players such as Shakib Al Hasan and Mushfiqur Rahim, selection should follow the number produced by combining all formats, not the form of the last match.

Contrarian: Correlation Is Not Causation

My greatest fear here is in my own work. Data can tell any story, and when the story is elegant the urge to verify it drops. Someone will say: "In matches where Bangladesh passed 50 in the powerplay, they won 70 percent." Sounds superb. But direction is hidden inside: good teams play on good pitches, and good pitches make powerplay scoring easier. Powerplay runs are not the cause of winning; both are the consequence of the pitch.

This is the trap that breeds heatmaps and viral charts. My fix is simple — pre-register the question, then look at the data. Decide in advance what would change my mind. Otherwise I start building a story to fit what I found, and the table goes blind in the same way pundits do.

The second caution is specific to Asia. The analytical frameworks that work in European leagues — pressing, possession, half-spaces — cannot be lifted wholesale into Asian domestic cricket. Resources are thinner, video operators fewer, domestic camera coverage incomplete. Where ball-by-ball data does not exist, honesty means staying silent about that player rather than inventing a number to fill the gap. Moving from Bangladesh to Manchester taught me this: you can import the method, never the conclusion.

Takeaway

I do not dismiss the broadcast. Bangladesh's commentators are the sound of my childhood — some of them broadcast a match's nervous system in public, which no table ever will. The spreadsheet did not interrupt the broadcast; it simply outlasted it.

If there is something to look for next season, look not at the first ten overs but at the 31st to 40th. Asian sides still treat those ten as "the middle," and that is precisely where the real difference is written. The question is not Jadhav's final over; the question is who was keeping the accounts on the way to it.