World CricketUmpire's Call: The Error Zone Where Cricket Refuses to Answer
World Cricket

Umpire's Call: The Error Zone Where Cricket Refuses to Answer

**সংক্ষিপ্ত উত্তর:** আম্পায়ার্স কল হলো ডিআরএসের সেই Status, যখন হক-আইয়ের ট্র্যাকিং দেখায় বলের অর্ধেকেরও কম অংশ স্টাম্পে লাগছে, অর্থাৎ প্রযুক্তিগত অনিশ্চয়তা আছে। তখন মাঠের আম্পায়ারের আগের সিদ্ধান্তই বহাল থাকে এবং রিভিউকারী দল রিভিউটা হারায় না। **মূল তথ্য:** - লর্ডস, ১৪ জুলাই ২০১৯: বিশ্বকাপ ফাইনাল ও সুপার ওভার টাই হওয়ার পর বাউন্ডারি কাউন্টব্যাকে ইংল্যান্ড ২৬–১৭ ব্যবধানে জয়ী হয়। - আইসিসি ২০১৯ সালের অক্টোবরে বাউন্ডারি কাউন্টব্যাক বাতিল করে সুপার ওভার পুনরাবৃত্তির নিয়ম চালু করে। - আইসিসি ক্রিকেট কমিটি ২০২১ সালে আম্পায়ার্স কল পর্যালোচনা করে সেটি অপরিবর্তিত রাখে। - মেলবোর্ন, ১৯ মার্চ ২০১৫: রোহিত শর্মার নো-বল বিতর্কে বাংলাদেশ রিভিউ চাইতে পারেনি; ভারত ১০৯ রানে জেতে। - আম্পায়ার্স কলে রিভিউ না হারানোর নিয়ম দলগুলোর জন্য কৌশলগত "ফ্রি শট" তৈরি করে। **সূত্র:** আইসিসি ম্যাচ রিপোর্ট — লর্ডস, ১৪ জুলাই ২০১৯ এবং মেলবোর্ন, ১৯ মার্চ ২০১৫ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: আম্পায়ার্স কলে রিভিউ কেন হারায় না? উত্তর: আইসিসি প্লেয়িং কন্ডিশন অনুযায়ী সিদ্ধান্ত বহাল থাকলেও আম্পায়ার্স কলের ক্ষেত্রে রিভিউকারী দল রিভিউটি ধরে রাখে, ফলে এটি কার্যত বিনামূল্যের পরীক্ষা। প্রশ্ন: বলের কত অংশ স্টাম্পে লাগলে আম্পায়ার্স কল হয়? উত্তর: বলের অর্ধেকের কম অংশ স্টাম্পে আঘাত করলে সেটি আম্পায়ার্স কল হিসেবে গণ্য হয় এবং মাঠের সিদ্ধান্ত বহাল থাকে। প্রশ্ন: বাউন্ডারি কাউন্টব্যাক কেন বাতিল হলো? উত্তর: ২০১৯ বিশ্বকাপ ফাইনালের বিতর্কের পর আইসিসি অক্টোবর ২০১৯-এ নিয়মটি বাতিল করে সুপার ওভার পুনরাবৃত্তি চালু করে, যাতে টাই ফলাফল থেকে কৃত্রিম বিজয়ী তৈরি না হয়।

Three red dots lit up on the big screen. Then, in small white letters, two words surfaced — UMPIRE'S CALL. The sound thirty thousand people made together was neither a roar nor a boo. It was a question. The batter, half a step into his walk out of the crease, stopped. The bowler finished his follow-through and stood with hands on hips, utterly still. The slip fielder picked up the ball and looked straight at the screen. In that one moment cricket does its strangest thing — the technology answers, but it does not say "yes" or "no." It says: "I am not sure enough, so the decision on the field stands."

What DRS does no longer needs explaining. Hawk-Eye tracks the delivery and projects the path to the stumps. But the third umpire's job is routinely misread. His job is not to state the truth. His job is to determine whether the on-field call was wrong by a margin clear enough to overturn. That distinction is everything. It is a process that measures not truth and falsehood, but the distance from truth.

