The Data That Never Arrived: Silence and the Verification Crisis in Cricket Analysis

It was almost half past three in the morning. In a room in Sylhet, under a table lamp, a spreadsheet lay open on the laptop screen. Twelve columns, forty-four rows. Yet every cell of the one column I had sat down to fill carried the same words: no data. No score, no strike rate, no over-by-over record. Only emptiness, and a question beside it. That night I understood that a cricket analysis does not die at the point of a wrong inference. It dies in an empty cell. From my years of watching the game, I can say this: the analyst's real work is never gathering information; it is deciding which piece of information deserves belief and which does not. Yet we almost always do the opposite. We bow the moment we see a number. But a number and a proof are never the same thing. A number comes from somewhere, from someone, through some process. That path is precisely what we never look at. Cricket today is a republic of numbers. ODI, T20, or the five-day Test — each format has its own arithmetic, its own average, its own tempo. These three sets of figures cannot be exchanged for one another, yet day after day we mix them in our conversations. The patience of a Test and the storm of a T20 are not the same; a century weighs differently in the two formats. Still, we use one's record to write another's future. The wave of analytics reached Asian cricket quickly. IPL auctions, the Right to Match card, every franchise's data desk — numbers are now the language of decision. A player's price is set by his strike rate over three seasons, his powerplay-to-death-overs split, his injury history. But where those numbers came from, who verified them, who placed them on the table — that question is never asked in the auction hall. After rain, the Duckworth-Lewis-Stern method rewrites the target. A match's result can rest on that single formula, yet how many know its mathematical basis, or the data on which its wickets-in-hand model stands? We accept the outcome; we do not know the process. The 'umpire's call' of the DRS is the same — whether ball-tracking stayed within or crossed its margin of error decides the result. Truth here is a fraction of a calculation, and we treat it as a final verdict. But my real thought is not here. My thought is what happens when the information itself never arrives. Then an analyst has two roads. One: place his own guess in the empty space and build a story. Two: stop and say — there is no data, so there is no conclusion. The first road is easy, popular, and dangerous. Because a number no one ever verified, once printed, never comes back. I have sat in commentary boxes and watched a single wrong figure spread through an entire broadcast. Someone said, 'his average is above forty'; someone picked it up; someone built analysis on top of it. Two hours later the number had become true. Yet no one once turned around to ask where it came from. On social media the spread is faster still, because the speed of sharing outruns the impulse to question. This is where I believe cricket's data system has a large gap. We talk a great deal about data, but almost nothing about the chain of custody behind it. This is close to the philosophy of the blockchain — a record, once written, cannot be altered, and every step is linked to the step before. In cricket statistics we do the exact opposite. Numbers change, sources vanish, no one is held accountable. Suppose a bowler's economy rate suddenly falls. The question should be: in which format, at which venue, against which opponent, over how many overs? A good economy on a home turner and the same figure in hostile conditions are two entirely different things. But our memory keeps only the final number and discards the conditions. So even with data in hand, the analysis goes wrong. I have often seen large decisions built on a tiny sample. Five matches of form have made a player 'talented' or 'useless'. Yet the rule of statistics is that the smaller the sample, the louder the noise. The swings across five matches are not proof of talent; they are the sound of probability. We mistake that noise for music. Take a real example. On January 5, 2026, at the Melbourne Cricket Ground, the first men's One Day International was played between Australia and England. According to public records, that match was essentially a rain-abandoned Test replaced by a limited-overs game. Yet from that single day we inherit thousands of ODI records, which we then blend with Test records. The origin was accidental, yet we treat the system it spawned as eternal. The consequence of a missing chain of custody is that analysis drifts toward rumour. Someone gives a fact, someone believes it, someone builds the next fact on it. A genuine chain forms — but a chain of inference, not of verification. In the blockchain a record is immutable and verifiable; in cricket's oral culture that record is instead the most flexible and least verifiable thing there is. I have watched a London television broadcast from Sylhet, and the same match's Asian coverage from a Dhaka desk. One match in two places, and the numbers sometimes differ. One feed gives a run rate, another gives a different one. Which is right? The question does not arise, because each viewer believes his own screen is the truth. Cross a border and language changes, tempo changes, sometimes the data changes too. Here I feel a small unease. Born abroad and working in Bangladesh, I have learned that information never travels neutrally. Data that is 'true' in one country is seen in another light elsewhere. No one is accusing anyone; no one is verifying either. And where there is no verification, what remains is not information. It is belief. The silence between overs taught me that absence is still a formation. When the stadium empties, when the camera looks away, when a cell on the scorecard stays blank — that is not mere zero, it is an active decision. The data no one supplied is often the data that speaks loudest. When the crowd goes quiet, the data starts speaking in whispers. I want to hear that whisper. In 2026, watching a derby behind closed doors, I understood that the absent crowd was the loudest character in the ground. It is the same with cricket data. The column that is empty is telling us: here, no one has proved anything. If we fill that empty cell with a guess, we betray not cricket but our own story. I count the seconds after the ball leaves the hand, because truth arrives late. That lateness is as true in cricket as in data. But the economics of modern analysis does not forgive lateness. The reader wants the result, not the process; speed, not verification. So the analyst who honestly says 'there is no data, I cannot say' seems slow, while the one who manufactures a conclusion in two minutes seems sharp. This inverted reward is the real danger. On the auction floor, in the broadcast studio, at the office data desk — everywhere speed is praised, not verification. No one asks, 'what is the source of this number?' They ask, 'how fast did you reach a conclusion?' So in the age of data-driven decisions we perform the least data-driven task of all — auditing the chain of the data itself. Here is my contrarian position. We think the enemy of analysis is superstition or ignorance. In truth its greater enemy is overconfidence — the habit of placing a guess in an empty space and passing it off as fact. An honest analyst is recognised not by the number of conclusions but by the courage to withhold them. And that courage matches the blockchain's philosophy: what cannot be verified is not written. We have built a continent of data without anyone seeing its foundation stone. Test, ODI, T20 — we drew the borders of these three states in the rulebook, then erased them in our analysis. We made instruments like DLS and DRS the judges of truth, yet we keep their margins of error out of the discussion. Numbers are sacred to us; process is invisible. Every format has its own grammar, and every format's data should be read in that grammar. In a Test, patience is a skill; in a T20, patience is also a limitation. The same player is two people in two formats. But our short memory drops every format into one box, then judges one by another's measure. It is this blending that dresses manufactured conclusions in the clothes of truth. The verification crisis is not merely academic; it has a market price. A player bought on a wrong figure becomes a burden on the team for years. A big contract given on the flash of a small sample, then the cost of an unaccounted injury. In cricket's economy, bad analysis is not cheap; it is one of the most expensive errors of all, because it stays hidden. I remember the irritation of that night's spreadsheet, forty-four rows, every cell empty. Then, slowly, it became a kind of calm. Because those empty cells reminded me that the analyst's job is not to make truth but to seek it. And pretending to have found what is not there is not analysis — it is broadcasting. This honesty matters even more in cricket data, because the game is now an object of global investment. In the Asian heartland — India, Bangladesh, Pakistan, Sri Lanka — money, emotion, and national pride mix behind every decision. A false figure here does not merely ruin a column; it exploits the faith of millions. That is no small responsibility. So the question now stands plainly before me. When we say 'the data says', who is accountable for that data? Who verifies it, and who verifies the verifiers? If the answer is 'no one', then all our number-driven confidence rests on one thing — belief, not proof. The last ball is not a deadline; it is a door left ajar. Before stepping through it, we should always ask one question: did this information truly arrive, or did I write it myself? The pitch is a poem whose over-breaks and line-breaks I annotate — but the word that is not in the poem, I will not read aloud. Before shutting the laptop that night I wrote one line: 'no data — no conclusion.' Simple, uncomfortable, honest. Perhaps cricket analysis's next big leap is not in adding more numbers but in building an immutable ledger of verification. A ledger where behind every figure stands its source, its conditions, its margin of error — just as a blockchain never forgets its own history. Cricket has taught us that silence, too, is a language. The silence of a stadium, the silence between overs, and the silence of an empty data column — all three say the same thing: how honest our analysis is depends on what we choose to do with what is not there. Cricket's real challenge today is not another big shot; it is refusing to fill that silence with a lie.