The Echo of an Empty Dataset: In Cricket Reporting, the Costliest Mistake Is the One That Sounds True

The File That Contained Nothing

In a small studio in Bangalore, in the empty hour between two commentary blocks, a document lay open in front of me. Eight analytical sections, eight tables, more than forty rows, and at almost every position the same typed sentence: insufficient information. No match name. No team. No format. No date. Only an emptiness, neatly formatted so that nobody would be tempted to fill it.

That emptiness arrives in a commentary booth every single day. In the third over a name comes up, the person beside you on the mic says the boy made a pile of runs at under-19 level, and you have two roads in front of you. One: carry the sentence forward. Two: stay quiet until the scorebook is in your hands. I took the first road at seventeen, and I have been paying interest on it ever since.

2026, the KSCA under-19 final, on the practice ground at M. Chinnaswamy. I was calling it for my school's WhatsApp radio, seventeen years old, a torn scoresheet in one hand and an earphone that kept cutting out. Devdutt Padikkal made 82 off 67 balls. In the first over I mispronounced his surname three times. When he was run out at the non-striker's end, I said the boy was walking off to the sound of his own name being corrected. The clip was forwarded four hundred times in our school group. A local KSCA scorer sent me a list of every player's correct pronunciation.

The name I mispronounced is the one I still hear at night. That evening I wrote a rule in my diary: it is better to report what happened late than to report it wrong. The rule followed me all the way to the document that has nothing written in it.

That document reminded me of something that sits in every cricket newsroom in some form. When a scorecard opens and there is nothing inside it, the easiest task is to fill it from memory. The hardest task is to leave it empty and explain why it is empty. The rest of this piece is an answer to that question: where cricket's information comes from, where it breaks, and where it starts looking so beautiful that it stops feeling like a lie.

From the Scorebook to the Screen

Cricket may be the only sport where the spectator can count every ball along with the ground. That count begins on paper. A scorer sits, writes by hand, records every run, every extra, every wicket, the start and end of every over. The paper becomes a digital feed; the feed becomes the broadcast graphic you read on screen.

There are three places in that chain where error enters.

The first is scoring. A wide that was not a wide, a bye that was a leg-bye, a catch that dropped and was not a boundary — these things arrive in the scorebook and then never correct themselves. The second is the feed. Several public statistical platforms, among them well-known names like ESPNcricinfo and Cricbuzz, draw their data from scoring agencies; if the source lags, the score on your screen can sit an over behind the real one. The third is transmission — the instant a journalist or commentator lifts a number off a screen and puts it into a sentence.

Most of the damage happens at the third point, because there is no checksum there.

So I sort sources into three tiers. The first tier is the primary document: the scorecard, the match referee's report, the board's official release, the ICC rankings table, the World Test Championship points table. These are not claims. They are documents. The second tier is the correspondent — a named person who was actually present. The third tier is what I call the forward: fan accounts, aggregator pages, screenshots without a date.

The third tier is not worthless. Often the first whisper arrives there. But a whisper is not information until the first or second tier confirms it. I keep a folder on my phone called Screenshots Without Dates. There are more than forty images in it. To this day I have not said one of them aloud on air.

All of this matters because the loudest thing hidden inside that empty document was the absence of a date in any row. In cricket, a date is what separates an event from a story. 19 November 2026, Ahmedabad — that is a date. That evening Australia beat India by six wickets, and the sound of more than a hundred thousand people shut off like a room. Write that evening as simply the final, and the reader remembers nothing. Without a date, a cricket report is a diary with pages and no numbers.

Format Is the Lens Through Which Numbers Are Read

The most common and least noticed error in cricket writing is carrying one format's statistic onto another format's player. The error happens because the number looks identical — average, strike rate, economy — while the scale underneath it has moved.

In T20, an economy under seven is strong, up to eight is acceptable, and above eight you are under pressure. In Test cricket there is no such economy benchmark; the question is how many overs a bowler held up and how many wickets came. A strike rate of 130 is low in today's T20, a middle-order weapon in ODI cricket, and in Test cricket something closer to a warning that a batter is playing in the air and the next morning's new ball will find him.

Batting averages behave the same way. In Tests, an average around forty is good and anything past fifty is a rare category. In ODIs the average has lost weight over the last decade as the game sped up; strike rate and situation-specific output now matter more. In T20 the average alone is close to a useless number — fifteen not-outs in twenty innings will lift your average and give your team nothing.

This is why a cricket claim without a format label is not a weak claim. It is not a claim at all. It is a sentence you can tilt in any direction and it will sound true in every one of them. Readers do not catch the difference, because readers read the number and not the scale.

I have a practical method here. Before I look at any player's numbers I ask three questions: which format, how many innings, and in what situation. Only after all three are answered does the number speak. Before that it stays silent — and working with silent numbers is something I had to learn in the booth, after I once described a young batter's first-class average in a T20 context and received an email the next morning from a coach containing exactly one line.

Size and Sample: One Season Is Never the Truth

Cricket's biggest illusion is that a good season proves a good player. An IPL team plays fourteen league matches in a season, and sixteen or seventeen if it reaches the playoffs. If a batter gets fourteen innings, is out inside ten balls three times and finishes not out on forty twice, the season-end strike rate will tell you a story that says almost nothing about his actual ability.

The same holds for bowling. A T20 bowler gets forty to fifty overs in a season. Economy is a number where two bad overs and eighteen good ones still land you near seven. If those two bad overs came in the death, the real story is not in the economy — it is in the situation of those two overs.

My notebook has a column titled how much sample. Beside every claim I write how many innings it rests on. A claim built on fewer than ten innings is a story I can tell, not a judgement I can make. Past thirty, the conversation opens. Past fifty, and repeated across different conditions, something can finally be said.

