Umpire's Call: The Monitor Does Not Lie; the Angle Does

In February, at the Wankhede Stadium, the second innings of a Test match, the 87th over. The spinner released the ball, the batsman pressed forward onto his pad, and the ball skidded into the inside of the leg. The on-field umpire did not raise his finger — not out. The fielding side took a review. On the giant screen, ball-tracking appeared: a portion of the ball would have struck the leg stump, but less than half of it. The third umpire said, 'Umpire's call — the on-field decision stands.' Sixty thousand spectators roared as one. The captain waved his arms, arguing, 'The ball was hitting the stumps!' But the answer was simple: yes, it was; but the law says that is not enough. That single scene — one decision, one screen, one frustrated captain — brings me to today's discussion. Because cricket's review system, the Decision Review System (DRS), is no longer merely a technology; it is a language, a protocol, and a politics. And at the centre of that politics sit two words: 'Umpire's call.' DRS was first used in 2026, in a Test series between India and Sri Lanka. India opposed it at first, publicly questioning the accuracy of ball-tracking. After the 2026 World Cup, India gradually accepted it, and today a major match without DRS is hard to imagine. The system works across several layers: ball-tracking (Hawk-Eye, Virtual Eye), edge detection (UltraEdge, Snickometer), and live audio. Each team gets a fixed number of reviews per innings — two in Tests, retained if successful; usually one or two in limited-overs cricket. But the most contentious part is 'Umpire's call' — a zone where the technology says the ball would have hit the stumps, but not with certainty. The definition of this zone has changed over time. Initially the rule was that the centre of the ball had to strike the stumps. In 2026 that rule changed — since then, if half the ball strikes the stumps it is given out; anything less is 'Umpire's call.' And here lies a subtle point that I first learned sitting at Stockley Park in 2026. In 2026, at 53, I joined the Premier League's VAR pilot project as one of four London-based analysts. I audited 38 matches, logging 12 overturns, 47 checked incidents, and 3 missed calls that later became training clips. I designed a seven-point review checklist — angle, offence, point of contact, speed, offside line, restart, communication — which cut average review time from 84 seconds to 52. From that experience I understood something that applies exactly to cricket's DRS: technology does not state truth; technology states a probability, and the law decides how much of that probability is acceptable. How does ball-tracking work? Cameras capture the ball over several frames as it travels toward the wicket, then a predictive model calculates where it would have landed. That model is not perfect — pitch, seam, spin, wind all introduce a certain amount of uncertainty. Hawk-Eye's margin of error can range from a few millimetres to centimetres. So when the ball grazes the very edge of the stump, the technology itself is not certain. 'Umpire's call' is the acknowledgment of that uncertainty. Now consider: if a ball lands two centimetres inside the stump, and the tracking error is two centimetres, how can the technology say it is out? It cannot. It says, 'It might be.' And the law says 'might be' is not enough — the on-field umpire's decision is final. Here my first signature line comes to mind: the monitor does not lie; the angle does. Sitting in the review room, I saw many times how the same incident tells two different stories from two different camera angles. Cricket is the same — a front-on camera and a side-on camera show the same ball's path differently. And here is the biggest similarity between VAR and DRS. In VAR our core principle was 'clear and obvious error.' That is, we did not overturn a decision unless the error was clear. Cricket's Umpire's call stands on exactly the same logic: if the evidence is not clear, the on-field decision survives. At the 2026 Russia World Cup I reviewed all 64 matches, logging 29 penalties, 22 VAR reviews, and 3 overturned penalties. In the France-Croatia final, I built a decision tree for the 38th-minute handball by Perisic and that 3.5-minute review. Each step was a question: did the ball hit the hand? Was the hand in a natural position? Was the hand moving toward goal? Every 'yes' moved the decision toward a change. Cricket's DRS has a similar decision tree, but a less transparent one. In an LBW review the questions are: did the ball pitch in line? Was impact in line? Would the ball have hit the stumps? The first two are usually clear; the third is the uncertain one. And that uncertainty is 'Umpire's call.' My 2026 experience adds another layer. During the pandemic I joined the Premier League's behind-closed-doors task force, analysing 92 empty-stadium matches. I found that without crowd noise, referees' whistle-to-signal delay rose by 0.8 seconds. I built an audio-cue protocol, standardising phrases like 'check complete' and 'on-field decision stands.' The league credited it with reducing communication errors by 18 percent. Empty stadiums made the audio protocol louder than any crowd. In cricket, DRS's problem is not only ball-tracking but communication. What the third umpire sees on the screen, the spectator does not see in full. The screen often shows only the final outcome — 'Umpire's call' — but not the uncertainty margin of the ball's path. So the spectator thinks the technology saw the ball in exactly the right place, yet the decision did not change. That information gap is the real fuel of the controversy. At Euro 2026 and the Tokyo Olympics I analysed 51 Euro matches and 32 Olympic matches. I examined the Denmark-England semi-final penalty review — a 2.1-minute check. There I saw that even when the decision is correct, a longer delay increases spectator frustration. In cricket's DRS time is also a factor; but cricket is faster, because the decision is relatively mechanical. An LBW review usually finishes within a minute, a catch review even faster. Now I come to the part where I want to stand against the crowd. The popular complaint is: 'Umpire's call is a conspiracy to protect umpires.' I do not accept that. But I also do not accept that the system is perfect. The real problem is not the technology, but the threshold. If a ball hits 49 percent of the stump, it is not out; at 51 percent it is out. Yet physically there is no difference between those two balls. We have divided a continuous event into two with an artificial line. That line is necessary — because the uncertainty of technology must be absorbed — but it is never 'justice'; it is a compromise. Here I recall a lesson from VAR. Had we stayed stuck to the 'clear and obvious' rule alone, many correct decisions would have remained wrong. So at times we had to soften the threshold. Cricket faces the same question: should the Umpire's call margin be reduced? Or increased? My answer: before arguing about the margin, bring transparency. If the screen showed — 'the ball is 3.5 centimetres inside the stump, but our error margin is plus or minus 2 centimetres, so it is uncertain' — the spectator would not rage; they would understand. Anger comes from uncertainty, not from the decision. Another matter: emotion versus law. On the last day of a Test, with the last wicket, an Umpire's call — emotion peaks in that moment. But the law does not know emotion. In my refereeing life I learned that a player's emotion cannot be the basis of a law, but a player's emotion shapes public opinion for or against a law. In the 2026 World Cup final, the decision to award six runs after the ball ran to the boundary off Ben Stokes' bat was also a moment of rule application, where emotion and law seemed to collide. DRS's Umpire's call carries the same conflict. The famous Ian Bell incident of 2026 is also worth remembering — when two sides understood the explanation of a review in two different ways. From that, cricket learned that a protocol must not only be correct, it must be communicated. Even today that lesson is incomplete. So what is the future? I have three proposals. First, in every major tournament, the error margin of ball-tracking should be published — not just the final decision. Second, a permanent, universal standard for the Umpire's call threshold should be established, identical across all formats. Third, the communication protocol should be standardised — as in VAR's 'check complete.' At 62 I now understand that technology does not take the umpire's place; technology makes the umpire more accountable. The question is not whether the monitor tells the truth — the question is whether we are willing to admit the monitor's limits. And if we do not show that limit, in the next ten years we will see the same scene again: sixty thousand spectators roaring, and a screen staying silent.