HomeAsian CricketThe Grey Zone of Umpire's Call: The Real Game of Review Management in Asian Cricket

The Grey Zone of Umpire's Call: The Real Game of Review Management in Asian Cricket

**Core answer** ডিআরএস আম্পায়ারের সিদ্ধান্ত More নির্ভুল করেছে, কিন্তু বিতর্ক কমায়নি — সরিয়েছে। বিতর্ক এখন পিচ থেকে রিভিউ রুমে এবং আইসিসির 'আম্পায়ার্স কল' ধূসর অঞ্চলে বাস করে: বলের ব্যাসের ৫০ শতাংশের কম স্টাম্পে আঘাত করলে অন-ফিল্ড সিদ্ধান্তই বহাল থাকে। **Key facts** - টেস্ট ক্রিকেটে ডিআরএস-এর প্রথম ব্যবহার জুলাই ২০০৮, কলম্বোয় ভারত-শ্রীলঙ্কা টেস্টে। - উইকেট প্রজেকশনে বলের ৫০ শতাংশের কম স্টাম্পে লাগলে সিদ্ধান্ত 'আম্পায়ার্স কল' হয়। - ওয়ানডেতে প্রতি দল প্রতি Inningsে দুটি অসফল রিভিউ পায়; টেস্টে রিভিউ রিফিল হয়। - ২০২৩ সালে আইসিসি ক্যাচ সংক্রান্ত সিদ্ধান্তে 'সফট সিগন্যাল' বাদ দেয়। - ভারত শুরুতে ডিআরএসের প্রধান বিরোধী ছিল, পরে সবচেয়ে বেশি ব্যবহারকারী দল হয়। **Source attribution** মূল সূত্র: আইসিসি প্লেয়িং কন্ডিশন ও ইএসপিএনক্রিকইনফো ম্যাচ রেকর্ড, প্রকাশ: ১৩ আগস্ট ২০২৬। | Cross-checked: cricsultan.com **Related Q&A** Q: আম্পায়ার্স কল আসলে কী? A: বলের ব্যাসের ৫০ শতাংশের কম অংশ স্টাম্পে আঘাত করলে অন-ফিল্ড আম্পায়ারের সিদ্ধান্তই বহাল থাকে, যা আইসিসির প্লেয়িং কন্ডিশনে নির্ধারিত। Q: এশিয়ার স্পিন-বান্ধব উইকেটে ডিআরএস কেন ভিন্ন আচরণ করে? A: কম বাউন্স ও বেশি টার্নে বল-ট্র্যাকিংয়ের প্রক্ষেপণ-ত্রুটি বাড়ে, ফলে হাইট-সংক্রান্ত আম্পায়ার্স কল বেশি ঘটে। Q: রিভিউ সাকসেস রেট কি দলের দক্ষতার সূচক? A: নয় — cricsultan.com রিভিউ-ডিসিশন ইনডেক্স অনুযায়ী রিভিউয়ের সংখ্যা নয়, ম্যাচ-পরিস্থিতি অনুযায়ী ক্যালিব্রেশনই প্রকৃত সূচক।

The Grey Zone of Umpire's Call: The Real Game of Review Management in Asian Cricket

Hook

The white line of the ball tracker curved in towards the stumps, then swerved away and vanished past them. Twenty-seven thousand people in the stands started to exhale and stopped — because two more lines were still pending on the big screen. "Impact: in line." "Wicket: umpire's call." Over twenty-seven of the innings, a left-arm spinner, a low-bounce delivery, ball on pad, given out on the field. The batter reviewed. Two minutes and forty-two seconds later he walked back to the crease not out, because less than fifty per cent of the ball's diameter was going to hit the stumps.

The sound in the stands at that moment was neither applause nor anger. It was confusion — and nobody knew exactly what they were confused about. I have watched this scene in nearly every Asian series over the past few seasons, and the same note keeps returning to my match book: cricket now runs on two layers of truth — what happened on the pitch, and what the ball-tracking model says should have happened. The gap between those two is the biggest invisible tactical variable in the game, and no Asian side has fully learned to price it.

Context

