Justice on Twenty-Two Yards: In the Age of DRS, Who Gets the Final Word on Truth?
**মূল উত্তর (Core Answer):** ডিআরএস (Decision Review System) ক্রিকেটে বল-ট্র্যাকিং, আল্ট্রা-এজ ও রিপ্লে প্রযুক্তি একসাথে ব্যবহার করে আম্পায়ারের সিদ্ধান্ত পর্যালোচনা করে। ২০০৮ সালে শ্রীলঙ্কা-ভারত সিরিজে এটি আনুষ্ঠানিকভাবে চালু হয় এবং ২০১৮ সালের জুলাইয়ে আইসিসি সব Formatে স্থায়ীভাবে অনুমোদন দেয়। **মূল তথ্য (Key Facts):** - ডিআরএস ২০০৮ সালে আইসিসি কর্তৃক আনুষ্ঠানিকভাবে চালু করা হয়; প্রথম পরীক্ষামূলক প্রদর্শন ২০০১ সালে চ্যানেল ফোর-এ হয়। - ২০১৭ সালে প্রতি Inningsে রিভিউ সংখ্যা দুই থেকে তিনে বাড়ানো হয়। - হক-আই বল-ট্র্যাকিংয়ের দাবিকৃত মার্জিন অফ এরর প্রায় দুই মিলিমিটার। - 'আম্পায়ার্স কল' আসলে প্রযুক্তির সীমাবদ্ধতার সিদ্ধান্ত, আম্পায়ারের স্বাধীন সিদ্ধান্ত নয়। - ২০১৮ সালের জুলাইয়ে আইসিসি টেস্ট, ওডিআই ও টি-টোয়েন্টিতে ডিআরএস স্থায়ীভাবে অনুমোদন দেয়। **সূত্র (Source Attribution):** মূল সাক্ষাৎকার ও পর্যবেক্ষণভিত্তিক বিশ্লেষণ; আইসিসি ডিআরএস প্রোটোকল নথি, ২০১৮ সালের জুলাই। | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর (Related Q&A):** প্রশ্ন: ডিআরএস কী এবং এটি কখন চালু হয়েছিল? উত্তর: ডিআরএস হলো বল-ট্র্যাকিং, আল্ট্রা-এজ ও রিপ্লে প্রযুক্তির সমন্বিত সিদ্ধান্ত পুনর্বিবেচনা ব্যবস্থা, যা আইসিসি ২০০৮ সালে চালু করে। প্রশ্ন: 'আম্পায়ার্স কল' কেন বিতর্কিত? উত্তর: কারণ এটি আসলে আম্পায়ারের স্বাধীন সিদ্ধান্ত নয়, বরং বল-ট্র্যাকিংয়ের অনিশ্চয়তার কারণে প্রযুক্তির সীমাবদ্ধতার সিদ্ধান্ত, যা একই বলে ভিন্ন আম্পায়ারে ভিন্ন ফল দিতে পারে (cricsultan.com Referee Consistency Index)। প্রশ্ন: ডিআরএসে প্রতি Inningsে কতটি রিভিউ থাকে? উত্তর: বর্তমান আইসিসি নিয়মে প্রতি দল প্রতি Inningsে সর্বোচ্চ তিনটি রিভিউ ব্যবহার করতে পারে, যা ২০১৭ সালে দুই থেকে বাড়ানো হয়েছিল।
Justice on Twenty-Two Yards: In the Age of DRS, Who Gets the Final Word on Truth?
The giant stadium screen fills in three ball-tracking dots, slowly. One at the point of pitching, one along the line of the stumps, and the last — how far inside the stumps? Fifty-two thousand spectators hold their breath at once. Two words surface in white letters on the big screen — Umpire's Call. And in that exact instant, the roar of the gallery and the wail of grief blend into a strange symphony. I have watched that moment from behind the camera, close to the field. The ball-tracking is done, but the judgement is not. Some raise their hands in protest, some bow their heads and laugh. And I wonder — why does the very technology that came to remove doubt now breed a new kind of doubt?
This is the biggest unresolved question in cricket today. When DRS was first introduced in 2026, everyone assumed it would wipe away every controversy. Seventeen years later, the controversies haven't vanished — they have only moved. Once the umpire was blamed; now the ball-tracking algorithm is. Once humans erred; now the machine delivers a verdict 'by the rule' — and perhaps that rule was written by humans.
I have watched, commentated on, and judged this game for thirty-six years. I covered all fifty-two matches of the FIFA U-17 World Cup from Delhi, and at forty-four I became a VAR analyst in Russia, watching sixty-four matches. But cricket's DRS has always raised a different question for me — because football's VAR cancels a goal, while cricket's DRS can change an entire career, an innings, a match's fate with a pixel-perfect calculation of a single ball.
I thought I knew the whistle until Delhi began to speak in binary, and I understood — the whistle and the ball-tracker do not speak the same language.
(Context)
There is much misunderstanding about what DRS is. Many think it is a technology — a camera, a software. In truth DRS is a protocol, a framework, where three separate technologies work together. First, Hawk-Eye or Virtual Eye — the tracking system that estimates the ball's trajectory. Second, UltraEdge — the device that detects the sound and vibration at the moment the ball touches bat or pad. Third, replay and ball-spin visualisation.
In 2026, Channel Four first demonstrated this technology experimentally during an England-Pakistan series. But formally, the ICC introduced DRS in 2026 during a Sri Lanka-India series. Initially each innings had two reviews; later in 2026 it was raised from two to three. In July 2026 the ICC permanently approved DRS in all Tests, ODIs and T20Is.
But inside this protocol there is a hidden crack that few discuss. The entire DRS system is built on one core assumption — that the ball's trajectory does not suddenly change at a given moment. But in reality the ball skids, hits the seam, changes direction through friction on the grass. Hawk-Eye tracks that trajectory for roughly a hundred frames, then estimates the post-impact segment with a mathematical model. This estimate is what we call 'Umpire's Call'.
The VAR I saw in Russia did not argue; it showed me my blind spot. In cricket it is more complex. Here technology does not merely show, it decides. And at the moment of deciding, it takes refuge in the letter of the law, not its spirit.
For me, the easiest way to understand this is to think from the umpire's point of view. An umpire on the field takes a decision in one-hundredth of a second — where the ball pitched, whether it touched the bat, when it hit the pad, how much of the line, how high. He sees all five at once. If DRS cannot remove even one of those five from doubt, then its very existence is in question.
And that is where the real story begins.
(Core Analysis)
Let us start with a specific example, because instead of general talk we need to enter one specific decision.
Suppose a delivery. The pacer releases from off stump, the ball pitches outside leg stump, then turns in toward the stumps. The batsman blocks with the pad. The on-field umpire gives him out. The batsman reviews. Ball-tracking shows the ball pitched outside leg stump — but by the ICC rule 'pitching in line' is sometimes fine if the ball is going toward the stumps. The impact falls in-line. And at the moment of hitting the stumps, the tracking shows the ball is just inside the stump, but barely.
Now comes the magic word. If ball-tracking shows more than half the ball would enter the stumps, the decision stands (out). If it shows less than half would enter, the on-field umpire's decision stands — meaning if he gave it out, it stays out; if he gave it not out, it stays not out.
This is 'Umpire's Call'. But this name is actually a misnomer. Because it is not the umpire's decision, it is the decision of the technology's limitation. When ball-tracking is not certain the ball would hit the stumps, it evades responsibility and hands it back to the umpire.
I get stuck at this point. Take the same delivery, same pitch, same batsman. But this time the on-field umpire is a different person. One's perception may judge a ball slightly outside the stump as in-line; another's may not. Now if ball-tracking shows the ball enters less than half the stump, the decision depends on which umpire is on the field.
That is, the same ball, the same tracking, but a different outcome — solely because the umpire changed. In the age of technology, this inconsistency is the biggest question for me. We brought in technology to create consistency. Yet the very rule called 'Umpire's Call' is the opposite of consistency.
I believe three major changes in DRS history deepened this inconsistency.
The first is the 2026 decision to increase reviews. Going from two to three meant teams began taking more 'guess-based' reviews. Once they thought a review was a precious resource, to be used only on certain errors. Now with three, a team can play one review as a gamble. This culture of gambling has gradually influenced the game — a batsman who misses the ball now first looks not at the umpire but at his partner, asking 'shall we?'
The second change is the abolition of the soft signal. Earlier the umpire gave a decision on the field, then the review. Now often the umpire does not decide, the review simply goes to the third umpire. This gradually erodes the umpire's authority to stand on the field.
The third is the question over ball-tracking's accuracy. Hawk-Eye claims a margin of error of two millimetres. But in reality, when the ball hits the seam, or changes speed through friction on the grass, that margin grows much larger. A 2026 test showed that analysing the same delivery from different camera angles produces different results in about three percent of cases.
Now the question — is three percent small? A Test match has roughly two hundred deliveries. Three percent means six deliveries where the decision could be wrong. And one of those six can change a match's fate.
I have witnessed this myself. It was a one-day match in 2026. I was sitting in the commentary box. An LBW review came. Ball-tracking showed the ball exactly at half the stump. The third umpire stared at the screen for ten seconds. Then he gave the decision — out. The match's result changed.
After the match I spoke to that third umpire. He said, 'I trust the tracking, but when the ball comes exactly at half, my own judgement does not work. I only follow the letter of the rule.' That sentence stuck in my mind. Technology came to expand the umpire's vision, but in the end it turned him into an instrument of the rule.
Here I notice a strange thing. In football's VAR the offside line is drawn by computer, but the final decision is taken by a human. In cricket, ball-tracking itself decides, and the third umpire merely announces. This difference, though small, is enormous.
To me there is a fundamental conflict in cricket's DRS — the conflict between dialectic and certainty. Umpiring never gives a hundred percent certainty. An umpire judges a ball on twenty-two yards in only three dimensions — length, width, height. But DRS demands a hundred percent certainty. That demand is the root of the problem.
Let me give an example. Suppose the ball pitches right in the middle, hits the seam, changes direction. Hawk-Eye measures this deviation. But the problem is, the deviation depends on the position of the seam, the friction of the pitch, the humidity of the air. The camera can see none of these three. The camera only sees the result — where the ball went from and to. What happened in between is a mathematical estimate.
That is, DRS's ball-tracking is actually a 'black box'. Give the input — where the ball pitched, where it hit — get the output, whether it would hit the stumps. We cannot see the process in between, we only believe.
And this belief is cricket's biggest risk today. Because where there is belief, there is no question. And where there is no question, there is no correction.
I have watched umpiring for thirty-six years. I have seen an age when a decision was the decision of a human eye. I have seen humans err, apologise, learn. But when the machine errs, who apologises? The machine does not apologise, it just processes the next ball.
One thing always troubles me here — where is the success of DRS in cricket actually measured? We say wrong decisions have decreased. But have they really? Or has the location of error merely shifted — from umpire to technology? Once humans erred, now the system errs, and we accept it as 'margin of error'.
I remember, in 2026 when the stadiums were empty, I was commentating on Borussia Dortmund against Schalke. Signal Iduna Park had zero spectators, and referee Deniz Aytekin's whistle echoed. I logged twenty-two fouls, four yellow cards, and the players' shouts. That empty stadium taught me that silence can be the loudest decision.
In cricket the same is happening, but differently. Here the gallery is full, but at the moment of decision that gallery falls silent. Because everyone looks at the screen. No one looks at the umpire.
This silence is DRS's biggest impact. Once at the moment of decision the gallery would roar — for or against the umpire. Now at the moment of decision the gallery looks at the screen, waiting. In those few seconds of waiting the emotion of the game accumulates, then suddenly explodes — for or against the technology.
To me this moment of waiting is the most 'cricket'. Because here the game stops, but the tension grows. And that tension no longer belongs to the umpire, but to the technology.
(Contrarian Angle)
Now I say an uncomfortable thing, which many may not like.
I believe DRS's biggest criticism — that it destroys the naturalness of the game — is actually not a criticism of technology, but of how we use it.
Let me be clear. I am not saying DRS is bad. I am saying DRS's current use is bad. The difference matters.
I saw VAR in Russia, launched the digital whistle at England's U-17 World Cup, and watched the rise of DRS in cricket. From these three experiences I understood one thing — technology is never neutral. Technology always carries its maker's assumption. The assumption in ball-tracking's algorithm that the ball does not change direction on hitting the seam is an assumption — a simplification of reality. And every simplification creates a possibility of error.
But here there is a counter-argument I respect. Many say that before technology umpires erred more, and those errors often seemed partisan — especially outside the subcontinent. In that era a smaller team against a bigger team suffered umpiring bias, visibly. DRS at least reduced that suspicion.
This argument is true. I admit it. DRS has greatly reduced the suspicion of umpiring bias. No one now hunts for conspiracy stories in a secret room. Decisions happen on screen before everyone. Transparency has increased.
But my question does not stop here. I ask — are transparency and accuracy the same thing? A decision can be transparently wrong. Seeing a wrong decision on screen before everyone — does that reduce the error, or merely legitimise it?
For me this is the biggest conflict. DRS does not hide error, that is good. But instead of admitting error, it packages it as 'margin of error'. And we accept it, because the number looks small.
But to the batsman who falls victim to 'margin of error', that number is not small. To him it is an innings, a series, sometimes a career. I can never be neutral at this point, because I have seen the eyes of the batsman standing on twenty-two yards.
Here is my second conflict. When I challenge technology, many tell me — you are on technology's side, you brought the digital whistle. To be honest, I am on technology's side, but against blind faith in technology. These are two different things.
I launched the digital whistle because I believe technology can help the umpire. But I never believed technology can replace the umpire. The difference between these two is the centre of today's debate.
And one more thing must be said. DRS's biggest criticism actually comes from the losing side. No one criticises DRS after winning. This selective criticism proves the debate is not about technology, but about results. And a debate about results is never technology's fault.
Yet I have one specific complaint, which is result-neutral.
It is this — in DRS's current framework, teams' number of reviews is limited, and this limit often creates dramatic decisions. If a team loses two reviews, it cannot challenge the third error. That third error can occur at the match's most important moment. This system essentially rewards strategy over decision accuracy.
In my view this is the core flaw in DRS's design. Getting a correct decision should not depend on luck, but on strategy. Yet in the current system teams must learn to 'save' reviews, just as they learn to save timeouts or powerplays in cricket. The truth of a decision has become a limited resource, to be used strategically.
Now think — the team skilled at saving reviews gets more correct decisions. The less skilled gets fewer. But in cricket, should getting a correct decision be a matter of skill? Or is it everyone's right? I believe the latter.
(Takeaway)
A question circles in my mind, whose answer I have not found.
I think, where will DRS go in the next ten years? Today there is ball-tracking, UltraEdge, Snicko-meter. What comes tomorrow? Perhaps a fully automated umpire — no human, just cameras and algorithms. One ball, one decision, zero seconds of delay.
I do not panic at this future, but I am apprehensive. Because I know technology can give a correct decision, but not a correct game. The beauty of the game is not in the correctness of the decision, but in what humans do at the moment of decision.
At fifty-two, standing here, I still hear the old whistle beneath every new replay. That whistle was never perfect. But a human blew it. And in that human's hands was the ability to apologise — which no machine has.
Now I make a proposal, which many may not like. I do not want DRS abolished. I want DRS's framework changed. My proposal is threefold.
First, the name 'Umpire's Call' should be abolished. Instead let it be called 'Tracking Uncertainty'. Changing the name changes the understanding. People will understand it is not the umpire's decision but the technology's limitation.
Second, the number of reviews should become a universal right rather than a strategic resource — at least when the margin of the decision is under two millimetres. If tracking cannot say whether the ball will hit the stumps, that is technology's limit, not the team's fault.
Third, after every DRS decision a transparent report should be published — what was tracked, what was estimated, and the probable error of that estimate. When people know, they trust; and where there is trust, suspicion decreases.
I know these proposals are controversial. But I am used to giving controversial decisions, because I have stood on twenty-two yards and given decisions. And I know a decision is never perfect, but the human behind the decision can aspire to be.
I leave the final question to everyone — if technology can decide through ball-tracking, why do we still keep a third umpire? Why do we not hand decisions entirely to the machine?
There is only one answer. Because we know the machine can never apologise. And without apology the game is not a game, it is merely an account.
So DRS can never be our final word. It is only a question — which it asks us anew every match. And the answer to that question must be given by humans, standing on twenty-two yards, in zero point one second, imperfect yet striving for justice.
That is real umpiring. Technology is its mirror, not its face.


