The Empty File, The Full Ground: Where the Cricket Information Chain Goes Silent

2:47 in the morning. One screen is lit in a London office; the rest of the room is dark. On the screen sits a table — eight rows, eight cells, each carrying the same sentence: insufficient information. Title field, N/A. Source field, N/A. Player field, N/A. Time-sensitivity field, N/A. The printer ran out of cartridge weeks ago, so the room has no sound except the laptop fan and the rain outside. An empty desk has its own soundtrack. It is not noise. It is the sound of absence.

The next morning, a minicab driver in Croydon winds down his window and asks me for the score. I tell him the file is empty. He thinks for a second, then laughs: then it is your computer that is ill, not the cricket. The car pulls away. I stand on the pavement. That one line contains this whole column.

I began writing cricket at the Prothom Alo desk in Dhaka in 2026, covering the Wills Cup. There was an unwritten rule in that newsroom: however many gaps a report has, the scorecard can have none. Not printing a wrong number is the first lesson of journalism, and nobody teaches it — you learn it from the glance of the senior on the desk. Nine years later, in London, I find that same lesson returning at a larger scale, except the scorecard has become a pipeline and the senior has become a table that says: insufficient information.

It helps to understand how a single cricket report is born. In the first step, someone watches the match, breaks it apart, pulls out information points — who scored what, what shifted in which over, who was hurt, what the crowd sang. In the second step, another desk joins those points into meaning: format, technique, team, market, governance, risk, rumour, industry flow. This is not really a machine story. It is a story of two desks in a newsroom, with new names. When the first desk comes back empty-handed, the second desk has only one honest move: show the empty hand.

The trouble is that the person sitting at the second desk is always under pressure. Readers are waiting, an editor is looking, the slot is blank. Then the hand moves by itself. A name can be filled in, a score can be remembered into existence, a trend can be guessed at. This is where cricket journalism's deepest danger lives, and artificial intelligence did not discover it — humans discovered it long ago. An empty cell always pleads to be filled, and a writer who cannot easily refuse that plea will one day be caught inside a story of their own making.

I have my own version of this. On 22 April 2026, a first-year Sports Journalism student at City, University of London, I covered Leyton Orient's 3-0 home defeat to Crewe Alexandra, which confirmed relegation from League Two. I did not write a match report. I wrote 1,200 words about the two thousand supporters singing 'Orient Till I Die' after the final whistle. Classmates said it was too soft. I rewrote it four times, and each time the result line moved lower and the human line moved higher. Since then I have kept a rule: if fan feedback stings, wait 24 hours before rewriting, so collective memory does not flatten my own voice.

That rule still works, only the setting has changed. On 11 July 2026, the World Cup semi-final, England lost 2-1 to Croatia after extra time. Kieran Trippier scored from a fifth-minute free-kick; Harry Kane won the Golden Boot with six goals. Those two facts will be found in any database today. Nobody in the Croydon fan park that night was cross-checking them. After Trippier's goal a stranger hugged me, and the piece was shared by four thousand supporters. Where a fact takes hours to reach a database, a touch takes seconds to reach a stranger — and the journalist's job is to record the distance between the two.

Now the real question. The pipeline has returned empty, and rather than mourning it I want to ask: is an empty return a failure, or is it the most honest output available? The industry calls the first null handling and the second source transparency. My old desk calls it not lying.

Think about how many hands a cricket fact passes through. The scorer at the ground, first hand. The statistician in the broadcast box, second. The feed provider, third. The news agency, fourth. The sub-editor on the desk, fifth. The social media caption writer, sixth. Then a fan park, a minicab, a corner shop — seventh, eighth, ninth. Each hand is an entry; each entry is a witness. The experiments with distributed ledgers in sports data are attractive precisely because of this: nobody can quietly delete an entry. But cricket's real ledger was never on a server. It lived in tea stalls, on bus seats, in the conversation outside the mosque while people took off their shoes.

Remember that night at Liverpool. On 22 July 2026, Liverpool beat Chelsea 5-3 at Anfield to lift the Premier League trophy in an empty stadium. I was interning at a London sports desk, interviewed twelve season-ticket holders over Zoom, and wrote about the echo of the Kop's absent songs. The piece ran on a fan site and drew thirty thousand reads. Its first hundred words contained no goal description — only echoes, empty seats, and a song nobody sang. The strongest sentence in cricket writing is often the one where nothing happened, and writing it takes courage, because the urge to fill empty space is built into the profession itself.

Where does that urge come from? Three places.

The first is commercial. An empty slot means empty advertising, empty clicks, empty subscriptions. When a cricket site's editor sees traffic fall, he will not tell the writer to be more honest. He will say: give me more story. That pressure is invisible, and it is daily.

The second is technical. A language model can produce a thousand words a second and never knows whether it is lying. Ask it for a match report with no data behind it, and it will politely invent a match — lovely cricket, perfect timing, a believable score. The frightening part is not that it lies. The frightening part is that it lies well. And readers cannot tell, because a well-written lie smells faint.

