The DRS Threshold: The Invisible War Between Clear-and-Obvious and Umpire's Call

On an evening in 2026, I sat at a sports new-media desk in Dhaka as a junior VAR analyst. On the monitor was a Bangladesh Premier League match — Abahani Limited Dhaka against Sheikh Russel Krira Chakra, Abahani leading 2-1. In the 89th minute, a collision inside the box, and the on-field referee pointed to the spot. I watched the moment from six camera angles — the referee's initial call, the 48-second VAR check, and the final decision. I logged everything. That night, the desk's first standardised review template was born. I understood that memory is not a review protocol. The speed of the game is such that the eye sees one thing and the mind distorts it; but a timestamped log never lies. Today I sit with the same question about cricket's Decision Review System. What VAR is to football, DRS is to cricket. The core aim of both is identical — to catch the errors of the umpire's eye. But at the centre of both lies one invisible war: where exactly is the line between the clear-and-obvious threshold and umpire's call? The question looks harmless but is dangerous. Because "umpire's call" — that single phrase — is the most contested, most under-analysed and most misunderstood rule in cricket. I built the five-point log in Dhaka because memory is not a review protocol. Today, with the same method, it is time to open up the machine inside DRS. DRS was born in July 2026. It was first used experimentally in the Test series between India and Sri Lanka. Since then the system has stood on three pillars — ball tracking, edge detection, and the review protocol. Ball tracking leans on Hawk-Eye technology; edge detection relies on UltraEdge, Snickometer and Hot Spot; and the protocol is the framework of rules that decides who may review, when, and when the technology's verdict is final. The rule looks simple. Each team gets two unsuccessful reviews per innings; in Test cricket the count resets after 80 overs. The window to review is 15 seconds. After the on-field umpire's decision, either the fielding side or the batter may challenge within 15 seconds. The TV umpire then examines multiple angles, ball tracking and audio before delivering the final verdict. If the decision is overturned, the team keeps its review; if the decision stands, the review is lost. The first trap hides here. In an umpire's call, the decision stands — so the team loses the review. But the question is: if the technology shows the ball would have hit the stumps, why should the decision stand? The answer lies inside the credibility of the technology, and that is the most complex part of the whole system. From my experience I can say this: anyone seeing the DRS screen for the first time assumes it is a neutral machine — binary, zero and one. In reality it is not. Ball tracking is an inferential process. The cameras capture the ball frame by frame, and then a mathematical model projects its future path. The true path of the ball is known up to a few centimetres before the stumps; everything beyond that is the model's projection. And that projection carries a defined margin of error. That margin of error gave birth to umpire's call. Under ICC rules, if ball tracking shows the ball would have hit the stumps but only partially or within the margin, the on-field decision stands. In other words, when the technology cannot be certain, it hands the decision back to the human. A great conflict arises here. The same ball, the same line, the same length — but if the on-field umpire gives it out, it stays out after review; and if he gives it not out, it stays not out. The outcome of an identical event depends on that first human decision. To many critics this is unjust; to the technology it is an acknowledgement of honesty. I think this is cricket's most honest yet most uncomfortable rule. It admits that technology is not omnipotent. When the machine cannot speak, it refuses to speak — that is procedural honesty. But what reaches the viewer and the player is doubt, uncertainty and the feeling that the game is being mocked. Here I want to cite a precedent that still returns to my desk discussions. In football, VAR follows the same principle — clear and obvious error. If the referee's decision is not clearly wrong, VAR does not touch it. But in football VAR explains the reason to the viewer; in cricket DRS does not. This difference has opened a large gap in the acceptance of the two technologies. I want to reach one clear conclusion here, drawn from my years of watching matches: DRS is a decision machine, but it is not a communication system. And it is precisely this lack of communication that has given birth to every major review controversy. Let us go deeper into the error margin. The ICC itself admits a limit to the accuracy of Hawk-Eye and ball tracking. In projecting whether the ball will hit the stumps, there is an uncertainty of a few millimetres. The umpire's call circle is drawn within that uncertainty. If the ball's path is well away from the centre of the stumps, the technology can be certain — out or not out, final. But if the path grazes the edge of the stumps, certainty is lost, and the decision returns to the human standing on the field. This system has a subtle but important consequence. If a batter misses the ball and it strikes the edge of leg stump, his fate is determined by the on-field umpire's call. The technology here is not the judge; it is only the verifier. Many do not wish to understand this division of roles. At the Dhaka desk I built a habit — for every review I noted five things separately: the law, the camera angle, the contact, the clear-and-obvious threshold, and the final call. This five-point log taught me at which layer the conflict between technology and human actually occurs. That layer is the threshold. Because at the centre of everything hides a number — how much of the ball is hitting the stumps, how much of the ball is inside the line, how much the ball is clipping the stumps. These numbers appear on screen, but who sets the limit of that number? Not the technology — a human sets it. The ICC sits in a committee and fixes a threshold, and that threshold decides the fate of the game across the world. A hard truth hides here: we think of technology as neutral, but the technology's threshold is never neutral. It is a decision, a policy, a compromise. Someone determined it — and the outcome of that decision is seen in every marginal review. I say again, the DRS threshold is in fact a political decision, not a technological one. Because what technology gives is data; what the rule gives is a limit. Standing between the two is umpire's call. Now the economy of the review. Two reviews per innings — this number looks simple but is not. It is really an accounting of a resource. Losing a review means losing a strategic advantage. In Tests the count resets after 80 overs, but losing the second review within those 80 overs leaves you tied for the rest of the innings. Strategy enters here. When to review and when not to is an investment decision. A correct review means recovering the resource; a wrong review means losing it. For this reason experienced captains review only at major turning points. In my research a pattern keeps returning: the decision to review is often made under pressure, on emotion. And that is exactly where the error occurs. Because the decision to challenge the umpire must be made within seconds, while the evidence arrives afterwards. This gap in time is the system's biggest weakness. But my biggest observation lies elsewhere. I have noticed that DRS sometimes overturns a decision that was no less correct than the one it replaced — rather, the earlier decision was just inside the limit. That is, the technology sometimes changes a correct decision simply because the projection leaned the other way. At this point the logic of umpire's call clicks into place. Umpire's call gives the system a safety ring. If the technology is not certain, it does not impose its projection, but hands it back to the human. It is a principle of restraint — and unfortunately, restraint sometimes looks like injustice. Now to the comparison where I have the most experience. In 2026, during the Russia World Cup, I remotely tracked all 64 matches. My live spreadsheet recorded 29 penalties, 22 scored and 20 VAR overturns. That experience taught me that VAR and DRS suffer from the same disease — the management of uncertainty. The difference is in the process. VAR reconsiders a decision because the referee himself goes to the screen. In DRS the TV umpire decides alone, and the on-field umpire merely receives the verdict. This reduces procedural transparency in DRS. In football we often see the referee standing before the screen, the crowd watching what he watches. In cricket that scene is absent. The viewer sees only a final verdict, not an explanation. And how uncomfortable a verdict without explanation is, I understood in 2026. During the global hiatus of 2026 I covered the Bundesliga restart from Dhaka. I analysed the empty-stadium audio of the Borussia Dortmund 4-0 Schalke match. In an empty stadium the referee's audio can be isolated — and hearing it, I understood how important the communication of a decision is. I built a 48-hour emergency protocol: isolate the referee audio, map the echoes of the silent stadium, and verify offside calls with two independent angles. Three South Asian desks adopted that protocol. Its core lesson was — procedural transparency matters more than the decision itself. I now want to apply that lesson to cricket. The biggest problem of DRS is not the decision; it is the language of the decision. When the TV umpire says "umpire's call", the viewer hears "we are not sure, so the earlier decision stays". But what should have been said is — "the ball's path grazed the edge of the stumps, it falls within our margin of projection, so we respect the on-field decision." The difference between these two sentences is the difference between acceptance and outrage. Now to the debate that never ends — has DRS made the game better or ruined it? Here I want to take a counter-intuitive position. Many believe DRS has reduced the umpire's power. My observation is the exact opposite. DRS has actually made the umpire stronger. Because the umpire now knows every decision can be verified. This accountability has made the umpire more careful, more restrained. Where a decision was once final and unreviewable, it is now part of a process. But there is a danger here that no one mentions. When an umpire knows technology is behind him, he sometimes stops taking risks. He avoids the hard decision, trusting the review. I call this the "referee syndrome" — the tendency to hand the burden of decision to technology. In my view this is the biggest hidden cost of DRS. Because the soul of the game is the instant judgement of the human on the field. If that judgement erodes, the game loses its human core even if the technology is correct. But I am not a pessimist. I think DRS is an immature technology, not a failed one. Any technology is immature in its first decade. VAR was, and still is. What matters is that we teach technology to admit its limits. Here is my strongest recommendation. The DRS screen should show not only the final verdict but the degree of uncertainty. If ball tracking can say "this ball will hit the stumps with 60 per cent probability", that should be shown. The viewer would then understand why the decision is uncertain. I favour adding a "confidence score" to ball tracking. When the machine is not certain, it should admit it — not hide it. And that admission may restore the viewer's trust. The second recommendation concerns the TV umpire's communication. As in football, cricket too should give a brief explanation with the decision. A few sentences should state where the ball struck, which angle informed the decision, and why it is not a clear error. That much explanation can calm much of the controversy. The third recommendation is about training, not protocol. Umpires need DRS-awareness training. They should be taught in which situations the technology will be certain and in which it will not. Then they will know when to stand firm in their own decision. Now I want to return to an uncomfortable truth I cannot avoid. The acceptance of DRS is not equal worldwide. In markets like Bangladesh, India and Pakistan, viewer expectation differs from that in Europe and Australia. This gap is not only technological; it is cultural. I want to be honest about my own market. The South Asian cricket viewer sees a decision through emotion, not logic. Here the umpire is not merely a judge; he is part of the game. So when technology overturns his decision, the viewer does not see it as a victory of technology but as a conspiracy against his hero. This emotion cannot be ignored. Because the game survives on this emotion. So reforming DRS requires changing not only the technology but the culture of communication. The decision needs a story — the story of an explanation. Let me draw one last comparison. In football, the biggest criticism of VAR is that it kills the flow, stops the celebration. In cricket, the criticism of DRS is different — the uncertainty of the decision. But at the core of both is one question: does technology make the game fair, or does it merely make it unfair in a different way? My answer is that technology has made the game fair — but unevenly. Where technology is certain, it delivers justice. Where it is uncertain, it leaves doubt. And that doubt gives birth to every major controversy. At the Dhaka desk I follow a rule — I call a review final only when I can verify it with at least two independent angles and one audio source. This rule has made me slower but has reduced errors. DRS needs the same rule — no final verdict without dual verification. I also admit my method sometimes feels cold. Removing emotion makes writing accurate but lifeless. DRS has exactly the same problem — it wants to be accurate but cannot keep the soul alive. The balance between the two has not yet been found. So my final verdict is not that DRS is good or bad. My verdict is that DRS is a process that has not yet learned to explain itself. A machine that does not admit its own limits never earns trust. And without trust no review system can survive. The referee's eye is not an instinct; it is a habit built frame by frame. DRS must learn that habit — frame by frame, admitting doubt, explaining decisions. Only then will technology become the game's partner, not its enemy. The question is no longer about technology; the question is about us — are we willing to accept technology's uncertainty? Or do we want a certainty that no machine can ever give? The answer to this question will decide where DRS stands in the coming decade.