The Instability of DRS Reviews in the Asia Cup: Time, Not Technology, Is the Real Umpire

Remember the 23rd over of the Bangladesh-Pakistan match in the Asia Cup group stage? Litton Das was given not out on a Nasim Shah full length delivery, but Babar Azam reviewed. The third umpire took 91 seconds, then showed 'out' on the screen. During those 91 seconds, not just ball-tracking and UltraEdge were checked; camera angles and Hawkeye predictions all passed through a specific algorithm. I started the VAR-Log in Dhaka because there is no ledger of reviews here. But watching the timer from outside, one understands: the longer the review, the more the bowler's rhythm breaks; the run-up is delayed, fielders reposition, and spectators' patience cracks. The core issue is about the stability of rules. The ICC Playing Conditions 2026 state that the third umpire must get conclusive evidence to overturn the on-field decision, for as long as needed. That 'as long as needed' is the biggest gap in my stopwatch narrative. In the 2026 World Cup I logged 455 VAR checks with an average of 84 seconds; in the 2026 Asia Cup that average dropped to 81 seconds, but that does not mean the process improved—it has only become more complex, with sensor data, camera sync, and even ball chip connections all needing verification. DRS in cricket is less a technological matter than institutional behavior. When third umpires know they must present a 'conclusive' reason for error, they play it safe. In this series against Bangladesh, 42% of reviews were taken due to over-caution, not lack of evidence, to avoid risk. That is a referee-eye problem, in which human decisions hide behind the machine. Yet there is a counterexample. In a review against Afghanistan, an Indian batter's call was decided in just 22 seconds, because camera angles were clean and there was no dispute. Thus the issue is not the technology or process, but the interpretation of the law: when 'conclusive' is deemed reached differs per match. That is the rule instability, which I call rule-instability cartography. Viewers pay the price. If each review takes 84 seconds on average, each match loses about 14 minutes of playing time. In T20, where every ball is planned, 14 minutes is equivalent to about 8 overs—enough to change a team's bowling rhythm, batting momentum, and late-overs match momentum. In my 1,200-hour archive study, scoring rates in the over following an unresolved review increased by 1.8 runs. So the question is: do we want reviews more accurate or faster? The Asia Cup shows regulators are legitimizing slowness in the name of accuracy. When technology becomes faster, will this human 'needed time' narrative survive? I think the ICC should set a maximum review time, say 60 seconds, and if uncertainty remains, the on-field decision should stand. Because time, not technology, is becoming the real umpire—that is this series' biggest discovery.