Eight Sections, Forty Tables, Zero Numbers: The Room in Cricket Reporting Where Nobody Writes 'I Don't Know'

Pune, Bund Garden Road. A young sub-editor places a file on my desk. Eight sections. Forty tables. Three columns in each table, and in every cell the same sentence: 'Insufficient information — assessment not possible.' He asks, 'Sir, do we run this?' The deadline is forty minutes away. I turn the pages and find that where a player's name should have been, there is an instruction — 'identify from the information points above.' The job the report was built to do had never begun. The room was empty; the file looked full.

I thought of an October morning in 2026. Nehru Stadium, Maharashtra vs Mumbai, Ranji Trophy. My first solo assignment, three months into a trainee's job. Maharashtra were bowled out for 148 before tea. I filed 600 words on the groundsman who had watered a pitch he was told not to water, and on a 19-year-old No. 9 who blocked 71 balls without scoring. My editor cut it to 280 words but kept the groundsman's name in the second paragraph.

That day I started a silence notebook. Three things per match that never reach a scorecard — the sound of a bat handle being taped, a bowler talking to himself at fine leg, the tea tray arriving during a collapse. Twenty-nine years later, almost every documentary script I write still opens with a line lifted from that notebook.

This piece is the notebook's other direction — about the data chain that now writes cricket's story, whose weakest link is not an algorithm but our habit of believing every blank must be filled.

The modern information chain is long. The scorer's pencil, the scorecard, the database, the franchise analytics deck, the broadcast graphic, and finally the WhatsApp forward on which forty million people write 'see, I told you.' Something is added at each link and something is lost. What is lost is usually what the hardest-working person in the ground had recorded.

A new kind of file has entered this chain — the 'deep analysis report'. Eight sections, thirty columns, five stars for ratings. The template is so elegant that leaving it empty feels like an insult to it. The most dangerous document in cricket is not the wrong report that shows a false lead in a chart; it is the empty report wearing a beautiful format, because the reader assumes something was measured.

A table header does not always demand data. It demands filling. When a 'format context' column sits empty, by the next morning one of three things is inserted — an old match reference, a fragment of debate, or something heard from someone. In cricket, format is the first gate. A 45-ball 70 is an explosion in T20 and ordinary in a Test innings. An economy of 6.5 is thrift in ODI and extravagance in T20. Until the format is fixed, no number is good or bad — it is only a figure waiting to be decorated with someone's opinion.

The same applies to the empty player column. In the winter of 2026 I covered the fixing beat, after Hansie Cronje's confessions and Mohammad Azharuddin's life ban. I was bad at that beat. Stakeouts bored me and I kept drifting to the Deccan Gymkhana bar where retired Ranji players drank. The story that taught me journalism came from there — a former wicketkeeper describing the exact silence in a dressing room when a teammate was asked to underperform in a 2026 one-dayer. I wrote 4,000 words, 'The Long Room', about what a fix does to a friendship, not to a table.

That beat gave me a rule that should have grown stricter in the data age: a reporter trained on documents distrusts any claim whose source he does not know — and that suspicion applies to his own copy. If my report says 'economy' and I do not know which format it belongs to, I should delete the line. Cricket journalism has never had the luxury of writing first and thinking later.

The archive is never silent; it just waits for a microphone — and empty files are the loudest part of that archive.

The pitch remembers what the scoreboard forgets. That is an old line of mine, and I now think it should be turned around. The scoreboard does not forget; it never records what it had no instrument to record. The curator hosing a Ranji square at 5 a.m., the veteran with 9,000 first-class runs and no cap, the scorer whose pencil wore down to a stub, the third umpire deciding in two frames — all of them sit in a ledger nobody uploads. When an analytics report leaves those columns blank, it is technically correct and professionally dishonest.

The second risk is scale. One empty report is an accident. A thousand empty reports become a genre. If the intent is that every report fills eight sections, then eventually a filler arrives on his own. People borrow from old matches, guess the weather, write 'strong likelihood'. And the reader, who has never touched that ground's soil, cannot tell, because the format has given him confidence.

The third risk is names. When a file shows an instruction where a player's name should be, the machine that built it never reached the reading desk. It is as if someone handed you a scorebook with 'write name here' printed in the batsman's box. In cricket we call that an invalid scorebook and stop the match. In data reporting we call it a draft and move on.

The fourth risk is attribution. A reader skims a forty-table file. He sees the headline, sees the tables, and assumes a real match was really analysed. Beauty of language is a double-edged tool here. The cleanest-looking report is often the one least thought about.

One more thing, and it is a direct hit on my own trade. Analytics has not made cricket truer; it has made cricket more formatted. The graphics are from 2026; the sourcing is from 2026. Franchise analytics decks are produced at the same speed at which press passes are handed out, and a press pass has a price. A journalist who has worked with a franchise for twelve years will not write about its selection calls as fast as an outsider will. I am not making an allegation; I am saying that where access exists, it must be declared in the copy, and the question must be asked anyway. The 2026 beat taught me that.

Now the part least written about. We blame the machine. We say the algorithm erred, the tool misled. The truth is that an empty file reached print: that is an editorial failure, not a technical one. The bravest line in an eight-section report is 'we do not know', and no editor fears printing it — the fear is that the reader will mistake it for laziness.

Here cricket's information culture shows its real weakness. We never built a grammar for zero. Cricket values zero — a batsman's duck, a team's nought, overs remaining. But a zero of information we treat as a professional crime. The urge to fill a blank table comes not from the algorithm but from our training. We taught reporters that every blank must be filled; we did not teach that some blanks are more honestly written about than filled.

The effect lands where coverage is thinnest. The Ranji knockout footprint stays thin until the final, zonal selectors have been replaced by franchise scouts, and a first-class season passes as if nobody watched it. This is not a lament; it is a description of structure. The day we record Ranji numbers with the seriousness we give IPL auction prices, we will find we have real data to fill — and no need for an empty template.

I count the words because someone counted the hours. I wrote that line for myself; it is time to apply it to data. The scorer who held a pencil for six hours was not employed to fill eight sections of your report. He was employed to record the truth. If we cannot fit that truth into the template, the fault is the template's.

After the final ball, the room keeps talking. Analytics entered the room, laid forty tables on the desk, and the room went quiet. In a few years, as cricket stands at the door of the 2028 Los Angeles Olympics, a new audience will read through data a game we watch with our eyes. What will matter then is not how many tables you built, but how often you wrote 'we do not know' — and how often you went looking afterwards.

That morning I handed the file back to the young sub-editor. Not running, I said. Until we know the format, the venue and the player's name, we have no story — only a beautiful emptiness. He asked what we would run instead. Eight hundred words on the groundsman, I said. And yes, his name stays in the second paragraph.