The same sample problem has a second face: home and away splits. A batting average against spin in India and an average against swing in England are two different organisms. A player averaging seventy at home and thirty away is not a bad player. He is a player about whom the information is still incomplete. And while the information is incomplete, describing him as complete is the oldest habit in cricket reporting.

One more thing belongs here, and few people write it: no limited-overs result can be interpreted without the toss and DLS. Rain-revised targets have changed outcomes, and teams have been handed advantages they did not earn. In the review system, umpire's call is a rule under which the ball is striking the stumps, less than half of it is hitting, and the on-field decision still stands. DLS and umpire's call sit inside every scorecard, and every scorecard does not show them.

Money and Sport: Two Currencies That Never Convert One to One

₹15.25 crore is not a number. It is a decade of a family's arithmetic, a town's second cricket ground, and a negotiation conducted in a living room.

At the February 2026 IPL mega auction, Mumbai Indians bought Ishan Kishan back for ₹15.25 crore. That day I did not open with the price. I called three Ranchi fans I had met on a cricket forum. One of them said: we do not lose players, we loan them to the country. That sentence was the most accurate report of the whole day.

The discipline required here is that an auction price and a sporting value are two different currencies with no fixed exchange rate. A franchise paying a large sum is not buying a player's international ceiling — it is buying his availability, his brand's local reach, and his place in that team's structure. Sometimes all three live in one player and the price looks correct. Sometimes they do not, and a year later the price looks like weight.

The first Women's Premier League auction in February 2026 is the cleanest example. Royal Challengers Bangalore bought Smriti Mandhana for ₹3.4 crore. That figure arrived at a point where the performance was already established; the question was what the market would pay for it on the day the market was born. When a market is born, its first price is not a measure of value. It is the beginning of a measure.

So when I write an auction report I keep three things apart. The price. The team need behind the price — which slot the purchase fills. And the household arithmetic no screen shows: what the contract buys and what it costs. A large contract gives a family security and takes it away from the city where the first ground is. That sentence sounds sentimental; it is as concrete as a retention list.

One more. When a player gives up a central contract or asks for a No Objection Certificate to play an overseas league, that story usually belongs to administration more than to sport. The cricket question is small; the question of power between board, schedule and player is large. Writing it as a cricket story is the mistake I try to avoid.

The Roar Has Its Own Scorecard

The 2026 IPL was played in the United Arab Emirates, in empty stadiums. That year I made a twelve-episode audio diary for a Bangalore sports startup called The Empty Roar. On 28 September 2026, Royal Challengers Bangalore and Mumbai Indians went to a Super Over, with Navdeep Saini defending eight. I recorded ninety seconds of silence in my bedroom and wrote over it that the thirty-two thousand seats at Chinnaswamy were the loudest character in the match.

A roar with nobody in it still counts as a roar. That sentence still returns to me whenever a scorecard tells me how many people were at a match. A scorecard has a column for attendance. It has no column for volume. That does not make the sound less true. It means the sound has to be verified differently — recorded, timestamped, attributed to a witness.

In the same way, when the crowd moved online, the roar did not disappear. The crowd moved online; the roar just changed address. The commentary scrolling under the stream, the threads, the six-in-the-morning voice notes in WhatsApp groups — these are the new postal addresses of the same sound. I keep a folder of thirty-second voice notes from spectators, from eighteen cities. When I need the feeling of a match, I do not open a scorecard. I open that folder.

That method holds because it leaves no room to lie. You cannot mark someone's feeling as incorrect, but you can always say when you heard it, from whom, and from which city. Feeling has a scorecard too. Nobody just builds it.

The Contrarian Case: The Shortage Is of Restraint, Not Information

The common assumption is that cricket lacks information. The opposite is true. A cricket writer today has ten times the data available in 2026 — line and length on every ball, shot maps for every batter, matchup histories for every bowler, fitness reports, every bid in every auction. The shortage is not of data. The shortage is of the skill of staying quiet once the data arrives.

Analytics made cricket writers more confident and less careful. Writers once had few facts, and so wrote cautiously. Now they have endless tables, and so try to answer every question — even questions that do not yet have answers.

In my experience one thing has damaged trust in cricket reporting more than anything else: the sentence that sounds true. A wrong sentence is caught easily, because the number is wrong. The dangerous sentence has a correct number and a wrong format, or a wrong sample, or a wrong situation. It reads so well that nobody has time to challenge it.

That is why the most valuable line in that empty document was not one containing a statistic. It was the line saying that no player, team or match could be identified. In my view, the fastest alarm in any cricket data pipeline is not a wrong number — it is an empty name.

I have applied this to my own work. My notebook now carries three lines after every match: what is known, what is not known, what to find out next time. That list is never published. But everything that does get published passes through it.

One more contrarian note. Many colleagues believe audiences will not read soft news. My experience is that audiences read most eagerly the piece that says something has not yet been confirmed, because it gives the reader credit for their own intelligence. Ending a story with the line that this is all we know for now does not leave it unfinished. It enrols the reader in the search.

Looking Ahead

Cricket's next phase will be faster. World Test Championship points will shift with every series, franchise calendars will keep colliding with international ones, and every auction will manufacture a story that someone has to file in a hurry. Something always gets left behind in that hurry — the date, without which a story is not remembered.

I will not argue that we should write more slowly. I will argue that we should write what we do not know. The next time a number appears on screen and you feel a story forming, ask one question: in which format, on how many innings, and in what situation. If all three answers arrive, write the story. If they do not, write the silence. That silence is part of the same match.