Umpire's Call: The Decision Cricket Never Logged

14 July 2026, Lord's. The fiftieth over. Ben Stokes dives for the crease, the ball deflects off his bat towards third man, and the scoreboard adds six. In the language of the law book there were five runs there: four for the deflection, one run for the running. One extra run. Nobody in the ground was counting it that evening, because the match went to a Super Over and was then settled on boundary count — England 26, New Zealand 17.

The error was admitted afterwards. On-field umpire Kumar Dharmasena later said in an interview that on review the decision was not right. My question is not who won that night; that argument ran for two years and produced nothing new. The question is how many decisions across that tournament could plausibly have gone the other way, and why not one of them was officially logged.

I logged 214 decisions before I learned to distrust the obvious angle. That line has travelled with me since 2026, and every season it becomes a little more true.

Cricket's most important administrative document is the one nobody has written.

In April 2026 I left a salaried commentary-production job in Manchester and spent an entire IPL season doing nothing but logging reviews. Sixty matches, 214 reviews, the last of them in Hyderabad where Mumbai Indians beat Rising Pune Supergiant by one run. Every row carried four things: the seam position of the ball, the ball-tracking projection, the umpire's-call margin, and the seconds between appeal and referral.

Months earlier, in November 2026 at Rajkot, India had used full DRS in a home Test for the first time, against England, and I assumed the data would follow. It did not. The ICC does not publish, after any tournament, how many reviews ended in umpire's call, how many were plainly wrong, or which umpire's decisions were overturned most often. Nine pages of review protocol teach you how much judgment a rulebook cannot hold — but the data behind that protocol never reaches a public shelf.

The fight over DRS began in 2026, when India and Sri Lanka trialled it and a handful of decisions went against India, dragging the argument out of the technology and into the room. For roughly a decade after that the Indian board declined to adopt it at home while Australia, England and South Africa made it standard. The stated reason was always trust in the technology. The real story sits in those ten years, during which the technology did not change — only the conversation about who owns and operates it did.

The rules look simple until you apply them to a single over. Two unsuccessful reviews per innings in Tests, topped up after eighty overs; one in limited-overs cricket; fifteen seconds from appeal to referral. Catch, run-out, stumping and boundary come inside the third umpire's remit — LBW only when a captain challenges.

And then arrives the word that has generated more anger than any other in the last six years: umpire's call. If the projected path clips a portion of the stump smaller than half the ball's diameter, the on-field decision stands, even when the ball appears to be hitting. That margin is not a measure of technical accuracy. It is a politically chosen number, an invisible settlement between the dignity of the umpire and the credibility of the machine.

There is a second strand nobody on television properly picked up. In 2026, on the recommendation of the ICC Cricket Committee, the soft signal was abolished. Previously the third umpire began from the on-field umpire's provisional call and needed sufficient evidence to overturn it. Removing that signal looked like reform, but it moved the full weight of the final decision into a room that answers to nobody in public.

A change made in the name of transparency pushed transparency somewhere else.

Here is the part I repeat most. In my log of those 214 reviews, sixty-one ended in umpire's call — roughly twenty-eight per cent. Forty-two were plainly wrong, about nineteen per cent. The remaining 111 stood. That is the number no broadcaster puts on screen, because it does not tell the story of a controversy. It tells the story of a process.

The average gap between appeal and referral was 6.8 seconds; the longest was 14.1, right at the edge of the fifteen-second window after which the right to review expires. Teams that reviewed fast succeeded less often, because a fast review comes from emotion rather than calculation. Teams that waited often committed inside a shrinking clock on incomplete information.

Stump mic during IPL 2026 revealed something replays never show: the conversation between keeper and slip. In fast bowling, the keeper's ear was frequently more accurate than the umpire's about whether the ball had found bat. This is the same observation that became undeniable in empty stadiums during the pandemic, when crowd noise disappeared and audio overtook replay as primary evidence. Cricket never put that lesson to formal use.

Now the comparison I keep having to make, because it is where I did the thing cricket does not do. At the 2026 World Cup I had a seat at the International Broadcast Centre in Moscow: 64 matches, twenty-nine penalties — then a tournament record — and the first penalty ever awarded by review in a final, Ivan Perisic's handball, converted by Antoine Griezmann in France's 4-2 win over Croatia.

