Autopsy of an Empty File: What a Cricket Data Desk Does With a Null Result

2:40 a.m., Mumbai. Nothing on the desk except the glow of a screen. The file was named stage1_cricket_world_0413.json. I opened it the way twenty-seven years of habit has taught me to open a scorecard — top first, then bottom, then top again. There were eight fields. Seven were empty. The eighth carried a single label: “cricket_world”.

No title. No source. No article type. The information-points list was blank. The entities field carried an instruction — “identify from the information points above” — which meant identifying from points that did not exist.

I had opened the ledger before sunrise; by noon the numbers had not rewritten the story, because there were no numbers. What came back was a clean null result: the frame complete, the cargo zero.

It is worth explaining what normally happens at this desk, because an empty file is never only an empty file. The pipeline runs in four parts — the original source, stage-1 extraction, the list of information points, and the eight-dimension stage-2 analysis. The rule is hard: every conclusion behind one information point, every information point behind one source and its date. Where there is no information point, there is no sentence.

That rule once saved a night. 21 May 2026, Rajiv Gandhi International Stadium, Hyderabad, the IPL final. Mumbai Indians made 129/8 and beat Rising Pune Supergiant by one run. My match report that night did not begin with “the momentum shifted”. It began with Jasprit Bumrah’s 17th over, and I fixed that over using a death-overs pressure index — runs leaked per dot ball under a rising required rate. The index flagged the over before any columnist did, and on that night I first understood that the centre of a report could be an over rather than a scoreline.

A year later, 1 July 2026, Moscow. Spain completed 1,029 passes against Russia — the highest World Cup figure since 2026 — and lost on penalties after a 1-1 draw. My shot-quality model had Spain above 2.5 expected goals from 25 attempts. The blog’s first line was that possession without penetration is a bookkeeping error, not a style.

In both cases the same thing held: there was a number in the first paragraph, and a source behind the number. Tonight’s file had no number, no paragraph, no source. It had a frame with eight dimensions, thirteen tables, and “N/A — insufficient information” in every row.

Eight dimensions, eight N/As

That output was not wrong. It was technically correct. Format and match analysis, player technique and data, team landscape and ranking, league and commercial ecosystem, rules and governance, risk side, public narrative and expectation, industry transmission — all present, all tabulated, all answering with N/A.

It is the equivalent of a scorecard going to print with handsome columns for batsmen, clean boxes for runs, a separate lane for dot balls — and every box left empty. Real paper, real signature, no match. When I opened the file, my first thought was that somebody had handed me a blank scorecard and asked me to read it aloud.

The first rule of this desk is that I do not file a report by filling in tables on all four sides. Count first, question second, narrative last — that is the whole method. And when the count is zero, the thing to write is an explanation of the zero, not a story.

The format is the step that was never climbed

The largest gap among the eight dimensions sat on the very first step: format. Test, ODI or T20 — without that, no cricket number speaks.

One example makes it plain. A strike rate of 130 in the 2010s marked an elite T20 opener; today it is close to the minimum standard for a good one. A strike rate of 80 is never the target in the first ten overs, is sometimes exactly the right call in the 45th, and frequently means nothing at all in a Test first innings. Look at bowling: an economy of 8.5 in the 12th over of a T20 is worse than par, while the same 8.5 in the 17th over is often a better bargain than a powerplay spell.

No baseline, no metric; no metric, no conclusion; no conclusion, no article. The file had no format, so the first door of the analysis was found shut.

This is where my own biggest professional risk surfaces. Several desks have fallen into this hole in recent years — lifting a Test baseline and laying it over a T20, or pasting the men’s structural frame onto the women’s game without adjustment. Consistency disguised as fairness is the easiest posture to take, which is why it is the most common. Treat context as a variable, not a disclaimer: declare the baseline first, say so when you shift the window, say it before the reader has to ask.

The tiers of coverage, and the selections made in the dark

Something else surfaced here that belongs to the whole cricket data industry, not just this file. Ball-by-ball data is not distributed evenly. The IPL has multiple providers, cameras, stump mics and tracking on every delivery. International cricket arrives with edge tracking and commentary feeds. A large share of the Ranji Trophy still yields partial scorecards — some rounds complete, others with two innings and no ball-by-ball detail at all. Women’s domestic cricket leans on scoreboards for much of its length. In associate cricket, plenty of matches have no publicly available delivery-level record whatsoever.

