Umpire's Call: How DRS's Half-Ball Clause Writes the Result of a Match

The entry in my ledger for 25 August 2026 is still marked in red ink. Headingley, third Ashes Test, fourth innings, late afternoon. Nathan Lyon bowling, Ben Stokes pinned on the pad, umpire Joel Wilson saying not out. Australia reviewed. The ball-tracking graphic floated onto the screen — the ball would have struck leg stump, but its centre fell outside the outer edge of the stump. Review failed, on-field decision upheld, Stokes unbeaten, England won by one wicket and kept the series alive. That single graphic exposed an uncomfortable truth to millions of viewers: in cricket, "correct" and "proven" are not the same thing. Sitting between them is a clause called Umpire's Call. DRS first appeared on a field in July 2026, at the Sinhalese Sports Club Ground in Colombo, in a Test between India and Sri Lanka. It began as an experiment, with a limited number of player reviews and visible discomfort among umpires after each one. Between 2026 and 2026 the ICC turned it into a permanent framework. Today, teams get two unsuccessful reviews per innings in ODIs and T20Is, and two per innings in Tests, topped back up to two after 80 overs. The LBW review protocol runs in three stages: where the ball pitched, where impact occurred, and whether the ball would have hit the stumps. The first two stages are almost binary — pitching outside leg or impact outside the line ends the review immediately. The third stage is the real battlefield, because there ball tracking makes a prediction, and that prediction carries its own margin of error. That margin has been written into the law as half a ball. An international cricket ball measures 22.4 to 22.9 centimetres in circumference, which puts its diameter at roughly 7.1 centimetres. If the centre of the ball sits inside the outer edge of the stump, tracking says "out"; if it sits outside, tracking says "Umpire's Call". In practical terms, that leaves a grey zone of about three and a half centimetres on either side. Three and a half centimetres — half the width of a cricket ball. That half-ball has decided a World Cup, and it has decided an Ashes. I opened my 2026 DRS ledger again, and the same clause was staring back at me. That was when I understood the problem was never the accuracy of ball tracking. The problem is the arrangement that decides who carries that grey zone. One thing needs clearing up first: Umpire's Call is not an "error". It is an acknowledged limit written into the protocol. But the spectator in the stand cannot see that limit. They see a ball travelling towards the stumps, then the words Umpire's Call on the screen. Their brain says: the ball was hitting, so why is it not out? That is where most conspiracy theories and most abuse are born. The second layer is the economics of review retention. Under the ICC playing conditions, if the outcome of a review is Umpire's Call — meaning the on-field decision stands — the review is still returned to the team. That makes a speculative LBW review effectively free for the side taking it; the only real cost is time. And time is cricket's scarcest resource, especially in the era of over-rate enforcement. Because it is free, reviews have multiplied. When a spinner bowls into the leg-stump line and a batter is pinned on the pad, the captain now reaches for the review almost reflexively. There is nothing to lose. Of the reviews I logged during the 2026 ODI World Cup, a significant share were cases where the distance between impact and the stumps already suggested the verdict would land in the grey zone. The review was not being taken in hope of evidence. It was being taken in hope of a lottery. There is another layer almost nobody remembers — the distance of the impact zone. Under the protocol, when a batter has advanced a long way down the pitch from the stumps, the predictive element of ball tracking is not given full weight, and the on-field decision takes precedence. In practice, that means the batter brave enough to come forward is the one who enlarges the grey zone for himself. Aggressive batting and defensive adjudication are knotted together inside the same clause. The third layer is asymmetry. Same clause, same half-ball, but the price is not the same for both sides. A team with a dedicated ball-tracking analysis unit knows which umpire leaves how much grey zone on which line. A team without one guesses. That information gap never appears on a scoreboard, but it ends up written into the result of a series. This is where my diaspora rulebook comes in. Domestic cricket in Bangladesh — the National Cricket League, the Dhaka Premier League, the Bangladesh Cricket League — went without full DRS for a long time. Some matches had limited cameras, some had none at all. County Championship cricket in England, by contrast, has had ball tracking and Snicko as routine for years. So the same player, under the same law, grows up learning two different risk calculations. Experienced cricketers like Shakib Al Hasan or Mushfiqur Rahim came through a domestic system with limited technology, yet DRS has accompanied almost every major decision of their international careers. Nobody measures that gap. The fourth layer is time. A review means a stopped game, a slow-motion replay on the big screen, a wait. I have kept a habit of logging durations since 2026, first in a VAR protocol ledger for football, later in cricket. Review durations in cricket have crept upward because the number of decision layers has grown — pitching, impact, wickets, no-ball checks, catch validity, boundary contact. Stack those layers and a single review can run past two minutes. In Tests that is tolerable. In T20 it is poison. Last winter I sat in Mirpur and watched exactly this. Under the floodlights the tracking graphic rotated on the big screen, and in the next row someone was shouting in Hindi, someone else in Bengali. When the words Umpire's Call appeared, the ground made one sound — irritation, laughter and complaint mixed together. Some of them did not know the written law. But they knew that what their eyes had seen and what the screen had ruled were not the same thing. That gap is cricket's biggest communications failure. And that is where the real tactical trap sits. Teams no longer treat the review only as a tool for changing decisions; they treat it as a tool for stopping play. Breaking a bowler's rhythm, disrupting a batter's concentration, buying time for a new batter — all of it has moved inside the review. Umpire's Call does not close off that abuse. It makes it easier, because the punishment for a failed review is, in many cases, nothing at all. The conventional reading is that Umpire's Call protects the umpire's authority and keeps the game human. It is a graceful sentence, but it does not survive the arithmetic. Umpire's Call actually protects the reputation of the technology, not the umpire. If the system had to deliver a final verdict on every three-and-a-half-centimetre case, the blame for its errors would land directly on the ball-tracking provider. Arguments would erupt over camera frame rates, the position of the seam, the friction of the pitch. The grey zone called Umpire's Call lifts that liability off the tracking company and places it on the shoulders of the teams. The team loses the review, the team loses the decision, and the technology stays infallible — because the technology is never declared wrong, only marked uncertain. The real casualty of this arrangement is transparency. The viewer never learns whether the review was 52 per cent or 48 per cent. They hear one word. Yet almost every decision in cricket is now measured in numbers — strike rate, expected runs, spin revolutions. So why is the ball-tracking percentage never shown on screen? Where the referee's eye sees uncertainty, the spectator sees only a verdict. That distance is deliberate. The second counter-intuitive point is that we argue far less than we should about the unequal distribution of technology in domestic cricket. We write for two weeks about a one-second decision in an international match, while nobody ever convenes an inquiry into a National Cricket League match lost to the absence of technology. That inequality, off the field, is the bigger clause — Root: Referee. The 2026 T20 World Cup will be played in India and Sri Lanka, and the Champions Trophy experience is already in the ICC's hands. The question is no longer whether DRS survives. The question is how wide the grey zone will be, and who will carry it. The next entry in my ledger is still blank. It will record which match, which over, which clause. Only one thing I know for certain: as long as those three and a half centimetres are not explained in front of the spectator's eyes, the abuse around Umpire's Call will continue — and the benefit of that abuse will go precisely to those whose liability is never written down on paper.