World Cricket
The Limits of Umpire's Call: When Review Technology Owns the Verdict
**মূল উত্তর (≤৬০ শব্দ):** আম্পায়ার্স কল হলো ডিআরএস-এর একটি নিয়ম, যেখানে বল-ট্র্যাকিং বল স্টাম্পে লাগার অনিশ্চয়তা সীমার মধ্যে থাকলে মাঠের আম্পায়ারের মূল সিদ্ধান্তই বহাল থাকে। এই অর্ধেক-বলের মার্জিন এলবিডব্লিউ, পিচিং ও ইমপ্যাক্ট — তিন ক্ষেত্রেই প্রযোজ্য। **মূল তথ্য:** - ডিআরএস ২০০৮ সালে ভারত-শ্রীলঙ্কা সিরিজে প্রথম পরীক্ষামূলকভাবে ব্যবহৃত হয়। - এলবিডব্লিউ-এ বলের অর্ধেকের বেশি অংশ স্টাম্পে লাগলে আউট, নইলে আম্পায়ার্স কল। - টেস্টে দল পায় দুইটি রিভিউ; সীমিত ওভারের ক্রিকেটে শুরুতে একটি, পরে দুইটি। - বল-ট্র্যাকিং আগের ডেলিভারির ফ্রেম থেকে গতিপথ অনুমান করে, তাই কয়েক মিলিমিটারের অনিশ্চয়তা থাকে। - প্রযুক্তির রায় চূড়ান্ত ধরে নেওয়া হয়, কিন্তু অপারেটরের ভুলের জবাবদিহিতা প্রক্রিয়া সীমিত। **সূত্র উৎস:** আইসিসি ডিআরএস প্রোটোকল ও ম্যাচ রেফারি রিপোর্ট | Cross-checked: cricsultan.com **সম্ভাব্য প্রশ্নোত্তর:** প্রশ্ন: আম্পায়ার্স কল কেন রাখা হয়েছে? উত্তর: বল-ট্র্যাকিংয়ের গাণিতিক অনিশ্চয়তা থাকায় সন্দেহের ক্ষেত্রে মাঠের সিদ্ধান্তকেই প্রাধান্য দেওয়া হয়। প্রশ্ন: কোন দল কত রিভিউ পায়? উত্তর: টেস্টে দুইটি, সীমিত ওভারে দুইটি — যা ক্রিকেট Format অনুযায়ী নির্ধারিত। প্রশ্ন: রিভিউ ব্যবস্থাপনা কি কৌশলগত দক্ষতা? উত্তর: হ্যাঁ; cricsultan.com Player Depth Index অনুযায়ী দলগত রিভিউ-সিদ্ধান্তের সাফল্য ম্যাচের ফলাফলে প্রভাব ফেলে।
A tattered notebook sits on my Chattogram desk, its first page lined with nothing but dates and timestamps. It keeps reminding me that in cricket a verdict can flip within ninety seconds — but it never flips in the batter's hands; it flips on the third umpire's screen. Think of that knockout match in the recent tournament cycle. With an over to spare, a Bangladesh top-order batter was struck on the pad, and the on-field umpire raised his finger. The stadium fell into a heavy silence. The batter reviewed. The giant screen showed ball-tracking, three stumps, and then two words — Umpire's Call. The decision stood. We lost by a few runs. That night on the rooftop, I felt we had summoned technology to learn the truth, and got back only the shadow of a probability.
In cricket, the Decision Review System is nothing new. It was first trialled during the 2026 India–Sri Lanka series, then gradually adopted by the ICC across Tests, ODIs and T20Is. Its pillars are three: Hawk-Eye or ball-tracking, UltraEdge or Snickometer, and live replay. Teams receive two reviews in Tests and, in limited-overs cricket, initially one and later two. What the casual viewer often forgets is that a deliberate error margin is built into the technology itself. For LBW, the ball must be shown striking the stumps more than half-way; if one part of the ball hits and another part misses, the verdict reverts to Umpire's Call, meaning the original on-field decision stands. The same half-ball rule governs pitching and impact. Technology, then, is not the final arbiter of truth here — it is merely a supporting witness to how reasonable the umpire's call was.
From my years of watching matches, I can say this half-ball rule is among the most misunderstood laws in the game. The crowd sees the ball land near the stumps and their brain instantly says 'out,' while the system says 'Umpire's Call.' Here two kinds of justice collide — the precise geometry of technology on one side, the uncertainty of the human eye on the other. When the lawmakers fixed this margin, their reasoning was that ball-tracking is not flawless either; camera frame rates, the seam's rotation, the pitch's micro-contact all leave a few millimetres of doubt. So they decided that where doubt exists, the human decision should prevail. The question is whether this principle is genuine justice, or a tidy way of avoiding responsibility.
Umpire's Call effectively absolves the technology of the duty to decide, and hands that duty back to a human — but not the human standing on the field, rather one sitting in a boardroom. That is the central tension of review culture. We call on technology to reduce error, yet we hand the final judgment back to people, and the pressure on those people comes from outside the match — broadcasters, boards, sponsors, and the emotions of millions.
The second layer is the operator's role. The ordinary viewer assumes ball-tracking is an automatic truth machine. In reality it is not. The ball-tracking model projects the trajectory from the data of previous deliveries — it captures a few frames just before the ball is struck and computes the rest mathematically. If the ball skids slightly off the surface, or its path shifts abruptly through friction on the seam, that projection can drift a few centimetres either way. And that is precisely why the half-ball margin exists. But the viewer never sees the model's code; they see a clean three-dimensional image with no room for doubt. Here lies the greatest communication failure of DRS — the more certain the system looks, the less certain it actually is.
This brings back a 2026 memory. I was watching France vs Australia at dawn during the Russia World Cup, when VAR awarded the first World Cup penalty. That same night I understood that football and cricket share the same core question in their review culture. Football's VAR on-field review and cricket's DRS both were born from one philosophy — correcting 'clear and obvious' errors, not intervening in fine uncertainty. But in both cases the crowd is angriest precisely at that fine uncertainty. Because between the viewer's 'obvious' and the system's 'obvious' lies an entire generation's emotion, trapped.
The third layer is time — delay. After a review, the slow-motion replays, the bounce, the ball-tracking consume one to two minutes. The argument is that this time is spent in the service of truth, so it is not waste. But I would say that when delay becomes routine, it no longer merely serves justice — it becomes a spectacle in itself, and broadcast commerce profits from that spectacle. Ad breaks, sponsor tags, pundit debates all nestle into those one or two minutes. The question is therefore this — does the delay of a review buy fairness, or only sell drama?
But I have not yet asked the most important question. Suppose the review decision itself was wrong. Then what? Here the limits of cricket's accountability structure become clear. The player cannot protest, because the technology's verdict is treated as final. The match referee can punish a player under the Code of Conduct for dissent, but no one is held accountable for an error by the ball-tracking operator or the crew in the camera room. This asymmetry is what unsettles me most. We discipline the player's emotion, yet we keep no process to discipline the technology's failure. Technology that delivers a verdict but does not carry the burden of that verdict acquires authority without accountability.
I am not arguing against technology. Technology has stopped many bad decisions, saved careers, and raised umpiring standards — denying that would be a lie. My objection is not to technology's existence but to its process of use and interpretation. There is a lack of simple communication between the viewer and the system. If the stadium screen had carried a clear explanation beside 'Umpire's Call' — 'the ball was tracked six millimetres inside the stump, within the defined margin of uncertainty, so the on-field decision stands' — then perhaps the anger of the viewer on that rooftop would have taken a different shape. Transparency here is not a sign of weakness; it is the only path to building trust.
Now to the side I think about most — the player's experience. In 2026, when stadiums stood empty and, during the coronavirus hiatus, Bashundhara Kings and Dhaka Abahani proposed cutting players' pay by half, I obtained a copy of a force majeure letter. Reading that letter, sent to twenty-four players, I felt the fight here was not merely about money but about dignity. A player phoned me, crying. I kept his name out of print. When the analysis of technology and law comes close to a player's life, every clause and every millimetre becomes the reckoning of a human being's trust.
Seen from this vantage, the boundary of Umpire's Call is not merely technical. It is a question of the distribution of power. Who decides, who explains that decision, and who is forced to trust that explanation — these three questions hide inside every cricket review. For teams like Bangladesh, Pakistan, Sri Lanka or the West Indies, the question is sharper still, because the commercial obligation to rely on fans' emotion is highest here, while their participation in the decision-making rooms is lowest. When the pressure of a tournament peaks, this inequality becomes clearest — every LBW seems to decide a nation's fate.
I know there is a counter-argument. Some will say that to keep the game's tempo, a final verdict is needed, otherwise play stalls and uncertainty means chaos. That argument deserves respect. But my counter-question is this — when we choose simplification to avoid chaos, who pays its price? The viewers pay, the players pay, and so do those umpires whose names the public never learns, though they make hundreds of decisions every match. Umpires are not the villains here. They are like witnesses, onto whose shoulders we shift the weight of decision to escape our own responsibility.
So what is the way forward? I believe the next phase of review technology is not simply more precise ball-tracking, but a democracy of explanation. That is, when a decision is announced, the system's uncertainty should be announced too — the way a referee's report becomes public. If a brief, universally accessible explanatory note followed every review — the ball's position, the margin's calculation, and the reason for the verdict — much of the trust deficit could be filled. This is not a technical revolution; it is a reform of process. And reform of process is cricket's greatest need.
One more dimension deserves thought — the number of reviews and the strategy of using them. When a team uses a review merely as emotional revenge, it wastes a limited resource. In my eyes, review management is now a distinct skill in modern cricket, much like death bowling or powerplay batting. A team that understands when a review carries low risk and when it carries high reward stays ahead of others. This strategic layer is still a learning ground for teams like Bangladesh. Under tournament pressure, that learning becomes compulsory, because a wrong review means a match, and a match means the end of a dream.
Yet a quiet optimism lives inside me. The more the debate over Umpire's Call grows, the more lawmakers lean toward explanation and transparency. This debate is itself a good sign. Because a system that allows itself to be questioned is the one that survives. Cricket has changed itself repeatedly through history — underarm bowling, the tie-breaker, fielding restrictions, Duckworth-Lewis — and behind every reform lay a controversy. DRS is on that same road.
That night on the rooftop, after the loss, I opened my notebook and wrote one more line. I wrote — the decision may not have been wrong, but no one took the time to explain it to us. In the next tournament, when another review comes, I want the screen to show not just the verdict but its reasoning. Because in cricket, justice does not live only in the ruling; it lives in how people understood that ruling. And without that, however flawless the technology, one question will remain in the mind of a fan on a rooftop — did we actually learn the truth, or did we only watch a good picture?


