Umpire's Call Is Not a Wrong Decision — It Is DRS's Most Honest Measurement

That night in Mymensingh still sits with me. A district league final, the last over, a left-arm spinner, the batsman trapped on the pad, and the umpire keeping his finger down. I was not watching the television feed; I was frame-stepping a phone recording of the broadcast, fourteen stills, tracking the projected line of the ball against the leg stump. The ball was grazing it — but grazing by how much? That small gap is the whole argument, and its name is umpire's call. Fourteen frames can overturn a decade of habit, and that night I understood that the most contested words in cricket are not 'out' or 'not out' but these two.

DRS first appeared in a Test match in Colombo in July 2026, between India and Sri Lanka. It began as a tool for edges and lbws; today it covers front-foot no-balls, caught-behind, even obstruction. Under the ICC playing conditions, an lbw review runs through three checks: where the ball pitched, where it struck the pad, and whether it would have hit the stumps. The first two carry their own tolerance for the 'in line' determination, and on the third, if ball-tracking shows the ball hitting the stumps but the point of contact falls within half a ball's width of the edge, the on-field decision stands. That is umpire's call.

Here is the part that gets lost. Hawk-Eye and Virtual Eye admit their projections carry an error band. Bounce, spin, air movement across the ball's flight from pitch to stump produce a few centimetres of unavoidable uncertainty. If the projected path sits inside the measuring instrument's own margin, what should the law do? It says the man on the field keeps his call. That is an honest acknowledgement of a measurement limit. Umpire's call does not protect the umpire; it is a method for admitting the technology's own error. A rule is a hypothesis until the replay tests it.

Now the part nobody wants to say. Fans see umpire's call and conclude the technology has invented an excuse to shield the umpire. The batsman feels the same — the ball was hitting, yet I am not out. The real problem, though, is not umpire's call. It is the economics of the review. Losing a review is not merely losing an opportunity; it rewires a team's entire decision-making psychology. In the final over, a player will not risk a review on a doubtful catch, because an earlier one was burned on umpire's call. The more a review becomes precious, the more players review on emotion rather than information. That part is measurable, and that is where teams bleed.

My habit of keeping a review clock began at Russia 2026. On 16 June, in France against Australia, the penalty review for Antoine Griezmann ran three minutes and twenty-six seconds — the first VAR-awarded penalty in World Cup history. While the panel argued about justice, I counted the clock and wrote down the correct restart. Football's review delay and cricket's review delay are different stories, but the core question is identical: how long does a decision take, and who holds the game's momentum while it does?

In Bangladesh cricket, Shakib Al Hasan, Tamim Iqbal and Mushfiqur Rahim have all stood on both sides of that line. From years of watching matches on the ground and on screen, I have come to think our argument usually goes to the wrong address. We blame the technology, but nobody explains where its tolerance sits. Broadcasts show the projected line and never the uncertainty band around it. So viewers assume that if the line clips the stumps, the batsman should be out. But a line and a limit are two different things.

My claim is simple. The problem with umpire's call is not its existence; it is its presentation. If the technology knows its own error band, that band should be shown to the audience too. Had the graphics shaded the half-ball-width margin at the point of impact, half the controversy would never have been born. Transparency does not hide technological error; publishing the error is exactly what builds trust in technology. Where no limit is shown, every umpire's call reads to a fan as a conspiracy.

So should the review count change? Two reviews an innings, retained on success and lost on failure, leaves players short on information and long on risk. Automatic review of every decision, instead of a limited quota, would strip away the pressure of emotional choices. Cost and time are the real barriers. But if a one-minute no-ball check can stop a match for several minutes, how long does it take to shade an error band once?

The grey strip between the umpire's on-field call and the limit of ball-tracking is the most misunderstood space in cricket. Until broadcasts show that strip, the argument over umpire's call will not stop. The question is not about technology. It is about presentation, and the honesty of that presentation will decide how much faith the game finally keeps.