The Day the File Arrived Empty: Why 'No Result' Is Cricket Reporting's Most Honest Outcome

At two in the morning in a London flat I opened the laptop and went into the folder. The folder was named after a date. Inside was a single file. The title field read N/A. The source field read N/A. The type field read Unclassified. Beneath that sat a table with a column headed 'information points', and that column was empty all the way down. One thing in the whole document was not empty: a label reading cricket_asia.

My hands went to the keyboard first. Thirty-seven years of habit. An empty cell and an urge to fill it. I started wondering which match was on in Colombo, which series, which board decision. Then I remembered that this was the same moment that left me unable to write for two weeks in Cornwall in 2026. My editor had sent a single question then: what remains when the crowd is gone? The answer was silence, and the silence eventually became the script.

This piece comes from that same place. There is no team name here, no batting average, no contract figure. What exists is an empty file, and a writer sitting in front of it deciding whether to fill it or not.

What the Machine Cannot Say

Cricket analysis runs on a simple chain. The first stage pulls small factual units out of a document: who, when, in which format, did what. The second stage arranges those units across eight layers — format, player, team, league, governance, risk, public narrative, industry transmission. Every sentence in every layer stands on one of those units. No units, no sentences.

The chain has broken in three places. The information-point list is completely empty. There are no entities at all — no team, player, board, coach, ground or competition, not a single name. And the domain label reads cricket_asia where the specification requires Cricket. That third detail is what makes me suspicious: this is probably not an empty article but a parser that failed.

Think about it. If a pipeline returns title, source and type all as N/A while still assigning a domain label, the pipeline found the document but could not get inside it. A paywall, a JavaScript-rendered page, a Bengali or other non-Latin source the extractor could not tokenise, a video or social post with no body text — any of those could be the cause. I am speculating here, and labelling it as speculation.

The territory is familiar. At the London World Athletics Championships in 2026, Wayde van Niekerk won the 400m in 43.98 and Mo Farah took the 10,000m in his final track race. I filmed warm-up laps, mixed-zone silence, athlete podcasts, and cut a twelve-minute episode. A large portion of that footage was never used. The camera was running and nothing was happening. Only later did I understand that the 'nothing was happening' was the actual document.

Staring at the empty cell brings something to mind. Cricket already keeps an empty column. The scorecard has a cell called 'no result'. When rain comes, when light fails, when a crowd walks onto the field, play stops — but the scorecard is not torn up. The cell stays where it is.

The Grammar of the Empty Column

13 March 2026, Eden Gardens, World Cup semi-final. Sri Lanka made 251. India were 120 for 8 in 34.1 overs, needing 132 more. Then the stands turned, the game stopped, and the match referee awarded the result to Sri Lanka.

Now ask what the result of that match was. The scorecard says Sri Lanka won. Someone else says India lost. Someone else says it was an incomplete match. All three can be written, and all three conceal part of a truth. What actually happened is that a game was stopped, and the stopping was the biggest event of the night.

Cricket accepted this problem long ago. Hence weather rules, Duckworth-Lewis-Stern, reserve days, the phrase 'no result'. Other sports resist the vocabulary. In football, an abandoned fixture sends clubs to court over who gets the points. Cricket moved a step further and conceded that some matches have no result, and that this too belongs in the record.

Here is my objection. If a scorecard can hold an empty column, why can't cricket journalism hold an empty page?

The second thing to learn is the format question. A batter's strike rate of 130 cannot stand alone. For an ODI middle-order anchor, 130 is roughly par or better; for a T20 finisher, 130 is clearly below par. Same number, opposite conclusions. Without the format you reach no conclusion, and if you reach one it is not a conclusion but a guess.

Without a format, a statistic is not a number. It is a rumour.

The same applies to averages and economy rates. A batter averaging 45 in Tests and a batter averaging 45 in T20 are not the same man. The first ten overs with the new ball and the T20 powerplay sound adjacent and behave nothing alike. A white ball does not move like a red one, and a floodlit stadium is never as quiet as Lord's.

That is why I cannot write a single sentence in front of this empty file. If I did, it would be about my memory rather than about cricket. Readers do not pay for my memory. They pay for accuracy.

The Pressure of the Template