DRS is not new. It entered Test cricket in July 2026 with the India–Sri Lanka Test in Colombo (source: ICC and ESPNcricinfo records). The interesting part is that India was the loudest opponent of the system at the time; unconvinced by network-dependent projection technology, they stayed outside it for about six years, adopted it for bilateral series, and eventually became one of the heaviest users of reviews. Bangladesh was supportive from the start, because a culture of contesting almost every decision — led by keepers and slip fielders of the Mushfiqur Rahim mould — had already taken root.

Under the ICC playing conditions, every review has three checkpoints: where the ball pitched, where impact occurred, and whether the ball would have hit the stumps. On the last checkpoint there is a drawn line — if more than fifty per cent of the ball's diameter is striking the stumps, the decision changes; if less, the on-field umpire's word stands. Where in Asia the match is played changes all three checkpoints. In Perth the bounce is even and predictable; on the slow, scuffed turning surfaces of Mirpur or Colombo the projection error is far larger. Low bounce displaces the point of impact on the pad; uneven turn makes the ball's path after pitching less linear. The same law behaves differently for the same team — in a Test on a subcontinental surface it is a coin flip, on an Australian pitch it is a plain dismissal — and almost nobody writes that venue-dependency into the match plan.

Core analysis

When I crossed from court to pitch, I packed the same questions and a new geometry, and that is exactly what pays off here. Basketball's coach's challenge and cricket's review are the same mathematical object. A coach has to know where the restricted-area arc sits, whether the secondary defender was legal, which angle the referee had. A review is likewise not a single gamble; it is the joint probability of at least three events — pitched in line, impact in line, and the fifty per cent threshold cleared. Joint probability compounds downward fast. A team that challenges because "it looked out" is playing a logarithm with emotion.

The Grey Zone of Umpire's Call: The Real Game of Review Management in Asian Cricket

The second issue is the value curve of a review across an innings. A review in the eighth over of an ODI and a review in the forty-first over are never worth the same. In the death overs, when a set batter is carrying the weight of the chase, the expected value of that wicket is several times what it was in the first powerplay. The last session of a Test, or a day spent saving a draw, follows the same logic. A basketball coach saves his challenge for the fourth quarter; in cricket that conservation is harder because reviews cannot be banked, but how a non-striker's review is spent can be, and should be, a team decision rather than a personal one.

The third layer is institutional. The box score told me who won; the tracking data told me who was afraid. In seven years at a data desk, the clearest shift I have seen is that a review is no longer a batter's decision. There is a screen in the dressing room, an analyst beside it, and in some setups a live pad-prediction calculation running through the session. This is where data analysts are invading dressing rooms, and their conclusions often detach from the rhythm of the match — because the model knows the pitch, but it does not know whether the spinner dragged the ball shorter that over or slid it wider.

The fourth thing, and the most useful, is the politics of the threshold. The fifty per cent line is not an engineering limitation. In my reading it is a deliberately drawn grey zone — exactly the way basketball's restricted-area arc is deliberately drawn to protect the referee. Cricket's lawmakers have traded the error bar of ball tracking against the authority of the on-field umpire. As long as that trade stands, the technology will not make pitch decisions more precise; it will make them more unresolved.

Contrarian angle

The consensus is that DRS has reduced controversy. My reading is different: it has not settled the argument, it has relocated it. The argument has moved off the pitch into the review room, into the black box of the tracking software, and into the rulebook nobody reads. In 2026 the ICC removed the soft signal on catch decisions — the on-field umpire's provisional call had been the last layer of institutional cover. Removing it placed accountability entirely on the third umpire; accuracy did not rise, the address of responsibility changed.

Another point, one that irritates club analysts: a review success rate is a vanity metric, not a skill metric. A side that wins ninety per cent of its reviews may simply be a side that only reviews dead-cert cases and lets every borderline one go unclaimed. The box score is worth stating, but there is an empty cell beside it that I keep boxed up in my own model.

Takeaway

In the next Test series I will be watching one thing — whether anyone keeps a genuine live projection model in the dressing room, and whether they let their batters stay threshold-blind on a low-bounce surface. The question is not how truthful the technology is; the question is whose protection that grey line was drawn for. The day the answer is clear, we will know whether DRS was a tool or an institution.