The Empty Scorecard: Silence Inside Cricket's Data Machine

A few days ago a record file landed on my desk. The schema was flawless — the title field, the source field, the date field, the summary field, all present, closed, valid. Inside there was nothing. No match name, no player list, no event list. The system threw no error. No red flag, no warning, no exception. Only one field came back filled: "cricket_world". The machine knew this was a cricket story; it had no idea what was in it. On an editor's desk such a file is not news, it is paperwork — entirely valid and entirely hollow. In desk language we call it silent failure: the apparatus does not work, but it performs working perfectly.

Seeing that file took me back to a December evening in 2026. I was six months into a copy-desk job at The Times of India in Mumbai, sent to the Wankhede Stadium for the Ranji Trophy final only because the senior writer had a wedding to attend. Amol Muzumdar, twenty-two years old, batted two days and made 260 against Delhi. I filed 900 words on the empty upper tiers, the linseed-oil smell of the dressing-room corridor, the groundstaff who clapped every single as though it were a wicket. My editor cut it to 300 and kept one line: "Cricket is the only art form where the audience is allowed to interrupt." The number stayed on the board; the smell of linseed oil stayed on my hand.

Back then records were made by hand. Carbon copies, scorebooks, match referees' signatures, bound volumes in the newspaper library. The risk was legible — a number could be wrong, but it could not be absent. If the scorebook said 260, then 260 existed somewhere, in somebody's pen, in somebody's memory. An error could be caught because some trace of the error survived.

Between April and December 2026 I watched that trace break down. After the Hansie Cronje revelations the CBI inquiry ran in Delhi and I stood outside those hearings watching Mohammad Azharuddin leave with his collar turned up — the same wrist I had written poems about at fourteen. In December 2026 the BCCI handed him a life ban. I filed 400 words, took three months of unpaid leave and went to my aunt's house in Guhagar on the Konkan coast, where the phone signal died at the gate. I read no cricket news until March. What those months made clear is that an inquiry's real battle is not over allegations but over documents. The CBI inquiry ran for months because the written record of what had to be proved was scattered. Between April and the verdict, the winter taught me how institutions breathe — slowly, and with no camera present.

When the IPL launched in 2026 I was handed the Mumbai Indians beat. I spent three seasons in team hotels, learning what never reaches a press conference — which player travels with his mother, which one is quietly broke. I spent three seasons learning the corridors before I understood the lights. That access was paid off on the night of 2 April 2026 at the Wankhede, when M.S. Dhoni made 91 not out, the winning six off Nuwan Kulasekara landed eight rows below my press seat, and 33,000 people produced a sound I have not heard since. A stadium can hold a record and still hide the people who made it possible.

Today those same records — 260, 91, 33,000 — live not in my handwritten scorebook but in a chain of machines. Score feeds, aggregator databases, multilingual platforms, and now extraction pipelines that read articles and pull facts out of them on their own. The person who used to guard the fact now sits at the end of the chain, not the beginning.

That is my real worry. The risk profile of cricket's information system has inverted. Twenty-five years ago the fear was that a number could be manufactured — the Cronje and Azharuddin era taught exactly that, that a record can be bought and a match sold. Today the fear is that a number can vanish, and vanish without regret, because it will vanish behind a complete, valid, schema-true document.

The distinction matters. False data gets caught. It clashes, it collides with an old scorecard, it is exposed by a fan's photo archive. False data has an intention behind it, and an intention has a finger that can be caught. But empty data has nothing behind it — no intention, no finger, no mark you can lift and place before a court. Validation checks structure, not truth: whether the field exists, whether the brackets close, whether a value of the specified type is filled in. It does not check whether the value is true. So a hollow shell, every field present as designed but containing nothing, passes every check. That is precisely its power.

