From an Empty Shelf to a Full Ledger: How the Invisible Layer of Cricket Data Is Built

I started with a pencil, because the numbers were speaking too softly. In March 2026, sitting in a room in Barishal, night after night, with a second-hand laptop and a hand-drawn scorebook, I charted all 132 matches of the Bangladesh Premier League. Each shot rose onto that page, and I wrote it down. No one saw it. No highlight package features a photo of that scorebook. But that was my first dataset. Now, ten years later, when I sit in a press box and read a 'data report' that says 'insufficient information, analysis not possible'—I feel the crisis of cricket is not on the screen but inside the ledger. And to understand that, we have to go back to where the forgotten information first drops away: Stage One. I noticed something strange. Last week, a sub-agent handed me a document titled 'Stage-2 Deep Analysis Report.' It had a massive matrix, eight dimensions, a 500-word framework. But every cell read: 'N/A – insufficient information.' The information points were empty. Only one label survived: 'cricket_asia.' I paused. Because I know that feeling. It is the moment you realize there is a gap somewhere in your data pipeline—and that gap says more about your process than any analysis you could have produced. Stage One is the layer where 'information points' are extracted from an article—who played, how many runs, which format, which venue, what date. This is not easy work. It is as laborious as a hand-drawn scorebook. But if this layer is wrong, then no matter how advanced your Stage Two model, no matter how beautiful your graphics—it is all false. That is why that report is so valuable to me. It shows the system can detect its own error. But the system cannot correct it unless someone looks back. Now let us look at cricket. This week, the Asia Cup schedule was announced, IPL auction preparations are underway, and Bangladesh's domestic tournament has ended. Thousands of data points are being created every match. But who is collecting these points? Who is verifying them? Who is publishing them and who is keeping them hidden? Here is the real story. Because every cricket statistic is the product of a decision—who is charting, how they are charting, what they are omitting. And behind that decision are human hands, late nights, arguments, and countless errors. When I enter Cricket Australia's 'PlayHQ' platform, I see nearly a million records. But beside each record, in small print, it says who entered it. Some entries were made right after the match, some three days later. Some have names, some do not. Where does this incompleteness come from? It comes because data collection is not a centralized decision—it is a distributed, messy, often blind process. In England's 'Play-Cricket' system, I found a 2026 club match where the two teams' scorecards showed different scores. 87 versus 91. Both were 'official.' This is not a bug—it is part of the system. Because a scorecard is not a representation of match reality, but of one person's memory. And human memory bends. The biggest proof of this bending memory is the IPL auction and player valuation. This month, nearly 200 players were retained or released for IPL 2026. These decisions were made on a set of numbers—strike rate, economy, match-winning innings. But where do these numbers come from? They come from a process that is usually not transparent. For example, I spoke with an analytics team of an Asian franchise (I will not name them). They said the 'dropped catch' data for a domestic match comes from their own subscribers, who note it on their phones and send it in. That means the field data first enters a human mind, then a phone, then a server. At each step, something is lost. And this lost information later determines a player's career. I want to pause here. Because one thing I have seen repeatedly: our biggest mistake with cricket data is believing numbers mean truth. But a number is actually an agreement—a social contract that we all agree to measure a specific thing. Without that contract, numbers are meaningless. In the 2026 Asia Cup match between Sri Lanka and Bangladesh, the rain rule (DLS) was applied. The result is still debated because two different methods were used to calculate the revised target. I followed two media reports—one said Bangladesh won by 2 runs, the other said the match was abandoned. Both were published, neither was 'official' but both were credible. Now which does a fan believe? They believe the one that reached them first. And that is our new ledger—where truth is determined by the speed of propagation, not the speed of accuracy. However, a warning must be drawn from this entire discussion. When I say data is incomplete, I am not saying data should not be used. I am saying that before using data, one should know its source, its emptiness, its limits of error. This distinction is what separates a data journalist from a hype-maker. A hype-maker builds stories with numbers. A data journalist verifies numbers with stories. And this process of verification is the foundation of our new cricket culture. I return to my room in Barishal. There, the old notebook still exists—132 matches from 2026, hand-written. I open it. Some pages are stained, some writing is illegible. But behind every number is a memory—a shot, a sound, a moment. Data is not just numbers; it is a ledger of memory. And our job is to respect that ledger, acknowledge its gaps, and move forward on its basis. The future of cricket is in data—but it will only be true when we acknowledge data's incompleteness. Because the claim of completeness is often another name for falsehood. And the acknowledgment of incompleteness is the first truth.