The Empty Column: The First Mile of Cricket's Data Chain Has No Owner

October 2026. Nehru Stadium, Pune. Maharashtra had collapsed for 148 before tea, and I — three months into a trainee's job, sent from The Indian Express office on Bund Garden Road — was sitting in the scorer's box. A ruled register lay open, columns drawn in blue and red pencil. The old scorer wrote so slowly that I assumed he was doing it on purpose. Then, on one delivery, he left the 'how out' box blank and drew a small question mark in it. I asked what it was. He said, "The umpire's signal wasn't clear. I'll fill it tomorrow from the newspaper."

That question mark travelled with me. Twenty-nine years later I am looking at it again at scale — not in a stadium, but in an empty software table.

A few days ago a cricket analysis pipeline returned its output to me. Title: N/A. Source: N/A. One-sentence summary: blank. Author stance: N/A. And the most important field of all — the list of information points — entirely empty. The only thing filled in was the domain label: cricket_world. The system knew this much, that it was cricket, and nothing beyond.

In cricket, information does not travel on a straight road. It moves through a chain of six hands: the umpire's signal on the field, the scorer's register, the live-feed operator at the ground, the agency server, the broadcaster's graphic, and finally the newsroom. Something is lost at every handoff. The Ranji Trophy has been running since 2026 and its scorecards are still filled in on the ground by scorers employed by state associations; only after that does the number reach a screen. When an analysis comes back empty, the fault is usually not in the last link but the first.

Cricket journalism already has a word for this situation — the amended card. Two lines used to appear on an inside page after a match: there was an error in the previous scorecard, here is the correction. The data desk's world has no correction column. There, an error does not show; it simply flows downstream.

An empty list of information points is not the absence of data; it is the record of a handoff nobody filled. That is what turns a blank output from a technical glitch into an administrative document.

There are four kinds of failure and they need to be told apart. First, capture failure — the event never happened, or nobody was watching. Second, parse failure — text arrived but the system could not read its structure. Third, routing failure — the right cricket story went into the wrong bucket. And fourth, the most common and least discussed: the 'nobody was assigned' failure. The event happened, the ball is on video, twenty people saw it, but no one was employed to write it down. Cricket has a name for that job: scorer. The newsroom has no name for it, which is why it never appears.

Second, something thirty years of press boxes has taught me: an empty list has two possible answers, and only one is honest. The honest one is — "no analysis can be done here, because the thing to be analysed was never recorded." The other is today's great temptation: grab the domain label and produce three thousand words in a confident tone. I call it label-based writing — writing from the taxonomy rather than from the event. It reads like analysis; it does not type like one.

A label is not an event. 'Cricket' is an umbrella, not a match. If nothing from under that umbrella — not one date, not one name, not one over — makes it out, then what has been produced is not an article. It is an echo.

Third, what the 2026 register taught me: authenticity does not need a filled box, it needs a column. That scorer knew that if he guessed 'stumped' and it later turned out to be 'caught behind', his entire book would be questioned. So he left it blank. One question mark, one open route. Today's pipeline has deleted the question mark itself — blank space gets filled in, with no note of when or by whom.

I keep a separate diary I call the silence notebook. Three things per match that never reach a scorecard go into it: the sound of tape being wrapped around a bat handle, a bowler talking to himself at fine leg, the tea tray arriving in the middle of a collapse. The pitch remembers what the scoreboard forgets. Every documentary script I write still opens with a line lifted from that notebook — because I count the words not out of fondness for words, but because someone once counted the hours.

Now the part of this whole affair that is being said least. The first reflex everywhere will be: 'automation failed, the system let us down.' That diagnosis feels half-finished to me. A pipeline cannot print what nobody wrote down. Look at the data chain of any large cricket newsroom today and you will find spending has risen on screens, dashboards and visualisations — and fallen on the man who sits at the ground with a pencil, who picks up the phone on the first ball of the second innings and asks, 'brother, who got the wicket in the third over?'

The day that man was removed, the output was always going to look exactly this empty. This is not an AI failure. It is a staffing decision that surfaced in the output twenty months later.

And the more uncomfortable point: an empty list feels like a crisis only because we have built a system with no vocabulary for 'I don't know.' We turned 'information gain' into volume. The day an analysis came back empty was, in fact, that system's most honest day — it did not lie. It simply reported that its first mile was shut.

So the next time a cricket number arrives in front of you — a strike rate, a fielding map, a 'trend over the last five matches' — do not ask which dashboard it came from. Ask whose pencil first put it on paper, and where that pencil placed a question mark.

After the final ball, the room keeps talking — provided there is someone in the room to hear it. The archive is never silent; it just waits for a microphone. The day we emptied the scorer's chair, the microphone was taken away — and ever since we have been sitting in front of that empty chair asking why there is no sound.

Cricket has one rule: look at the pitch before the first ball is bowled. The same rule governs analysis. Fix the first mile, then talk about the second.