What the Scoreboard Keeps Silent: Cricket's Data, Absence, and the Search for Tamper-Proof Memory

Half past nine at night. The rain over Rangpur stopped half an hour ago, yet the smell of wet earth still clings to the air. On the laptop screen the live-text window is open. A match is running, and I am writing ball after ball. Then the feed dies. Where the opener's name should sit, there is a gap; where a run should appear, a zero. The router's green dot is glowing, yet no data comes. One delivery — and no description of it.

That was the moment I met cricket's most honest kind of account. What the scorecard cannot hold is called absence. The sound of sixty-four thousand people breathing at once, an over suspended for rain, the boy on the bench whose innings never began — none of these reach a scorecard. Yet my whole working life has been spent in exactly those empty spaces.

What happened that night was a technical fault. But it placed me before a question whose answer will shape the future of cricket journalism: when we translate the game into data, what are we really translating — and what do we lose?

Today's cricket writing no longer runs on pen and paper alone. It runs on a pipeline. At the first stage, a match or a report is broken into information points — which team, which format, which player, what event, what time. At the second stage, a deep analysis is laid on top of those points — tactics, ranking, commerce, governance, risk, public narrative. The architecture rests on one idea: every conclusion must be cited from an information point; without data, no verdict can be drawn.

What arrived before me that night was the opposite. An analysis with every field blank. No title, no source, no information points, no names. The engine honestly admitted it had nothing, and by the rule it drew no conclusion. The question now is not easy, but it is simple: is a blank analysis only a technical failure, or does it point toward something deeper in cricket journalism?

I have written live text for cricket and football since I was twenty-seven. First at a semifinal in Kolkata, then in a Russian summer, then in an empty stadium in Dortmund. In each place I learned the same thing — the most important part of a game usually sits outside the scorecard. Now that the cricket world is being rebuilt around data, that old lesson has become newly relevant.

The scorecard is an incomplete archive.

We treat the scorecard as a document of truth. Yet only a small fraction of a full match lands there. How far the fourth ball moved in, how much a batsman's hand trembled, how far the keeper shifted his feet — there is no column for any of it. The scorecard tells you who was out, not who almost survived.

In October 2026, at Kolkata's Salt Lake Stadium, I did my first live text — the FIFA U-17 World Cup semifinal. England beat Brazil 3-1. Rhian Brewster scored a hat-trick, Phil Foden controlled midfield. In my hand was a sheet of statistics — pass counts, possession, shot maps. I closed the sheet. Because what happened in the sixty-sixth minute has no column. The Brazilian players paused for a moment and looked at the scoreboard, and sixty-six thousand people went silent together. That silence was a sentence — its first half written before the match, its second half written by no one.

From that night I began to treat match commentary as a memory palace, not a scoreboard. I began collecting sounds — the crowd's breath, the stains left on the grass, the weight of a paused moment. That habit later became my signature.

Data's new promise, and its limit.

Modern cricket has arrived promising to fill those empty spaces. Ball-tracking measures the path of every delivery; Hawk-Eye tells you, in centimetres, where the ball struck the pad; analysts compute the success rate of every shot zone. In football, expected-goals models tell you which shot should have been a goal. In cricket, metrics called expected runs and impact have entered team selection.

Here my second objection arises, one I learned from years of watching matches and hovering near dressing rooms. Data analysts are entering the dressing room, but their conclusions are often detached from the actual rhythm of the match. An analyst may say that a batsman plays spin slowly, so he should not be pushed up the order. But the model does not capture that the batsman woke that morning with an old ache returning to his wrist as he caught balls on the practice mat. The model does not know what was said in the dressing room before the opening pair walked out.

