Umpire's Call: Where Ball-Tracking Technology Is Stopped by Law

A familiar scene. Ball-tracking throws a projected path onto the screen, showing the ball grazing the leg stump, the degree of contact perhaps a third of the stump. The on-field umpire has given it out. The third umpire stares at the monitor for a few seconds and upholds the call — out. One section of the crowd slumps in frustration, another applauds. By the next morning social media erupts: DRS is broken, the technology protects the big teams, and the most repeated question of all — if the technology exists, why does the umpire's call matter at all? I have watched this scene for years. On cricket's DRS screen, and before that on football's VAR monitor. In 2026, during the Chile versus Cameroon match, Milorad Mažić's four-minute VAR review pushed me down this road. That day I forgot the result, spent 72 hours building a 4,200-word timeline against IFAB's 2026 VAR protocol. The habit survives — the moment a flashpoint appears, I first ask: which clause, which playing condition, which technology protocol applies here? The argument about umpire's call is not really about technology; it is about law. Those who ask why, when the technology knows the right answer, we return to the umpire, skip a fundamental point. Ball-tracking is not an absolute truth. It is a projection, a mathematical estimate with its own margin of error. What DRS gives us is a structure for decisions, not perfect truth. DRS was born in 2026, with the trial use of the player review system in the India–Sri Lanka Test series. Since then three separate technologies operate inside it. The first is ball-tracking — Hawk-Eye or Virtual Eye — tracing the ball's path to answer LBW's three questions: pitching, impact, wicket. The second is edge detection — Snickometer or UltraEdge — whether the ball touched the bat's edge. The third is visual mapping, a record of where exactly the ball struck. Under Law 36, three conditions must be met together for LBW. The ball must pitch in line with the stumps or on the off side. It must strike the pad in line with the stumps or on the off side, if the batter is playing a shot. And the ball must be going on to hit the stumps. On the DRS screen these three steps are checked in sequence. The first two are usually clean — true or false. The complexity begins at the third step, the wicket. That is where umpire's call enters. If ball-tracking shows the ball will hit the stumps, but the amount of contact is less than half the stump's width, the on-field umpire's decision stands final. Given out, it stays out; given not out, it stays not out. The technology only confirms the decision was not impossible; it is not certain enough to overturn it. That half-stump threshold is the centre of the debate. This system is not static. In 2026 the ICC abolished the soft signal. Previously, if a catch was in doubt, the on-field umpire gave a soft signal, and video evidence generally could not overturn it. After the change, the third umpire decides independently. The reform itself proves the process is being continuously refined. The number of reviews is also rule-bound. Two per innings in Tests, a different tally in limited-overs. A successful review is retained; a failed one is spent. So before deciding, a team must calculate risk. That calculation turns DRS from pure technology into strategy — when to review depends on a team's patience and capital. Now let us walk the decision tree step by step. A review really answers one question: is there a clear and proven error in the on-field decision? If yes, it is overturned; if not, it stands. At the pitching step, if the ball pitched on the leg side, the review fails immediately. Whether the batter played a shot is irrelevant here — leg-side pitching is itself a barrier. The impact step is subtler. If the ball was outside the line of the stumps when it struck the pad, and the batter is playing a shot, the review fails — even if the ball would later have gone on to hit. But if the batter is not playing a shot, the calculation changes, because then off-side impact can also be out. This fine condition is unknown to many viewers, yet it sits at the root of every controversy. The complexity rises at the wicket step. Where ball-tracking says the ball will go is a probability distribution. Pace, spin, bounce, friction — the algorithm estimates from all of it. That estimate has a defined margin of error. The ICC playing conditions acknowledge that uncertainty and draw a half-stump line. Inside that line the decision rests not with the technology but with the umpire. Here a statistical logic operates. Watching the game over years, I have come to think of umpire's call as a buffer that covers the technology's shortfall in confidence. If ball-tracking were fully accurate, umpire's call would never be needed. But a projection is never fully accurate, so the law creates a safe zone. The logic is comparable to football's VAR. In the 2026 World Cup final between France and Croatia, Néstor Pitana awarded a penalty after a VAR review for Ivan Perišić's handball. That day I forgot the celebration, re-watched all 64 matches and logged 29 VAR reviews and 20 changed decisions. The same principle holds — VAR hunts clear and proven errors, and does not intervene in grey zones of doubt. At the 2026 Qatar World Cup, semi-automated offside changed that philosophy. The technology cut offside checks to about 25 seconds, because the decision became a mathematical calculation of a line, not a human eye's guess. Cricket has not yet reached that point, because cricket's decisions are three-dimensional, and the ball's future path is a probability, not a line. In 2026, when COVID-19 halted football, I watched the Bundesliga's May 16 restart and built a spreadsheet — 500 referee decisions from the 2026-20 season, each coded under Law 12 and Law 3. That practice taught me that consistency of process matters more than outcome. Cricket's umpire's call is part of exactly that consistency. The problem is not technology; it is communication. The ball-tracking is shown on screen, but why this decision was reached is not explained to the crowd. A spectator sees the ball hitting the stump yet the batter given not out. To them it looks like technological failure. In the language of law, it is the process succeeding. In Bangladesh's side, experienced cricketers like Shakib Al Hasan and Mushfiqur Rahim keep exactly this calculation in mind when taking a review — check pitching and impact first, then wicket. Experience is decisive here, because a wrong review means spending capital. This strategic layer rarely enters the discussion. Now to the most common proposal — abolish umpire's call. The logic is simple: let the technology give the right answer, remove the threshold. But this is a mistaken idea. Abolishing umpire's call does not increase accuracy; it merely transfers ownership of the error. The uncertainty of projection remains; remove the threshold and that uncertainty slips directly into the outcome, with no safe buffer. Viewers want certainty; the law offers process. Anger is born in the gap between them. After VAR arrived in football, I heard that VAR reduced controversy. The truth is VAR moved controversy from the pitch into the review room and the grey zones of the rulebook. Cricket's DRS has done the same — decisions are faster, but satisfaction has not grown. Umpire's call protects the umpire, yet simultaneously creates ambiguity. Because a review's outcome depends on what the on-field umpire originally said. Same ball, same tracking, but two different initial calls from two umpires produce two different results. That sense of inequality erodes trust. When technology enters, a new duty arises — to admit technology's limits too. Where ball-tracking estimates, drawing a threshold is the intelligent move. A technology that claims to know no limits does not reduce controversy; it increases it. Umpire's call is a rare example of that admission. The future will likely move on two fronts. On one side, technology will become more accurate, the error margin will narrow, and the weight of umpire's call will fall. On the other, communication of decisions will become more transparent — on-screen explanation, step-by-step display, a stated reason at every turn. Cricket can learn from football's semi-automated offside: alongside speed, it must deliver explanation. Regulators may now take another path — publicly declaring the limits of the technology. If viewers know ball-tracking's margin of error, the half-stump threshold will seem reasonable to them. Where opacity exists, anger exists. Transparency thus becomes more urgent than the technology itself. My sense is that over the next decade DRS will grow more automated, but the umpire's role will not vanish. Because cricket's decision is not only mathematics; it is the game's atmosphere, pressure and context. The law therefore seeks a bridge between human judgement and technological calculation, and umpire's call is one brick of that bridge. The question will no longer be whether umpire's call stays or goes. It will be how, at this junction of law and technology, the viewer's trust can be restored. DRS has made decisions faster, but understanding is still pending. The next controversy, then, will not be about rules but about explanation.