Umpire's Call: Is DRS's Most Controversial Clause Finally Heading for Repeal?

Chinnaswamy Stadium, Bangalore. 7:42 pm. The fourteenth over. A left-hander goes for the sweep, the ball strikes the pad, and the umpire shakes his head. The big screen fills with the ball-tracking projection: the ball is hitting leg stump — but only just. The blue line clips the inside edge of the stump and slides past. On screen: “Original decision: Not Out.” The review fails. The batter stays at the crease. Three thousand voices in the stands cut off mid-roar. Two balls later, an almost identical delivery. The ball again finds the edge of leg stump. This time the umpire raises his finger. Review. On screen, nearly the same image, the same projection, the same “Umpire's Call” — but the decision stands: Out. Same delivery. Two outcomes. The only variable is the on-field umpire's first call. That single clause is cricket's most discussed, least understood, and probably least popular law. I am writing about it today because eight years of review logs have shown me a pattern — and the pattern is not about the technology. It is about the protocol. The Decision Review System was first used in international cricket in 2026, in the Test series between Sri Lanka and India. After long debate, the ICC Cricket Committee gave the technology formal standing, and since then ball-tracking, Eagle Eye and UltraEdge have become inseparable from the decision-making process. But DRS was never a decision machine; it is a decision process, with technology at one end and human judgment at the other. The process runs in three layers. Where did the ball pitch — outside off, inside leg, or in line? Where did it strike the batter — in line or outside? And finally, would it have hit the stumps, and by how much? The first two layers are binary. The third is where the technology concedes its own limits. Ball-tracking is a prediction, a probability. It can say “the ball would have hit the stumps.” It cannot say “the batter is certainly out.” That gap is filled by Umpire's Call. The rule runs like this: if ball-tracking shows the ball hitting the stumps, but the contact is so marginal — less than half the ball — that it falls inside the technology's own margin of error, the third umpire has no “conclusive evidence,” and the on-field decision stands. A delivery clipping the edge of leg stump will be out if the umpire gave it out, and not out if the umpire gave it not out. In Tests, each side gets two reviews per innings, refreshed after 80 overs; in ODIs and T20Is, two per innings. A successful review is not returned — it is spent. That arithmetic has turned reviews into a tactical decision, not merely a matter of fairness. The burden sits on captains — from Virat Kohli to Rohit Sharma, from Joe Root to Steve Smith, each balances this account every series. The nature of Umpire's Call differs by format. In Tests the ball seams more and batters defend, so pads are struck more often — and that is why reviews dying on Umpire's Call are more common in Tests. In T20s, batters sweep and flick, the ball often pitches in line, so “out” calls are more certain. One law, different outcomes across formats. Nobody measures that difference, yet it shows how context-dependent the clause is. India's role here is notable. In the early years of DRS, the BCCI was sceptical of the technology for a long time — its argument being that the technology was not perfect, and therefore should not be able to overturn a human decision. India later adopted it, and today the commercial intensity of Indian cricket has accelerated its spread. In England, cricket is governed through tradition and the county structure, slowly and conservatively. In India, it is governed by the IPL's broadcast market, sponsorship deals and viewership numbers. Here, DRS is not only a tool of fairness but an element of entertainment — every review is several minutes of drama, graphics and slow-motion replays. Those who want Umpire's Call abolished make a simple argument: if the technology says the ball is hitting the stumps, it should be out, and what the on-field umpire thought is irrelevant. Those who defend it say the technology has a tolerance, and if we ignore that tolerance we will end up valuing ball-tracking's estimate above human judgment. I have been inside that argument many times — not only in front of a screen, but at scorers' tables, reading match-referee reports. For eight years I have kept a review log for every major tournament: how many reviews in a match, how many succeeded, how many died on Umpire's Call. The review log became a ledger of every moment the game held its breath. One pattern returns again and again — the number of reviews lost to Umpire's Call is never lower than the number of successful ones, and often higher. Picture it: the same delivery, same pitch, same pace. Two umpires make two decisions. The technology shows the same thing both times — the ball hitting the stumps, but at the edge. Result: one batter out, one not out, from the same ball, on the same day. In cricket's rulebook, this “same input, different output” is rare. Umpire's Call is exactly that rare place. My first objection, then, is not to the technology. It is to the protocol. The problem is not Hawk-Eye or Virtual Eye; the problem is that we are translating a probabilistic model into a binary decision, when the model itself carries uncertainty. We ask the technology a question it cannot answer with certainty, and then we treat its answer like a court's verdict. The second angle is who the protocol serves — the broadcast or the fairness of the game. The dramatic animation on screen looks to a spectator like a single truth. But the technologists know that the ball's position is estimated frame by frame; camera resolution, frame rate, the seam, spin and air all combine into an estimation model. The ball-tracking companies themselves do not claim that model is flawless. The spectator sees the technology, not the law. They see the ball hitting, and so Umpire's Call reads to them as “the technology told the truth and the law lied.” I once read a match-referee report in which a single Test innings produced eight reviews, five of them ending on Umpire's Call. That is, in cases where teams were certain the ball was hitting the stumps, they lost their review in more than half of them — simply because the on-field umpire's first call differed. The report's language was blunt: “no conclusive evidence to overturn.” Yet on the screen the spectator had watched the ball hit the stumps. That gap is what builds distrust. To the player, the matter is more tangled still. When a batter takes a review, he is trusting the technology. When he sees on screen that the ball hit the stumps but the review fails, the system feels to him not merely flawed but unjust. I have heard a batter ask — the screen says I am out, so what did the umpire see? The answer exists in the law, but nobody explains the law on the field. That absence of explanation is the greatest damage. Football has the same problem under a different name. Semi-automated offside carries a tolerance too — so fine that the eye cannot see it. But there the tolerance is stated in numbers, so the argument stays at the margin, not at the principle. If cricket published its ball-tracking margin openly — in centimetres, in percentages — the distrust would fall sharply. Now to the counter-argument almost everyone avoids. Many assume that removing Umpire's Call would fix the problem. My logs suggest the opposite. The margin of error lives inside the technology; changing the rule does not erase the uncertainty, it only moves the blame from the umpire's shoulders to the technology's. A marginal delivery would then be given out even though it sat inside the model's own uncertainty — we would be imposing a probability as certain truth. The decision would be more transparent, not more correct. The real problem is not technology; it is the binary. Cricket wants decisions in yes/no, while ball-tracking delivers probability. Umpire's Call is born from the collision of those two languages. The solution, then, is not simply to scrap the clause. It is to make the protocol admit probability in its own language — as is done with “marginal” calls elsewhere, where the word is stated openly. The second counter-point: emotion against the law. The roar of the crowd, the batter's stricken face, the silence of the dressing room — these do not override the logic of the law, but they erode trust in it. The biggest lesson of my eight-year log is that cricket's argument is not really about technology; it is about the transparency of the decision process. Where the ICC does not make clear how wide the margin is, why, and who sets it, every Umpire's Call breeds a small rebellion. There is a precedent. In 2026 the ICC abolished the “soft signal,” which had privileged the on-field umpire's initial call on low catches. That decision showed the ICC will accept structural reform — when the evidence accumulates. Exactly that accumulation is now under way on Umpire's Call. The ICC Cricket Committee reviews the clause regularly, and recent meetings have discussed its future. My sense is that within two years we will see either a reform — the margin stated more clearly and universally — or an experimental tournament with Umpire's Call removed entirely. I am filing this prediction. If I am wrong, I will log it, and the next article will be the accounting for that error. I once wrote 3,400 words because one handball deserved a full autopsy. This clause deserves no less, because it returns every match, every innings, many times over. In the end, every cricket law rests on a belief — that the more transparent the decision, the more trustworthy the game. Rules are not walls. They are load-bearing beams, and I test every joint. — Root: Referee