I remember, in 2026, doing live text for Borussia Dortmund against Schalke as the Bundesliga restarted. An empty Signal Iduna Park. Eighty-one thousand three hundred and sixty-five seats vacant. Erling Haaland scored in the twenty-ninth minute, but the only sound was the ball and the tread of two hundred masked officials. That night I felt a tiredness so deep that after the match I withdrew to Rangpur for two weeks and refused to answer the phone. There I wrote 'The Silence Between Whistles'. One line read: eighty-one thousand empty seats shouted louder than any derby.

That experience taught me how much of a full match data can hold. Suppose a model extracts from that 4-0 match Haaland's scoring rate, his shot speed, Dortmund's passing network. To the model it is a perfect match. Yet the stadium's silence — the true character of that game — sits in no field of the model.

The credibility of a record depends on who writes it.

Now to the real question. What does a blank analytical report actually say? It says: if the input holds no information, no conclusion can exist. That rule is in fact the foundation of every cricket record. A scorecard is credible on one condition — that whoever writes it writes honestly.

Cricket's history contains moments when that trust broke. In August 2026, at Lord's, during the Test between Pakistan and England, allegations of spot-fixing emerged. The ICC's Anti-Corruption Unit investigated, and in February 2026 a London court convicted three Pakistan players — Mohammad Amir, Mohammad Asif and Salman Butt; the ICC banned each for five years. The affair reminded cricket of a fundamental truth: whether a no-ball in a given over was truly an accident cannot be judged from the scorecard alone.

March 2026 at Cape Town, in the Test between Australia and South Africa, offered another example of ball-tampering. Cameron Bancroft was seen using sandpaper, and after Cricket Australia's investigation Steve Smith and David Warner received one-year bans while Bancroft received nine months. These episodes push me toward a question: if the record of the game can be corrupted so easily, how do we know a match's data is true? And here a new word entered my writing — blockchain.

A blockchain is essentially a shared ledger where, once information is written, secretly altering it later is nearly impossible, because each entry carries the cryptographic imprint of the one before it. In football with Sorare, in basketball with NBA Top Shot, and in fan tokens spread across various leagues, the sports world has shown interest in the technology over recent years. Cricket has felt the ripple too; some leagues and boards have touched platforms for digital collectibles and fan engagement.

Imagine this: if the data of every delivery were written to a blockchain, then the next day no one could claim that ball was not a no-ball. Whether a boundary crossed the line — video proof, timestamp and ball-tracking — everything would sit sealed in an immutable ledger. Points tables, player records, disciplinary decisions — all would carry an audit trail.

But here I must stop. A blockchain can make the ledger immutable, but who writes in the ledger, and whose name is left out — that decision still rests with people. If a few officials of a board decide that an event will not enter the ledger, the immutable ledger will simply remain immutably incomplete. Technology preserves testimony; technology does not create it.

If data is authority, whose authority is it?

Data has already become an authority in cricket. DRS was first trialled in July 2026, in a Test between Sri Lanka and India; then it was a doubtful experiment. Today ball-tracking and UltraEdge are trusted more than the umpire's eye. Whether a player is out is no longer a matter of the umpire's conscience; it is a matter of a pixel in a ball-tracking system.

A danger hides here, one I have never seen from outside the field but have grasped by looking at the scoreboard. DRS can tell you how close the ball came to the stumps, but it cannot tell you what was running through the batsman's mind — whether three dot balls in a row had made him abandon his own game. The silence that breaks an innings is measured by no technology. We have begun to treat the measurable thing as the important thing, and to deny the important thing when it is not measurable.

The peripheral voice is the game's true history.

In 2026 I covered a World Cup in Russia as a field commentator. At Spartak Stadium in Moscow, Iceland drew 1-1 with Argentina. In the sixty-fourth minute Hannes Halldórsson saved Lionel Messi's penalty. After the match my editor wanted a match report. I gave him a twelve-hundred-word essay on small nations and collective memory. It was shared twelve thousand times.

Why? Because I did not write statistics. I stayed standing after the final whistle and recorded the Viking clap — eight thousand voices, one rhythm. Iceland's total population is only around three hundred and thirty thousand. A small nation was making its own memory in a stadium, and I was its witness.

