Empty Sheet, Green Board: On Cricket's Data Desks, 'No Flag' Has Never Meant 'No Risk'

It was twenty minutes to three in the morning at a Delhi data desk. Eight tabs were open on the screen — format, player, team, league, governance, risk, narrative, transmission. Each tab had a table, each table had headers, and under every header the same line: 'insufficient information'. No score, no player, no venue, no date. A junior analyst looked at the screen and said, "There's no red flag, ma'am." I asked, "No flag, or no data?" He paused for two seconds. The most expensive mistake in this profession happens inside those two seconds.

What sat in front of me that night was not cricket analysis. It was an empty shell that the framework had filled in so neatly it looked complete. The domain label was populated — cricket_world — and everything else was blank. This is not a hypothetical. Last week a Stage-1 extraction returned exactly that payload: title N/A, source N/A, summary blank, information points empty. The machine classified the document and then stopped reading it.

The most dangerous data failure in cricket is the one that makes no noise. A wrong number starts an argument, gets caught in the argument, and is corrected the next morning. A missing number sits quietly on the table and looks like a green board.

What an information point is, and why cricket cannot be read without one

A cricket analytics pipeline runs in three stages: classification, extraction, analysis. The first says what the document is about. The second pulls out information points — atomic facts such as "the batter scored 84 off 51 balls" or "after rain, the target was revised to 187 under DLS". The third puts those facts in front of the model and asks whether the claim survives.

When the second stage returns empty while the first looks populated, what gets produced is not analysis. It is a negative-control fixture. The fault signature is clean: the classifier fired, the extractor did not. This is not thin information. It is zero information, and formatting zero information like a clean report is the actual hazard.

I have a cheap rule for this, learned at Hyderabad in 2026 on the wrong side of one run: a claim that cannot be written as a phase number does not survive the edit. But the rule has a second half — a phase with no number at all demands silence. Silence and 'all clear' are not the same sentence.

The format gate: the first question, and the one that matters

Every analytical error in cricket traces back to one place — dropping Test, ODI, T20 and The Hundred into the same vessel. A T20 death-overs economy of 8.2 is a serviceable figure for a fast bowler; the same 8.2 in a Test first spell devalues him. A number from one format is not evidence about another. That is why a format tag should be a hard gate rather than a courtesy. If Stage-1 cannot say which format the document belongs to, Stage-2 should not run.

I say this from practice, not principle. In 2026, at forty-eight, I left fifteen years split between print desks and odds floors to join a Delhi trading desk that priced international cricket for offshore-licensed operators — the only woman among fourteen traders, and the only one who had never played the game. I rebuilt our T20 pricing around three fixed blocks: powerplay, middle, death. Everything else — momentum, pressure, big-match experience — was cut.

21 May 2026, Rajiv Gandhi International Stadium, Hyderabad. Mumbai Indians made 129/8 and beat Rising Pune Supergiant by one run. At the innings break the market had Mumbai as underdogs. My death-overs economy benchmark did not. The difference was that I had written the benchmark down before the match, so afterwards I did not have to prove my point — I only had to put both ledgers side by side.

One run decided the final, and I had already written down why it might. That reads well, and that is precisely the danger. One match is one match. The correct lesson from that night was not that the model was right; it was that the model produced a number before the match and the match argued with it. The day I start saying a single game proved the model, I have broken my own frame.

The empty ledger: counting Ranji coverage

There is another kind of empty data that never shows up on a screen — coverage counts.

I keep two ledgers: what the model said, and what happened. The gap is the lesson. For several years I have counted Ranji knockout match-days and the reporting on them side by side. The two lines do not move together. Matches get played; reports do not get written. And where reports are not written, the following year it is assumed nothing happened there.

What survives after the crowds leave is the only honest measure of a cricket economy. The IPL did not damage Test cricket in India; it damaged the Ranji Trophy's claim on relevance, and nobody priced that. Broadcast rights are the biggest, cleanest dataset on the desk, which is exactly why they mislead. A rights figure is the price of a contract, not the health of a sport. Health is further down — domestic match-days, under-19 participation, and the reporting on matches played in front of empty stands.

So when a data sheet comes back empty, my first question is not what went wrong. My first question is whether the emptiness is real or procedural. In the Ranji case the emptiness is real, and that is the story. A server failing overnight is not news. Ten years of silence is.

Integrity: 'unassessed' and 'clear' are not synonyms

Here the matter turns from technical to ethical.

An empty payload produces no anti-corruption signal of any kind. It must never be read as clean. The cases that reached the Anti-Corruption Unit — Cronje in 2026, Pakistan's spot-fixing in 2026, the IPL in 2026 — were not caught on vibes. They were caught because somebody's sheet would not reconcile: the sequence of deliveries in one over, the choice of bowler after a toss, a batter slowing without reason. On a day the data desk returns empty, that pattern check simply did not happen. The status is not 'clear'. The status is 'unassessed'.

The gap between 'no flag' and 'no risk' is the least audited gap in cricket. The commentary box is the best example — the last un-audited room in the sport. Nothing is questioned for forty overs, and then three decisions are declared obvious in one over because nobody called them wrong. Not objecting and being right are different conditions.

The contrarian side: the danger is not a wrong number, it is a silent one

People ask me what the biggest failure at a data desk looks like. They expect to hear 'a bad model'. The truth is duller.

The danger is not the wrong number that starts an argument. The danger is the number that never arrived, and the formatting that took its place. A blank page looks blank — nobody mistakes it for a report. But an eight-tab document with headers, footers and 'N/A' in every cell manufactures authority. A selection meeting leans on that authority and then reports that 'the analyst raised no red flags'. What actually happened is that the analyst was never given data.

There is a second trap, and it catches people like me hardest. Phase pricing works so well across a season that it feels equally authoritative on a single match. I now attach a sample size and a stability test to every phase claim, and where it is one match I write 'one match'. Russia 2026, the first VAR World Cup. I built a dead-ball expected-goals model because the market still used possession as a proxy for control. A record 29 penalties were awarded across the tournament. 15 July, Moscow — France 4, Croatia 2, and three of France's four goals originated from dead-ball situations. That same week a client replied to my note with one line: "Women don't read defensive lines." I answered with the spreadsheet.

The first VAR World Cup taught me to price dead balls before anyone argues about them. It also taught me that a correct forecast is still a sample. Twenty-nine penalties is a tournament statistic, not a law of football.

Every recalibration I have done began by admitting the old baseline was honest then. The 2026 model was not wrong; it was right for the data that existed. What was wrong was assuming it would stay right.

The next-round signal

The next time a scorecard, an analyst's sheet or a selection report lands in front of you with 'no flags' written all over it, ask one question: is this silence because everything was fine, or because the data never arrived?

I give my contributors a one-page template and a hard cap on narrative sentences. Next season I am adding one line at the very top: the format tag. If it is absent, the report stops. Because a document with no format in it is not about cricket — it only looks like it is.