Zero Information Points: When Cricket's Data Desk Files an Empty Report

9:40 a.m. Third net, outer practice square, Narendra Modi Stadium. The left-arm spinner was releasing the ball so that it came straight onto the batsman's pad line — the ball was fully visible and the batsman still could not play it. I wrote the date, the net number, the session and the wind direction into the notebook. That has been the sequence since 2026. Then the phone buzzed.

The email carried a fourteen-page PDF. Title: 'Cricket Domain — Deep Professional Analysis'. Eight sections, eleven fields. Against every field, the same phrase, repeated: 'N/A — insufficient information.' The array on which the entire document was supposed to stand was empty. Zero of eleven fields were usable for analysis.

That document said one thing worth more than any sentence in its fourteen pages: this is not an analysis of material, because no material arrived.

In the last four months I have received eleven such reports. Ten were full — coloured graphs, arrows, a 'Player Depth Index', an 'Impact Score'. Not one of the ten contained a single point I could match to a page in my notebook. The eleventh was empty, and it was the only one I trusted.

Context

In the summer of 2026 I sat on the sports desk of The Times of India, and the desk's first rule was simple: what is not in the notebook does not go into the copy. That rule was never technophobia. It was a rule of sequence — see it, write it down, then print it. Forty years later, standing behind the third net, the sequence has not changed. The notebook went to a screen; the rhythm stayed on paper.

In April 2026 the paper cut the cricket page to a single column and handed me the Gujarat Lions beat on a digital desk. From the Rajkot camp I filed a 600-word nets notebook for forty-one consecutive days while the franchise slid to seventh with four wins from fourteen. Traffic was modest. The team's video analyst screenshotted two of my seam-position notes. The franchise died within three years; the format outlived it.

That same season I imposed a two-source rule on everything seen at training — a player's own words, or a coach's confirmation, never an agent's. The rule slowed my copy by a day and made it the most quoted on the beat.

13 March 2026, Rajkot. Ranji Trophy final, Saurashtra against Bengal. Jaydev Unadkat had 67 wickets that season, and Saurashtra won on first-innings lead. It was the last major cricket played in India before the shutdown. Then eight months of silence. I did not pitch features; I went into the archive and digitised thirty-one years of notebooks, 214 of them, indexed by ground, bowler and session. When domestic cricket resumed I was the only reporter on the beat who could pull a 2026 Motera pitch note in under a minute.

Today that beat also includes the documents that arrive before the match does — tracking apps, DRS ball-tracking pages, Impact Player calculations, data-desk reports. I weigh every new tool against the ninety-sessions standard: can this thing survive eyewitness verification? It took ninety nets sessions before I trusted the app. It took forty minutes to trust this empty document, and the reason was that it had not lied.

The core

The difference between empty and partial is the whole case. If a scorecard is missing one bowler's figures, that is information — you know where to look. If the scorecard has no match in it, that is not a data problem, it is a printing problem. Here eleven of eleven fields were null — total, not partial. A partial null is information; a total null is a diagnosis.

And the most dangerous line in any cricket report is this: 'no red flags found.' It makes two very different things look identical — checked and cleared, versus never checked at all. This document did the honest thing in its risk section: it recorded the risk rating as unavailable, not low. That distinction matters to any desk that reads 'N/A' as a green light and passes it along.

I learned that distinction on my own neck in February 2026. Four mornings before the day-night Test at the Narendra Modi Stadium I stood behind the Gujarat nets watching Axar Patel's arm angle against left-handers. I wrote a carefully hedged note — England's top order would not be able to score off the straight ball. Axar took eleven wickets; England made 112 and 81; India won by ten wickets inside two days.

My desk wanted the 'pink-ball magic' angle. I refused it and filed instead on the lengths Axar had bowled in a Ranji semifinal three seasons earlier. The pink ball did not change the game; the light did. But light does not take wickets — length does, and that length was already written on a page of my notebook from that semifinal.

Had I been handed a pre-filled template that night, with the 'magic' box already ticked, I would have printed a sentence that was flawless in grammar and wrong in fact. That is the real data-desk problem — not bad numbers, but pre-filled boxes.

Because a template demands filling. Eleven fields, eight sections, deadline in front of you. A junior with two hours will fill the boxes, and will fill them with adjectives: 'the young batsman's confidence', 'aggressive intent', 'a positive dressing-room atmosphere'. Those sentences are not lies; they are unfalsifiable, and unfalsifiable copy is the actual enemy. The problem is not too much information. It is too many boxes.

What a real information point looks like I can show from my notebook. It has a date. It has a name. It has a place. And it has a way of being checked. The note from the twelfth morning at Rajkot in 2026 read like this: 9:40 a.m., third net, the seamer's final stride four inches further forward than the previous day, the ball travelling towards the batsman's inside shoulder. That fits in five words and cannot be extracted from any application.

A third rule I imposed on myself in 2026: no strike rate enters my copy without its format in the previous sentence. A Test strike rate and a T20 strike rate are different languages; merging them is like reading a spinner's average off a seamer's economy. The empty document, at least, borrowed no numbers. It did not say what it did not know. In journalism that is a favour, and I will not be shy about calling it one.

Measured against my own ninety-sessions standard, the verdict is clear. The document failed — but it failed honestly. It named its own failure, it named the place where the pipeline broke, and it printed the most important line of all: do not attribute any conclusion here to the underlying article, because the article was never read.

That is what I have done in my copy for forty years — what I did not see, I did not report as seen. The only difference is that I have a notebook instead of fourteen pages.

Tempo is what remains once the noise has been subtracted. The Ranji final in Rajkot in March 2026 was played in an empty stadium. In an empty stadium I finally heard the bat, not the applause — and the sound tells you where the wood did not meet. We watched that match without a crowd and it held as much information as any packed final, possibly more. The same happened with the empty document. Strip the template away and what was left was clean.

The contrarian side

The easy outside reading writes itself: 'there, the data desk is useless, the eye was right.' I reject that, and I reject it on the evidence of my own archive. The failure was not an excess of information; the failure was a template with no information in it. The data desk is not my opponent — in 2026 it gave me length data I could not have assembled alone in a fortnight. I gave it ninety sessions. It earned them.

Second, and more important: the dangerous report is not the one that arrives empty; it is the one that arrives eighty per cent full. An empty report protects the reader because it leaves the door open — the reader knows there is nothing behind it. An eighty-per-cent-full report counterfeits the very method that is my capital, without the labour the method rests on. Every sentence reads fine and collapses on inspection. That empty fourteen-page file was more honest than its ten full siblings, and that is not an achievement of an algorithm — it is the achievement of a desk that did not suppress a null result.

Third, the fastest-spreading version of this in the current market. A transfer fee is a rumour with a deadline attached to it. Auction and transfer copy arrives with all eleven boxes filled — purse arithmetic, bid figures, 'sources say'. Information points? Zero. The same zero that sat in this PDF, only without the warning label attached. The day cricket writing finds the nerve to print 'N/A — insufficient information', a great deal of noise will subtract itself.

The signal ahead

After the match-fixing scandal of 2026 and the IPL spot-fixing fallout of 2026, I learned that accountability targets institutions, not villains. The institution here is the desk that let a zero-information record travel. The question is not who wrote the fourteen pages. It is why nothing stopped them before they were filed.

This season's real test is whether the desk accepts 'we do not know' as a filed line, without an apology attached. In March I open the prediction ledger and read every technical claim I signed. This time the ledger gets a new page, and on that page there will be one entry: a document arrived empty, and it told the truth.