The Umpire's Call Debate in DRS

The Decision Review System, introduced experimentally in 2008 and as an ICC standard in 2009, was designed to give players the ability to challenge clear umpiring errors using ball-tracking, snickometer and Hot Spot technology. The system has substantially reduced the number of glaring errors in modern Test cricket, but one element of its design — the 'Umpire's Call' provision applied to LBW reviews — has become one of the most persistently controversial features of the modern game. The Umpire's Call provision operates as follows: when an LBW dismissal is reviewed, ball-tracking technology projects the ball's predicted path. If the ball is projected to clip the stumps but more than half of the ball is still outside the stumps at impact, or if the ball would clip but not substantially hit the stumps, the on-field umpire's original decision stands. In effect, marginal calls — where the ball is genuinely close to hitting the stumps but the technology cannot confidently say it would have done — default to the umpire's original judgement. The provision was introduced because the developers and the ICC's cricket committee recognised that ball-tracking technology, while extraordinarily accurate, has known margins of error and the system's predictions in marginal cases are not infallible.

The Umpire's Call provision generated relatively little controversy in the early years of DRS, partly because the technology itself was new and partly because not all member boards used DRS in all formats. The BCCI's prolonged refusal to adopt DRS in bilateral series — discussed in a separate article — meant that the most prominent national team in world cricket was for many years not subject to the system at all. The picture changed substantially from 2017 onwards, when the BCCI relented and DRS became standard across virtually all international cricket. As the system became universal, the Umpire's Call provision became the focus of mounting criticism from players, captains and commentators — particularly when high-profile reviews in marquee fixtures, including Ashes Tests, India-Australia series and World Cup matches, saw apparently plumb LBWs upheld as 'not out' on the basis that the on-field umpire had originally said not out and the ball was only marginally clipping the stumps. The ICC Cricket Committee, chaired through much of this period by Anil Kumble, defended the provision repeatedly on the grounds that the technology's margins of error required a fall-back to the umpire's judgement.

Under DRS rules, when a batsman or bowling team reviews an LBW decision, if ball-tracking shows fewer than 50% of the ball hitting the stumps, the original on-field decision stands as 'Umpire's Call.' This means an identical delivery can be given out or not out depending on the on-field umpire's original decision, creating an inherent inconsistency that has frustrated players, coaches, and fans alike.

Critics argue that Umpire's Call defeats the purpose of having technology — if the ball is shown hitting the stumps, it should be out regardless of the on-field call. They point to matches where crucial wickets have been denied or given based on this margin, leading to unjust outcomes. Defenders of the system argue that ball-tracking has a margin of error, and Umpire's Call provides a necessary buffer that respects the on-field umpire's judgment and prevents over-reliance on technology.

The ICC introduced changes in 2023 to make the system clearer, but the fundamental tension remains. Former cricketers including Ricky Ponting, Virat Kohli, and Tim Paine have publicly criticized the rule. The debate reflects a broader philosophical question in cricket: how much authority should be given to technology versus human judgment? The ICC has periodically reviewed the system but has maintained Umpire's Call, arguing that eliminating it would significantly increase the number of overturned decisions and undermine umpire authority.

“My personal opinion is that if the ball is hitting the stumps, it is hitting the stumps. They should take away the umpire's call, if I'm being perfectly honest.”

“I have a strong opinion on this. The on-field umpire's decision should not come into the picture once technology has shown the ball is hitting the stumps. Out is out.”

“The principle underpinning DRS was to correct clear errors in the game whilst ensuring the role of the umpire as the decision-maker on the field of play was preserved. Umpire's call allows that to happen.”

“You need the umpire's call. It's not there to back up the umpire; it's to give the margin of error for the technology. The ball-tracking is not infallible.”

“It's confusing for the spectator. We tell the audience that the ball is hitting the stumps, then we tell them it's not out. That's not a good experience for the people watching.”

The Umpire's Call debate has produced a series of substantive ICC reviews without producing any fundamental change to the underlying provision. The 2016 revision tightened the margins — increasing the proportion of the ball that must be shown to be hitting the stumps for a 'not out' decision to be overturned — but retained the basic principle that on-field decisions stand in marginal cases. Subsequent ICC Cricket Committee reviews in 2018, 2021 and 2023 considered and rejected proposals to scrap the provision. The principal technical defence offered by the Cricket Committee has been that ball-tracking technology, while highly accurate, has a published margin of error of approximately 2.6mm in the predicted impact location. In marginal cases — where the ball is projected to clip the stumps by less than that margin — the system genuinely cannot confidently say whether the ball would have hit the stumps or not, and the fall-back to the umpire's original judgement is the most defensible response. Critics, including Sachin Tendulkar, Ben Stokes, Nasser Hussain (in some columns) and a substantial proportion of broadcasting commentators, have argued in response that the provision creates an inconsistent and confusing experience for spectators and that the ball-tracking margin of error is sufficiently small that the binary out/not out call should simply be made on the predicted path.