Empty Input, Honest Answer: The Value of Verifiable Data in Cricket Analysis

Last night in my Liverpool flat I opened an analysis report on my laptop. Seven pages. No match format, no team name, no player name, no innings detail. Every field repeated the same line—insufficient information, cannot assess. At first I assumed a software bug. By the third page I stopped. This was not a bug. This was honesty. Memory pulled me back to August 2026. Liverpool beat Arsenal 4-0 at Anfield. I was a nineteen-year-old student, and instead of the scoreline I was writing on Twitter about Mohamed Salah's 57th-minute goal—the sprint, the Kop's collective inhale, the curl. That twelve-tweet thread was retweeted eight thousand times. The Anfield Wrap asked me for a 1,200-word report, and I rewrote it three times until four in the morning, chasing the feeling of one breath. The thread began as numbers and ended as a confession. I learned that a single true moment can carry an entire match. Today that lesson is returning from the opposite direction. Cricket now runs not on moments but on a flood of numbers. Expected runs per ball, win probability per over, a heatmap for every fielding placement. Beside the scorecard there is now another scorecard—the data's. And inside that data hides a question nobody asks: where did these numbers come from, and who verified them? That empty report showed me something strange. The system analysing the match had no information—so it invented nothing. It left the space blank, wrote plainly that assessment was not possible. And yet this is exactly where humans fail. When we see a gap we fill it with story. If a name is missing we guess a name; if an innings is missing we imagine one. The greatest sin of cricket punditry is precisely this—covering the gaps in data with narrative. I have watched cricket and football data for twelve years. One thing has become clear: the problem is not too little data, the problem is data that looks complete but cannot be verified. If I cannot trace an average back to its source, it is not a statistic—it is an illusion. And you cannot pick a team, pick a player, or understand an opponent's weakness with an illusion. This is where the idea of blockchain becomes strangely relevant. Blockchain's real promise is not any currency—it is the immutability of a record. Once a transaction is written it cannot be erased, cannot be altered, and anyone can verify it. Cricket data needs exactly this quality. If every ball of an innings were recorded in a way anyone could trace backwards, the confusion over 'why did this player's average suddenly change' would perhaps disappear. Imagine it—every ball of a five-day Test, every DRS review, every catch, all stored in a verifiable ledger. The umpire's decision, the third umpire's frame, the ball-tracking data—all in one place, immutably. Then there would be no need to write 'insufficient information', because the information would exist. And where it did not, we would at least know where it was lost. In my experience cricket analysis has three layers. First, the event: who scored how many, who took how many. Second, the explanation: why it happened. Third, the forecast: what might come next. Most people love to leap to the third, because that is where the story lives. But if the first layer cannot be verified, the second and third are pure fiction. From an empty input no beautiful prediction emerges—only a beautiful lie. There is a subtle point here. In modern cricket the word 'expected' works like magic—expected runs, expected wickets, expected fielding saves. But expected means a model's estimate, not an event. And however elegant a model's estimate, it can never take the place of a verified event. We often confuse the two—and that is when analysis drifts away from data and lands in astrology. I have another old habit my colleagues mockingly call 'duet architecture'—my pitches always arrive in pairs. Because a story cannot stand alone; it needs an echo. That night the empty report's echo was another experience—a Tokyo 2026 documentary in 2026, thirteen-year-old Sky Brown's bronze, where I turned falling into a metaphor for rehearsal. Thirteen years, twenty-eight days, falling twice and landing a kickflip indy on the third try. There every number was verifiable—age, score, date. That was the strength. Another memory returns. In 2026, during the Russia World Cup, I watched England versus Colombia in a packed Liverpool student flat. In the shootout Jordan Pickford saved Carlos Bacca's penalty and Eric Dier scored the winner. I wrote a thread from that room—the twenty-two seconds of silence before Dier's kick, the half-eaten pizza, the neighbour's scream. It was shared fifteen thousand times. A BBC Radio Merseyside producer wrote: 'You write sound.' In a Liverpool living room, the World Cup spoke seven languages and one heartbeat. We passed the remote like a trophy, and the room became a country. I still carry that lesson—emotion first, scoreline last. But even emotion must have a truth. If the silence is not real, the beautiful sentence is a lie too. In cricket this truth is even stricter—here every ball has an account, every over has an identity. Beautiful writing cannot alter that account. Here is an example from my own work. In 2026, when Liverpool won the Premier League after thirty years but Anfield stood empty, I wrote a fifteen-minute documentary, 'The Silence of Anfield'. In it was Van Dijk's ninety-nine-point season, and the absence of fifty-four thousand fans. I interviewed a season-ticket holder watching from a hospital bed. Empty Anfield taught me that atmosphere is not sound; it is agreement. The script won an award. I learned that absence can be a character. But here lies the fine distinction. Absence can be a character, yet absence cannot be filled with 'perhaps it happened this way'. Nameless absence often means nothing was ever specified. So my rule: state once, plainly, what is missing—then let the writing circle it, not substitute for it. That empty report showed me one more thing rare in today's cricket culture—the courage to say no. Today twenty thousand predictions are made before every match, ten 'exclusive' analyses printed before every series. Nobody says 'I don't know'. Yet the honest analyst's first qualification is this—when there is no information, to say there is none. Now I come to the uncomfortable place where my colleagues will disagree with me. In today's cricket world everyone says we need more data. More cameras, more tracking, more heatmaps. I say the opposite. The problem is not a lack of data, it is the misreading of data. Looking at a heatmap we think we have understood a player. In truth we have understood only where he stood, at which moment. Why he stood there, the heatmap never says. To me the heatmap is cricket's new tea-leaf reading—a modern version of telling fortunes from cards. The role a player plays within a system can never be shown by a warm-and-cold map. If we judge a finisher only by his strike rate, we ignore his hardest task—the risk of going hard in the final over. The number is there, but the context is not. This lack of context is not confined to heatmaps; it is spread across the whole analysis industry. When a player's agent selectively highlights a statistic—'last season his strike rate was 145'—he is telling a truth while hiding the context. On what pitch, in what situation, against which bowler, that 145 is never stated. And it is on exactly this selected truth that prices are set, contracts signed, teams changed. The most dangerous form of truth is not a lie—it is a partial truth. The cricket-data market runs on exactly this partial truth. So verification does not mean only 'is the number right'; verification means 'how much is this number saying, and how much is it suppressing'. For me a match never happens only on the pitch; it happens in the living room. In a Liverpool living room, seven languages and one heartbeat—there seven people nod together at every boundary, and when someone gets it wrong they are caught at once. The room is a kind of natural verification system: if one person errs, the rest cross-check. In the world of data we need exactly this room—a public place of verification where no number can stand alone. That night, reading the empty report, I felt I was perhaps seeing something rare—a system admitting its own limits. That seven-page document carried no match name, but it carried a lesson: when there is no information, the honest answer is 'I don't know'. In cricket culture that phrase is so rare that hearing it feels like someone misspoke. I believe cricket's future lies not in vast datasets but in trustworthy ones. Data you can trace backwards, whose every number carries a specific match and a specific date, that no one can later alter. This is blockchain's lesson—trust does not come from a slogan, it comes from verification. And cricket, being a game of numbers, has always had one simple promise as its greatest asset: what we wrote, happened. I went looking for a goal and found a grammar for belonging. The first condition of that grammar is simple—whatever you claim, prove it. So next time you read any analysis, ask one question—where did this number come from? If you get no answer, the number may be beautiful, but it is not true. And an empty report that dares to say 'no information' may be more honest than a full one. The question is no longer mine but all of ours—do we want a cricket culture where every claim is verifiable, or one where a beautiful story is enough?