I have seen this pattern in three places. The first is cricket coverage. The space the Ranji Trophy gets during a season is thin outside the knockouts — roughly 140 matches are played, and nobody has counted how many of them keep a detailed scorecard, a description, a verified history alive in any public database. Thin coverage means thin input, and thin input means the extraction layer has nothing to fill from. But the layer remains, it keeps running, and it returns a record that does not look like a failure.

The second is the 2026 inquiry. The same problem existed then, only without the technology. There was no call record for the player being questioned, no written proof of who met whom in which room, and the old version of the scorebook that got replaced was rotting in somebody's cupboard. Silent failure existed in 2026 too — not in a machine but in the inertia of offices. One difference remains: back then an absent fact was detectable, because even its box did not exist. Today the box arrives pre-built, and that is the most misleading thing of all.

The third is the file that landed on my desk. It contained a list of undecided fields: which source, which date, whose statement, whose inference. All zero. A line at the bottom stated plainly that no analysis beyond these zeros was possible, and I had to concede the writer was right. The most expensive truth in journalism is saying nothing. I have spent thirty-four years in this trade — as a Madras correspondent for Sportsworld, then in freelance writing for The Telegraph and elsewhere — and I can say with confidence that the writer who does not fill empty space with imagination is the one who lasts. The one who fills it shines for a season, and then every old piece of his becomes an object of suspicion.

But I must also put a finger on an inconsistency in that file that a first glance would skip. Every field was empty — no title, no source, category unclassified, summary blank, the list of information points blank. And yet one field was filled: "cricket_world". That small thing is large. It means the category label sitting there did not come from any fact inside; it was imposed from outside, or inherited from a layer above. The apparatus was trusting itself in the one field for which it had no evidence. In journalism we have another name for that: bias. And bias is exactly what makes an empty record dangerous, because it gives the reader confidence that someone is watching.

Now the part where I have to open a road to disagreeing with my own argument. The loudest anxiety in cricket writing these days is about volume: the flood of machine-generated material, the web of false claims, the statistics with no author. That anxiety is legitimate. But I am still not ready to accept that false data is the greatest threat. False data makes noise, and noise gets caught; empty data stays quiet, and the quiet keeps travelling. The report that started this column did not publish a single false story. It published nothing at all. And still it passed through the entire process unstopped.

So let me write my own falsifier and leave it there, because without it this whole argument is a taste rather than a conclusion. If every automatically produced cricket record carried three things — a named verifier whose name the public can see, a complete publication date, and an audit trail showing whether the material passed through human editing — then my entire argument collapses. In that case I would have to concede that the real problem is misinformation and volume, and that silent failure is a fringe worth ignoring. Does such a marker exist in today's indices? Cricket's public databases — platforms like cricsultan.com that carry a verification layer — do part of this work, but they cannot save the matches that reach only an automated pipeline and never reach a human being.

At the centre of this whole affair is a man whose bio contains nothing, and that man is the verifier. When I sat at the Wankhede in 2026 there was a gentleman beside me who reconciled the count all day and signed a sheet in the evening. If his count and my scorecard had differed, there would have been an argument, and even if the argument went unsettled, at least two people would know a difference existed. Today that argument has been replaced by an empty field. And nobody argues with an empty field, because arguing requires somebody to be wrong.

I am not writing this in despair. Every big story of this year's tournament cycle — a selection dispute, the arithmetic of rest and rotation, how many balls a player actually bowled — comes down in the end to one question: whose record is it, and on what authority does it stand. The cricket lover who asks how a batter's average fell across two matches is the same lover who must be able to ask why those two matches were never logged, or the whole analysis stands on sand. Half the spectator's right lies in the statistic, and the statistic's whole right lies in its verification.

So the next time somebody tells you what the selection committee's numbers say, ask one question — who touched this number, who counted it, who signed it. If the answer is silence, then understand that the score is up on the board and the person who wrote it has gone missing. The number will stay there. The question is who will be the one to prove it — and when, and in which written document, he will be willing to put his name.