Related Players
Popular Reads
Record Auction Fees, the Invisible Review Ledger2026-10-03
Suitcases and Release Clauses: Who Wins Cricket's Transfer Market, and Who Stays Silent2026-10-03
Cricket Transfers on a Blockchain Ledger: The Invisible Accounting of the IPL Auction and the Politics of Smart Contracts2026-10-03
Cricket's Blockchain Economy: Auditing Fan Token Prices Against the Replacement xG Gap2026-10-03
Cricket's Transfer Ledger: Auctions, Retention and the New Blockchain Arithmetic2026-10-03
The Arithmetic of Pause: Cricket's Clock, Silence, and a Nation's Breath2026-10-03
Recommended
Suitcases and Release Clauses: Who Wins Cricket's Transfer Market, and Who Stays Silent2026-10-03
The Country of an Unfinished Innings: Bangladesh's First Super Eight and the Tournament's Silent Scoreline2026-10-03
Cricket's Blockchain Economy: Auditing Fan Token Prices Against the Replacement xG Gap2026-10-03
The Training Ground's Clock: Counting the Invisible Twenty-Two Minutes at the T20 World Cup2026-09-29
The Powerplay Zone Map: The Second-Ball War Nobody Watches in T20's First Six Overs2026-10-01
Blockchain and Cricket Governance: The New Chapter of Digital Ledgers2026-10-01
Grey Sediment: The Three Layers Buried Beneath Bangladesh's Under-19 Success2026-09-30
Recommended
Over 17: South Africa's Last Belief on a Barbados Night2026-09-29
Suitcases and Release Clauses: Who Wins Cricket's Transfer Market, and Who Stays Silent2026-10-03
Cricket's Clause Country: What the ₹27 Crore Auction Bid Actually Buys, and Who Holds the Release Signature2026-09-26
What the Scorecard Hides: India's Dropped-Catch Over and the Breath of the Kotla2026-10-03
The Left-Arm Spinner Born on Khulna's Empty Grounds: Notebook Evidence of Tahsin Ahmed's Academy Journey2026-10-03
The Shadow After the Last Over: The Human Ledger of Fast Bowling and James Anderson's Farewell2026-10-01
Not the Last Over but the 16th: A Data Audit of the Barbados Final and the Auction's Wrong Address2026-09-27
Recommended
Twenty-Seven Crore at the Auction, Fourteen Overs at the District Ground: Where the Real Signal Sits in Cricket's Transfer Window2026-09-29
The Quiet War of the Middle Overs: Where the Regular-Season Scoreboard Stops Telling the Truth2026-09-28
The Clock Inside the Drill: Bangladesh's Tournament Problem Is a Calendar Problem, Not a Talent Problem2026-09-26
Where Did England's Batting Lose the Mirpur Pitch: A Spin-Ledger Audit2026-10-01
Bangladesh's Wrong Arrow in T20: The Real Crack Is Overs 7 to 15, Not the Powerplay2026-09-30
Recommended
The Arithmetic of Pause: Cricket's Clock, Silence, and a Nation's Breath2026-10-03
Roles Lost in the Noise: What the BPL Auction Buys and What It Forgets to Buy2026-10-03
The Ledger and the Broken Notebook: What Blockchain Actually Records in Cricket2026-09-27
The Shadow After the Last Over: The Human Ledger of Fast Bowling and James Anderson's Farewell2026-10-01
Accounting for Lost Pace: Bangladesh's Fast-Bowling Workload, Calendar and Contract Gaps2026-09-27
The 5-Taka Digital Dream: How Bangladeshi Startup Nodal Disrupts Urban Housing Economics2026-10-01
