Stamped ‘No Risk’ on an Empty File: The Crack in Cricket’s Information Chain

The file opened and there was nothing in it. Title: N/A. Source: N/A. Author: N/A. The information-points array was empty. The player who should have been named was absent, the scoreline was absent, and so was the format label — Test, ODI or T20 — that every cricket metric hangs off. The document ran to eight sections and all eight ended on the same sentence: insufficient information.

Below that sat the risk matrix. Six rows — sporting, personnel, commercial, rules and integrity, public opinion, systemic. Each row N/A; each cell marked insufficient information. And directly underneath, the most dangerous line in the whole file: no risks flagged. In thirty-four years I have read more rubber stamps than documents, and the expensive mistake is never the one with a wrong number in it. It is the one with no number at all, signed off anyway.

The habit started at Mohali on 25 April 2026. After a Mumbai Indians–Kings XI Punjab match, Harbhajan Singh slapped Sreesanth. Match referee Farokh Engineer filed his report: eleven matches and one hundred per cent of the match fee. Harbhajan appealed; the sanction fell to five. I covered both hearings and understood that night that the second hearing is the better story. The first tells you the punishment. The second tells you which clause the punishment stood on, and why the clause moved.

So I stopped reporting verdicts. Every piece now carries the article number, the names of the panel, and whether the appeal road is open or shut. Editors began routing disciplinary briefs to me because my copy told them what could actually be overturned. The clause on page forty-seven that nobody read became my beat.

In May 2026 I was in Mumbai when Sreesanth, Ankeet Chavan and Ajit Chandila were arrested in the IPL spot-fixing case. For the next two years I read the papers almost nobody opened: the Mudgal Committee findings, and the Lodha Committee report of 2026 that suspended Chennai Super Kings and Rajasthan Royals for two seasons each. I built a four-hundred-entry spreadsheet of tribunal outcomes — charge, panel, sanction, appeal result. It showed sanctions falling by roughly half on appeal. The spreadsheet did not lie; the ban sheet did.

That dataset cured me of first verdicts. Every sanction I file now carries the appellate route, the overturn rate from my own numbers, and the name of whoever appoints the panel. It made my copy slower and more accurate, and it made me unbearable at press conferences.

The paper trail arrives in a different shape now. Instead of a referee's report there is a data payload: stage one extracts facts from the source, stage two tests them. The file in front of me was a stage-two report. Its stage one had come back empty.

It is worth counting what was missing. No title, no publisher, no date. No author stance — which means it is impossible to establish whether the source was reporting, analysis, opinion or promotion. No time-sensitivity assessment. And above all, no information points: the atomic, verifiable factual units on which every conclusion is supposed to rest. The framework's own rule is blunt — each conclusion must trace back to a point. With zero points, any conclusion would be fabrication.

The cost of that single emptiness is immediate. Batting strike rate, bowling economy and average are format-relative. In T20 an economy under 7.0 is treated as elite; in Test cricket the same figure is meaningless, because the arithmetic of overs works differently. The ICC publishes three separate ranking tables — Test, ODI, T20I. With no format tag you cannot even select which table to open. A conclusion drawn from a document marked N/A on format is a number with its unit amputated. On the field, it means nobody can say whether the ball was bowled or thrown.

The most instructive detail was not the empty field but the one that pointed at itself. The entities box instructed the analyst to identify teams and players from the information points above — and there were no information points above. A self-referential null. Technically, that is the most valuable clue in the file, because it does not suggest a truncated scrape. It suggests a field-mapping error: somewhere the pipeline failed to read the document and moved on regardless.

Four causes are plausible. Three are routine — a paywall, a JavaScript-rendered page, a video or podcast whose transcript was never generated. The fourth should unsettle the largest market in cricket: a parser slipping on Devanagari. If that is what happened, Hindi copy will keep falling silently out of the system and no dashboard will light up red. The story is engineering. The consequence is journalism, in the language fewest people in the building are tasked with reading.

One thing in the empty document was genuinely useful: the minimum-information specification printed under each dimension. Format label, competition, innings state, score, venue, pitch, toss, DLS revision. Player name, role, format, the specific claim, one season-level statistical anchor. Team, competition, ranking, home or away designation. The right way to read those lists is as a first draft of a stage-one schema validator. Six mandatory fields. Any one null and the document does not pass go.

The report's only hard finding is that the failure surfaced at the analysis stage and was never stopped at ingestion. That gap looks small and costs a lot. In 2026 the record I had was thin but it existed — charge, panel, sanction, appeal. Here the record does not exist at all. And in cricket that difference changes the shape of a sanction faster than anything else: no paper, then rumour; rumour, then a panel; a panel, then an appeal. All three rungs run on documents.

The mainstream reading of this episode is that the guardrail worked. Fairly stated, that reading is right in three places and I will not argue with any of them. First, refusing to analyse an empty payload was correct — nothing was invented. Second, refusing to backfill the blanks from general cricket knowledge was more correct still, because that is where invention begins. Third, tagging every conclusion with a confidence level was correct. Those three things make the document worth reading.

The argument is whether the guardrail was designed or lucky. The report concedes no null-input schema check was found upstream. The empty file therefore left ingestion, reached analysis, and stopped only because the person reading it was honest. Next time the reader is tired, or on deadline, or on another desk in another city — and six N/A rows become one line on a slide: no risks flagged. Nobody writes underneath that line whether risks were absent or merely unseen.

The real exposure here is epistemological, not cricketing. Absence of evidence is absence of evidence; it is not a clean bill of health. Six N/A rows say we did not look at six things. A reader will take them to mean six things are clear. I have watched editors slip on that distinction for twenty years, and I slipped once myself — in 2026, when I filed on the first hearing in the morning and read the appeal outcome that evening.

For anyone whose answer is simply more data, a warning. This pipeline records what was parsed. It does not record whether the source existed, whether the fast bowler had workload clearance, what the selection committee decided, or how a board spokesman bent a word. Clean data does not prove the pressure was clean. That blind spot belongs in the same paragraph as the praise for the dataset, not in a disclaimer at the end.

On 16 June 2026 I sat in front of a monitor with a stopwatch for France–Australia because I wanted to know how long the first World Cup VAR review actually took: 82 seconds from Andrés Cunha's signal to Griezmann's penalty. I filed a protocol explainer that night, then one per round. FIFA later claimed decision accuracy had risen from 95 per cent to 99.3 per cent. I timed the replay until the frame stopped arguing, and learned that a number is only as good as the frame it was measured on. 99.3 was a claim about a protocol that day, not proof of a truth.

A blank scorecard is an interesting document. It does not say the match was drawn; it says nobody wrote the score down. Three things are needed before the next cycle — a hard gate that blocks any file with an empty payload, the six-item retrieval brief promoted into an actual schema validator, and a separate audit of entity extraction, because the box that pointed at itself is still wired in.

Before I blame a referee, I read what the referee was told. In this file nobody was told anything, and the stamp was ready anyway.

The question is not how many empty files arrived that day. It is how many have left the building stamped no risks flagged in the last few months, with nobody in the room willing to call an N/A an N/A.