Not Out, Umpire's Call: The Ledger of Cricket's Review System Nobody Bothers to Keep

The ball struck the pad, the on-field umpire shook his head. The batter reviewed. Ball tracking arrived on the big screen, the delivery was clipping leg stump — umpire's call, the field decision survived, and the batting side had burned a review. Two overs later, the same batter edged into the slips off the inside half of the bat, the finger went up, and that side had no challenge left. After the match, everyone talked about luck, about pressure on the fielding unit, about the umpire's nerve. The decisive event had happened somewhere else entirely: inside the margin of a tracking model that nobody names and no broadcaster puts on screen.

I have watched this game for forty-five years, but my notepad changed shape when I was fifty-two. I no longer write the match; I write the ledger of its decisions. When I launched The Referee's Ledger in 2026, I coded all 380 Premier League matches of 2026-17, logging 1,142 yellow cards and 34 red cards, and understood something simple: an official's judgement does not shift overnight, it shifts as a trend, and a trend can be written in numbers. The 2026 database turned discipline from a whispered verdict into a public pattern. I have tried to do the same thing in cricket, because cricket's decision system is the most documented on earth and the least audited.

The history matters, otherwise today's argument has no weight. DRS began in July 2026 with the India-Sri Lanka Test in Colombo. Early use was optional and varied by board. Then it became mandatory across formats, but the real change came in October 2026, when the ICC ruled that a side retains its review if the outcome is umpire's call. That single line rewrote strategy, because before it, umpire's call meant certain loss. In June 2026 the ICC scrapped the soft signal, so on-field umpires no longer had to commit before the television umpire. From the 2026 IPL, TV umpires began announcing review outcomes and reasons over the stadium public address system, and the ICC carried that habit into its own events. In 2026, ODI sides were given two reviews per innings instead of one. Three structural changes in eight years, and yet after every tournament we file the same sentence: umpiring controversy again.

In my own ledger I keep four separate columns game by game. Who reviews and in which over. What share of reviews return as umpire's call. How many seconds the television umpire takes to reach a decision. And how far a team's fast bowlers drift outside off stump in the ten overs after losing a review. Four columns, four separate identities.

The first column is the most uncomfortable. A review is almost never a tactical decision, because the person making it is the batter or captain who is himself inside the emotion. In my count, a heavy share of powerplay reviews concern lbw, where the tracking margin does the loudest talking, because the ball swings early and the batter is not sure of his own pad position. The biggest decisions arrive in the death overs, when the review has already gone. It is a story of bad investment, with the least capital available exactly when it is needed most.

The second column is where the real analysis lives. Umpire's call is not a verdict; it is a margin of forgiveness. Ball tracking projects a path and allows a band of possible error, and if that band overlaps the stumps, the decision goes back to the field. The wider the band, the more reviews are wasted. My ledger keeps wicket-to-wicket line and tracking margin as separate fields, because with spin the forgiveness band behaves differently — when a ball turns two ways off one pitch, low clipping is close to inevitable. Umpire's call is not a correct decision; it is an arithmetic grey zone that we have sanctified in the name of logic. The danger is that the zone stays unexplained to players, and an unexplained rule manufactures argument.

The third column is the least discussed and the most publishable. How long a television umpire takes is a measurable index. When VAR landed in 2026 at the World Cup, referees were taking well over a minute, and the tension in the ground grew in step with the wait. Empty stadiums in 2026 did not remove pressure; they moved it into the protocol. Writing my twelve-point checklist that year, I understood that speed and accuracy cannot be delivered together — only traded against each other. Cricket's review length is still searching for the answer to that impossible equation.

The fourth column measures what actually changes on the field. Once a side knows it cannot challenge, its quicker bowlers start drifting away from the stumps and pushing the ball further outside off. The reason is psychological: a bowler with a challenge in hand is brave, a bowler without one looks for safety. The power of a review system lies not only in decisions but in the courage it grants, and that is the least measured thing of all. Discipline is not a mood. It is a structure with timestamps, and cricket still is not writing it down.

Here is my first disagreement. The accepted sentence is that technology is reducing umpiring error. My ledger says the opposite: technology has not removed error, it has relocated it. Error used to sit in an umpire's eye. Now it sits in the model's choice of band, in the definition of the margin, in the camera's frame rate. There is one difference. We can accuse a field umpire, reject him, score him. In front of a tracking model we are helpless. The centre of this is agency. Umpire's call now protects no human being; it protects the system whose index never enters the conversation.

My second disagreement concerns the review culture itself. Cricket's review is not a logic machine, it is a pleading machine, and pleading has become a medium — much like the transfer market, which has its own red cards, and most of them are never shown on television. One contract, one fee, one clause buried in small print, and behind it a model nobody votes on.

One caveat must be stated plainly. I will not transplant this structure into football without limits. VAR arrived in 2026 and referees learned to announce quickly, but football is continuous play while cricket is discrete — ball onto stump, pitch, pad, each event separately adjudicable. Review accounting does not transfer directly between the two. A footballing audience presses back from the other direction, and a cricket writer should say so out loud before drawing the comparison.

After years of watching, I have learned that one human detail teaches more than the sanctity of the system. At Eden Gardens, a ground that holds more than 132,000, the crowd did not stay silent; it roared at the replay on the big screen and then fell quiet. The television umpire took a second longer than expected. In that second, the whole stadium understood that a partial decision, born of its own emotion, had just invoked reason.

Three proposals for what comes next. First, publish an officials' index after every major tournament — decision consistency, review time, the frequency of low clipping. Second, make the tracking model's confidence explain itself in plain language on the screen, so spectators know why three of four reviews died on the model's own uncertainty. Third, measure the officials' workload, or we will keep scoring individuals and never the environment around them.

The real question sits elsewhere. Why do we demand a perfect decision while refusing to ask how it was reached? No technology owes us an explanation, and no authority is obliged to publish one. If cricket keeps rejecting disclosure, accuracy will buy it nothing.