Eight Columns, All Blank: The Cricket Data-Chain Failure No Scorecard Shows

The file landed at 11:40 pm. Eight tabs — format, player technique, team landscape, league commerce, rules and governance, risk, public narrative, industry transmission. Every tab was filled in. Every cell carried the same sentence: insufficient information, assessment not possible.

Title blank. Source blank. Information-point list blank. In a payload I was supposed to turn into tomorrow's page, there was exactly one solid thing — a tag, cricket_asia — and even that is not a valid value in the taxonomy, which expects "Cricket".

I had forty minutes to turn that file into a good story. I knew forty minutes was enough. A fictional death-overs spell, a fictional auction figure, a fictional young batsman whose "technique looks mature" — and the page fills. Nobody catches it. That is the oldest failure in this trade, and it was lying open in front of me in one file that night.

Nine matches had cameras. The story was in the ones that didn't.

I have logged every ball by hand since 2026 — from the years when wire copy delivered a bare scorecard and no ball-by-ball record existed. At first it was a habit. Then it became a method. Before the model, the ledger. Before the ledger, the ground. I set that order for myself and have not changed it since.

In 2026 I turned the habit on the Ranji Trophy. Twenty-seven teams, roughly 115 matches, and only nine of them had any broadcast feed. Nine. About seven per cent of the season was on camera; the rest never reached a highlights package. I built a phase-split table from those nine matches and my own ground notebook. It surfaced a twenty-one-year-old Mumbai batsman: Shreyas Iyer, 1,321 runs at 73.38, scoring at better than nine an over through the first fifteen. I published the table with method notes attached and mailed it to every franchise analyst whose address I could find.

After that day I stopped writing "talented youngster". I wrote: 1,321 runs, 73.38, phase split attached. My copy now arrives with an appendix, and I know it is annoying at desk meetings.

Dot-ball pressure, who was bowling the difficult overs, what a wicket was worth — none of that sits in the scorecard. The scorecard is a summary written by someone with an interest, and I read it as a claim, not as evidence.

In 2026 the habit paid. That July, at Lord's, the women's World Cup final — India, chasing 229, were 191 for 3 and lost by nine runs, bowled out for 219. My post-match template published twenty-five minutes after the last ball, and it carried one line no mood report carries: the last seven wickets fell for 28 runs. I did not write it as a story of temperament; I wrote it as a sequence of deliveries. Seven wickets, twenty-eight runs, one ball at a time. After that template the office rule was fixed — numbers before adjectives. I sent the same two-line email for four years.

I open this old ledger because that blank file is the next link in the same chain, running in the opposite direction. Once I was chasing what nobody had filmed. Now I am handed what nobody wrote at all.

The fault sits at the first step, not the last

Eight tabs, all empty — and all empty does not mean "there was no story". If there had been a story, its title and source would have been filled first. In my experience, when title and source are both null, the fault is not at the summarising layer. It is upstream of that — fetch, parse, paywall, a truncated response. A pipeline failure, not an editorial judgement. And the worst thing about a pipeline failure is that it happens quietly.

At the top of that risk list was not sporting risk. It was fabrication risk. A filled-in analysis on a blank sheet. I am certain that if the file had gone to a fast-handed sub-editor, by morning a widely read story would have been printed with not one true fact in it. That story would have read well. That is why it is dangerous.

The second failure was taxonomy. The tag cricket_asia is not in the approved list, which expects "Cricket". It looks small, but such tags decide downstream routing — which desk a story reaches, which benchmark it is compared against, which season report counts it. One bad label contaminates a whole domain's benchmarks, and years later an analyst builds a wrong conclusion on a polluted baseline.

The third and most technical failure is format. Test, ODI and T20 numbers do not interchange — average, strike rate, economy all have different scales. Until the format is fixed, citing any figure is inadmissible, even a correct figure. This is the commonest error I see: an IPL season becoming an international claim, or a T20 economy rate being applied to a Test new-ball spell. If format is missing from the input, the conclusion is not permitted.

The fourth failure is the least visible and does the most damage. If a later input supplies a player's name but not the format, the framework's cardinal sin comes alive — format blindness. In that state an analyst has two options: stay silent, or guess. The second is always easier.

So I fixed a six-line minimum condition sheet for my desk and stuck it on the first page of the ledger. Title and source. Explicit format. At least one named entity — team, player, board or league. At least three concrete information points. Match or competition context — series, venue, tournament. And a date. Six lines. The distance between those six lines and astrology is professional journalism.

I should record that the same condition applies to my own old list. My 2026 Ranji table stood on nine venues of footage and my private notebook, not on 115 matches. It was a biased sample and I said so when I published it. For a man who has paid for every entry out of his own pocket, it is very easy to believe his archive is the population. It is not.

Silence is not evidence

Now the part where I have to doubt my own reflex.

For some years I have trained myself to make every column overturn a settled view. That has become a brand reflex and it is the weakest part of my work. Not every column has to overturn something. Often the conventional read survives the audit, and a professional has to write that it survived. What I have to write this time is harder still.

An empty dataset is not a signal. It gets misread from both directions, and both errors are expensive. First error: treating silence as clearance — "see, nothing turned up, so there is no problem." Second error, the one people like me find more attractive: treating silence as accusation — dragging politics, selection bias or integrity questions out of an absence. In both cases I am doing what I am trained to do: converting absence into evidence.

Nothing here justifies a question against a board, a league, a player or an official. What exists is one bad file. Yet that bad file has exposed a real problem, and the problem is not in the game; it is in the reporting.

Given the time to think, this is what I think: in Indian cricket, the data question has never been technical. It has been administrative. Ball-tracking, fitness data, selection analytics all sit inside the board's walls. The question is not whether a number is accurate. It is who is measured, who is measured accurately, and who decides which measurement counts. Outside the press box, my only option is to keep the account of that, and to write my conditions alongside my comment.

One more correction. It is an industry commonplace that more than seventy per cent of global cricket revenue comes from the Indian market. I have not verified the full source or the year, so let me be explicit — that is context, not my finding. You cannot expect a man who spent twenty years printing that every claim needs a method to stay quiet about his own most convenient number.

What is not clear belongs blank in the ledger

My one signal for the next season belongs to no player and no team. It is the question of who keeps the account of the material nobody watched. In 2026 I took that job on myself, because the sheet was only being filled at nine matches. In 2026 the sheet fills on a server, and when it arrives empty the whole desk treats it as a technical glitch and moves on.

The right response to a blank input is not decoration. It is an alarm. Coverage with no title, no source and no format demands a check before it demands a story. The question is not which story went unpublished that night. It is who signs the blank sheet — and whether, the next time eight columns arrive empty, the desk tries to fill them or picks up the phone.