The Empty File: When the Scorecard Reads 'Insufficient Information'

It was 2:40 in the afternoon. The air-conditioner in the Bengaluru office hummed its one flat note, the cup had left a round ring on the desk, and the laptop screen held a file with not a single number in it. Eight sections: format analysis, player technique, team landscape, league economics, governance, risk, public narrative, industry transmission. In every cell of every section, the same sentence — "insufficient information, assessment not possible."

In twenty-one years of doing this, it was the first time a report had arrived on my desk that told me nothing at all about its own subject. No title. No source. No information points. No names. Only one label — "cricket_asia" — and beneath it, a void filled in with great professional honesty: N/A.

The scorecard says nine; the story keeps running. Here there was no scorecard at all, and the story was still running.

Context: a two-stage pipeline with an empty stomach

Our desk works in two passes. The first decomposes a source article into information points, core viewpoints and entities — players, teams, events. The second analyses those points across eight dimensions: format, technique, team landscape, commerce, governance, risk, narrative, transmission. My habit is to open the first-stage file before writing anything long, because I believe that what has not been counted should not be written.

This time the first stage came back empty. No title, no source, no points. And what the second stage did is a specimen of professional honesty rarely seen in cricket: it wrote, in every cell, that analysis was impossible — and added a warning that drawing conclusions from an empty base would violate its own rules.

Stop there for a moment. In cricket news, such a document is almost revolutionary. Our industry is expert at filling blank space. During a transfer window, one tweet becomes three paragraphs "according to sources." On auction day, estimates, rumours and an agent’s phone call get braided into a single thread. Nobody was doing me a favour here — a file was empty, and it announced its emptiness.

But in cricket, an empty file can mean two entirely different things, and failing to tell them apart is the actual subject of this episode. First: nothing happened on the ground — no match, no selection, no controversy, therefore no record. Second: something happened, but the extraction failed — the source was unreachable, the parsing broke, or the original article was hollow to begin with.

In both cases the file looks identical. Both say N/A. And that is the oldest problem in cricket journalism: we are not short of data; we are short of provenance. A Ranji middle-order batter’s nine not-outs sit in some scorecard, but no reporter ever wrote what they meant, because no one was ever sent to ask. The figure existed. The interpretation did not.

Core: the two-ledger book, with one ledger blank

My work has always been written in two columns — the Sri Lankan recollection and the Indian present. This file opened a third column, and it is the most uncomfortable one: the column with nothing in it.

Look from the Sri Lankan side. Board statements, selection-committee briefings and contract disputes have been the real cricket news there for years. Readers already know that an official release and the truth are not the same object. So "insufficient information" is not an insult there; it is a permanent condition people have learned to live inside. Look from the Indian side. The expectation is different: something new every hour, an opinion on every rumour, and leaving a blank blank is treated as laziness.

Here my most reliable example arrives, and it begins with numbers and moves past them. July 23, 2026, Lord’s, the Women’s World Cup final. England made 228/7; India were bowled out for 219 — a gap of nine runs. India were 191/3, with Punam Raut’s 86 and Harmanpreet Kaur’s 51. The desk wanted 300 words of wire copy. I filed a 1,200-word pitch-side notebook about the hush near the Long Room and the tears by the boundary. Two editors returned it. One digital desk ran it.

That day I made a rule I still keep: every match file opens with three sensory details and one verified number, never with commentary. Applied to this empty file, the result is plain — I have the three sensory details (the hum, the ring, the screen’s glare) and not one verified number. So what can be written is not about cricket but about cricket’s information machinery.

And that machinery asks a blunt question. When a document says of itself that it holds nothing, what does a reader trust? The rumour that arrives confident, or the honesty that arrives empty? Experience says the reader picks confidence. That is where the trouble begins — the market rewards confidence and does not reward verification. In transfer windows this is at its clearest: the release-clause structure, the wage bill and the agent’s movement are the real story, but headlines are built on the fee. A fee is hard to verify; a clause is harder still to read; so the easier of the two gets printed.

There is another layer that is easy to skip. An empty file does not only show an absence of information; it shows a power structure. Where coverage is never sent, data is never made. The lower domestic pyramid, regional-language commentary, the groundstaff, the pre-2026 record of women’s cricket — those files are structurally empty, and they are empty because nobody took on the job of filling them. When I close such a file as "insufficient information," I am not recording that absence. I am ratifying it.

Contrarian: the illusion of more data

Cricket journalism’s firmest belief is that more data makes a better story. It never breaks, because every year hands it a new instrument — pitch maps, strike-rotation grids, economy splits, tracking cameras. But the empty file showed the reverse: abundance of data and availability of information are different things, and in cricket the first is rising while the second has stalled.

Consider a Ranji fast bowler’s fourth-day spell count. You will find it in three places. You will find nowhere on paper which tape he bowled it on. Three numbers, zero context. And a number without context becomes an opinion that anyone can read to suit themselves. This is my other quietly held disagreement: calling the return of a three-at-the-back line progress is convenient, when it is often just a structure for avoiding the reputational risk of a four-man line — the same convenient frame as calling a rumour news.

The same logic has a dangerous second use. Saying "the information is insufficient" and falling permanently silent is also a kind of theft — of time, and of the reader’s trust. My own habit has been exactly that: think, delay, and by the time the file closes the subject is stale. A WPL final, a selection storm, an auction night — these are over before the file is done. So I set myself a rule: a 600-word fast field note on every event, and the long braid reserved for subjects that genuinely need the archive. Publish the note, bank the material. Treating an empty file as a certificate of integrity and sleeping inside it is the bigger betrayal.

In 2026, the IPL in the UAE ran 60 matches with no spectators. On September 19, 2026, Chennai beat Mumbai by five wickets in Abu Dhabi, and the loudest thing in the ground was the dugout. I recorded 43 minutes of ambient audio — breath, spikes, the echo of the toss. One editor returned it as too quiet. A digital desk ran it. That taught me that absence is reportable, provided you can say what is absent. Today this file says exactly what is absent: title, source, names, date. All of it.

Takeaway

Two lines of decision come out of reading this file. First, I will not publish it — not as news, not as analysis. Second, I will keep it on record, because it is itself a story: the Asian cricket information chain has knots beyond which nothing travels, and we fill those knots with rumour.

The next time a file comes back this silent, the question should not be which headline we use to fill it. The question should be who left the filling undone — and for how long it has been undone.

Some columns are unwanted because they are early. And some files stay empty because nobody ever treated filling them as their job.

Nine runs. Whole life. Here, not even nine.