Empty File, No Verdict: Where the Chain of Evidence Breaks in Cricket's Review Ledger

There is a file on my desk. Eight columns, and one sentence printed against each of them — insufficient information. Format: insufficient information. Match nature: insufficient information. Players: no name recorded. Teams: no identity. Venue: none. Weather and DLS: no signal. Time sensitivity: not assessed. Source quality: not assessed. The risk matrix carries six rows and all six say the same thing: cannot be evaluated, Stage-1 data required.

In twelve years on this beat I have counted such files. On a Delhi digital desk at two in the morning an incomplete file is not news — a press release lands half-formed, a scorecard line goes missing, a match referee's report arrives as a headline with no body. But a completely empty file is a different kind of document. It is not a record of a match. It is a record of the process that stopped that match from becoming a record.

In my trade the correct name for this is not an opinion but a finding: the chain of evidence has broken somewhere, and the place where it broke is itself the story.

Early in my career I made a rule that still sits on the first page of my notebook — no ruling is stronger than the paper trail behind it. An empty file is the cleanest test of that rule. A reporter sitting in front of it has two routes: write that nothing exists, or fill the blank with his own opinion. The second route is easier, faster, and by far the more used on this beat. It is not the route I take, which is the subject of this piece.

What it costs, and who pays

In any review system the first casualty is the player who drew the wrong call — but the real cost begins afterwards.

I remember an afternoon in a Ranji knockout. Final session of the fourth day, a batter reviews a leg-before appeal, ball-tracking shows the ball striking the leg stump by half a ball's width, the on-field call stands, and the review burns. Next over the same batter is lbw again and walks back with no review left. The scorecard records only 'lbw'. The match referee's report records nothing at all. The broadcast package keeps it as a three-second graphic.

That is the human consequence I place before the paperwork in every piece — the player who spent a review, the bowler fined for over rate, the table that shifted on a penalty point. If the reader does not see the consequence first, everything that follows — clauses, levels, appeal routes — reads as clerical exercise.

An empty file claims the same victim first. When the record stays incomplete, that afternoon's delivery, that half-a-ball margin and the whole session after it vanish without a mark. The next time someone reopens that review there will be no basis for comparison. Procedural continuity ends exactly where the document ends.

How a ruling is built: a chain of four documents

A review or a disciplinary decision passes through four separate documents in cricket. Naming them separately is half the analysis.

The first document is the playing condition — the ICC's conditions and the tournament's own regulations. It fixes the umpire's-call margin, decides which reviews survive and which burn, and settles the moment at which a run-out appeal becomes void.

The second is the official's on-field record — the umpire's decision, the sequence of signals, the instant the appeal was lodged. This is the part the camera never shows in full.

The third is technical testimony — the ball-tracking margin, the UltraEdge spike, the replay frame. I treat it as a witness, not a verdict. A witness gives a statement; the court decides — and in cricket the court is the third umpire or the match referee, not the graphic.

The fourth is the match referee's report and the sanction sheet. Nobody quotes this document and almost nobody writes about it, though it is the one that can move a points table.

My writing follows the same sequence: chronology, then exhibit, then verdict. I do not invert it on purpose, because inversion turns a report into an opinion.

Exhibit A: the 2026 spiral notebook

At nineteen, a knee injury ended my playing career, and that summer I sat in Delhi University's library during the Champions Trophy and logged every DRS review across fifteen matches in a spiral notebook — eighteen reviews in all. Nine upheld, six overturned, three umpire's call. Every row carried over, ball, batter, and the third umpire's name.

That notebook gave me the habit I still work by: before calling a decision wrong, write its over, its ball and its precedent. India lost the final to Pakistan by 180 runs at The Oval, and I wrote nine hundred words about that defeat with no byline and hardly a paragraph of cricket in it — just the ledger and its summary.

What the ledger taught me is that a ruling's age is set not by its day but by its document. A review that looked reasonable that evening can buckle two seasons later against the very same law, and the only way to find out is to reread that day's playing condition today. I do this repeatedly. Whenever an old argument returns to the headlines, I open the old ledger to see which decision had aged badly.

Exhibit B: the summer of 2026 and 'clear and obvious'

