Eight Columns, Seven Empty: The Crack in Cricket's Data Tower Nobody Wants to See

One night in the middle of this tournament cycle, an audit file came back to the desk. It had eight columns: format and match nature, player technique and data, team landscape and rankings, league commercial mechanics, governance and rules, the risk matrix, public expectation, and industry transmission. Seven of the eight carried the same line: N/A – insufficient information. In the eighth, two words survived — cricket_world.

For forty years I have read the scorecard before the quote. This time there was no scorecard. The payload on which the report was to be built had a null title, an unclassified source, no time-sensitivity assessment, and an empty list of information points. The entity field referred to itself — "identify from the information points above" — while above there were none.

Stopping is not weakness in cricket. It is technique. A batter who declines the shot is not conceding; he is buying room for the next ball. This report does the same.

Cricket coverage now stands on three floors. At the bottom is extraction — the raw material, where headline, source, fact, quote and date come out. In the middle is analysis, where those facts are sorted into format, team, player and time. At the top is judgement — what the reader consumes, and what the selection committee, the market and the commentary box all stake money on at once.

The most basic condition of the whole structure is format. An average of 45 in Test cricket and a strike rate of 145 in T20 are both correct numbers, and they cannot be substituted for each other. The new ball in a Test, the powerplay in an ODI and the death overs in a T20 have different currencies. Format is the foundation; every conclusion rests on it. When the foundation vanishes, the tower does not stand. An excuse does.

The habit of that foundation is old for me. Before the 2026 Ranji final I drew my field for every opposing batter in a spiral notebook — the gap behind point for one, deep square leg for another. The field map was a conversation before the ball was bowled; you argued it with the captain until he agreed. The title came in Madras, and all three of my wickets in the final fell exactly where the notebook had written them.

In February 2026 I sat in a Mumbai hotel ballroom for the first IPL auction — a transfer window with no history, only a purse, a spreadsheet and my economics degree. I drew pre-match field maps for Muttiah Muralitharan and argued that the last four overs were a separate sport. Chennai reached the final that season and lost in Navi Mumbai to Shane Warne's Rajasthan Royals by three wickets. The auction set the price; the final taught me the value.

That is the logic this audit should be read with.

The first question in the audit was not what the article contained. It was what the article did not contain — and that absence repeated itself identically across every column.

Headline, source, information points and time sensitivity are four fields with no technical relationship to each other. Their failing together is not the signature of thin content. It is the signature of a pipeline. Any published cricket article should carry at least one of them; a simultaneous silence across all four points to a single upstream failure rather than piecemeal damage.

The audit listed four probable causes — a paywall or login wall, a JavaScript-rendered page body, an image- or video-only post, and a language or encoding mismatch. Confidence was rated medium or low in every case, which is honesty. A pipeline that returns emptiness cannot diagnose its own illness.

Every cell of the risk matrix reads N/A, from injury and workload to the rollover of broadcast rights. All three nodes of the transmission map are blank — youth development, national team, broadcast market, one line each. Not one team, player, league or board is named.

And here is the part that stings. The report gave one star to each of its four value dimensions — sporting value, industry value, timeliness value, reference value. The first three stars mark absence. The fourth star went to the protocol that called emptiness by its name instead of filling it in. In forty-five years of cricket writing I have seen that star awarded very rarely.

Because the pressure is real. There is a deadline, the tournament is running, and somewhere in the feed a new story is dying every hour. The cheapest route with an empty payload in hand is to fill it with narrative — a "source", a "source close to", a sentence that sounds true. Twenty-six years ago in the Chepauk pavilion I learned this the hard way, when our younger players went quiet amid the fixing headlines and two admitted they had been approached, and told nobody. I put no names on the table and listened for four hours. Silence in a dressing room is data you must learn to read.

But there is a thin line between reading silence and manufacturing a story out of it. This payload stands on the right side of that line.

The easy conclusion is that the platform is guilty. Some piece of technology will always be found. My first charge does not go there.

The real failure is the gate that let this payload through without stopping it. A file with zero information points and a null headline cleared automated quality control. That tells you the gate has no minimum-viability check. A system that cannot distinguish "nothing" from "not yet" can shut down silently one day, and nobody will know.

The second charge is against the industry. We are in the habit of filling nulls with narrative, because empty space frightens the publisher more than it frightens the reader. In a tournament cycle that pressure doubles — flag, story, emotion, and in the middle of it a column that is genuinely blank.

Silence comes in two kinds here, and the distinction matters. A quiet room often carries load — if everyone is silent, something is being said. But sometimes the room is simply tired. This payload's silence is load-bearing, because it repeats identically across independent fields. Four separate checks do not return the same answer unless something has broken upstream.

That is my only strong warning: an empty report is never a clean bill of health. A field that reads "no data found" cannot be read as "no risk found". Letting null remain null is the hardest condition of this entire exercise.

When the pipeline runs again, four things bear watching. Whether headline and source return — that decides the genre. Whether format is confirmed, because without it every number is borrowed from another format. Whether at least one team, player or board is named. And whether three hard information points arrive — a score, a date, a decision.

Three points is enough to start four of the eight dimensions immediately. If they do not arrive, the answer stays what it is today, and that answer will not be wrong.

The question is not why the data desk returned empty-handed. The question is: on the day it returns with three solid points, will we analyse them, or only decorate them?