From that night I decided I would speak not only to players but to fans, to stadium workers, to the security guards standing at the boundary. The owner of the tea stall outside the Sher-e-Bangla National Cricket Stadium is a witness to how many matches — that is in no database. The auntie who follows the match on the radio, her reaction is the true weather report of a nation's emotion. The scorecard says who won; they say why it mattered.

This is why I write for the peripheral voice. But here too there is a caution I remind myself of again and again: when writing for the peripheral voice, there is a danger of drowning their mouth with your own song. If I render the shopkeeper's feeling in my own language, it is no longer his speech but mine. So I listen first, record, and only then write — and if listening is impossible, I admit on the page itself that the portrait is incomplete.

A blank report is also information.

Back to that night's blank screen. When an analysis writes 'insufficient information' in every field, it teaches us to recognise two different things. One is — there is no information. The other is — there was information, but it was lost in the pipeline. Confusing the two is dangerous.

My own experience says the second is more common. Something was written about a match, the information existed, but a fault during extraction left everything blank. The real lesson is this: 'there is nothing' and 'it does not matter' are not the same. If someone treats a blank result as 'no news', they may have buried a significant event that deserved a headline.

That night I understood that cricket journalism's greatest risk is not the absence of data; the risk is failing to recognise the absence of data as an absence of data. And this caution belongs not only to engineering but to editing.

The blind spot caught in the mirror.

Now to the part where I face my own profession. As a cricket writer I have two great traps. The first is nostalgia. Bangladesh's cricket history is loaded with emotion, so every piece easily wants to become an elegy for a golden afternoon. The second is over-symbolising the ordinary — the temptation to turn a dropped catch into a metaphor for national grief.

Here the lesson of the blank report is useful. When the data is empty, I cannot fill it with my own emotion. Just so, when the data exists, I should ask myself — is this information really the story of the match, or am I using it to tell my own story?

There is a larger blind spot that is becoming clearer in the data age. We think more data means more truth. But the process of analysis is itself selective. Who gets measured, which moment rises as information, which stays silent — someone is making these decisions. When an analyst says 'this batsman plays slowly', his model was probably built while excluding a cricketer who did not play that series for reasons off the field. Whoever is not measured is absent from the model; and what is absent from the model might as well never have happened.

So my position on blockchain technology is mixed. An immutable ledger is useful for cricket, because the record of the game is a public trust. But if the technology secures only a ledger that was already incomplete, we get only a small room behind stronger walls. Strong walls do not make a window.

The lesson of the sixty-sixth minute.

My oldest lesson returns. In that semifinal in Kolkata, in the sixty-sixth minute, what I saw in the eyes of a paused player is in no database. The silence I felt in the empty Dortmund stadium of 2026 is in no expected-goals model. The rhythm of the Viking clap that night in Russia, made by eight thousand voices at once, does not rise onto any statistics portal.

These three moments share one thread: in each I was witness to something that cannot be measured. And precisely for that reason my profession survives. If every truth of the game could be caught in a scorecard, I would have no work. The cricket writer's job is not to discover truth, but to hold in memory the truth that truth leaves blank.

That blank screen was therefore not only a failure. It was a mirror. The more perfect our data systems become, the clearer it will be that a large part of the match falls outside them. And our task is to keep looking at that outside part.

What is not yet written.

In the coming years cricket will move more deeply toward data and blockchain-based records. Every delivery will be an entry, every decision a verifiable seal. On this path many errors will be corrected, many quarrels will stop. But this change will make the cricket writer's work harder, not easier, because then our task will be to find the empty spaces that the system wants to keep silent.

When I look at the screen tonight, the empty fields no longer irritate me. They remind me that the first ball of the game has not yet been bowled. One delivery, whose description no one has written yet. In that empty space, perhaps, lies the most honest story of the next match.