The Fifty Percent of Umpire's Call: The Question DRS Never Answers

Three frames were rotating in slow motion on the big screen. The ball had pitched outside leg, straightened into line, and the thin green line of ball-tracking stopped dead in the middle of the stump — but across 49 percent of it. The third umpire said into the headset, "Umpire's call." The on-field decision stood, the review stayed with the fielding side, and the match hung in the narrow gap between 49 and 51. What the crowd did not understand that night was not the limit of the technology. It was the design of the law. The television graphic shows a perfect truth, yet the final decision does not come from that pixel; it comes from an estimate. I did not spend that night with the scorecard. I spent it with the appendices of the ICC Playing Conditions. Across my twenty-six years of watching the game, one thing keeps returning: the clear and obvious error is usually not in the pixel; it is in the premise. I trace a call backward until I find the assumption wearing a badge. DRS was first used in July 2026, in the Test between Sri Lanka and India at the SSC in Colombo. Its stated purpose then was the correction of clear errors, not a re-trial of the game. Eighteen years later the technology has changed a great deal — ball-tracking is sharper, UltraEdge and Hawk-Eye have been added, camera frame rates have climbed — but the central question has not moved: who makes the final call, and against which standard. Players, coaches and broadcasters all want the same thing, consistency. But consistency cannot be measured unless we first agree on what we are measuring. The ICC protocol states that to overturn an on-field decision on LBW, ball-tracking must show the ball hitting more than half the stump. At exactly half, or less, the decision becomes "umpire's call" — that is, the on-field umpire's. Here sits a small but enormous detail: on an umpire's call the review is not lost, it is returned. If the batsman is out, the reviewing side is happy; if not out, the bowling side is. Either way, the fifty-percent line punishes nobody directly. In June 2026 the ICC abolished the "soft signal." Before that, when a catch was in doubt, the on-field umpire's initial gesture carried the weight of evidence, and the third umpire needed a "clear" reason to overturn it. It was a strange arrangement in which the guess weighed more than the truth. The abolition of the soft signal shows that officiating culture is slowly conceding that doubt and decision are not the same thing. By the same logic, since 2026 the ICC has brought in in-match penalties for slow over rates — a fielder pushed out of the ring. A rule is not only a punishment; a rule is the protection of a match's rhythm. Now to the real work. What does ball-tracking actually measure? The cameras calculate pace, spin and pitch point from the first few metres after release, then project the rest of the journey from pitch to stumps mathematically. In other words, the last few inches are not seen by any camera — a model draws them. The model is remarkably accurate; there is no doubt about that. But it is still an estimate, with its own margin of error, and that margin is never shown to the viewer. We see only the green line on the screen, never the confidence level behind it. And here is the fault line in the premise. The law asks, "Was the umpire's decision clearly wrong?" The technology answers, "The ball would have hit 49 percent of the stump." The two questions are spoken in different languages. The first is the language of probability; the second, of geometry. Between what the model measures and what the law wants to know lies a gap in translation, and we call that gap "umpire's call." The law never said technology would deliver the truth. The law said that where doubt exists, the on-field decision stands. Strangely, this system is working as intended — if you look at it through the eyes of the law. Umpire's call is therefore not a bug; it is the consequence of the law's design. The problem is that the viewer mistakes the technology for a judge, when here the technology is only a witness. A witness never writes the verdict. When we say "the ball was hitting the stumps, yet he was not out," we are in fact blaming the design of the law, not the technology — and the law is our decision, while the technology is not. Compare it with football's VAR. There too, the phrase "clear and obvious" was meant to do the same job — to keep the on-field referee final on borderline calls. But in practice VAR has repeatedly crossed that line, because once a perfect image is shown, granting human leeway becomes politically difficult. Cricket's umpire's call is more honest than VAR, because it admits its own limit in numbers. At the 2026 World Cup I logged 29 VAR reviews; the lesson was one — referees protect referees, the law does not. In 2026 I worked on empty stadiums — a thousand matches from the Bundesliga's Project Restart and the Premier League. In that era of empty stands, which began with Borussia Dortmund's 4-0 win over Schalke 04, the home team's penalty rate fell from 0.28 to 0.19, and referee card counts dropped 12 percent. The lesson is plain: an official is not a camera, he is part of the system — crowd, pressure and environment change his decisions. In cricket, that same human sits inside umpire's call. So the "human element" is not a sacred constant here; it is a variable — and a variable should never be treated as a constant. The bigger problem lies in the retention rule. Because an umpire's call returns the review, teams acquire a clear incentive — to review on guesswork, since the cost of failure is low. Review numbers rise, the rhythm of the match breaks, and television gets its drama. This, in my view, is DRS's greatest weakness, not ball-tracking. By the same logic I argue that huge signing-on fees for free agents are more opaque than transfer fees — because where the rules leave a gap, opportunists step in, and that is a problem of structure, not of the game. And the error in the premise is not confined to LBW. In the 2026 World Cup final, the ball deflected off Ben Stokes's bat and ran to the boundary off Martin Guptill's throw; under one clause of the law, six runs were awarded, and that decision turned the match. Technology was not to blame there — the assumption behind the clause was, an assumption that never imagined this situation. A rule is a hypothesis; sports culture is the memory that resists the test. Now the popular solution: scrap umpire's call, and if the ball hits the stumps, it is out. The argument is flawless emotionally, weak analytically. Remove umpire's call and you take away one known bias — the umpire's estimate — and seat in its place an unknown bias: the ball-tracking model's own extrapolation error, whose limits the viewer never sees. We would then use the word "clear" to cover a mathematical uncertainty, and pass it off as truth. That is a move from one kind of deception to another, where the new system claims more authority than the old while being less honest. Yet on one point I agree with the critics: the retention rule is unjust and should change. I will change my position if it can be shown that the ball-tracking model can publish its own uncertainty margin in numbers, and that this margin is genuinely smaller than the fifty-percent line. Until then, the real reform is not deleting the technology — it is publishing the technology's limits. If cricket avoids the mistake VAR made, it will survive. Looking forward, I would say the next big change will come through publishing the margin — showing on screen how confident the ball-tracking is. Not by removing the umpire, but by showing the arithmetic of his uncertainty. I have frozen the fifty-percent line and looked at it, and I have seen that fairness has a rhythm nobody measures — how the first over and the last over of a match are judged by the same standard. The question, then, is simple: do we want the truth, or the picture of the truth?