A year later the World Cup ran in Russia. I logged fourteen VAR reviews from the group stage the same way, then set them against the Champions Trophy exhibit.

One methodological note belongs here, because skipping it is how copy later gets caught out. The Champions Trophy ledger held eighteen reviews; the comparison table used eleven. Only those built like VAR reviews were selected — the ones carrying a third category beyond 'on-field call stands' and 'on-field call overturned'. Filtering for comparison is a method. Hiding the filter is a problem. I wrote the filter into the screenshot, and that table is still in my files.

VAR speaks of a 'clear and obvious error'. DRS speaks of 'umpire's call'. Both are saying the same thing — the reviewing official is confirming that the first decision was not wrong enough to be reversed by machine. The difference is the width of the protocol's doorway, and the entire argument lives on that width.

That piece earned me my first byline at twenty, on a Delhi digital sports desk. Afterwards I reversed the order in every controversial decision I wrote: first what the rule permits, then what the fan feels. And I stopped using the word robbery until I could cite a specific clause and a specific timestamp. The habit slows my copy. It also makes it unusually resistant to correction.

Exhibit C: 2026, empty stands and the stump mic

The 2026 IPL was played in the United Arab Emirates with empty stands. The crowd roar that normally buries every sound was absent, and that was the year I understood that the stump mic is the most honest referee on the field.

I built an audio log across sixty matches: twenty-seven clearly audible appeals, fourteen on-field exchanges, three code-of-conduct charges. Every clip had a timestamp, every charge a date. I then cross-checked each clip against the IPL Code of Conduct and the match referee reports, including the Royal Challengers Bangalore versus Mumbai Indians match of 28 September 2026.

The work produced one conclusion: broadcast audio is no longer entertainment, it is evidence. And evidence carries the same condition as any court document — its custody must be clean. Which mic produced the clip, in which over, cut at which frame, and whether any portion was removed: all of that matters as much as the clip itself.

After that piece, every disciplinary article of mine carried a source-trail box — clip time, clause number, report date. Filing got slower. Corrections fell. And I learned that audio can be read the way paper is read, provided you stop listening and start reading.

Exhibit D: the 2026 mega auction, read as a rulebook

Two years later I covered the IPL mega auction not as auction news but as a rulebook story. Six hundred shortlisted players, two hundred and four sold, ten teams, a purse of ninety crore rupees, four retentions per franchise.

I built a table of purse deductions, retention penalties and bid increments, then filed a two-thousand-word explainer that barely mentioned star signings. The real question was how three teams reached the final round with under five crore, and where their purse arithmetic slipped.

The ledger taught me verbal hygiene, my strictest habit today. 'Sold' and 'signed' are not the same thing. 'Retained' and 'available' are not the same thing. And if a bid breaches the purse floor, that is the biggest line in the story, not the name of the star. I was given the auction beat because my copy never confuses these, and never confuses a milestone with a unit of analysis.

The same method applies to transfer stories. No transfer story is complete until it can survive one referee — a tale built from an agent's noise, sourced murmurs and the mood around the camp will not pass that test. Player agents are football's most expensive hidden cost, and noise is their weapon. Only a receipt answers noise.

'Umpire's call' is a margin, not a controversy

A correction of language comes before a correction of argument, because words get fixed first.

On screen, umpire's call appears when the projected path of the ball and the wicket zone overlap in such a way that the decisive portion of the ball stays inside the on-field decision's envelope. It is a defined margin, not an exemption. Calling it a loophole is like calling the offside line a trick.

My rule: state the margin numerically, quote the playing condition that sets it, and only then judge. The number is the argument. Remove the number and what remains is atmosphere, and atmosphere does not stand up in a hearing.

The broadcast feed: a witness, not a publicist

One thing hides in every big controversy — what the third umpire was shown and what the director chose to air are two different feeds.

On the third umpire's monitor, frame selection, camera angle and replay speed are set by protocol. What reaches the public has passed through an edit, which may well omit the angle that decided the ruling. So whenever I write about a disputed decision, I state plainly which feed I am describing.