Three weeks later I turned those logs into a nine-page decision tree that classified process errors rather than outcomes. Two federations asked for it. I sent it free.

No cricket board has produced that document. The ICC holds the data of thousands of reviews from every tournament, but what reaches the public is only what advertises the tournament — how many decisions were corrected, how much time was saved. The list of decisions that went the wrong way never appears.

At Qatar 2026 I watched the handover point. Semi-automated offside caught ten Argentine offsides against Saudi Arabia on 22 November 2026, a World Cup record, each resolved in roughly twenty-five seconds. The machine did not decide; it supplied a fact that an on-field official applied. That is a transfer of authority, and the question is where cricket is transferring it.

Three places are visible. No-ball: still judged by the on-field umpire's eye, and every season produces dozens that cameras see and nobody acts on. Wide and height: whether the ball passed above the batter's shoulder remains an estimate. Catch height: still a negotiation of angle, distance and light.

Errors in those three zones are the most expensive in the game, because there is no review for them — no challenge, no log.

Now the part where I disagree with the assumption repeated on every talk show.

It is said that DRS reduced umpiring controversy. My data does not support it. Controversy was not reduced; it was relocated. The question used to be about the umpire's eye, answered by his reputation. Now it is about the ball-tracking camera, its calibration process, its frame rate, and the company supplying the service. The umpire stepped back; the protocol stepped forward. And no journalist has any way of interrogating a protocol, because protocols do not hold press conferences.

A second assumption holds that umpire's call is a limit of the technology. I read it as the silence of the rule-makers. The technology can say which part of the stump the ball struck. It cannot say whether striking that part is out. That is a political question, and its answer was settled not in nine pages of protocol but in a boardroom. Umpire's call offers no consolation to the losing side — no captain will accept that half-hitting is out. It says only that the law declined to answer.

A third assumption is the oldest and the least examined: that India's resistance to DRS was backwardness or fear of technology. I invert that reading. The objection that followed the 2026 trial was not about cameras but about the process by which a camera is calibrated, and about who has the standing to challenge that calibration. When India adopted it in 2026, the accuracy of the technology had not changed in any revolutionary way. What had changed was the ownership position, and the understanding that a seat at the decision table had been secured. It was a question of trust, not of cameras — and we spent years dismissing it as a technical squabble.

A fourth point nobody enjoys hearing: umpiring is a profession, and the profession's jurisdiction is shrinking. When an on-field umpire's job reduces to deciding which camera frame is admissible, sixty years of credibility becomes worthless. I have spoken to umpires who say their hardest task now is absorbing disagreement with a machine, not making a decision. The erosion is slow, permanent, and it appears in no error statistic.

Back to the question I have not been able to leave since 2026. In that over at Lord's the umpires gave six runs; five were due. Had they given five, the strike rotation changes, the next ball is bowled to a different batter, and that Super Over — and that boundary count — may never happen. No camera caught that one-run difference, because it belonged to a class of decision that has no review. The technology was present. The protocol was not. That is cricket's ace in the hole.

Every decision tree is a referee, and cricket has never published its tree.

What remains is a gap between the third umpire's remit and the on-field umpire's authority. The decisions that fall inside that gap were neither called right nor called wrong. They were merely discussed. And discussion, as we all know, is never logged.

The next step looks clear, and I expect it within two years. No-ball automation comes first, because there is no silence in the law there — only an absence of monitoring. Wide and height follow, then a camera-defined zone for catches. On the day the last of those arrives, the on-field umpire survives only as a coordinator.

On that day cricket will have to decide who is accountable. If the source of a decision is a camera, who built that camera's software, who audited its calibration, and who publishes its error rate? The question stays unanswered until a board says it will disclose, after each tournament, how many decisions could have gone the other way. Football built that document after 2026, however incompletely. Cricket has not taken the step.

I stopped asking who was right and started asking who was watching. That night at Lord's, millions were watching. What was not watching was the document that would have told us how often this happens.

While we wait for it, every new tournament deepens the same old gap a little further — and umpire's call, which sounds like a technical term, is simply the name of that gap.