The Empty File: What Went Unsaid in Asian Cricket's Data Room

Two forty in the morning, Pune. The tea on my desk has gone cold and there is an open file on the screen with eight fields in it. Title: empty. Source and URL: empty. Publication date: empty. Information points: empty. Core viewpoints: empty. Entities — teams, players, boards: empty. Time sensitivity: not assessed. And the eighth field, the only one still alive — a single tag: cricket_asia.

That is the shortest cricket report ever delivered to me, and possibly the largest. A system whose job was to read one piece of Asian cricket each morning opened eight boxes, looked inside all eight, and walked away leaving them empty. No player, no ground, no score, no date. Only a geography — Asia. As if someone had said: cricket happened yesterday, but I cannot tell you where, between whom, or who won.

Thirty years ago I would never have held such a file, because thirty years ago no file existed until somebody picked up a telephone.

My first job was on the sports desk of The Times of India in 2026. There was an unwritten law there, printed nowhere and known to every sub-editor — no line without a name, no paragraph without a date. When I moved to The Hindu in 2026 the desk got bigger and the cloth a little cleaner, but the law did not change. And on the Sharjah one-day circuit, where I spent eight years, I saw that law in its hardest form: every conversation began with the question "who said it?" and if the answer was "you'll find out," the conversation ended there.

That desk no longer exists. The room no longer exists. The system that handed me an empty file that night is not a newspaper desk but an automated pipeline whose work is to read somebody else's sentences, pull facts out of them, and drop those facts into fields. Every publisher now runs one, or rents one, or buys the output of one.

These pipelines have one virtue worth understanding: they do not lie. When the article in front of them contains no name, no number, no date, they simply return the fields empty. And the habit of our entire industry has been to treat an empty field as "nothing found" — or, far more dangerously, to fill it from our own priors.

I did not do that. I closed the file and went to bed, and by the next morning I understood that what I had been looking at was not a technical fault. It was an X-ray of the whole beat.

To explain that I have to go back into my own work — the work I have done since 2026, when I first decided I would never open a script with a result.

18 June 2026, The Oval. Pakistan beat India by 180 runs; Fakhar Zaman made 114. A year later, offered a film on India and Pakistan, I did not begin with that scoreline. I picked up a calendar, and the calendar had a hole in it — the last bilateral tour, the winter of 2026–13. Every meeting since has existed only inside an ICC event or an Asia Cup. September 2026, Dubai: India beat Pakistan twice in five days, and neither was a bilateral series. It was a host country's favour.

The film was called "The Only Way We Meet," and I built it on three witnesses — a player, a groundskeeper, a fan. That was not an artistic flourish. A highlight reel can be assembled without truth: four cuts, one music track, a voiceover, and the story is done. Three witnesses cannot be assembled without truth. Somebody had to be on that ground. Somebody had to cut that grass. Somebody had to buy that ticket.

Two broadcasters called the film unpatriotic and passed. I still have not decided whether I was right. But I knew I could not put a thing with no evidence on a screen and let adrenaline carry it.

Here is the link to that empty file. Absence has a formation too, and it plays every week. In 2026 the absence of India–Pakistan cricket was information, not rumour — no date, no ground, no series. And to write that absence I needed exactly one thing: a human being who had lived inside it.

The file that night contained no human being. No player, no groundskeeper, no fan. Only a geography. That is the difference between an empty room and an empty file — even an empty room has walls, and somebody built them.

The most honest meaning of an empty file is this: nobody made the second phone call.

I remember what a phone call cost in 2026. You booked a trunk call, an operator connected you, and if you had not said your piece in three minutes the line went dead. That expense disciplined us. You did not pick up the phone unprepared, because picking it up was a cost.

Today the call is free. A message, a voice note, an answer by midnight. And still the call does not happen — because the reward has changed. In 2026 the reward came from being right; a wrong line meant a red face on the desk at dawn. In 2026 the reward comes from being present. Right or wrong, if your line is on a screen by nine, the algorithm pays you.

My clearest memory of my own error is Adelaide, 19 December 2026. India bowled out for 36, their lowest Test total, Josh Hazlewood taking 5 for 8. I wrote the whole crisis chapter in one night, and in the morning I deleted a paragraph — the one with the redemption in it, the one where India came back. I deleted it because it was not true; it was a habit. A story that ends at 36 has to end at 36.

That same habit is what fills an empty file. We are addicted to comfort. We cannot bear a field left blank. We think that leaving it blank means our work is unfinished, when in fact filling it with something that never happened means our work is ruined.

I learned this concretely in the summer of 2026, and it is still the rule I work by.

