The Empty File, the Full Commentary: Cricket's Evidence Crisis

A cricket-analysis packet landed on my Bengaluru desk last week. Eight sections. A risk matrix with five rows, where likelihood, impact and mitigation were all marked "Unknown." A transmission map with six arrows, each one trailing an N/A. An expectation-gap table with three columns and nothing in them.

Only one field in the entire file was populated: "Domain: Cricket (Asia)."

No scorecard. No venue. No temperature. Not a single ball logged, not a single player named. That was the anomaly. The file was not incomplete — it was complete. Nothing had been left out by accident. The space where information should sit had been left deliberately empty, and what filled it was honesty. The machine ran at full speed with no fuel, and the machine handled the absence of fuel with good manners.

I have spent more than twenty years at the edge of grounds, in commentary boxes and in club coaching, and I have seen hundreds of these files. The difference is that they usually look full. They carry names, numbers, dates — and the same hollowness. The empty file did what full files never do: it stripped the structure naked.

What a real match audit records

After the 2026 IPL final I built a twelve-part, frame-by-frame series. Mumbai Indians beat Rising Pune Supergiant by one run at the Rajiv Gandhi International Stadium. The series logged every yorker of Jasprit Bumrah's twentieth over, plotted Krunal Pandya's 47 on an over-by-over space chart, and mapped Rohit Sharma's boundary-rider placements at three separate moments. There was not a sentence in that report without an over number, a ball number and a field setting behind it.

The next year I applied the same method to Test cricket after India lost 4-1 in England. The innings-and-159-run defeat at Lord's and the Trent Bridge win went onto the same sheet. We tagged 1,146 deliveries, marking every top-order leave outside off stump against seam position and the state of the slip cordon. The desk wanted a star-worship post-mortem; the file contained length, seam and leave counts.

That work imposed two rules I no longer write without. First, a three-match minimum sample. One innings does not settle a technique; one over does not reveal a field-setting intention. Second, a caveat sheet. Before any claim, I have to write down what could weaken it — weather, toss, injury, pitch age, sample size.

Everyone claims this discipline. Few practise it. What the empty file exposed is what remains when the discipline is removed: the skeleton. Eight sections, a matrix, a map. Analysis still looks like analysis without any information in it.

Five leaks, and they are in our own reporting

The risk flags recorded in that file are, in effect, an indictment of everyday cricket coverage. Mixing formats. Extrapolating from a single-match sample. Home-ground bias. Failing to strip out the toss and DLS. DRS umpiring controversies that compromise the fairness of a result. These are the five leaks through which most published tactical commentary drains away.

Format-mixing is the most common and the least detected. A T20 strike rate becomes evidence of a Test No. 5's technical flaw. A one-day spell becomes proof that a bowler tires in his second spell. The reality is that when the format changes, four things change with it: the age of the ball, the constraints of the field, the availability of DRS, and the batsman's risk calculus. A number that carries meaning in one format becomes decoration in another.

The single-match sample is the cleverest leak, because it tells the truth. What happened in one innings did happen. The problem is that the same innings does not repeat on a different pitch the following week. Most of the questions I get asked sit here — "why wasn't that bowler used in that spell?" The answer is usually not technical. It is in the workload table, the travel schedule, or an injury report nobody published.

Home-ground bias is the third and the most concealed. A home average is not comparable to an away average, yet the two get placed in the same table and a career is judged on it. In India this leak does double damage: home numbers make a spinner look great, away numbers make the same spinner look inadequate, and both times pitch age, heat and DRS fall outside the count.

Leaving the toss and DLS out of the equation is the fourth. The toss does not matter equally everywhere, but where it matters it can be the largest component of the result. A score made after DLS never reflects the true tempo of that innings. Call an innings "slow" when it was built before rain, and you are not reading a match — you are reading a rulebook and calling it performance.

The fifth is DRS. An umpiring controversy has a direct bearing on the fairness of a result, and yet it gets filed under "debate." A match decided by a review yields only half a technical lesson.

The argument was settled off-air

