DRS and the 'Umpire's Call' Debate: The Monitor Does Not Lie, But Who Draws the Boundary?

Over recent seasons of Asian cricket, the most debated DRS decisions have stopped at the same point. On the screen, ball-tracking shows three red dots angling into the stumps, the corner flashing 'Hitting', and yet the on-field umpire does not raise a finger. The reason is 'Umpire's Call'. A viewer who has stayed up all night wonders — the technology says out, so why is it not out? The question is simple; the answer is not. And that is exactly where the real centre of Asian cricket's DRS debate hides. The argument is not about the accuracy of the technology, but about how much authority we grant it. From my long years of watching matches, I can say every DRS controversy really asks two questions — where did the ball go, and whose hands should hold that answer. And within this very confusion lies the future of Asian cricket's decision-making culture. DRS began in July 2026, with the India-Sri Lanka Test in Colombo. Since then, three pillars have stood in Asian grounds — ball-tracking, UltraEdge, and the umpire's call rule. Under the ICC playing conditions, every review is examined in three stages. First, where the ball pitched — outside leg or off stump, or in line. Second, the point of contact with the batter, or impact — was it in line with the stumps. Third, whether the ball would have hit the stumps. If any of these three stages is 'inconclusive' or 'borderline', the decision stays with the on-field umpire. Asian reality adds another layer — the BCCI resisted DRS for years, and full acceptance came only around 2026-17. DRS arrived later in one-day cricket, and in a still narrower scope in T20. Review counts and rules also shift by format, another source of confusion for viewers. So in Asian cricket, DRS is not merely technology; it is also the politics and trust of several boards. Technically, DRS rests on the combination of three systems — Hawk-Eye's ball-tracking, UltraEdge's sound-based edge detection, and the third umpire's judgement. Each system has its own limits. UltraEdge can catch the sound of a bat edge or pad friction, but wind or crowd noise can create confusion. Ball-tracking measures speed and angle accurately, but its dependence on the future path is a matter of estimate. So DRS is never a single technology — it is a composite decision built from several partial truths. The key to understanding that ball-tracking can be wrong lies in its mathematical structure. The cameras genuinely observe the ball up to two points — after pitching and after contact with the bat. After that, the system estimates, or predicts, the rest of the journey to the stumps. In other words, a large part of the red line that meets the stumps on screen is not real observation but mathematical estimate. That estimate has a margin of error. The ICC has built that margin directly into the umpire's call rule. If the system shows the ball hitting less than half the width of the stump, it is 'Umpire's Call' — the on-field decision stands. On leg-side pitching, the rule grows more complex — the ball pitching there is not automatically not out, but the umpire's call margin widens. On Asia's spin-friendly wickets, where the ball bounces lower and turns, ball-tracking's prediction comes under the greatest pressure. For a spin delivery that kicks twice, estimating the future path is harder for the tracking system than for a fast ball. The review accounting has also changed the pace of the game. Under ICC rules, each innings carries two unsuccessful reviews; a successful one is retained. So a bad review costs a team not just one decision but some of its future confidence. In Asian matches I have repeatedly seen captains hoard the last review and lose a big opportunity in the middle overs. Yet the statistics say reviews that fall to umpire's call are far more numerous for impact and wickets than for leg side. That is, the reviews most often wasted are also the most uncertain ones. On Asia's spin-dominated conditions, where the ball is slower, review time is tighter, and every second makes the captain's decision harder. Here a subtle inconsistency appears. In football's VAR, the logic was 'clear and obvious error' — the referee's decision is overturned only for a clear mistake. Cricket's umpire's call carries exactly the same philosophy. Technology will not replace the umpire; it will only correct the big mistake. But cricket's inconsistency is that we view the same technology in two different ways. For catches or boundaries, we accept UltraEdge or Snicko almost as infallible proof. Yet with ball-tracking we admit it can be wrong. Two different statuses for the same technology in the same match — that is the root of the viewer's confusion. There is another layer — frame rate and calibration. The more frames a high-speed camera records, the smoother the ball's path appears. But camera count, angles and light differ from ground to ground. At some Asian venues, variations in tracking-system calibration have been observed, which can produce different results for identical deliveries. The monitor does not lie, but the angle and the calibration can — I wrote that repeatedly during my own VAR days. My seven-point checklist — angle, offence, point of contact, speed, offside line, restart, communication — applies almost letter for letter in cricket too. Only in one respect is cricket different: here it is not the speed of the decision but its explanation that matters more. The third umpire's announcement works on the same subtlety. In football's empty stadiums we learned when to say 'check complete', because without crowd noise every word echoes. In cricket, a single sentence from the third umpire decides the fate of millions, so clarity of sound matters even more there. The more players and fans hate umpire's call, the more it reveals whom the rule is really for. Give technology final authority without umpire's call, and we would have to accept that ball-tracking's estimate is never wrong. In reality it is. And the cost of that error would fall on the batter, when the ball might have missed the stumps. So umpire's call is really an acknowledgement of technology's limits, and at the same time a protection of the on-field umpire's authority. But the real blind spot is transparency. Transparency is not technology's enemy but its greatest ally. On screen, viewers see only the final outcome — 'Out' or 'Not Out' — not the confidence interval or the probability. So the decision feels mysterious, and mystery always breeds distrust. From a remote desk in Russia, we learned exactly this — a decision that cannot be explained, however correct, is never accepted. My hope is that in the coming season, Asian cricket will do at least one thing — show the measure of ball-tracking's uncertainty on screen. If viewers can see with their own eyes how much of the ball's path is observation and how much is estimate, then umpire's call will no longer be a source of irritation. More technology is coming; that is certain. There is only one question — will we trust technology blindly, or will we also show its boundary? Because a game that calls on technology also bears the duty to explain technology's limits.