The Scorecard With No Numbers: A Lesson in Analytical Honesty

After the rain, a scorecard lay in the press box in Chattogram. Nobody picked it up. The paper had gone soft, ink had bled into one corner, and it was exactly in that wet corner that the innings figures had dissolved. I lifted it and spread it flat on the table. The empty boxes survived—thin black borders, each one waiting for a number, and no number coming.

A week later a piece of analysis reached me, and its architecture looked precisely like that wet scorecard. Eight large sections, a dozen subheadings, tables, ratings, a risk register—and inside it, row after row of 'insufficient information'. No player named. No team. No venue. No date. One label had survived: cricket, region Asia.

I looked at those empty boxes for a long time. They were not mistakes. They were the most honest sentences of that day.

Cricket is a game where you cannot speak without numbers, and where speaking only with numbers turns into lying. That gap between the two is where my work lives. I learned the game from a touchline where every shout became a scene—someone shouting from behind the stumps, someone shouting from under the scoreboard, and those shouts were my first textbooks.

In 2026 I played in the Dhaka league for Udity Club as an opening batter and wicketkeeper. Behind the stumps you learn something no scorebook records—the height of the ball, the batter's hesitation, the bowler's breathing. The scorebook does not hold any of it; the scorebook holds only outcomes. That was when I understood that what is written in a scorebook is a record of events, not an explanation of them. I went on to coaching, then to analytical writing, and that plain truth has not changed.

In our part of the world, cricket's numbers live in tea stalls. The scroll runs under the television, a fantasy league advertisement sits beside it, and the table argues—who is good, who is good at the death, who breaks under pressure. Those arguments are beautiful; they are what keeps the game alive in a society. But when the foundation of the argument is laid in the wrong frame, the beautiful argument becomes the most dangerous lie in the room.

In cricket, format is the first door; without opening it you cannot enter any room beyond. Test, ODI and T20 rest on fundamentally different logic. Test cricket is patience against the new ball, the arithmetic of breaking an innings across five days. ODI cricket is the craft of control between two new balls, the discipline of drying up runs through the middle overs. T20 cricket is a budget of a limited resource split into three phases, where powerplay, middle and death each use a different currency. The same bowler with the same economy rate is three different people across three formats.

A strike rate of 145 is elite in ODI, ordinary in T20, and close to meaningless in Test; an economy rate of 8.5 is catastrophic in Test, acceptable in ODI, and roughly par for a T20 death bowler. An analyst who quotes these numbers without first establishing the format is not merely getting a number wrong—he is dragging that number out of its own country and sending it into exile. After that, the number will serve any story, because it no longer has a home.

Here is the second problem. Asia is a region, not a competition. An Asia Cup fixture, a bilateral series between two Asian sides, a night at an IPL auction, and a governance decision by the Asian Cricket Council are four entirely different stories with four entirely different analytical routes. The first is a story of play, the second of relationships, the third of money, the fourth of power. A single label cannot hold any one of them.

The transfer window is not a market; it is a rumour with a heartbeat. A price rises in an auction room, and that price is not evidence of a player's strength in international cricket—this is the game's oldest error, committed afresh every season. But even to write that sentence you need a name, a contract, a figure. Without a name there is no analysis left, only opinion.

A null result is not a failure; it is a result—provided you label it as one. The report's very structure was its biggest trap. Eight sections, a risk matrix, ratings, scenario projections: that many labelled boxes make the hand itch. There is a natural pleasure in filling a blank, and that pleasure is the danger. Because whatever gets placed in a blank box looks tidy, sounds credible, and is entirely invented. An invented strike rate, an invented auction premium, an invented injury concern—all three come off the same assembly line, and the factory is called 'perhaps'.

The distinction between result and process matters here. A team wins because of a toss advantage, because a catch goes down, because a DLS calculation falls its way; and we write it up as 'a new force'. One century in a single-match sample and a player is declared 'back in form', and that sentence circulates for three months. The gap between a team's home average and its away average is one of the widest in cricket and among the least mentioned. None of these cautions arrive by themselves—they all require a format, a venue, a sample before they can be placed inside any framework.

One thing is worth holding on to. Cricket's statistical archive is a ledger, and the greatest virtue of a ledger is verifiability. Who wrote what, in which format, at which venue—if that metadata does not travel with the record, the number stops being evidence and becomes decoration. The property the blockchain world celebrates as an immutable record is exactly the property cricket's archive needs, not as technology but as habit. If a scorecard can state who wrote it, when, and from what source, the road in for a falsehood narrows considerably.

The empty stadium taught me that absence has a sound. In 2026 I sat for hours in the abandoned Chattogram Abahani ground and recorded the thud of the ball, the shouts of twenty-two men, the lonely echo of a single goal. The hush between Eriksen taught me the same thing—silence is not empty, silence is information. A shortage of information is itself information, if you have the nerve to admit it.

Now the other side. We usually assume the problem is bad data. I think the problem sits elsewhere—in narrative pressure. There is a market for hot opinion, where something must be said daily and some name must be attached to a declaration. In that market, saying 'I do not know' is close to professional suicide. But an analyst who never says it gradually devalues his own 'I know'.

There is a blind spot we all share. We believe more data means more truth. More data means more numbers, and more numbers means more opportunity—the opportunity to pick a convenient number and tell a convenient story. We do not remember scorecards; we remember a sentence. Collective memory will always choose the story over the empty box. That bias is the least discussed of all, because it is about us.

The next time someone shows you a number and tells you a story, ask three questions. In which format? On what sample? From which source? If the answers do not hold, you need not throw the number away—just put a label beside it reading 'unverified'.

I do not chase trophies; I follow the quiet arcs between them. Those arcs explain why a team loses, why a player stalls, why an archive empties out.

When the rain stopped I did not throw the scorecard away. I folded it into my notebook. The empty boxes are still looking for a number, and I still do not know what it is. There is no shame in not knowing—far less shame than in pretending to know.