Where there is no camera, there is no audit of selection — and selection is mostly made there. I wrote that line in my ledger three years ago; tonight it stands next to an empty file again. We publish a player’s death-overs numbers every week in the IPL; an August-September Ranji round produces no public record of a 22-year-old spinner’s rhythm. The result is that the data argument stalls precisely where the selection has already been made. The audit happens where the audit is least needed.

An empty stadium is not silence — it is a control group with seats. A match without a feed is not mute either; it tells us what the loud fixtures are actually measuring. When a former cricketer says the Ranji standard is falling, my first question is not about the conclusion. It is: how many matches of ball-by-ball data do you have, which window, and what did you exclude? If the answer is nothing, that is an expressed guess, not an assessment.

This is why a standing weekly slot for women’s cricket is fixed at this desk, measured with the same lens. Equal standard does not mean identical metric — it means the baseline is changed openly, not quietly.

Looking for the eleventh over

Sitting in front of the empty file, I did what I do before every report: I went looking for the turning point. There was no turning point, because there was no match. The model was built for football; cricket broke it by the eleventh over, which is my oldest complaint. Since 2026 I have kept a fixed glossary of fourteen metrics so that no editor can ask me to tone down the stats. Every entry in that glossary assumes at least one delivery of record exists.

Tonight not one entry applied, because the preconditions were missing. Sometimes I do not find the outlier; sometimes the outlier finds my spreadsheet at 2 a.m. Tonight was a third thing — there was no spreadsheet.

What a null result is, and is not

One distinction matters here, because the term is used loosely in cricket. A null result is a statement that the available evidence does not support an assessment. It is not a negative assessment. Absence of evidence and evidence of absence are different animals.

A cricket example. Ball-by-ball records for many Ranji matches of the 1970s and 1980s are not publicly available. That does not mean no good player existed in that era. It means our feed was not where the cricket was. The same gap operates today, and it sits at the root of a historical injustice done to any neglected regional player. When we say “there was no data then”, what we are actually saying is “we were not watching then”. Those are not the same sentence.

So my verdict on this file is plain: it must not be read as any judgment about a player, a team, a league or a match. It is not proof of a dip in form, of a board’s negligence, or of a franchise’s commercial decline. The most dangerous move available is to fill an empty box with meaning.

Where the real fault sits

The instinctive reaction is that a parser or a scraper failed and the technical team owns it. My ledger says otherwise.

The fault usually sits in commissioning. The story is ordered first and the numbers are requested afterwards. An editor needs 800 words before six in the evening and already holds a thick impression about a player; the data desk is asked to gather support for it. On the day the support does not arrive, what gets published is not an empty file but a confident paragraph — because empty columns do not survive meetings.

The problem is not only technical, it is incentive-shaped. The market does not punish an empty feed; it punishes an empty column. That is why, after a decade of “data-driven” cricket writing, coverage of several Ranji rounds and women’s domestic fixtures stands exactly where it stood ten years ago. The number of dashboards has grown. The perimeter of coverage has not.

I owe my own accounting here, because publishing wrong calls beside right ones is a condition of this desk. More than once I have built a full story out of a partial scorecard and discovered later that the over I had hung the entire turn on was itself incompletely recorded. That was not a column error, it was a foundation error. My monthly model audit was weak in those months, and I recorded it as such.

And one thing must be recorded too: it is not the fan’s fault for wanting a story. Wanting a story is how people watch cricket, not a defect. The defect lives in the incentive held by the broadcaster, the editor and the agenda-setter, where the evidence should be checked before the story. Keep the accused and the system under inspection in separate columns.

What to watch next

The next time someone says a series has turned, or the Ranji standard has dropped, or a young fast bowler is losing his edge, ask three questions — how many matches of ball-by-ball data, which window, and at which over did the thing change. Whoever cannot answer all three has an opinion, not an analysis.

And on the desk side, one technical condition should be added: no record should pass to the next stage without a title and at least one verifiable information point. Tagging an empty record as failed_extraction, keeping it out of the aggregated feed and re-ingesting from the original source — a three-step gate is cheaper than the entire cost of this night.

The most valuable number in sport is not the most discussed one. It is the one least often checked. Before the first over of the next Ranji round, I will have a single question — is that match being fed or not. If it is not, that match is being played for somebody else, not for me.