Here is the real problem. A vast eight-layer mould, and a completely empty input. That pairing is dangerous, because a mould cannot tolerate empty space. Every layer has a table beside it, every table has cells, every cell has somewhere to write. Anywhere without writing invites writing.

That urge exists in people and in machines. Journalism has an old name for it: the believable paragraph. You read a passage and it is smooth, it has numbers, dates, quotations, and nowhere a source. The paragraph survives for one reason only — it reads well.

The larger the template, the more convincing the invented story sounds.

The most important sentence in the document was buried in it, and it was about language rather than cricket. It said that an absence of evidence does not mean 'no evidence of risk'; it means 'no evidence either way'.

Between 'no evidence' and 'no evidence either way' lies the entire ethics of journalism.

In the transfer window that distinction is at its sharpest. In January, a dozen names circulate every day. A club appears to be doing nothing. First sentence: 'the club is in crisis.' Second sentence: 'the club has not yet completed a signing.' The first sells; the second goes unread. The second is the true one. Silence is a fact, not an interpretation of a fact.

In January 2026 I chased the paperwork behind Enzo Fernandez's move from Benfica to Chelsea — £106.8m, family phone calls, an overnight flight, his first coach in Buenos Aires. Doing that work taught me one thing: a contract is sometimes a machine for postponing its own verdict. The loan-with-obligation deal does exactly that. The club pays nothing today, borrows the player, and a smaller club spends the next three seasons manufacturing a half-finished product it does not own. The document does not announce a result. It delays one.

Sponsorship clauses are quieter still. One sentence sits there in which a player signs away the right to speak on certain subjects. That is another 'no result' — an empty cell in the scorecard of speech that was supposed to be filled by the player himself.

At this point I stop. I name the clause, I name the person, and I stop. I do not reach for adjectives about the system. The reader supplies the verdict, because I have sworn off supplying it.

Seen from the Other Side

Everyone will call an empty file a failure. I call it probably the most honest output this pipeline has produced.

Consider the alternative. Suppose the machine had filled the empty cells. Suppose it had placed an invented headline in the title field and slipped four or five plausible-looking numbers into the information points. The reader would not have noticed. I would not have noticed, because I would have read it and assumed a colleague had gathered it. That is exactly how a false fact enters the industry — through one empty cell and one small question of conscience.

The fact that did emerge here is not about cricket. It is about the pipeline. The empty cell is itself a fact: it says the problem is not in the analysis but in the gathering. That is new information, information nobody had before this piece, and it satisfies the information-gain condition more completely than anything in the eight layers would have.

A second reversal. We love the almost. Fourth place, the rained-off day, the catch that was never taken, the teenager whose sprint was heard but not kept — I have written about these for years, because they are the truest record of a career. The clock is not a verdict; it is a character in the story.

Yet we extend none of that generosity to our own work. We want a report to deliver a result daily, a ruling on every match, every empty cell filled. An industry that treats the 'almost' as history is afraid to say 'no evidence'. That inconsistency is the real blind spot.

One more thing. This empty output gave me no chance to think about ODI or T20 cricket, because even the format is unknown. That is a form of protection. The most common error in cricket commentary is applying T20 powerplay logic to a Test, or judging a finisher by a Test average. When the machine stays quiet, I cannot commit it.

A third reversal. London nights remember every split, every heartbeat, every almost. A pipeline remembers nothing. It only keeps a log. And in that log, tonight's real story is written — not in the title, not in the source, but in a mismatched label beside an empty column.

The Next Run

What I have now is one question and one task.

The question: do you want a paragraph that sounds true, or a paragraph that is true? The difference is not only moral. It is professional. A false fact, once printed, does not come back — it gets cited in the next ten pieces.

The task is to start the next run properly. Pull the original link again, raw HTML, JavaScript enabled, and check whether a non-Latin source is being read at all. Make the format field mandatory — Test, ODI, T20, The Hundred — and hard-block stage two when it is blank. Require at least one team and one individual name in the entity field. And keep the date, because an analysis without a date is never alive.

A teenager once sprinted, and the old world leaned forward to listen. That sprint's split time is still on the timing sheet, because nobody allowed it to be absent. The file in front of us now has no split and no scorecard. It does not need to be thrown away. Keep it as a document — proof that there was a day we did not know, and knew that we did not know.

Let the next scorecard arrive. Until then, leave one column empty.