Technology is a witness in cricket, and every witness has a chain of custody. The ball-tracking margin, the UltraEdge spike, the replay frame: all three are statements, and statements can be framed. Suspicion of a clean-looking graphic is a basic condition of this trade, because the cleaner the graphic, the fewer the questions asked — and that is the largest risk of all.

The invisible officials

Indian cricket has an entire layer that issues paperwork and is never quoted. Match referees. Third umpires. Pitch and ground committees. Tribunals and disciplinary panels.

I treat their documents as primary sources. I read the BCCI's record of procedural consistency the way others read a captain's press conference. A Level 1 sanction, a pitch rating, an over-rate penalty: these are documents in the same sense a scorecard is, and their effect is no smaller.

Here is the distinction I am strictest about: a match referee's sanction and a tribunal's finding are not the same instrument. They arrive in the same week, on similar letterheads, phrased alike — which is exactly why collapsing them is the easiest error available. My first two sentences always carry the name of the body, the offence level and the appeal route. The word 'authorities' never stands in for a specific panel in my copy.

The contrarian angle: the habit of filling the blank

This is where the piece returns to where it began.

Facing that empty file, a reporter has two routes. He can write that there is no material, so no conclusion follows. Or he can see eight blank columns and fill them.

The second route always wins, because the media ecosystem prices empty space at zero. It wants headlines, opinions, controversy. And when there is no source, the easiest source becomes the atmosphere — the mood around the camp, sources say, it seems that, it may be that. That is where reporting and storytelling stop being distinguishable.

I have no hesitation in saying this habit has done the most damage on this beat. Dressing-room colour, a player's anger, unrest inside a squad — none of it can be entered into evidence. Putting atmosphere where a statement belongs, and opinion where evidence belongs, are two forms of the same offence.

An empty file is not a failure. An empty file is a finding. It tells you the chain behind that article has broken somewhere, and until it is repaired, every word written over it belongs to the writer, not to the game.

The more dangerous version is when this style enters technical cricket reporting. Where ball-tracking shows a half-ball margin, writing 'the umpire's stubbornness'. Where a Level 1 code-of-conduct charge is on record, reaching for 'conspiracy'. Where a referee's report carries one line of fine, writing 'temperatures rising'. That may be fine for clicks. Not for the record.

On this beat, the record is the final appeal.

Protocol and outcome: writing the two separately

The largest linguistic failure in modern cricket coverage is that protocol and outcome are placed in the same sentence.

'Umpire's call took the team out of the match' merges two things: the consequence of a process and the consequence of a match. Whether the process was sound is one question. Why the match turned is another. Joining them makes copy feel fast and prove false.

So in every disciplinary piece I break the order deliberately — first what the rule permits, then what the fan feels. It slows the writing and makes it dispute-resistant. It is why I refuse words like robbery until I hold a clause number and a clip time.

The trap hidden inside the data

There is one more layer to this ledger that rarely gets written about — the disorder inside the data itself.

Every statistic exists in the cricket-analysis market, and every statistic carries its own frame. An average quoted without its margin, a spike quoted without its sample, a strike rate quoted without its situation: in disciplinary analysis these are as trustworthy as testimony without a timestamp.

The problem is not the data. The problem is the habit of turning data into a verdict. Ball-tracking gives a statement; the law weighs it; the official applies it. Three separate steps. A report in which the three collapse into one stops describing decisions and starts making them.

Ahead: a source-trail standard

Throughout this piece I have repeated one line — a ruling is only as strong as the paper trail behind it. Here is the proposal I close with.

Cricket coverage should make the source-trail box a standard, the way a methods section is standard in a scientific journal. Four lines with every disputed decision: the playing condition applied, the feed shown to the third umpire, the package that went to air, and the body that issued the sanction sheet.

If that four-line frame becomes standard, two things change. First, words like howler and robbery disappear on their own, because it is difficult to shout a number you are required to write down. Second, when a file arrives empty, it does not get published — it gets returned, with a note saying where the chain broke.

Technology is getting faster, expectations are rising, and the demand is for one thing: a clean answer. A clean graphic often takes away the habit of asking a clean question. Which old review will buckle two seasons from now against its own rulebook — that question should be written today, so that in two years there is a ledger to answer it from.

— Root: Referee