The third is cultural, and it is the most complicated. We cricket writers grew up on an expectation: every match must yield a meaning. Cricket is never only cricket; it is nation, migration, class, history, politics. I believe that too, and I will not abandon it. But it casts a shadow: when meaning cannot be found, we manufacture it. Turning an ordinary match into an epic, turning an empty data field into a profound crisis, turning a banal remark into a historic statement — these are symptoms of the same disease.

Here is my second argument. The biggest crisis in cricket's information system is not the false number but the excessive trust in numbers — because numbers do not speak on their own; the habits of the people behind them do. My old suspicion of heatmaps comes from here. A heatmap can show that a batter is weak on the off side. It does not know he is playing through injury, or that team management told him to leave the ball, or that his mother is in hospital. A heatmap is a picture of a habit, not of a life. When we substitute it for a life, we get something beautiful, clean and entirely false.

An uncomfortable admission belongs here. If today's empty file had carried the name of a major star, I might not have accepted the table so easily. The pressure around writing about stars is different. Star-first tactical breakdowns are my least favourite genre — the player as isolated genius, the crowd as scenery. But honestly, I have fallen into that trap. Once, writing about a transfer, I spent nearly two thousand words on fees and statistics and kept only two lines for the fact that the boy was not learning the language of his new country, and what that would do to his game. My editor sent it back: you wrote the price, you did not write the person. Since that day my transfer pieces open with recovery, fear and hope.

I am twenty-seven now. Nine years in London have taught me something no database holds. In England, cricket's real newspaper is the street. In Croydon, the fan park turned a postcode into a passport — I saw it myself in 2026, when people who did not know each other sang the same song. In Tower Hamlets, in a barber's chair the day before a match, you can learn what the pitch will do in a way no feed has told you. In Birmingham, a corner shop writes the score on a slip of paper in the shopkeeper's own hand, and it is often faster than the official update.

I am not romanticising this. I am saying it because it is the source of my deepest professional fear. When the data is empty, the street knows — but the street's knowledge never enters a citation, so it never enters history. I have often seen the most accurate account of a match come from an exiled supporter who was not at the ground, was watching a buffering stream, and was telling his brother on the phone what was happening. That account is written nowhere. The next day's official report carries the clean numbers, and who cried when is lost.

Let me speak about translation, because it sits at the centre of my work. I have spoken with many cricketers and coaches through Arabic, French and Spanish interpreters. Every act of translation has two layers: what was said, and what the interpreter chose not to say. I now name the interpreter in every interview and state in the piece which sentence is direct translation and which is the interpreter's gloss. This is not politeness; it is a question of accuracy. A writer who passes off the interpreter's invisible labour as his own insight is deceiving the reader — politely, in elegant sentences, but deceiving him.

The same principle applies to today's empty file. What the pipeline did not give me, I will not invent. But why it did not give it, I will write. There are two possibilities, and their meanings are entirely different. One: the source article was genuinely empty or unreachable — a paywall, an encoding failure, an empty scrape. Two: the article existed, but first-stage extraction failed. The first is a journalism problem; the second is an engineering problem. The first is solved with a phone call, the second with a log file. Someone who does not distinguish them and applies the same response to both solves neither.

The frightening thing is that nobody usually looks for the distinction. An empty output appears, and everyone assumes the source is at fault. In my experience it is often the reverse — the source was fine, the person behind it was tired, the deadline ran out, the list stopped halfway. This happens daily in newsrooms. The difference is that in a newsroom somebody raises a hand and says: I do not have this, does anyone? In a pipeline, nobody raises a hand.

This is my most important observation. A pipeline's greatest weakness is not its failure but its silence — because failure is visible and silence is not. A wrong score at least creates an argument, prompts a check, produces a correction. An empty cell creates no argument at all. It simply stays quiet, and then somebody fills it with a guess. That is why every empty field should carry a mandatory signature: who left it empty, why, and when it was last checked. That is real chain of custody. Whatever the technology is called, the principle is old — whoever makes the entry signs it.

I want to be clear, because misunderstanding is likely. I am not against data. I look at data every match, at form, at recent trends. My argument is that data is the beginning of a question, not the answer. Consider the regular season. The table often lies, because it does not know who played how many matches away from home, who played through injury, whose schedule was cruellest. Over recent years I have built a simple habit: look at the fixture list before the table. Most of the time, the team said to be in crisis played four of its last five against top-four sides, and one of those away. That fact is not in the table, and without it the table is meaningless. I found it because I watched the matches, not because I read the scorecards.

About that watching. For eleven years I have watched cricket — first from the stands in Dhaka, later on a screen at a London desk, sometimes standing in a fan park. That watching taught me something no report contains: rhythm. When a team breaks, it does not show in the scorecard; it shows in the half-second of hesitation before a dropped catch, or in a bowler's run-up losing one stride. That rhythm is the real information, and it cannot be captured in numbers, only in description. And description is why writers are needed.

Now the part where my profession is not comfortable.

