Nothing Beyond the Scorecard: Cricket Coverage's Empty Information Point

March 2026, the Eden Gardens press box. After the match a file landed on the desk — twelve hundred words, twenty-two names, nine 'key points', and not a single scene. The scorecard was the one already open on my laptop. The toss line was the one that had gone on the wire twelve hours earlier. Nobody had written how wet the grass was at the third-man boundary that evening, or which chairs in the stands had stayed empty. The notebook was damp; the square was already speaking in half-sentences — and not one of those sentences reached the file.

This is not a complaint about one careless reporter. It is the condition of the supply chain through which cricket understanding reaches the desk. The most common thing in that chain is no longer the scorecard — it is analysis that looks like a scorecard. Framework complete, conclusion ready, and the last line saying plainly: insufficient information.

In February 2026 I spent eleven hours on the floor of the mega auction in Bengaluru. Kolkata paid ₹12.25 crore for Shreyas Iyer — a captain bought to fix a dressing room he had never entered. Mumbai paid ₹15.25 crore for Ishan Kishan and Chennai ₹14 crore for Deepak Chahar. All three figures were in every database before the evening ended. What was not recorded was the agents' thumbs, the silence at the franchise tables, and the eleven seconds a bid takes to land — the seconds in which you learn who a franchise is afraid of.

In November 2026, with the same magazine having furloughed me for four months, I was running a newsletter called Third Man from my parents' flat in Bhowanipore. I watched the IPL in the UAE on a 32-inch screen and wrote 2,400 words titled 'The Crowd Is the Instrument'. That year rewired my ear. In an empty stadium, absence becomes an event: the roar that never rose, the applause that never came. Two weeks later, on 19 December 2026, I stayed up for Adelaide and watched India fold for 36 — and by next morning every desk had the same 36, the same eleven tweets, and nobody who could say what Bhuvneshwar's first five metres of run-up had looked like that morning.

Two years on, back in the same press box in May 2026. Sunil Narine, a 35-year-old off-spinner, was walking out to face the first ball of every innings. He finished the season with 488 runs at a strike rate above 180 and took the Player of the Tournament award. On 26 May 2026 in Chennai, Kolkata Knight Riders beat Sunrisers Hyderabad by eight wickets for their third title.

All of that is verifiable, and that is exactly the problem. All of it is everybody's.

The definition of an information point has broken. A fact already sitting in the public template — the score, the toss, a price in crores, a list of numbers — is not information; it is an entry pass. Information is what came from the ground, with a date and a situation attached, and cannot be copied out of the template. I have six years of numbers on thirty-two players and not one of them tells me in which meeting, after which objection, the decision to send Narine out first was taken. The 488 runs are downstream of that decision; they are not the decision. What I have trusted most in my reporting — the first five metres of a run-up — does not appear on any optical-tracking dashboard.

And that is why writing 'insufficient information' against an empty information point is not wrong, it is necessary. The error comes afterwards, when that emptiness is converted into a verdict — when the absence of a governance question is read as 'all clean', when nothing filling a pre-set framework is reported as 'no problem'. The reflex is old in cricket: the squad is announced and three sentences later selection is attributed to 'merit'. The rebuilt knee, the workload, the calendar built around franchise windows — none of it appears, because none of it has a box on the online form. I learned the game again from the angle of a rebuilt knee; India's hardest team to make is the second XI, and it is settled less by talent than by what a body can absorb.

The third sample is not from Delhi or Mumbai but from Kolkata. In the 2026 monsoon I filed 41 Cricket Association of Bengal first-division reports — Kalighat, Bhowanipore, Town Club. Most were rained off. In one, a 38-year-old left-arm spinner took 6/19 in a truncated P. Sen Trophy tie, and that became 600 words. That 6/19 is in no public database today. A system that had declared 'insufficient information' that day would not have been lying — it simply was not there. The same imbalance now shows in coverage budgets: two thousand words on a franchise press conference, two hundred on a Ranji knockout.

Format is non-negotiable here, because a benchmark without a format hangs in the air. A strike rate of 130 is useless in T20 and excellent in ODI. Ishan Kishan's ₹15.25 crore was set not by an ODI average but by the role a franchise wanted from him. Analysis that stacks numbers without fixing the format is weighing a Test third session and a T20 death over on the same scale. The Impact Player rule widens the gap — when fourteen players take the field instead of eleven, the old benchmarks quietly lose their footing and nobody notices. After the title I gave the desk one instruction: strike 'on paper' from previews. I want a line that describes what the ground is doing, not what the squad list promises.

Now the part where the conventional read must first be stated fairly. Cricket, we are told, has too much data now; analytics has flattened the game into numbers; the spreadsheet has replaced the commentary box. It reads well and it is wrong.

Cricket's problem is not too much data but too few observations — and the data it has is a copy of itself. Everyone has the 488 runs. Nobody has the wet grass at third man. Shreyas Iyer's price is on every screen; the dressing room that price was meant to repair has its door shut. Data did not replace observation; it gave a great many people permission to skip it. A team with 60% possession spends 60% of the ball in its own half and creates nothing — football has been taught that lesson for years, and cricket forgets the same lesson under the name of strike rotation. A DRS review running past two minutes cools a celebration the way scene-less analysis cools a reader's curiosity, and in neither case is a complaint filed.

Then there is a hazard that looks unrelated to cricket and does the most damage: the wrong label. The day a system files cricket under 'cricket_asia', every downstream link selects the wrong benchmark — and nobody objects, because the output's framework still looks correct. It is the same label error as the report written off a squad list before the first ball: tidy on paper, empty at the ground. I trust the first five metres of a run more than the last five paragraphs of a rumour; that is the only filter that survives between gossip and reporting.

The conclusion is the one I wrote in the notebook that March evening: the third man arrived late, and the empty seats kept his time. The next Indian team will be decided not on television but in a Ranji knockout that draws two hundred words of copy. The question is not whose data is bigger. The question is whether anyone will be at that ground — and if the answer is no, printing it as 'all fine' will be the real mistake.