The Empty Column Report: When Cricket's Data Pipeline Went Silent

There is a file on my desk with a single page in it, and the page is blank. Where the title should be: N/A. Where the source should be: N/A. And where the list of information points should be, there is nothing at all — not one item. This is not a joke. It is an analysis report. Eight sections, eight tables, more than three dozen rows, and in almost every cell the same phrase: insufficient information.

Thirty-eight years of scorecards have taught me plenty, including how they lie. At one Ranji match the scorer's pen had run dry and he wrote the last two wickets in pencil — I kept that page, because somebody's over was left unfinished on it. At one Test the telex arrived late and three of us in commentary filled thirty minutes on guesswork.

But never before has a report arrived with no news inside it. No match, no team, no ground, no format, no date. Not even a headline.

This is the silence of a commentator holding a live microphone who knows he must not speak about what he did not see. I learned that silence in an empty Dubai studio, where the stump mic was the only witness. What I heard, I wrote. What I did not hear, I left out.

The report is the second stage of a two-stage machine. The first stage reads a published cricket article and pulls out eight things: title, source, article type, central argument and author's stance, information points, entities (teams, players, boards, leagues), time sensitivity, source quality. The second stage builds eight analytical dimensions on top of those points — format and match reading; player technique and data; team landscape and rankings; league and commercial ecosystem; rules and governance; risk; public narrative; industry transmission.

This time the first stage came back with nothing in its hands. Title through information points, every field blank at once. The second stage did what a disciplined commentator should do: it refused to write.

In cricket analysis that refusal is not a small thing. Consider what an analyst actually holds — a scorecard, a spell log, a toss, a pitch report, the date. Remove the format and everything else goes meaningless. An economy rate of 6.8 is gold in T20; a Test average of 32 is ordinary; an ODI average of 45 with a strike rate of 88 tells two different stories that can both be true about the same player. Analysing a bowling plan without a format is like a commentator walking into the box after the toss without knowing who is batting.

That is why the report set a six-field minimum in front of every dimension: format, competition, teams and venue, innings or score state, toss and result, one line on pitch or weather. With none of them, no reading stands up. With two missing, everything becomes inference.

The empty payload is not an accident; it is a sample. That is the first and firmest finding. A genuine cricket article with zero extractable entities is close to impossible. Any article naming a team contains at least one entity. Any article containing a score carries a hint of a date. Every field empty simultaneously — title, source, type, argument, points, entities — says the article never arrived, or arrived and could not be read. That distinction matters: the first is a claim, the second is the pipeline's honest admission.

And from here cricket's oldest lesson begins: what was not seen is accounted for separately. I opened the notebook at Eden Gardens and let the follow-on speak. That page did not hold the greatest comeback in cricket history; it held one number — 171. India were 171 behind, VVS Laxman made 281, Rahul Dravid 180, and India won by 171. The number stayed the same. The direction reversed. That page taught me that the story lives not in the scoreboard but in the empty space between the scoreboard and the field.

Now turn the metaphor around. If every blank cell in this report were filled — filled by inference — the result would not be analysis but poetry that never read the card. In Barbados in 2026 I watched Jasprit Bumrah's 18th over fourteen times. India 176/7, South Africa 169/8, a seven-run margin, Bumrah 2/18 from four. After fourteen viewings I wrote one sentence. The sentence that came first — 'the over turned the match' — was true but incomplete; the real sentence was that Bumrah did not change his pace, he changed his line, and the captain changed the field to finish the job across the last three balls.

Building a chapter around one over taught me this: analysis is not what you can show, it is what you can decline to show. This report declined. That refusal is not its weakness but its credential.

Inside the refusal, though, sits a structural blind spot with direct consequences for cricket.

The languages in which domestic cricket is written are often the languages the machinery cannot reach — and the margin gets erased twice. The failure list the report itself compiled is familiar: paywalled pages, image-rendered PDFs, delayed-loading pages, non-Latin scripts. Now lay that list over the map of Indian cricket. Real Ranji Trophy coverage lives in Marathi, Bengali, Tamil, Telugu, Kannada papers. State association circulars go out in Hindi and regional languages. The day a fast bowler takes nine, the first report is not in the English press box but in a local correspondent's WhatsApp group.

If the extraction engine stumbles on Devanagari, the analytics industry's map of Indian cricket is really a map of the English-language press box. Then the familiar thing happens again: domestic cricket disappears from the papers first, and from the database second. The margin is where the miracle starts; the scoreboard only confirms it later. And if the margin is never recorded, there is nothing left to confirm.

The third thing looks small and is the most dangerous. The report logged the domain label as cricket_world when the contract asks for Cricket. One word. One underscore. And every downstream query, routing call and retrieval passes through the wrong cell. I have watched zonal selectors do exactly this — a player's file is misfiled under the wrong age group, and three years later when he makes a Ranji hundred somebody remembers the file was somewhere else all along. A classification error becomes a selection error. In machines it happens faster, and therefore costs more.

And fourth, which I say from the oldest wound in my own reporting. The report stated plainly that it found no integrity signal, positive or negative — and immediately added that this is not an integrity clearance but an absence of data. Every cricket journalist since 2026 should memorise that sentence. The Hansie Cronje revelations, the 2026 Pakistan spot-fixing case, the 2026 IPL betting scandal — none began with a 'no flags found' report, but every one of them had, somewhere in the middle, a report that had coloured an empty cell green. The absence of a flag is not clearance; it is unknown — and unknown should always be written as unknown, never as exoneration.

---

Now the flat truth that should always be written first: this report did what it was built to do — it refused to answer, because the question was never established.

The danger is not the machine. The machine worked. The danger is the human at twenty to midnight with a deadline and a blank cell in front of him. He has two roads: leave it blank, or fill it with adjectives. We have filled it many times. We have written match reports off the television feed. We have treated the hundred as the event and the match situation as context. We have sold India–Pakistan as a live bilateral when, since 2026–13, it has existed only inside ICC and Asia Cup windows.

I am a witness to my own work. In the 2026 IPL final, Mumbai Indians made 129/8 and beat Rising Pune Supergiant's 128/6 by one run; Krunal Pandya's 47 off 38 was the human hinge. Within ninety minutes of the last ball I published a ninety-second audio essay. I launched Pitch Poetry when the final refused to stay a single sentence — but the first word of that sentence was not an adjective. It was 'one run'. Number first, poetry after. That is the order.

Our industry talks about data constantly and fills blank cells with adjectives constantly. That is its real contradiction. Data is not a strength; the strength of data is that it lets you stay quiet in front of it. An empty table is more honest than a sentence written without a witness.

---

What next? The report prescribed its own medicine, and it is entirely unromantic: a hard gate. Stage two should not run unless the title is not N/A and at least one information point exists. Rejections should be logged, alerted, and the failed document fingerprinted so the extractor's behaviour on that source class can be inspected. An enum should be enforced on the domain label. And a date field should be mandatory, because without a date no narrative cycle can be positioned — no germination, no acceleration, no climax, no backlash.

All of this is process, and process reads as dull until you remember that this is the machinery deciding which Ranji spell is recorded and which stays anonymous forever. India's second XI is the hardest team in world sport to make — I have been writing that for thirty years. But that team is now built in a database before it is built on a field.

So I leave one question, written on the blank page I pulled out this morning: when Indian cricket's next big story breaks first in a language our machines cannot parse, who files that report?

The notebook is open. The page is blank. And today, for the first time, that feels like good news.