Cricket writing has an unwritten rule: everything that happens must have a cause, and the cause must be intelligent. A team lost? Tactical error. A player lost form? A mechanical flaw. A series turned heated? Politics. This explanatory instinct is our trade's life and also its trap, because in reality many things happen for no reason at all. A catch goes down because the sun was in his eyes. An innings breaks because the batter's mind had drifted home. A team loses because one day everything goes wrong. Write that, and readers say: this is not analysis. But the truth is often less elegant than the analysis.

Here is my contrarian point, and it will be a little uncomfortable. Much of what we cricket writers call deep analysis is a cultural ritual in which we arrange events after the fact so that they appear to have been inevitable all along. The ritual comforts us, gives readers a story, gives advertisers confidence. But it does not build predictive power; it merely tidies the past. The genuinely good analyst speaks before the match and accepts the risk of being wrong. Speaking after the match is easy, and speaking after the match makes everyone look clever.

I want to extend this to the empty file. When no data arrives, our instinct says: this is a crisis, build a big story about it. I say: no. Sometimes empty means empty. A tool failed. That is all. Making a legend out of it is also a kind of lie, told with emotion rather than numbers. And that lie is more dangerous, because people question numbers and nobody questions emotion.

Does that mean we have nothing to say about the empty file? The opposite. We have a great deal to say, not by inventing a story but by showing the process. I want to know what the source was, who checked it, where it stopped, who is accountable. These questions move something at the edge of cricket journalism into the centre: the labour of information. The person reconciling a scoreboard at three in the morning, the freelancer outside a stadium sending updates by phone — nobody sees their work, because when it succeeds it is invisible. And when it fails, everyone blames them.

My third argument sits here. The real asset of cricket's information economy is not its stars but the invisible workers who keep its facts trustworthy — and making their work visible means returning the game to its foundations. Seen this way, an empty output is not a technical fault; it is a human signal. Someone is tired. Someone was rushed. Someone skipped a step. That information may matter more than a complete report, if we learn to read it.

Let me go somewhere tender, because this piece would be incomplete without it. On 12 June 2026, at Euro 2026, at Parken Stadium, Denmark against Finland, Christian Eriksen collapsed in the 43rd minute. The match later resumed; Finland won 1-0. I organised a fan roundtable with a counsellor and then wrote. Since that day I keep rules: a trigger warning on every sensitive piece, a helpline number on every related piece, a counsellor's eyes on every draft. And one more: I will not chase reaction quotes from a player in distress.

Why bring these rules up? Because behind an empty file there is often a tired person, and behind a full one too. When we hurry, the finest things break first — how people are feeling, who is being left out, whose voice is missing. That is why I will not treat today's output as a failure. I treat it as a pause. In a pause we hear what the noise covers.

And here sits the greed I am most guilty of. Disaster stories are easy to write, and easy stories travel furthest. A post about a migrant family's struggle gets four thousand shares, while a post about the same family's ordinary Sunday gets none. That is fine, if we ask ourselves: am I writing this for the people, or for my own reader numbers? That question should sit in every draft, and it often does not. Kindness and greed can live in the same sentence, and the journalist's job is to tell himself honestly which is which.

I will not romanticise the crowd. A fan park is not always a beautiful place. There is drinking and abuse, women are made uncomfortable, poorer families stay outside because of ticket prices. The hug in that Croydon park was real, and so was the person standing alone in the same park because nobody knew him. A writer who records only the embrace and not the exclusion paints a half-truth, and the half-truth sells best.

Before closing, a practical note. What is the way out of an empty output? I have three simple proposals, none of them technological miracles.

First, every empty field needs a reason. Insufficient information is not enough; write why — the source was unreachable, or reachable but unreadable, or readable but not extractable. Those three demand three different responses, and without the distinction the second desk cannot decide anything.

Second, treat an empty output as a signal rather than a secret. If several consecutive runs return zero information points, the problem is in the process, not the source. That is a health check. Newsrooms that run it regularly print fewer errors.

Third, and most important: before filling the empty space, ask the street. In my experience, when an official feed goes quiet, a community is still talking. That talk needs verification, not blind belief, but it needs listening. Journalism is not only the delivery of facts; it is asking in the places where facts are missing.

All three proposals are an old sentence said anew. The senior on my first desk used to say: the scorecard never lies, but the scorecard never tells the whole truth. Today I would push it a little: a pipeline never lies, but a pipeline never tells the truth either — people tell the truth, the ones behind it, and the ones who carry it on the ground, on the pavement, in the corner shop.

Let me return to that night. 2:47, the empty table, the sound of rain. If I had filled in a name then, guessed a score, invented a story, the reader would have got something. But he would have lost something: trust. Trust is a strange thing. Once lost, it does not come back, not even with a hundred correct numbers.

The minicab driver did not come back the next morning. But his sentence stayed: the computer is ill, not the cricket. The cricket is well. The ground is full, the stands are singing, some are crying, some are going home. Our machines fall ill from time to time, and in those hours our greatest work is learning to keep quiet.

I leave the question with the reader. The next time you see an empty cell, a zero, a 'no information', ask: did nothing really happen, or did nobody look? The answer will tell us how much we love cricket, and how much we merely love the score.