The Weight of N/A: The Error of Ruling on an Empty Cricket File

Eleven-forty at night on a Kolkata digital desk. The template on my screen ended every single field in three characters — N/A. No match, no venue, no format, no date, no number. In twenty-nine years of this trade it was not the first such night; it is the habit I have fought longest.

The colleague in the next chair had already filled his page, headline included: "No irregularities found in the inquiry." I asked him which inquiry, which match, which date, under which condition. The answer was silence, and that silence was not proof of an outcome. It was proof of an empty cell.

Oval, June 2026, taught me the same lesson on a single delivery. I pulled twelve frames that night and placed each one against Law 21. That is when I understood that a judgement arrives last, and only when there is paper underneath it. Writing a clean sentence over an empty file is the easiest work in this business, and the most expensive.

Context: three documents and one question

No decision in cricket survives without three documents. First, the ball-by-ball log or scorecard: which over, which ball, what score, which batter. Second, the rulebook that actually governs that fixture. Third, the broadcast frame at native rate — not slowed, not trimmed.

I want to stop at the second document, because that is where most of the damage is done. The MCC's Laws of Cricket and a tournament's playing conditions are two different instruments. Law 21 (No ball) and Law 36 (Leg before wicket) read identically in a Ranji match and in a World Cup. But the Player Review — DRS — does not exist in the MCC Laws at all. It lives in the playing conditions, which means the ICC or the host board decides what is reviewable, in what order, and whether a team keeps its review on umpire's call.

So when someone says "by the rule he was out," the first question has to be: which rulebook? Asking it is not pedantry; it is the first task of the job. A referee does not invent the rule; he remembers where it was written.

The third document, the frame, deceives most often, because a frame can be coaxed. The still that gets captioned "clear" is frequently a slice lifted from a thirty-frame-per-second file in which you can see the ball's shadow, not the ball. I went back to the tape; the tape had not gone back to me. What the frames showed was evidence; what the frames did not show had to stay unsaid.

Core: four files, one habit

June 18, 2026, The Oval, Champions Trophy final. Fakhar Zaman was on three. Jasprit Bumrah drew the edge, MS Dhoni took it, the ground gave him out. Then the replay arrived and Bumrah's front foot was over the popping crease. No ball. That same Fakhar made 114 off 106, Pakistan posted 338 for 4, India were bowled out for 158, and the match went by 180 runs.

I filed a twelve-frame teardown of that delivery, checking every frame against Law 21. The statute is plain: the bowler's front foot may not land beyond the popping crease, some part of it must remain behind the line. In the frames the foot was over. The no ball was correct. The case here was against the process, not the umpire — at 140 kilometres an hour the eye has to travel from a landing foot to a released ball inside the same instant, and the faster that travel, the wider the margin for error. The night I stopped writing "the umpire got it wrong" was the night I began writing what the law permits him to see.

But the real lesson of that night sits in the arithmetic. One delivery did not lose that final. A 180-run margin is not the story of a single no ball; it is the account of ten wickets and one innings. The narrative that drew the most readers that night rested on the thinnest piece of evidence in the file. That was my first ledger lesson: the thing a headline is built on need not be the thing the evidence is built on.

From September 19 to November 10, 2026, all sixty IPL matches were played in the UAE in empty stands, and that July the ICC had suspended the neutral-umpire requirement for the pandemic — home umpires stood in the Southampton Test between England and West Indies. I kept a spreadsheet through every match: every review, every soft signal, every front-foot check. Across sixty games I logged 118 reviews, 34 per cent overturned, and 41 lbw reviews that ended in umpire's call.

Read 34 per cent on its own and the instinct is that umpiring was poor. That is the wrong use of a ledger. A review is not a random sample of decisions; it is a sample of the decisions captains were willing to bet on. A captain reviews when he is more than half certain, and when more than a third of the more-than-half-certain bets are overturned, the question is about captain calibration before it is about umpiring eyesight.

