An Empty File, a Loaded Question: In Board Coverage, the Missing Page Is the Real Story

A twenty-page dossier landed on my desk last week — formatted, headed, footed, dated on every sheet. The first page gave a title, the second said 'context', the third said 'facts' — and from the third page onward, every field read the same thing: blank. Title 'not available'. Source 'not available'. Zero information points. Only one field was filled: 'Domain: cricket, Asia'. A routing tag. It stung the way a torn last page of a match referee's report stings, because that is the page where the finding is written.

This is not a hypothetical. In the last few years, the way Indian cricket governance reaches us — board press notes, selection-committee minutes, AGM records, leaked emails — shows a clear pattern: the skeleton is complete, the substance is missing. This is not carelessness. It is design. The BCCI is not a public authority, so the RTI route is closed; the result is that every document that leaks becomes a rare artifact, and the silence around it is deliberate silence. I do not read that silence as accident. I read it as a document.

Go back to March 2026, Newlands, Day 3. Cameron Bancroft was caught with sandpaper, Steve Smith's eyes were wet, and the classroom argument ended there. I downloaded the ICC Code of Conduct overnight and opened Article 2.2.1. The arithmetic is well known: Smith and Warner got one Test each from the ICC and twelve months each from Cricket Australia; Bancroft collected three demerit points and nine months. One incident, two justice scales, three sentences. The 2,800 words I wrote for my college magazine that night taught me the rule that still underpins my work: do not write about a controversy until you have read the clause yourself. The habit makes me slow — I lost three commissions that year — but it is the habit that won me the trust of two Ranji umpires, who now send me their match reports without asking for anonymity.

Now the empty file. When a Stage-1 record has no title, no source, no type, no core argument, no information points, and only 'Domain: cricket, Asia' filled in, that is not 'little information'. It is zero information. For a discipline reporter the consequence is concrete: from that tag you cannot tell which match, which board, which dispute, or whether it is reportage or comment. Six months of reporting confirmed once again that in board coverage, the biggest story is not the document you get but the page missing from the report — and the reason for the absence, not just the absence itself.

Two kinds of absence must be separated, because in reporting that distinction keeps me sane. First: no record exists — as with the many Ranji Trophy disciplinary actions that have no public log. Second: the record exists and is withheld — as with IPL contract terms, which we learn from broadcaster filings, not board filings. And third: the record exists and is boring — most cases, and they don't feel like news. Ignoring that third category is cricket coverage's biggest omission. I write in every file which category the absence belongs to, because 'no page found' and 'page concealed' hide an entire institutional ethics between them.

Back to October 2026. Empty stadiums, IPL in Dubai. On Mayank Agarwal's second run the square-leg umpire signalled short run. Punjab finished level, lost the Super Over, and the table moved by one point. That night I started a newsletter, The Third Umpire, and its fourth issue was a 4,000-word anatomy of Law 18.3 — why on-field judgment sits outside every review protocol. Subscribers went from 400 to 3,100 in six weeks; among them umpires, coaches and two sports lawyers. That was the lesson I still apply to every file: rule failures travel further than tactical analysis.

Then February 2026, Ahmedabad. Narendra Modi Stadium, third India-England Test, ten-wicket win inside two days; seventeen wickets fell on day two. Match referee Javagal Srinath rated the pitch 'average' — zero demerit points, no published methodology. I wrote 1,200 words asking what 'average' means, who signs it off, and whether the rating system has ever been tested on appeal. A national sports digital outlet ran it as my first paid byline. That day I stopped apologising for a beat nobody else wanted. The byline convinced me that the beat no one covers leaves the most record.

Now the part where I fight my own habits. My biggest risk is treating every missing page as concealment. The suspicion is often right, and that is why it becomes a habit — but when it becomes the default lens, ordinary administrative mess gets printed as a cover-up. So I now rank gaps by stakes: does no record exist, does it exist and is it withheld, does it exist and is it boring — and I say which in the sentence itself. The second risk is the replay loop. I have watched a referee call 47 times; after the fortieth view, conviction hardens, corroboration does not. I cap the loop and write what the replay cannot show — the missing angle, the mic that was off.

And the biggest point, clearest at the bottom of the pyramid. The IPL has no shortage of documents — squad lists, trade windows, forensic broadcast contracts, everything on record. At the Ranji Trophy level of the same sport, disciplinary reports are thin, under-reported, sometimes with no public document at all. That gap is not only a coverage failure — it is a governance failure, and the two are the same thing. When there is no record of action against an uncapped player, you cannot even say whether he got a hearing under which clause. For him the clause is not abstract; it is his livelihood. I have built that into my filing system: one line at the top of every clause sheet — 'who does this clause land on?'

Takeaway. The way forward is to move from 'what happened' to 'who recorded it, and when.' Every board story should carry three dates — the incident, the record, the report. Where the three do not meet, there is the gap; and where there is a gap, the next question is ready. The question is not why the record was empty — it is who took responsibility for filling it, and whose file carries that name.

— Root: Referee