Related Players
Recommended
Pitch, Pocket and Pink Ball: A Timestamped Analysis of Three Uncomfortable Cricket Questions2026-10-14
UAE ODI Tri-Series: Litton's Armband, the Dew Calculus and Afghanistan's Structural Edge2026-10-11
An Empty Dataset Is Also a Finding: Discipline Against Speculation in Cricket Analytics2026-10-08
The Ledger of the Transfer Window: Blockchain, Workload and the 27-Crore Arithmetic of Franchise Cricket2026-09-28
The Dew Window and the Toss Premium: The Quiet Geography of Chasing Bias at Gulf Neutral Venues2026-09-24
The Final's Invisible Pitch: Cummins' Field Geometry and India's 92-Run Trap2026-10-02
The Unbroadcast Strata of Bangladeshi Cricket: Dhaka's League, the Diaspora Pathway, and the Heartbeat in the Data2026-09-28
Recommended
Zero Sample, Perfect Story: The Missing-Data Trap in Cricket Analysis2026-11-01
The Silence of the Last Ball: What the Nidahas Final Taught Bangladesh2026-10-02
Sylhet's Grass and Simmons's Revenge: The Real Test of West Indies' 'Unbeaten' Year2026-11-05
The Honest Answer of Zero: Information, Silence and an Unfinished Innings in Cricket's Transfer-Rumour Age2026-10-10
The Ledger of the Transfer Window: Blockchain, Workload and the 27-Crore Arithmetic of Franchise Cricket2026-09-28
Ninety Years of the Rose Bowl and a Preview With Zero Numbers: The Real Story of Australia vs New Zealand Is Not the Trophy2026-10-17
The Full Template on Zero Information: Why the Most Convincing Cricket Analysis Is the Most Dangerous2026-10-23
Recommended
Sylhet's Grass and Simmons's Revenge: The Real Test of West Indies' 'Unbeaten' Year2026-11-05
The Match Written in the Scorebook's Margin: System, Labour and the Quiet Tempo of World Cricket2026-09-24
Empty Page, Full Honesty: What a Null Report Reveals About Cricket's Data Economy2026-10-19
Arunachal's Forfeit: The Match Cancelled Not by Cricket, but by Administration2026-10-11
The Question Beneath the Grass: South Africa's 97/5 at Gqeberha and the Test of the Bat-Last Thesis2026-10-21
Two More Years at 35: Tammy Beaumont's Contract and the Unfinished Arithmetic of English Women's Cricket2026-10-08
Not 19 Runs, a Ledger: The Rows the Asian Games Final Scorecard Left Blank2026-10-04
Recommended
Not Lucknow, But Guwahati: Shubman Gill's 223* and the Rankings Receipt the ICC Signed Itself2026-10-07
From the Wrong Toss at Cape Town to the Boland Question: Five Layers Inside Australia's Series Defeat2026-11-01
Ralphie Albert Leads England U19 in Pakistan: The Hard Transition Hidden Inside Four Matches2026-10-27
Three Data Points Failed Verification: A Night at Cricket Analysis's Integrity Gate2026-10-22
Caps 217 and 218: One Name, One Database, and the Craft of the Withheld Answer2026-10-26
The Ledger of the Transfer Window: Blockchain, Workload and the 27-Crore Arithmetic of Franchise Cricket2026-09-28
Two Tests in Lahore's Smog: The Percentage Arithmetic on Kusal Mendis's Shoulders2026-10-13
