Eight Columns, One Filled: The Empty Report From Cricket's Data Desk

The document landed on my desk and the first thing I looked at, for reasons I cannot fully explain, was its skeleton. Eight columns. Format, player, team, league, governance, risk, narrative, transmission. Every cell carried the same sentence: "N/A — insufficient information." One cell was filled: "cricket_world." So the subject had not been found. Only the sport had.

I thought of 2026. Before the Ranji final in Madras I used to draw a field for every opposing batter in a spiral notebook — the gap behind point for one man, deep square leg for another — and argue the map with the captain until he agreed. That March, all three of my wickets in the final were caught exactly where the notebook said they would be. The field map was a conversation before the ball was bowled.

The sheet in front of me was that notebook turned inside out. The map was there. The batter was missing. That absence is the subject of this report.

Cricket's data structure stands on two floors. The first extracts facts from the source: who played, where, in what format, in what weather, under what pressure. The second builds arguments on those facts. The first floor cannot return empty and the second still produce an argument — and the report said so in unusually plain language.

What stopped me was not the emptiness. It was two of the boxes. The "entities involved" box read: "identify from the information points above." There were no information points above. The "source quality" box read: "judge from the source fields." The source fields were themselves blank.

Programmers call this a circular reference. In cricket I call it the stamped team sheet — eleven blank lines where eleven names should be, and the registrar's seal at the bottom reading: approved.

In February 2026 I sat in a Mumbai hotel ballroom at the first IPL auction with a purse, a spreadsheet and an economics degree. That season I drew pre-match field maps for Muttiah Muralitharan and argued that the last four overs were a separate sport. We reached the final and Shane Warne's Rajasthan Royals beat us by three wickets. We had costed every player that day. Nobody had costed the role. Eighteen years on I can say it plainly: the auction set the price, but the final taught me the value.

The empty report records four failures, and all four sit on the everyday tables of Indian cricket.

The line between input and conclusion has dissolved. The report cannot tell whether the article never arrived or arrived and was never read. In cricket that is the difference between a player nobody scouted and a scout's report that never reached the table. In the first case the selection system is at fault; in the second, the postal service. The remedies are different, and without the distinction we will always pick the wrong one. The man on India's bench is a product of exactly this darkness — nobody judged him poor, nobody looked at him at all, and in the record both read the same.

A template that instructs itself to fill itself. When the schema says "take it from above" and there is nothing above, the template is technically valid and substantively zero. In cricket this connects directly to the transparency we promise every series and forget every controversy. The big screen shows the third umpire's verdict; it does not show the reason. The spectator sees the outcome, never the argument. The person in the stands is the cheapest and most ignored audience in the sport — told what happened, never why. And when you withhold the reason, anyone can fill the space where it should have been. Rumour is the fastest commentator in the game.

The pressure to fill a blank. An empty input is dangerous precisely because it asks the next floor to write something. That pressure has cost cricket dearly. The 2026 home final is my standing case study: the most expensive assembly of talent in the world, undone by a role nobody had costed. Every cell in that team's template was full — average, strike rate, auction price, fitness report. One cell was empty: who bowls the seventh and eighth overs when the wicket has not fallen and the runs have not stopped. The empty cell was not filled. It was ignored. And so the market bought names, while the field kept remembering patterns.

The limits of the model. I am one of the people who won the data desk's argument; across four decades I have watched a tactical case settled at the data desk and then have to be re-fought in the commentary box. But winning is not the same as finishing. A model is an instrument, not a verdict. This report shows the instrument's failure mode — zero sample, unknown conditions, and an output that says, in eight places, "no assessment is possible." I trust that document more than the one that produces an eighty-seven per cent win probability from a three-match sample.

Everyone will call this a plumbing fault and move on. I read it the other way.

The empty template is the most honest document in the stack. Everything else — the filled cells, the decimals, the percentages, the arrows — offers no proof of its own reliability. This one does. It said "I do not know" eight times. In the entire analysis market of cricket, that is the rarest sentence available.

Here I have to restrain myself, because reading code into silence has been my fastest and most dangerous pen for forty years. Not every quiet room is a conspiracy. I have to say in print which silence is load-bearing and which is merely ordinary. This report is not load-bearing silence. It is plumbing. The pipeline broke; nobody is hiding anything. That makes it less interesting and far more useful, because plumbing can be fixed, and the only condition of the fix is to call the blank a blank.

In 2026, in the pavilion room at Chepauk, I listened for four hours without writing a single name on the table. That silence carried weight — a twenty-one-year-old convinced nobody was listening to him. Today's silence is not that. Today's silence belongs to a server that never read anything in the first place.

The fix is not a better template. A better template will only repeat the same error with cleaner formatting. The fix is to refuse to let a null travel as a number — not in the selection meeting, not at the auction table, not in the commentary box.

The next time a figure is quoted in a room, ask first: what is the sample? And then the question nobody asks: what did the template say before someone filled that cell with a number?

Silence in a dressing room is data you must learn to read. This week we also have to learn that a server's silence is a different thing altogether.