And the largest bucket carries no headline at all. Forty-one of 118 reviews ended with the system saying the evidence was not conclusive, so the on-field call stands. In more than a third of the sample the answer was neither right nor wrong but unknown. The most honest line in a ledger is the one where the answer is incomplete, and it is also the line most often missing from the newspaper.

March 2026, Newlands, Cape Town. Cameron Bancroft with sandpaper in his hand, and the fallout split cleanly into two jurisdictions. ICC match referee Ranjan Madugalle fined Bancroft 75 per cent of his match fee and issued three demerit points. Cricket Australia then banned Steven Smith and David Warner for twelve months and Bancroft for nine.

Nobody on that desk wanted the comparison, because the comparison landed plainly: the body holding the employment contract punished harder. Two rulebooks sat on the table, and neither one blinked. For me the interesting fact was not the size of the sanction but the scope of the power. The ICC Code of Conduct governs conduct on the field of play; Cricket Australia's Code of Behaviour governs the employment relationship. One incident, two instruments, two different questions. The same architecture keeps returning — the BCCI's NOC regime, the bar on contracted men in overseas leagues, workload clauses. Two books get placed on the table every time, and every time somebody has to say who can enforce. The book with the heavier penalty is not automatically the stronger law; the book with the contract enforces.

The DRS protocol deserves the same reading. Umpire's call is not a pardon. When ball tracking projects the ball hitting the stumps but the projected contact is too small to call conclusive, the playing conditions say the on-field decision stands. The system announces its own insufficiency. There is a second consequence that gets less ink: in limited-overs cricket a team retains its review on umpire's call, while in Tests it does not. That single line rewrites captaincy — in the short formats a cheap review becomes a real resource, and it usually gets spent on the least certain delivery of the innings.

The timing half of it I log separately. A review has no dramatic turn; it has a wait. Three hundred screens, sixty thousand people, a celebration stopped mid-air — and when the verdict lands, what remains is procedure rather than joy. Two minutes of waiting is enough to cool a goal celebration. My objection is not to the review but to its running without a clock. Put a timer on the big screen and a hard window on the third umpire, and the argument shifts from whether the call was right to how long the process took — and that argument can actually be won.

Contrarian: silence is evidence, of what

Now the part that empty file reminded me of. "No irregularities found," "the mood in the camp is fine," "we are looking at it week to week" — all three are sentences about something that was never said. Silence establishes exactly one thing: no statement was issued, no fixture was scheduled, no press conference was called. It does not establish that nothing happened. The quiet grounds taught me that silence is also evidence — but every piece of evidence needs a subject, and swap the subject and the evidence starts lying.

That is why I read comeback timelines more cautiously than most. "Week to week" often describes the state of a conversation rather than the state of an injury. On the day a rehab photo-shoot appears, the schedule moves earlier. This is not a failure of journalism so much as the shape of the information chain: the person speaking is the person with an interest in the statement.

The second trap grows out of my own method — placing two rulebooks on the same table as though they carried the same weight. Quoting a BCCI clause beside a smaller board's clause, at identical volume, is easy and looks fair. Two rulebooks on a table are rarely two equal rulebooks. After any comparison, one line is compulsory: who holds the power to enforce. If that line cannot be written, the comparison should be deleted.

Takeaway: before the file opens

My rule on that desk is now plain. Before a file opens, five things get asked for: format, venue, date, the governing rulebook, and one figure with its source attached. If any of the five is missing, the page stays empty — and an empty page is also information, provided it is labelled empty rather than filled with a conclusion.

The forward question is whether we can give the review the same publicity we give the scorecard. If every league published, at the end of each season, the number of reviews, their outcomes and the umpire's-call count, the annual argument about umpiring standards would move off mood and onto margin. Consistency is not a mood; it is a ledger kept in public. Mine is in its eleventh year, and the next argument will still open with it — not the headline, the margin.