20 July 2026, Derby. Harmanpreet Kaur made 171 not out off 115 balls and India beat Australia by 36 runs. Three days later, 23 July, Lord's. India slid from 191 for 3 to 219 all out and lost to England by nine runs. The film was called "Nine Runs," and it carried no commentary at all — only the players' voices.

Why? Because for twenty-two years I had made men's cricket films, and I knew what commentary does: it does not explain the story, it takes the story's voice away. That is exactly what had been done to the women's game for two decades. Every good innings got the same sentence — "she strikes the ball beautifully." There was no cricket in that sentence, only surprise, and surprise has no score.

So I removed the commentary and kept the breath. The player breathing. The player sitting in the dugout. The silence after a loss. The people who wept watching that film did not weep at the score. They wept because for the first time they heard a woman cricketer's actual voice, undubbed.

From that I made a second rule: no music under a loss, only ambient sound. And when in 2026 I had to make a twenty-eight-minute audio documentary on the IPL's UAE edition — Mumbai Indians beating Delhi Capitals by five wickets in the Dubai final on 10 November 2026 — I built it entirely from stump mics and the hum of empty stands. Locked down in Pune, I had nothing but sound. And in that sound one thing was audible: cricket was being played, and there was no crowd. When there is no crowd you learn how much of the game is sport and how much is show.

That year I adopted a habit I recommend to every young writer: the no-crowd draft. Write the first pass with the crowd muted. If the story stands without the noise, it is a story. If it sits down, it was only atmosphere.

Apply that test to the empty file. It is a no-crowd draft — no title, no name, no score. And it did not stand up. I have to accept that.

But the real question begins here, and it is a question about Asian cricket, not about software.

Demand for cricket in Asia is constant and enormous. Every morning millions of people wake and ask what happened yesterday. That question never falls, not in the rain, not in the year after a World Cup. When demand is that stable and supply — verified information — is that finite, the market does not fill the gap with verification. It fills it with inference.

Inference has its own grammar. Given a tag like cricket_asia, four ready branches open at once: a bilateral series, a regional event like the Asia Cup, a franchise league, a board-level decision. Each branch has a dozen sentences already written, because they have been printed a dozen times in the last decade. Filling an empty file from those sentences needs no reporter. It needs a keyboard.

And that is my real worry. The problem is not that a machine read nothing. The problem is that the article contained nothing worth reading — and a human being wrote it.

Which brings me to what almost nobody in this argument says, and what seems most true to me.

Everyone blames the machine. The machine invented nothing. It learned what we showed it. The oldest corruption on this beat is not a failure of verification; it is an appetite for access.

I watched that corruption up close during the match-fixing years around 2026. In those days a board's silence was a product, and you paid for it: you got the dressing-room line, and in exchange you did not ask the Ranji question. That bargain is never written down in a press box, but every senior reporter can smell it. I have been walking with that smell for forty-five years.

The machine is the industrial version of the same bargain. The trade used to happen inside a person — one reporter deciding what he would not write. Now it happens inside a system: somebody writes, somebody summarises, somebody republishes, and in the end the summary becomes the source. The empty file is not the last stage of that chain. It is its most honest stage. At least it did not lie.

The second misunderstanding belongs to readers, and it matters more. Readers assume an empty file means nothing happened. It does not. Silence in a payload carries no evidentiary weight. Absence of mention is not absence of event. That is precisely why I refused to fill it. Had I written one plausible sentence that did not exist, I would not have committed a small sin — I would have taught a billion and a half readers that the file was never empty at all.

I also have to admit I have written many such sentences myself. In the fever of the seventies and eighties I opened match pieces with the result because the desk demanded it, and I heard in the tape what I wanted to hear. So when I speak about verification I apply it to myself first. I do not treat memory as evidence. I treat the tape, the clipping, the date.

I listen for the pause between the roar and the replay. That pause is never actually empty — it holds the questions nobody asked. Who said it? Where is it written? On what date? Whose name? If those four have no answers, the pause is not news. It is noise.

So what now?

I hold no hope that every cricket publication will verify its fields by next year. The structure of the market is against it. But I hold some hope for readers. Open your morning cricket story and demand four things: a date, a source, a name, and one fact you can check yourself. That is not a small demand. It is the minimum below which a report stops being a report.

And if you ask me what to do with a file whose eight boxes are empty, my answer is this: close it, but do not throw it away. It is the cleanest document we have of a simple fact — that the record of the game we call history is rebuilt every morning, and every morning somebody would rather rebuild it without the work.

The scoreline is only the loudest part of the story. This time there was no scoreline at all. Only a silence, and the silence was telling the truth: nobody made the second phone call.