What Was Never Recorded Is Not Clean: Cricket's Silent Audit Failure

Twelve fields. Every one of them present. And in every one of them, the same entry: "not available." Format unassigned. Venue unassigned. Player unassigned. Date unassigned. At the foot of the document, a single line: no risks flagged.

This was not a scorecard. It was scaffolding that nobody had filled, submitted anyway. It landed on my desk last week under the heading of cricket analysis. I read it twice. The first time, I thought something was missing. The second time, I understood that the missing part was the report.

Cricket has no name for this, but the event is old. We say "nothing came up," and by the next morning we have read it as "nothing is wrong." That is the oldest hole in the game's data audit, and it decides more matches than any bowling plan.

Cricket's information system runs on checklists rather than information. A match referee's report has a space for an "incident"; nobody is required to write "normal." The Anti-Corruption Unit's monitoring log runs on flags, not compliments. The workload sheet counts overs. The NOC register records permission, not the reason for it. In the DRS log, one sentence keeps returning: on-field decision stands.

The design is identical everywhere. Flag the problem; leave the field blank if there isn't one. For a game, that is fine. For a system, it is lethal, because a blank field can mean two entirely different things: "checked, nothing found" or "never checked." The spreadsheet shows both in the same colour.

Now look at what the blank field costs. In 2026, Star India bought the IPL's global media rights for five years at ₹16,347.5 crore. Behind that money sits a single belief: that what is in the record is true, and what is true is in the record. The day that belief breaks, the price does not fall immediately. The day it breaks, fewer people turn up to bid.

The match referee's report is the cleanest illustration. Incidents recorded under the Spirit of Cricket go into a separate field. If two incidents are logged across a hundred matches in a season, the report says the game is being played cleanly. What the report actually says is that two incidents were logged. What happened in the other ninety-eight is in no field at all.

One disclosure, because this profession writes it too rarely. I am writing from a desk whose income partly comes from the same broadcasters, franchises and organisers whose data forms I am auditing here. That does not invalidate the piece; it means the piece should be read with a condition attached. A reporter whose source list and employer list keep converging should at least be expected to say, on every claim, where the claim came from.

The clearest example is the one every season review misreads.

The DRS log records a decision: on-field decision stands. At the end of the year, an analyst adds up those rows and writes: three reviews lost. That is not what happened. What was lost was not the review; what was lost was the technology's margin of error. Ball-tracking said the ball was not hitting enough of the stumps — meaning the evidence was not conclusive. In the log, that becomes the same line used for a ball nobody appealed for.

The real damage is that team management builds the next match's plan from that same log. A side that has "lost" three reviews will hesitate before sending one upstairs next time. A side that sent none will be called disciplined. Both are the same error wearing different shirts, and the log has one field for both. In the post-match meeting, nobody asks which definition of "lost" was in play.

After the 2026 England tour, I charted 1,146 deliveries from Lord's and Trent Bridge. Every top-order leave tagged, every slip cordon position logged, every length mapped for depth. One column I could not fill: "was this leave a decision or a reaction?" That was the column that mattered most. I left it blank and wrote in the report that it was blank. The desk asked why. I said: because filling it would be a lie. A three-match minimum sample and a caveat sheet have been habit ever since.

The second site is the workload sheet, where a blank field is the most expensive of all.

The sheet counts overs, spells, days, flights. It has no space for "reported stiffness, bowled anyway." So a fast bowler who sends down fourteen overs in 34 degrees of humidity sits in the same row as one who sends down fourteen on a cold day. The sheet is not lying. It is answering the question somebody asked — and has forgotten there was a second question.

The blank field travels upward. The coach sees overs. The selector sees availability. The board sees a fit player. Three floors of confidence rest on a column that was never populated. The risk here is linguistic rather than technical: "not injured" and "not recorded as injured" collapse into one word, and a fast bowler's career length is decided by that gap.

The toss and DLS behave the same way. A revised target after rain always survives as a number — 187 in twelve overs. No sheet records whose favour that number was tilted towards. Duckworth-Lewis-Stern is an algorithm, not a verdict. The scorecard prints it as a verdict anyway, and two years later an analyst uses that number to measure a side's "rain capacity."

The third site is the Ranji scorecard, and this is where the story reaches the auction.

One spinner takes 40 wickets on a turner at Chepauk. Another takes 40 on a flat deck in Rajkot. The scorecard records 40 for both. Pitch type, opposition strength, innings context — those exist in the scorecard but in no aggregated sheet. And the December auction runs off the aggregated sheet. This is not a scandal; it is a design choice. But the coverage dismisses the auction as theatre, while the actual talent policy of Indian cricket is written in that compressed column. The field we do not fill is filled by somebody else — in their own interest.

And the fourth example is the one cricket cannot afford to forget.

Lord's, 2026. Spot-fixing was taking place in the very match under international monitoring. The monitoring log came back clean. No flag was raised, because the system never saw a flag to trigger. What caught it was a newspaper sting. In February 2026, the ICC tribunal in Doha banned Salman Butt for ten years (five suspended), Mohammad Asif for seven (two suspended) and Mohammad Amir for five.

That example should hang above every cricket data audit. "No flag" and "no event" are not the same sentence. The day we treat them as one, the audit ends and only the form survives.

One thing must be written separately, because it cannot be entered into data. The pain of an injury does not appear on the sheet. A player's decision in 43-degree heat does not appear on the sheet. A night's sleep, a delayed flight, trouble at home — there is no column for these. I am recording them not as data, but as the boundary where my method stops working. The analyst who will not stay quiet here quietly converts them into a number, and that number then lies forever.

Now the plain reading, in full. Perhaps the document really was empty. Perhaps the source was a photo caption, a page behind a paywall, a day washed out by rain. Not every empty report is a con. Sometimes nothing genuinely happens, and the honest answer that day is "nothing happened."

But that is exactly the distinction that must be recorded. A pipeline that drops "nothing happened" and "nothing could be checked" into the same field is not auditing; it is stalling. A system that cannot tell those apart is not measuring risk; it is concealing it. The irony is that the empty report looks the safest of all, because nothing in it can be wrong.

This is where the media habit turns dangerous. We convert uncertainty into narrative, because narrative gets printed and a blank field does not. In 2026 the IPL was played in empty stadiums. The noise meter read zero. Empty stands did not remove pressure; they moved it into the players. Whoever called that season "pressure-free" was reading the meter, not the man.

The same error repeats in every report. The field is blank, therefore there is no risk. It looks like an argument. It is not an argument, it is a habit — and mistaking a habit for evidence is the oldest mistake in this trade.

After the next match, before signing the next report, ask one question: who filled in this field with "not available," and why?

If the answer is "because it was checked and nothing was found," the report is complete. If the answer is "because nobody looked," the report is unfinished, however many fields appear filled. The final looked like chaos until the field placement explained it. That one-run final in 2026 — Mumbai 129/8, Rising Pune 128/6, Krunal Pandya's 47 — was understood from the field map, not the scorecard. Next time a report comes back empty, do not look at the scorecard. Look at the map. And if the map itself is missing, write exactly that.

The series was not lost in a session; it was lost in the audit.