An Empty Column Is Also a Story: Cricket's Measurement Gap

Kolkata, 28 October 2026. The main press box at Salt Lake Stadium was full, so I was moved to the overflow tribune — no chair, a concrete step, a notepad balanced on my knees. England beat Spain 5–2 that night, and I spent the whole match charting England's 4-2-3-1 press off Spain's goal-kicks, counting the seconds between each restart and England's first shot on the turnover. A senior print reporter looked over my shoulder and said, "formations are for coaches." I filed 2,000 words with six freeze-frames anyway. Two habits came out of that night. The first: derive one number yourself before forming a judgement on any match, something that isn't already sitting in someone else's sheet. The second: don't look away from the empty space. Start with the empty chair; the formation will explain itself later. I gave myself that advice about stadiums. Last week I learned it applies to spreadsheets too. In front of me sat an analysis sheet for a cricket report. Title — N/A. Source — N/A. Article type — unclassified. The "information points" column was entirely blank. The "entities involved" cell read, "identify from the information points above," while above it there were no points at all. Twelve fields, eleven of them empty. The strange part was that the sheet looked complete. Every cell was filled; every cell held a tidy N/A. That sheet is itself a story, and it should be read like one. What happened is this: a system ran, returned zero, and forwarded that zero labelled as "insufficient information" rather than "failure." Nobody broke a process. And yet if anyone had trusted that sheet and written the piece, the piece would have been entirely invented. Cricket is the most auditable sport in the world. I say that having come up through a football lab, so take it as praise, not a favour. In football, pulling a pass map requires a subscription to a private tracking company. In cricket the scorecard is open — every over, every ball, every umpiring decision, every DRS review log. The auction purse is public. The retention cap is public. The date the Impact Player rule came in is public. That does not mean there is a shortage of information. It means there is a shortage of interpretation. And the shortage bites hardest when a system comes back empty-handed and someone decides that empty-handed means there is no story. My experience runs the other way. When the numbers are missing, the question gets sharpest, because you have no slide to hide behind. The last two years in Indian cricket have produced promises that can be audited against numbers. The Women's Premier League's first season began in March 2026 with five teams, and with it arrived the claim of "democratised coverage in regional languages." On 2 November 2026 at Navi Mumbai, India beat South Africa to win its first Women's World Cup — a tournament played on home soil whose broadcast claim was larger than its sporting claim. The question is not whether coverage grew. The question is how much of that growth was tactical and how much was simply score-reading. This is where the measurement gap opens. The data desk measures one thing; the commentary box sells another. The desk asks how many balls went outside off in that over, which batter had his length changed against him. The box asks when the hundred was completed. Both are correct in their own place. They are not the same story. The diagram is not the truth, but it is the first honest question. I learned that in 2026, watching the World Cup from a Hyderabad balcony at 11:30 PM. Russia's 5-4-1 against Spain did not look passive to me; the pass map showed 1,029 completed passes and 74 percent possession, yet Spain's only goal came off a deflection at a set piece. I wrote that the low block was not passivity but a deliberately narrow funnel. Possession left my vocabulary after that piece; "where the passes went" replaced it. I watched from a balcony, so I trust the delay more than the roar. DRS is the most honest piece of measurement technology in the sport, and the irony is that it attracts the most argument. "Umpire's call" means the on-field decision stands when ball-tracking falls inside the technology's error margin. The system is declaring, in public, that it is not fully certain. Very little technology in cricket volunteers its own uncertainty. And still the crowd reads that uncertainty as corruption. I think that reaction is not about the technology; it is about our habit of treating every zero as somebody's fault. A filled number cannot see three things, and those three things are what most cricket analysis leaves out. First, format. A Test bowling average and a T20 economy rate are two different languages, and collapsing them into one sentence is the most common error in this trade. A spinner with a Test average of 24 and a T20 economy of 7.4 is not an "all-format specialist" on that basis; that is marketing, not analysis. Second, sample. A strike rate across five matches is not a forecast for a season; it is a weather pattern that has been given a rating. Third, the human variable for which no sheet carries a column. A bowler changed his seam position. A captain changed his field out of stubbornness. A batter deliberately left one alone. That is cause, and cause is not measured. Read the XI backwards from the rulebook. That is my habit, and in cricket it pays better than it does in football. The Impact Player rule entered the IPL from the 2026 season, and that single rule redefined what a "performance" is. An all-rounder's value is no longer set by his two skills; it is set by which slot he can occupy in place of someone else. Comparing pre-2026 and post-2026 numbers without accounting for that rule is like averaging the scores of two different pitches. The auction side is the same argument wearing different clothes. Purse and retention cap decide who is available and at what price. The question is never "who is best"; it is "who did the system make available." A player's price is evidence of the scarcity of the slot he fills, not proof of his ability. RTM becomes the tool for hiding that scarcity — the franchise says "we kept him," when the truth is "we had nobody else for that job." India's second XI is routinely called the hardest team in world sport, and I find that claim half true. Treating bench strength as a talent question is the easy reading; it is fundamentally an allocation question. Ranji knockout data and the domestic-to-international conversion rate both say the depth is a policy output. When the selection calendar, central contracts and the league window jointly decide who plays when, "depth" becomes the name of that arrangement, not a property of any player. In April 2026, when freelance budgets were cut and three commissions vanished in a fortnight, I did what I always do under stress — I went to film. From the Bundesliga restart I hand-charted 412 high turnovers across 92 behind-closed-doors fixtures, chasing a mechanic nobody was writing about: how pressing triggers change when there is no crowd noise. No editor wanted a 3,000-word data piece, so the newsletter started. That stretch gave me a rule I still work by — publish the chart even when the argument is unfinished. Analysis paralysis is a failure mode, not a standard. Now the contrarian half, which I like most and fear most. That empty sheet was the most honest document of the week. We work in an industry that rewards filled cells. A heatmap fills the pitch with colour and hides the player's role — my oldest complaint. A hundred fills the column and hides the match situation. In that environment, a system that says "I found nothing" is producing the most trustworthy output on the table. I am not arguing that every empty report is a good report. Write the boring explanation first: the source was probably three lines and a photograph. Asia-region cricket briefs usually are — a fixture announcement, an injury update, a selection name. Extracting an eight-dimension analysis from that is building a bicycle out of a fish. The error was not in the source; it was in the expectation. But the whole point rests on one condition: an empty return is trustworthy only if the system also says how far it looked. "I found nothing" and "I did not really look" are not the same sentence. One field on this sheet admitted, unprompted, that source quality and time sensitivity had been left "not assessed" — which means the work stopped early, not that the source was thin. That is where diligence and laziness look identical, and only a line of disclosure separates them. Watch the second line, where the game hides its paperwork. A press box without a chair is still a press box; you just have to note who built it and who was not given a seat. In Kolkata I did not get the chair, but I got the notepad, and the notepad taught me that a byline is earned by the work, not the credential. So what to check next. The next time you read a cricket report — a scoreline piece or a selection piece — test three things. Is the format stated plainly. Is there at least one named entity you can verify yourself: a team, a player, a date. And most importantly, does the report tell you what it does not know. Trust the report that shows you its empty spaces. Ask the next question of the one that fills every cell. The next sheet will reveal which column was left blank this time — and that column may well be the whole story. A constraints paragraph, as I attach to every tactical proposal and am applying to myself here: this piece is built around an empty data sheet, so it contains no match, no player and no scoreline. I have deliberately not filled what is not there. The next sheet will show which column went blank — and that column may turn out to be the story.