If the ball strikes the stumps with less than half its width, it is "umpire's call." In technical language, that is the tracking error band. In political language, it is the boundary of authority on the field. When the rule was drawn in 2026, Hawk-Eye's precision was nothing like today's. Seventeen years on, cameras have changed, frame rates have risen, models have matured. But that fifty per cent line has never been publicly re-derived. Nobody knows whether today's technology deserves that margin at all. That is the most uncomfortable gap in the entire argument.

Umpire's Call: The Error Zone Where Cricket Refuses to Answer

And a bigger tactical distortion hides in the retention rule. On an umpire's call, the reviewing side does not lose the review. The rule has turned the review into a free shot. When the ball hits the pad, the bowler screams, and the side thinks "maybe it's marginal," asking for the review is not a cost calculation — it is a lottery ticket. At Headingley in the 2026 Ashes, Australia misread that calculation in the opposite direction. Having burned all three reviews, they watched Nathan Lyon trap Ben Stokes in front, and the replay showed the ball was heading for leg stump. There was no review left to ask for. One wicket in the match, one review in the balance.

Bangladesh's cricket has taken this scar from the technology more than once. On 19 March 2026, in the World Cup quarter-final at Melbourne, Rohit Sharma was on 90. Replays suggested a delivery from Rubel Hossain had risen above waist height, but the on-field umpire did not call a no-ball — and at the time, a no-ball decision could not be reviewed. The question stayed a question, because the system never granted permission to ask it. Rohit finished unbeaten on 137 and India won by 109 runs. The failure there was not the technology's. The failure was in the list that decides which questions may be asked and which may not.

Umpire's Call: The Error Zone Where Cricket Refuses to Answer

For some years now, sitting in the press box at Mirpur's Sher-e-Bangla Stadium, I have written these moments down. One evening at Bangabandhu Stadium my phone became a notebook and the crowd became a haibun — ten short fragments holding not a scoreline but sound and shadow. What those pages taught me is simple: a crowd never thinks about the rule, a crowd thinks about the match's fate. And the rule exists to settle the fate. This is where the invisible contract between the two sides is fraying.

Cricket is the only major sport that has taught its technology to say "I do not know" out loud — and then accepted that state of ignorance as a legitimate result. Tennis's Hawk-Eye says in or out; there is no "line's call." A ball touches the line by a fraction, and the decision is still clean. Football has VAR, where nothing changes without a "clear and obvious error" — but a thousand VAR errors still never turn the technology into a substitute for the decision. Cricket is different, because cricket's entire infrastructure has rested for more than a century on a human trust: the man in the middle knows. Technology has not erased that trust; it has drawn a new frontier around it.

To me this resembles an old sickness from the data world — the silent null. When an analytical process returns an empty result, and the process converts that emptiness into a populated report rather than an error, the reader never learns that nothing was found. Cricket uses the sickness in reverse: here the silent null is not concealed, it is announced. The screen says it plainly — uncertain, so the previous answer stands. The problem persists anyway, because the announcement lands in one place where nobody remembers it: the scorecard.

And that is where the question sharpens. Whose uncertainty is actually being protected? A trained umpire genuinely unsure is a defensible thing, and it is defensible that no single milestone should retroactively discredit him. But who pays for that protection? The fielding side. The result. The match.

So the scandal is not umpire's call. The scandal is the record. On 14 July 2026 at Lord's, the World Cup final tied and the Super Over tied, and a winner was then manufactured by counting boundaries — 26 against 17. Not a single ball of that countback was bowled.

The ICC abolished boundary countback in October 2026. A rule that conjured a winner out of a tie could be reformed. Yet in 2026 the ICC Cricket Committee reviewed umpire's call and left it untouched. The two decisions do not share a logic. One says: we are wrongly labelling a winner. The other says: there is no need to label the winner at all.

A scorecard never prints the word "unknown." That is cricket's most consequential omission.

The real debate is not about the technology's error — it is about the technology's disclosure. Where the line sits, who drew it, when it was drawn, and on what evidence: without those four answers, greater tracking precision will not restore trust.

This argument will return in the current tournament cycle, because every high-stakes match is a coin-flip between fortune and rule. In the stands nobody will be talking about margins. Somebody will look up at the screen, see three red dots, read two words, and ask out loud what the game means. As long as the scorecard offers one number and no asterisk, that question stays unanswered — and the next generation will decide whether that silence is honesty or just a habit.

Umpire's Call: The Error Zone Where Cricket Refuses to Answer

Related Players