The Empty Feed: How Cricket Counts the Silence Between Two Deliveries

6:40 pm. Twenty minutes to the toss. The table on my screen is lit and every cell in it is empty. The title field reads "not applicable," the source field reads "not applicable," the information-point count is zero. Outside, the groundstaff are watering the pitch, someone is dragging a set of stumps down the corridor, and the press-box coffee machine has failed for the third time. My laptop is telling me that, as of this moment, the world knows nothing about this match.

The press box does not stop. The colleague on my left asks into her phone, "Got team news?" I shake my head. She understands. Behind me someone throws the classic question — "What's the format, T20, yeah?" I say the scoreboard knows and my feed doesn't. Nobody is satisfied with that answer. They shouldn't be.

The notebook filled itself one stop before the stadium. Getting off the bus, the gate steward mentioned the pitch had been covered longer than usual, which means moisture. A local scorer sitting near the front said the columns on today's sheet had been extended, which suggests someone expects Duckworth-Lewis-Stern to come into play. The woman at the coffee stand said the queue was short, which means people believed the forecast. Three sentences, half an evening's information. They are in my notebook, dated and timed.

And the screen is still at zero.

That is the real subject here. Because on the evenings when cricket's data pipeline goes quiet, what we usually do is write guesses. And writing guesses is how you find the weakest joint in cricket journalism.

Cricket data is a staircase, and the first step is format. Without that step, nothing above it is reachable. Test, ODI, T20, The Hundred — the metrics do not transfer. A T20 economy of 8.0 is par; below 7.0 is excellent. A Test bowling average under 30 is elite; the same figure in ODIs is ordinary. Powerplay means overs one to six in T20, two fielders out. Test cricket has no powerplay, only the new-ball spell and the weariness of the final session. Death overs mean 16 to 20 — but in a Test, the decision to take the new ball at 80 overs is just as dramatic, and its numbers are a different language entirely.

From years of sitting in grounds, I can tell you this distinction is not only tactical but linguistic. A writer who reports a Test in T20 vocabulary does not produce false facts — he asks false questions. And the analysis that comes out of false questions reads beautifully while having no relationship to what happened on the grass.

The format field in my feed was empty. The first step of the staircase was missing. That does not mean I cannot write; it means every sentence I write will be an assumption.

The second gap was louder. The article type was flagged "unclassified" — the system could not even decide whether the source was a match report, an auction item, an opinion piece or a statistical feature. That sounds trivial and is not. A match report's truth and an auction's truth are different truths. One asks what happened; the other asks who went where for how much. IPL right-to-match cards, retentions, the gossip an hour before the hammer — different grammar altogether. National-team news brings no-objection certificates, central contracts, board-versus-player friction. Pour all three into one mould and the reader is misled, and that is not the reader's fault.

The third gap is deeper. No player, no team, no venue. My experience says even a poor extractor surfaces proper nouns, even when it has landed in the wrong domain. When not a single name arrives, the failure is upstream — in collection, or in schema mapping.

And one small signal deserves attention: the domain label read "cricket_world" rather than the expected "Cricket." Call it a typo if you like. I read it as a mirror. The pipeline did not know what it was looking at. A system that misidentifies its own subject will not catch the subject's subtleties — not the fifth-day pitch, not the field placement in the 16th over.

Now the part nobody discusses. Behind the blank screen there are people.

I write the substitutions the broadcast cuts away from. The scorer who presses a key for every delivery — no-ball, wide, leg-bye, penalty runs — that rhythm is the feed. The data operator at the boundary edge whose finger slips one ball behind, shifting an entire innings' graph by a line. The driver who moves us between grounds, the translator who builds a bridge between two languages in the corridor. The invisible scaffolding.

In Russia, the press bus kept time better than my heart. At the 2026 World Cup I filed from Volgograd on England 2-1 Tunisia and from Nizhny Novgorod on 6-1 Panama and 0-1 Belgium, and what I learned across those three matches is that a tournament's schedule is a bus timetable. The 3,000 England supporters who travelled, the ones waiting outside the Repino base — their stories never entered a feed. My 1,800-word piece on fan travel costs was shared 4,000 times because it carried routes, prices, songs, meeting points. Not data. Timetable.

But here is the honest part: I could write those pieces because I knew the score. Minute of the goal, scorer, ground. The facts existed and the story wrapped around them.

