When the Ledger Comes Back Blank: Record Integrity in Cricket Rulings

Last week a review file landed on my desk. Every field was present; every fact was absent. Title: N/A. Source: N/A. Information points: blank. Under 'Entities Involved' it read 'identify from the information points above' — and there were no information points above. So I did what I do before writing about any ruling: looked for the date, then the format, then the source. None of the three existed. A document that cannot say whether the match was a Test, an ODI or a T20 has no standing to comment on umpiring, in the same way nobody should call a review a howler without quoting the over, the ball and the playing condition.

On the same morning, an old IPL 2026 mega-auction sheet was open on my desk: 600 players shortlisted, 204 sold, 10 teams, a ₹90 crore purse, four retentions. 12 and 13 February 2026, Bengaluru. Which means 396 names never entered any sheet at all. An auction ledger records who was sold; it does not record what being sold cost. The blank review file and those 396 names are symptoms of one illness: a record forms only where a clerk or a camera is stationed, and where neither is present somebody types 'N/A' as though N/A were a fact.

I opened the old DRS ledger to see which decision still survives its own rulebook two seasons later. In 2026, at nineteen, a knee injury had ended my under-19 career and I sat in Delhi University's library logging every review of the Champions Trophy across 15 matches. Eighteen reviews went in: 9 upheld, 6 overturned, 3 umpire's call. Each entry carried the over, the ball, the batter and the third umpire's name.

On 18 June 2026 at The Oval, Pakistan made 338 for 4, India were bowled out for 158, and the margin was 180 runs — Sarfaraz Ahmed's side beating Virat Kohli's. I wrote 900 words on it for a college magazine. That was the first report I filed with a review-ledger appendix: over, ball and the playing condition cited first, the verdict on the decision second. At the time I did not know it would become a habit.

My first VAR byline began with the roar and ended with the ruling. Through the 2026 World Cup group stage I logged 14 VAR reviews and set them against 11 DRS reviews from the 2026 Champions Trophy in a single table. FIFA's 'clear and obvious error' and the ICC's 'umpire's call' posed the same question from opposite ends: what the rule permits, and what the crowd feels. That piece got me a first byline on a Delhi digital desk at twenty, and the comparison table is still in my files.

Umpire's call is not a window through which umpires escape. It is a defined margin. When ball-tracking projects the ball's future path, the real question is how much of the ball is entering the stumps. If less than half a ball's width is hitting, the on-field call stands — on screen the graphic looks like a coin toss, but on paper it is a number. The day we began quoting the mood instead of the margin, the language of review broke.

What troubled me about the empty file was that it committed three separate errors at once. The first was format. The tactical logic of Test, ODI and T20 cricket does not transfer. In Tests a side's reviews are topped up after 80 overs, so burning one is a long-horizon investment; in a T20 the same review is a wager settled inside an over. When a document will not even state the format, no tactical conclusion is admissible, and anyone who supplies one is selling a guess.

The second error was the tag. The label on the file was only 'cricket_world' — no Test, no ODI, no T20, no league. That is the everyday habit of the beat: drop everything into the 'cricket world' pot so that nobody has to decide what the story is actually about. In my experience, when a report omits the format, one of two things is usually true. Either the source never knew, or the source chose not to say, because naming the format would weaken the claim.

The third error was credibility, and it is the expensive one. A broadcast feed is a witness, and every witness carries a chain of custody. The replays shown to the third umpire and the replay the director chose to air are separate documents. The frame the crowd shouts at is often not the frame the decision was made on. In the same way, the blank report held two distinct facts: the template that came back, and the material that never reached the model at all. The replay shows the angle; the ledger shows what it cost. Until a writer states which angle was shown and which was cut away, the piece is reviewing the package, not the ruling.

The same discipline applies to institutional decisions. A match referee's Level 1 sanction and a disciplinary committee or tribunal finding are different documents; the letterheads look alike, the appeal routes do not. That is why the first two lines of every disciplinary piece I file carry the body, the offence level and the appeal route. 'The authorities said' does not survive in my copy, because 'the authorities' is not a body. In 2026, through the IPL in empty stadiums, I built a 60-match audio log: 27 audible appeals, 14 on-field exchanges, 3 code-of-conduct charges, each clip cross-checked against the IPL Code of Conduct and match referee reports, including the Royal Challengers Bangalore versus Mumbai Indians match of 28 September 2026. Stump mic became evidence only once every clip carried a timestamp and a clause number.

Sloppy language is sloppy record-keeping. 'Sold' is not 'signed'. 'Retained' is not 'available'. 'Shortlisted' is not 'in the auction'. I read the IPL 2026 auction as a rulebook for exactly that reason — purse deductions, retention penalties, bid increments — and three franchises entered the final round with less than ₹5 crore. That figure appeared in no star-signing story, because it generated no excitement. A team standing close to the purse floor sets its strategy by arithmetic, not by bidding.

The most useful lesson from that blank file fits in one word: the gap between 'no information found' and 'no information captured'. In cricket the same gap separates umpire's call from a technical failure. If ball-tracking fails, the on-field decision stands, just as it does on umpire's call. The record, however, must state why it stood. An empty cell is not an acquittal; it is an unanswered question.

There is a trap here that I have fallen into more than once. A blank file arrives with a deadline behind it, and the easiest move is to raise a narrative on top of the vacancy. Those 1726 words could be written from nothing — a little 'cricket is changing', a little 'decisions under pressure' — and the reader would be satisfied. The piece would read cleanly and verify as hollow. A ruling is only as strong as the paper trail behind it. I stopped using 'robbed', 'howler' and 'shameless' the day I could cite both the playing condition and the timestamp. The copy got slower; the correction notices nearly stopped.

The opposite error costs just as much: a piece that is all clause and no human being. The ledger is the interesting part, but a ledger injures nobody. A decision does. So one human consequence belongs at the top of every piece, with the paperwork after it: the batter whose review burned, the bowler fined, the 396 names that never reached a sheet, the over-rate penalty that shifted a points table and that nobody logged. A ruling with no record simply disappears two seasons later, and with it the standing to question it.

Next time a headline says a decision was robbed, ask for three things: the over and ball, the playing condition, and the margin as a number. And if the sheet says N/A, ask a fourth question — whose job was that field, and why is it empty. I keep the notebook open after the whistle because appeals arrive late; and a record, if it is honest, answers a late appeal too.