One thing I have watched for twenty-five years, and it becomes clearer every season: India's data desks won this argument long ago. Which matchup will be created, which bowler returns in which over, which angle works against which batsman — these are settled on an analyst's sheet, not on the field. What lags is the commentary box. And that lag is precisely where the public vocabulary of a "collapse," a "brave call" and a "mystery spinner" gets manufactured.

A series is not lost in a session; it is lost in the audit. The innings-and-159-run defeat at Lord's was not the product of one bad hour. It was the product of a count of balls left alone — a count nobody made during the match. The collapse was visible; the cause was not. By the time the cause surfaces, the audience has moved to the next series. My 1,146-delivery sheet was useful for exactly this reason: it showed what the scorecard did not.

It is also worth remembering that empty stands did not remove pressure; they moved it inside the players. In that strange 2026 stretch when grounds were silent, the voice changed, not the pressure. Those who assume the absence of a crowd made the game easier are merging two different things — atmosphere and responsibility. Atmosphere is external. Responsibility is not.

The risk of an imported framework

Here I have to say something about my own trade, because the fault is mine too. An analyst born in England and working in India has the vocabulary of seam position, the Dukes ball and April county cricket as a native language. That vocabulary is a strength. Vocabulary and authority are two different things, and conflating them is the easiest mistake available.

An argument that reads as correct through county logic can be wrong on a Chepauk turner in May. When the two frameworks disagree, the honest work is to report the disagreement — not to resolve it from the press box. The domestic record and the local weather ledger should be checked before speaking. This is precisely where a great deal of imported commentary declares Indian decisions to be "errors" and considers its job done.

What the numbers cannot hold

One paragraph has to be reserved for what I will not call data. I have seen spells that were correct in every table and wrong on the ground, because the bowler had not slept. In May heat, a batsman's decision-making shifts with fatigue, and fatigue does not sit in a spreadsheet column. Neither does fear — the fear that pushes a batsman near the end of his career into playing at a ball leaving him outside off.

I am not arguing these should be converted into metrics. I am arguing they should be named plainly as unquantified, not smuggled in under the cover of data. An analyst who will not admit his method is incomplete mistakes his limit for his strength. That has happened to me. The sheet always produces a pattern, and patterns are seductive to a man who trusts process. The sheet's job is to show a pattern, not to explain a match.

The commercial demand

There is a further layer. On a calendar with a new match every three days, demand for copy outruns demand for information. The auction is still covered as theatre, when the most consequential selection decisions in Indian cricket are made in a December spreadsheet rather than a February Ranji dressing room. And when the real selection forum is invisible, commentary must anchor itself to something visible — an innings, a statistic, an argument. The empty file is the cleanest evidence of that transaction: demand for analysis is so intense that the raw material is never checked.

The plain reading, then the complication

Read first what is in front of you, in full and without decoration. The file was empty. The analyst refused. That was the right call. With no match, player or venue on record, publishing performance ratings, team rankings or commercial valuations is not merely wrong — it is a fraud on the reader. Refusal is a legitimate professional act.

Now the complication. If refusal becomes a habit, it is also a product. An analyst who publishes "insufficient information" eight times running has built a safe house. Zero risk of being wrong, plus the pleasure of looking like the most honest man in the room. This is counter-intuitive branding in a white coat.

And here the real point emerges: the empty file is more informative than a full one. It shows that the pipeline producing cricket commentary has no filter at its mouth. Whatever arrived went straight through. Nobody asked who sent the packet, on what basis "Cricket (Asia)" was typed, or which match was supposed to be under discussion. Not the analyst's failure — the intake desk's. This is where regulatory and commercial pressure on cricket coverage converge. Every rule change is a scouting report written by a regulator; every scouting report is a market signal. With no input, none of it can be read — and that is the file's only solid finding.

One warning belongs on the record. "Asia" is itself a framework. In a file with no sporting information, that geography becomes the only fact, and the reader quietly assumes the subject is a regional rivalry, an Asian league or board politics. That assumption comes from no evidence. It comes from the habit of filling empty space. I have made that mistake in my career and hidden it. So this time I will write it plainly: there was nothing there.