The Empty File, the Full Record: Where Cricket Reporting Draws Its Evidentiary Line

The file opened at the Pune desk that night with a tag — cricket_asia — and nothing beneath it. No headline, no source, no information points. A geography, and under it, zero. A reporter facing that file has two roads. The first is the easiest sentence in the trade: 'something must have happened in Asian cricket.' The second is to admit the record contains nothing, and therefore so does the story. In forty-six years I have watched the first road taken far more often, in newspapers and in my own drafts. I took the second. On the desk sat the file I have kept open since March 2026. Three columns, stacked: the ICC charge, the national board penalty, the league consequence. The space between them is what I call the sanction gap. It is not abstract — it can be measured against one named player and one season's calendar. The ICC Code runs in four levels, from a warning and a fine of up to fifty per cent of match fee at Level 1, through a hundred per cent and one Test or two limited-overs matches at Level 2, two to four Tests at Level 3, and five Tests to a life ban at Level 4. The architecture is clean, and the cleanliness is the hazard. A well-drafted order reads like a closed case. It is not. Every sanction carries three unanswered questions: who verifies, by what date, and what happens when the date passes. In January 2026 the Supreme Court removed Anurag Thakur and Ajay Shirke and installed the four-man Committee of Administrators — Vinod Rai, Diana Edulji, Ramachandra Guha, Vikram Limaye. I was the only reporter on the Pune desk who set the draft constitution against the Lodha Committee's 2026 report line by line. The seventy-year age cap, the nine-year tenure, the cooling-off principle, one state one vote: each clause had a real name attached. One state one vote forced the Maharashtra Cricket Association at Gahunje to renegotiate its standing against Vidarbha. I published the clause-by-clause comparison as a public document and stopped writing 'board sources said'. Clause first, ruling after. That order earned its keep on 24 March 2026. Day three at Newlands, Cameron Bancroft's yellow sandpaper, and one night to explain why the ICC's Level 2 charge against Steve Smith — one Test plus a hundred per cent of his match fee — sat so far beneath Cricket Australia's twelve-month bans for Smith and David Warner and nine for Bancroft. The IPL contract for that season had already barred both men. South Africa won the Test by 322 runs and the series 3-1; the sanctions outlived the scoreline by years. A punishment is measured not by the months announced but by the matches actually missed. Twelve months across a calendar holding six Tests, fifteen ODIs and an IPL season weighs nothing like twelve months dropped into an empty window. The clause said nine months. The calendar disagreed, quietly, in a footnote. Follow the footnote. That is where the actual punishment lives. Then the case that became my template. 2 November 2026, Adelaide. Bangladesh needed a revised 151 in sixteen overs, finished 145 for 6, and lost by five runs. A complaint was lodged about Virat Kohli's feigned throw under Law 41.5 — fake fielding, a five-run penalty. Five runs. The law demands deliberate deception that actually deceives; a gesture alone is not enough. The official record held nothing establishing either condition. The ICC took no action, the scoreline stood, and the argument never died. That column gave me a framework: state the rule, state the evidentiary bar, state what the official record can and cannot prove. It travels to pitch reports, over-rate sheets and code-of-conduct hearings. It also cost me two dressing-room friendships I did not notice losing for about a year. The third case rests on documents rather than testimony. August to November 2026, the UAE bubble. The BCCI's bio-bubble SOP arrived eleven days before the IPL moved, some forty pages, and I read it against the ICC's June saliva ban. Suresh Raina left the Chennai Super Kings camp after thirteen members of the franchise contingent tested positive. On 10 November, Mumbai Indians beat Delhi Capitals by five wickets in Dubai in front of seats you could count. Empty seats do not silence a game; they only unmask the sounds. I re-watched six weeks of 2026 footage to test whether the standard had moved or only the room. The empty file carried a second lesson, technical in nature. The domain label should have read Cricket; it read cricket_asia — a geographic tag standing in for a category. It is the same error that runs through cricket analytics: lifting an IPL strike rate to argue an ODI claim. Format separation and label separation are one discipline. Where headline, source, type, stance and information points are all blank at once, substituting a specific claim for a geographic tag is no different from judging T20 capacity off a Test average. The problem is not missing information; it is measurement in the wrong unit. Here is the inverted argument. We assume the false story is the most dangerous. Experience says otherwise. A false claim can be checked, contradicted, killed. What survives is the plausible claim, built from context rather than document. 'Something must have happened in Asian cricket' contains no fact, so nobody can disprove it — and precisely for that reason it starts getting cited. That is laundering: giving inference the clothes of analysis. It is more expensive than a fake story because there is no way to take it off. Silence is also a finding. The ICC took no action at Adelaide; that is a fact and deserves recording as one. Nobody appealed. In twenty years, that is still the loudest thing I have heard — and the reason for no appeal may be a belief that the system will not listen. The match referee's silence does not repeal Law 41.5; it merely locates the evidentiary limit. The third hazard applies most to me. Forty years of watching institutional failure from outside produces a corrective impulse that quietly assumes it is explaining something to people who did not ask. The defence: begin every criticism in the board's own text, then in Indian reporters' prior work, and offer the foreign comparison last, not first. What an Australian or English governing body would have had to produce at this point is a legitimate question — as the end of an analysis, never the opening. What did I file that night? Nothing. I spent the night auditing the empty file and found the nullity uniform across every field. A genuinely thin article would still yield a headline and at least one information point. Uniform emptiness points to the pipeline, not the article — and to a batch-level defect rather than a single bad document. Cricket reporting teaches the same lesson: when fifteen files fail identically, the fault is in the room where they were made. The question past this one is ethical, not technical. Every cricket story stands on three pillars — a document, a date, and a name on the record. Where one is missing, the correct sentence is 'insufficient information', not an estimate. That sentence reads badly in print. It satisfies no reader, pleases no sponsor, and editors return it marked 'not a piece'. It is also the sentence that protects a player's career, a franchise's money and a reader's trust the next time round. Three things look likely to change. First, sanction-gap reporting will stop being confined to famous names: over-rates, pitch reports, late team-sheet changes all have their own charge-sheet-to-compliance path, and the gap there is just as real. Second, the IPL contract increasingly functions as the actual constitution of Indian cricket, with board statutes as the ceremonial layer above it — and a reporter who does not read the contract can never state the true length of a ban. Third, every desk needs a gate that returns any file carrying zero information points. Such gates are not built into newspapers; they are built into habits. The rulebook has a gap the exact shape of whoever is enforcing it. Filling that gap is not the court's job but the job of the reporter sitting in front of an empty file at eleven at night, deciding what to print. The next time a report opens with 'sources say', ask one question: which document, which date, and whose name is on the record. If there is no answer, there was no match there — only an empty file.