Tonight it is reversed. The story is here. The facts are not.

And that is where journalism's oldest test arrives: the temptation to fill the blank. Cricket has many names for it — "sources indicate," "club sources understand," "word from around the ground." In injury reporting the temptation is most dangerous, because clubs disclose the injuries that suit them and the rest stays behind the dressing-room door. A writer who fills that gap with inference will be caught eventually, and every accurate fact he ever filed will be doubted with him.

I learned this writing the oral history of Brentford's 2026-20 season. After the 1-2 play-off final defeat to Fulham at an empty Wembley, I spoke to 14 players, staff and a steward, wrote 9,000 words, and anonymised three sources at their request. How the club kept 1,200 furloughed staff and players' families connected was the spine of it. If someone had handed me an empty data table then and said "make a story out of this," I could not have. And if I had, nobody would have believed it.

An empty dataset is not the absence of an event. It is the failure of a system. A journalist's job is not to hide that failure but to name it.

Outsiders get this backwards. They assume an empty feed means nothing happened, so there is no news. The opposite is true. On the night the feed goes to zero, the biggest event in the press box happens not on the field but on a laptop beside it.

And the second misreading is cleverer, therefore more dangerous. We say "the algorithm failed." Algorithms usually fail where nobody remains to feed them. Feeds do not stop because the code is weak; they stop because the person who would have noticed a gap was made redundant last quarter. The biggest risk in cricket's information economy is not technical. It is staffing. We stare at the machine while the error sits in a budget line.

This is also where I want to push back on something. Format discipline is loosening across cricket analysis. Test averages sit beside T20 strike rates in the same table, "all-rounder performance indexes" are printed under one headline, and readers take the comparison as given. The ICC publishes separate Test, ODI and T20I rankings for a reason. The World Test Championship table and a T20I ranking do not run on the same logic. Analysis that refuses the distinction is not analysis. It is decoration.

I have a plain test. If you cannot tell, after reading a piece, how many overs the match was, the piece did not answer your question — it sent your curiosity to the wrong address.

At 7:15 the feed returned. Slowly, in pieces: two team names, then a venue, then the toss. By then I had the score the old way — from the big board, from the PA, and from a steward standing under the stand who said, "Slow pitch today, batters won't find it easy."

The empty stadium still had a pulse; I pressed my ear to the concrete. That was the lesson of 2026. A full stadium's pulse is louder still — it tells you who is winning, who is afraid, which over made the crowd go quiet. None of that is in a feed.

So what is a feed for? Structure. Who is batting, how many balls remain, who has the new ball. But why the fielder went to third slip, why the captain brought spin in the 14th, why the opener abandoned his natural game in the powerplay — those answers live on the grass, in the notebook, in the corridor.

I write the part the camera cuts away from: the three minutes behind the dressing-room door, the silence on the bus home, the empty cell between two columns of the scorecard that everyone skips.

That empty cell is the subject tonight.

And here is what we should be thinking about. What happens when a null payload moves downstream? The answer is simple and frightening: it becomes confident, fluent, beautifully shaped and entirely unsourced analysis. Cricket is drowning in that writing now. The line between what someone knows about an injury and what someone guesses has blurred past recognition. Many who hold forth on DLS targets do not know how Duckworth-Lewis-Stern actually works; they know that rain changes the target.

Over years of watching this trade, one pattern holds. The best cricket writers say "I don't know" most often. They can see where the blank is, and they decline to fill it.

Which is why tonight reads to me less as a failure than as an honest moment. A system admitting its own ignorance is more honest than most journalists manage.

The beat keeper does not cheer; the beat keeper counts the silence between. Tonight's silence was not between two deliveries. It was between two layers. And the question ringing inside it is not about any single match. It is about accountability: does the scorer's handwriting, one keypress at a time, reach the far end of the pipeline? Or does a label go wrong somewhere in the middle while all of us write confident opinions on top of the error?

Next match I will be on the bus again. The steward will say something, the woman at the coffee stand will read the crowd and forecast the weather, the scorer will widen his columns. I will write it down, dated and timed. And if the screen goes to zero again, I will print the zero.

Because readers want a story from me, not a wrong fact. And the hardest truth in cricket is this: the match ends, the scorecard remains. If the scorecard is wrong, nobody will remember who wrote the story.