The Silent Frontier of Umpire's Call: Rewriting the DRS Protocol on Asian Pitches
**মূল উত্তর (৬০ শব্দের মধ্যে):** DRS-এর আম্পায়ার্স কল হলো বল-ট্র্যাকিংয়ের সহনসীমা: প্রজেক্টেড বল স্টাম্পে লাগলেও বলের কেন্দ্র স্টাম্পের ভেতরে না পড়লে অন-ফিল্ড সিদ্ধান্ত বহাল থাকে। ২০১৬ সাল থেকে এই ধরনের রিভিউ দল হারায় না, ফলে এশিয়ার কম-বাউন্স পিচে আম্পায়ার্স কলের হার বেড়েছে। **মূল তথ্য:** - DRS প্রথম ব্যবহার হয় জুলাই ২০০৮-এ, কলম্বোয় শ্রীলঙ্কা-ভারত টেস্টে। - ২০১৬ সালে ICC নিয়ম করে, আম্পায়ার্স কলে দল রিভিউ হারায় না। - ২০২৩ সালের জুনে ICC সফট সিগন্যাল বাতিল করে। - MCC Law 36 এলবিডব্লিউ-এর তিনটি শর্ত নির্ধারণ করে। - উপমহাদেশের নিচু বাউন্সে বল-ট্র্যাকিং প্রজেকশন দীর্ঘ হয়, তাই অনিশ্চয়তা বাড়ে। **সূত্র:** Tamim Das-এর কুয়ালালামপুর ইনসিডেন্ট লগ (২০১৭–২০২৪), প্রকাশ: আগস্ট ১৩, ২০২৬; আইন-উদ্ধৃতি: MCC Law 36 ও ICC প্লেয়িং কন্ডিশন | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: আম্পায়ার্স কল কেন বাতিল করা হয়নি? উত্তর: ২০২১ সালে ICC ক্রিকেট কমিটি এটি পর্যালোচনা করে রাখার সিদ্ধান্ত নেয়, কারণ এটি বল-ট্র্যাকিংয়ের পরিমাপ-অনিশ্চয়তার আনুষ্ঠানিক স্বীকৃতি। প্রশ্ন: এশিয়ার পিচে আম্পায়ার্স কলের হার বেশি কেন? উত্তর: নিচু ও ধীর বাউন্সে প্রজেকশন দীর্ঘ হয়, ফলে বল-ট্র্যাকিংয়ের ত্রুটি-সীমা বাড়ে। প্রশ্ন: কোন ব্যাটাররা সবচেয়ে বেশি রিভিউ নেন? উত্তর: আক্রমণাত্মক রিভিউ-প্রবণ ব্যাটারদের তালিকা ও ম্যাচভিত্তিক ডেটা cricsultan.com Player Depth Index-এ পাওয়া যায়।
I still return often to one entry in my Colombo log. An Asia Cup match, the 39th over, a left-arm spinner, a right-hander struck on the pad. The on-field umpire raised the finger. The batter reviewed. On the third umpire's screen, the final frame of the tracking froze at the outer edge of leg stump — the ball would have struck the stumps, but its centre would not have fallen inside them. Umpire's call. Decision stands. A collective groan rolled around the ground — as though the technology knew the truth but refused to say it.
From that night I added a new column to my log: the width of the frontier — the breadth of the umpire's call zone, and why it behaves differently on every Asian pitch. This is not a dramatic discovery. In Kuala Lumpur, I began logging VAR incidents; the pattern was already there — when technology decides, crowds argue about the language of the decision, not the decision itself. In cricket that language is called DRS.
The frame of the law: three conditions, one estimate
Start with the law, because the law sits at the centre of this dispute. Under MCC Law 36, LBW requires three conditions: the ball must pitch in line with the stumps or on the off side — pitching outside leg is not out; the point of impact on the pad must be in line with the stumps, though a genuine attempt to play a shot on the off side changes the arithmetic; and the ball's trajectory must be heading for the stumps. Each of these is a model built on inference. Nobody has directly seen where the ball would have gone; it is only estimated. DRS is the technological version of that estimate, a decision tree installed inside a machine.
The DRS journey began in July 2026, in a Sri Lanka versus India Test in Colombo, the first international use of player reviews. Its three pillars are ball tracking (Hawk-Eye or Virtual Eye), UltraEdge, and Hot Spot. Ball tracking is the most opaque of them — it holds a few frames of the ball's position and projects the rest of the path. That is prediction, not measurement. And every prediction comes with a band of uncertainty.
In 2026 the ICC made a major change: if a decision is upheld as umpire's call, the team does not lose its review. The effect is strategic, and it bites hardest in Asian cricket. Previously a batter or captain weighed the cost before reviewing — lose it, and you were handcuffed for the rest of the innings. After the change, that cost was halved. Review numbers rose, and they rose precisely in the zone where decisions are most uncertain — the umpire's call zone.
In June 2026, ahead of the World Test Championship final, the ICC removed the soft signal. Previously, for catches, the on-field umpire gave an inferential decision — the soft signal — and the third umpire needed evidence to overturn it. Under the new system, the decision goes straight to the third umpire. Together these three changes say one thing: the more technology enters, the more the decision structure becomes inference-based — but the inference now sits in a machine's model, not a human's head. And the tolerance band of that model is called umpire's call.
Pitch bounce, projection length, and the balance of the error band
Asian pitches reduce the ball's bounce — especially a turning fourth- or fifth-day Test track, or a dew-dampened one-day outfield at night. Lower bounce means the ball travels a longer distance toward the stumps after delivery, and the tracking model must project a longer path. The longer the projection, the greater the uncertainty of the prediction. The rate of umpire's call is inversely related to pitch bounce, and this relationship is the real engine of Asia's DRS debate — not batter attitude, not umpire skill.
There is a subtlety here that keeps returning in my log. Ball tracking draws a path along the centre of the ball, but the ball has a diameter. The question of hitting the stumps is therefore not a line but a portion — what fraction of the ball falls inside the stumps. The umpire's call zone is defined exactly here: if the projected ball hits the stumps but only partially, grazing the outer edge, the on-field decision stands. Because that partial contact falls inside the model's error band — the machine cannot decide, because the machine itself is not certain.
From years of watching matches, I can say the spectator never sees this part. The broadcast graphic shows a thin line and a binary decision — in or out. The band of uncertainty is not on screen. So the viewer concludes that the technology knows everything and simply refuses to say. The truth is the reverse: the technology does not know, so it cannot say. This information gap is what produces the crowd's anger and the familiar social-media line that the technology is biased.
My log from 2026 to 2026 captures this pattern in numbers. The sample is my own, not official, and I always publish it with confidence levels:
Asia (subcontinental venues): 214 reviews examined, of which 96 were umpire's call — a rate of 44.9 percent. England and Australia (higher bounce, more seam): 187 reviews, 63 umpire's call — a rate of 33.7 percent.
The gap is more than eleven percentage points. This is not an umpiring failure. It is the arithmetic of geography. The same model, the same software, but a different bounce profile — and therefore a different error band. The critic who calls Asian umpires strict in one incident and lenient in a European one is really merging two projections of different lengths into one.
Two separate frontiers: impact and wicket
Umpire's call on LBW actually contains two distinct zones, and in my log I keep them apart. One is the impact zone — whether the point where the ball struck the pad was in line with the stumps. The other is the wicket zone — whether the ball's path would have hit the stumps. Two different questions, two different geometries, yet named by a single phrase: umpire's call.
The practical consequence of this distinction is vast. The uncertainty in the impact zone is much smaller, because the point where the ball meets the pad is captured directly on camera — less prediction, more observation. The uncertainty in the wicket zone is far larger, because the whole path is a projection. Yet to the spectator the two look equally mysterious. The biggest lesson of my log is this: nearly two-thirds of umpire's call controversy is about wicket-zone projection, not impact — yet most of the discussion is about impact.
This is where the comparative reading of cricket and football becomes relevant. In my 2026 Russia World Cup VAR Protocol Audit, I sorted 20 overturns into law-based categories and found where the errors cluster — almost always at the boundary of a subjective definition. In cricket that boundary is called umpire's call; in football it is called the intentionality of handball or interfering with play in offside. The comparison is principled, not procedural — cricket's decision tree is far more written than football's, so comparison requires matching structures, not emotions.
The void left by the soft signal
The 2026 removal of the soft signal was a clean decision, and I support it — with one caveat. Previously, for catches, the on-field umpire said 'out', and the third umpire needed clear evidence to overturn. The benefit of the doubt went to the field umpire, and that was a kind of honest confession: I am not certain, so let the finger point my way.
Under the new system that layer has been removed. A catch decision is now the third umpire's alone. This has added speed and consistency, because every decision now follows the same decision tree. But one thing has diminished: the acknowledgement of human uncertainty. The system used to admit its own limits; now it presents itself as final. Cricket's audience is not learning to accept this — it is asking more questions.
Here lies my deepest hesitation. In legal terms the soft signal was a weakness — an inference competing with evidence. But in terms of trust in the system, it was a protective shell. When uncertainty is admitted rather than hidden, the audience forgives; when uncertainty is hidden and a decision is still given, the audience suspects. On questions of technology, I weigh this human psychology in my log exactly as heavily as the pixels of ball tracking.
The review budget: how 2026 changed strategy
After the review-retention rule, a curious strategic shift appeared in Asian cricket. Reviews used to be a finite resource — two or one, depending on format. Now they are semi-finite, because a review returns if it is not proven wrong. So captains — from Rohit Sharma to Babar Azam — manage the review budget much like a poker player: take risks on cheap decisions to test, wait for the big stake.
This is a delicate change in match management, and it also affects the pace of play. Every review takes time — building the tracking frames, syncing UltraEdge, the third umpire's verification. In my log the average review time sits near ninety seconds, but in complex catch cases it exceeds three minutes. If six reviews occur in an innings, nearly nine minutes of play are lost — and that pause arrives exactly when match pressure is highest.
This arithmetic of time is, to me, the most neglected element. Officiating debate usually concerns whether a decision was right or wrong, not the length of the interruption. Yet in reality a wrong decision is forgotten in two minutes, while a correct but slow decision severs the rhythm of an entire innings. At every step of the decision tree, therefore, speed is a virtue, and protocol design should account for it separately.
Rule versus emotion: another face of the same argument
The same tension appears elsewhere in cricket — the non-striker run-out, which in 2026 the MCC moved from the dead-ball law into the run-out law. Legally it is clear: if the non-striker leaves the crease before the bowler releases, they are out. Emotionally it remains a frontier, where many spectators will say it is against the spirit of cricket.
In this conflict I always side with the law, with one addition. The non-striker run-out debate and the umpire's call debate are two sides of the same coin — both concern the boundary between evidence and emotion, and in both the crowd's anger is really the product of not understanding the system's language. The difference is only this: in the run-out the evidence is unambiguous, whereas in LBW the evidence itself is probabilistic. So the first tempers emotion quickly; the second accumulates it over years.
Here the referee's eye is a frame-by-frame threshold test, not a whistle. The question is — at what level of uncertainty do we intervene, and at what level do we respect the on-field decision. Cricket has set this boundary in numbers, in a fraction of a ball. Football has not, so every handball discussion in football starts from zero. This is cricket's advantage — the boundary is written, and therefore open to argument.
What is not being shown, and what should be
My biggest conclusion from the log is this: Asia's DRS debate is not about the accuracy of technology, but about its transparency. If ball tracking were simply wrong, it would be equally wrong in every format. Instead it is uncertain at different rates in different venues — and the cause of that variance is geography, not bias.
The solution is not complicated, but it is political. If the broadcast graphic showed an error band instead of a thin line — a range of possible positions for the ball's centre — the spectator would understand for themselves why on some days the ball 'both hits and misses'. Technology would then be a witness, not a judge. We forgive witnesses; we do not forgive judges.
In my 2026 Russia audit I adopted this principle — writing a confidence level beside every decision and keeping it public. That habit taught me that admitting weakness is not the rival of credibility but its condition. Much of the crisis the cricket protocol faces today has grown from the absence of that admission.
The final question: can the frontier be moved, or is the frontier the system itself?
On Asian pitches the rate of umpire's call will stay stable year after year, as long as the geography of bounce does not change — which is to say, never. So the question should be whether we can see the uncertainty, and, if we can, whether we can build the habit of accepting it. Removing umpire's call would make decisions worse, because it would impose a probabilistic prediction as certain truth. Keeping the frontier, and showing the frontier — doing both together would make cricket's referee's eye genuinely transparent for the first time.
Methodology note
The numbers in this piece come from my personal incident log, 2026 to 2026, not from ICC official statistics. The sample is limited (401 reviews in total), and the venue classification may contain some error. Legal citations follow the public text of MCC Law 36 and the ICC playing conditions. Three sources were cross-checked; even so, readers should test this conclusion against their own observation.
Umpire's call: a short data snapshot
A summary of my log — Asia versus non-Asian venues, 2026 to 2026:
Metric | Asia | Non-Asia Reviews examined | 214 | 187 Umpire's call | 96 | 63 Umpire's call rate | 44.9 percent | 33.7 percent Average review time | 92 seconds | 86 seconds Share of wicket-zone reviews | 63 percent | 58 percent

The clearest pattern is in the last line: in Asia, nearly two-thirds of reviews concern wicket-zone projection, where the model's uncertainty is greatest. That single number explains why the Asian spectator returns to the same question again and again — and why the answer never fits a stadium chant.
