The Third Umpire's Silent Room: DRS, Umpire's Call and the Birth of a Rule

Dusk settled over Kensington Oval in Barbados. On the giant screen flashed that familiar line—'Umpire's Call, Wickets: Umpire's Call'. Under the floodlights, the crowd groaned in unison. The ball tracking clearly showed the ball brushing the stumps, yet the batsman was not out. The on-field umpire kept his decision. The reason: the portion of the ball striking the stumps was 'clipping'—an impact not certain enough to overturn the on-field call. Where technology says yes, the rule says no.

That moment sits at the heart of modern cricket's most misunderstood decision system. I have watched the game from close to the boundary for fifteen years, reading the players' expressions and the umpires' gestures together. Based on my years of watching matches, when a crowd roars over 'Umpire's Call', it is really raging against technology—though technology is not the culprit here. The culprit is that fine distance deliberately inserted between the technology and the rule. I write that line again, the foundation of my method: rule first, emotion second.

The hook makes one thing clear—since DRS arrived in cricket, controversy has not reduced; it has moved off the pitch into the review room and the grey zones of the rulebook. In football, VAR did much the same. I will return to that comparison.

Context: The Birth of a Rule and Its History

To reach the heart of the debate, we must first know where the system came from. The Decision Review System, DRS, was first used in full at international level in 2026, in a Test match between India and Sri Lanka. Earlier, around 2026, some technology was trialled experimentally in domestic cricket in England, but the ICC never formally recognised it. Initially players had three reviews per innings; this was later cut to two, so that teams would not burn reviews carelessly and drag the game on. But however the number changed, one thing did not—the on-field umpire's decision is final, unless it is proven a 'clear error'.

That single word hides the core: 'clear error'. The ICC's playing conditions and the MCC's Laws of Cricket make this explicit—a review overturns a decision only when the evidence is beyond doubt. When doubt remains, the on-field decision stands. That one sentence is the parent of the controversy called 'Umpire's Call'.

In July 2026 the ICC made a major change—it removed the 'soft signal'. The soft signal was a practice where, in doubtful cases like a catch or run-out, the on-field umpire first gave a 'probable decision', which the third umpire then confirmed or overturned on evidence. Its flaw was obvious—an umpire who was not certain was forced to give a decision, and if the evidence was unclear, that wrong decision survived. After the soft signal was removed, the third umpire must now decide directly, on their own judgment. Responsibility became clearer, but a new pressure emerged—the third umpire now carries the entire weight of the decision alone.

Without this history, DRS cannot be understood. DRS was not born on one day, in the hands of one technology company. It was built step by step, revised after every controversy. And behind every revision was one question—how should power be divided between technology and the human?

Core Analysis: Ball Tracking, Margins of Error, and How the Third Umpire Reads

Now to the part where the real technical truth hides. Ball-tracking technology, mostly known as Hawk-Eye, works on a simple principle—several high-speed cameras around the ground capture the ball's position simultaneously, and triangulation then computes its three-dimensional path. Pitched point, bat impact, and trajectory towards the stumps are analysed as three separate stages.

Here the first problem appears. Every measurement carries an error. The number of cameras, the frame rate, ball spin and lighting conditions all affect precision. Hawk-Eye authorities openly admit their computation is not perfect; every measurement has a fixed 'margin of error'. So the trajectory shown may not be exactly the real path—it could be somewhat off.

From that margin of error, 'Umpire's Call' was born. If the ball is projected to hit the middle of the stumps, then whatever the error, the ball is hitting—that is certain. But if the ball grazes the very edge of the stumps, then within the margin of error it may or may not hit. That zone of uncertainty is called Umpire's Call. By rule, in that zone the on-field umpire's decision stands.

One fact must be stated, which many viewers do not know—Umpire's Call is not a technical decision, it is a political one. Ball tracking delivers objective data at that moment, but the line marking that data as 'uncertain' is drawn by humans—the ICC cricket committee, on which former players and umpires sit. How much uncertainty is acceptable is decided at a discussion table, not in a lab. This sentence makes us see the whole debate anew.

Now to how the third umpire reads. The third umpire receives several feeds—ball tracking, edge-detection like UltraEdge or Snicko, replayed footage and audio. But even with the data, the interpretation is in human hands. In edge detection, a spike or sound can also occur as the bat passes near the stumps or as the ball hits the pad. The third umpire must then judge—was that sound the bat, the pad, or the ground or pocket? That judgment is not made by technology; it is made by a person.

I opened the 110-page protocol again. Page 47 explained the whole restart. Just as a written restart rule and its on-field application leave a gap, so does every review's written protocol and the third umpire's interpretation leave a gap. That gap is the real field of investigation for an analyst.

Here I bring in an innocent statistic that clarifies the on-field truth. Scanning VAR data across several international tournaments reveals that a large share of reviews actually end in 'Umpire's Call'—that is, a big gap between the sides' expectations and the final result. Many reviews that look like 'obviously out' to a viewer become 'uncertain' under the rule. That gap creates the outrage.

Personally, the most fascinating thing to me is how batsmen take reviews. When a batsman feels the ball on the pad, he runs a mental calculation—was it in line? Did it pitch on the leg side? He knows that on the in-line question, Umpire's Call is more likely. So many experienced batsmen hesitate to review an in-swinger. This is not a decision of technology but of experience. Every review is thus a two-layer judgment—first the on-field umpire's, then the batsman's own inner one.

Here a gap between law and application deserves note. The law says a clear error changes the decision. But in practice 'clear' is unclear. One third umpire may think the evidence is enough, another may see the same footage and think doubt remains. Two umpires, the same technology, different decisions—this proves DRS is ultimately not a technological system but a human one that uses technology.

Contrarian Angle: The Truth the Gallery Refuses to Accept

When a crowd roars at 'Umpire's Call', it expects a simple logic—ball hits stumps, out; otherwise, not out. But cricket's rule refuses this simple logic, and there is a deep reason. The on-field umpire is part of the game—his physical presence, his decisions create a reality for the players. If technology overturned the on-field umpire on every review, the on-field umpire's existence would gradually become meaningless. Umpire's Call is therefore not just a technological guard but a conscious decision to protect the on-field umpire's authority.

Here I feel the problem lies in how people see it. The Carabao Cup trial did not invent VAR; it revealed who could read the rule. In the same way, DRS did not create controversy—it merely exposed who understands the rule and who does not. A viewer who asks, 'The ball hit the stumps, so why not out?' is really missing one line of the rule, which states that when evidence is insufficient, the decision stands.

Another thing the gallery forgets—technology is not neutral. Hawk-Eye tracking, UltraEdge sound detection, all obey a specific company's settings and limits, and those limits are set through negotiation with the governing body. Who sets the boundary of trajectory uncertainty, who draws the line between a true spike and a doubtful sound—the answers are not in the company's lab but in the ICC's room. So behind every 'neutral' technology hides a human decision.

Here I return to the cricket–football comparison, because a large part of my experience comes from football officiating. In football, VAR's guiding principle is 'clear and obvious error'. Cricket's Umpire's Call carries the same philosophy. In both sports, the governing body wanted to protect the on-field umpire's authority; in both, technology was kept as an 'assistant', not a final judge. But there are differences too. Cricket shows more trust in technology than football—because many cricket decisions revolve around a definite ball path that can be computed. In football, decisions are largely interpretative—whether a contact was 'enough' is something maths cannot answer. DRS is therefore more reliable than football's VAR, yet surprisingly both produce the same kind of outrage.

The Contract That Makes the Headline, the Subtle Clause That Makes the Investigation

My writing has a principle—a transfer fee is the headline, but the sell-on clause is the investigation. In the same way, the headline of a dismissal is the batsman's name, but the real story hides in the subtle clause that draws the line between out and not out. Since the abolition of the soft signal in 2026, the third umpire faces a pressure that is still not fully proceduralised. When a third umpire sits between the loud stump-mic spike and the doubtful ball tracking, his decision is not the output of a calculation—it is a judgment.

Referee's Eye | Scenario: Deep analysis of VAR—sitting in this groove, I see both cricket and football standing at the same crossroads. Both are moving towards automated technology. Cricket has already begun partial automation of LBW and ball tracking, where the on-field umpire only confirms the result. In football, semi-automated offside is already reality. If this continues, Umpire's Call may one day become history—technology will be so precise that the excuse of uncertainty will vanish. But what then? The question is not simple. Because removing uncertainty makes decisions more mechanical, and the game loses that human pulse—the umpire's voice, his firmness, his hesitation.

In my fifteen years of observation one thing is clear—the future of officiating lies not merely in technological precision but in finding the right balance between technology and the human. If a governing body makes technology the final judge, it errs. If it rejects technology entirely, it errs even more. That narrow middle path is the real challenge.

When a Rule Is Written, Who Writes It Is the Real Question

I keep returning to one question—who wrote this rule, who applies it, and who pays for it? The Umpire's Call rule was written by a committee of former players and umpires, applied by the third umpire, and paid for by both teams' players and millions of viewers. If no one reads this three-layer system carefully, every controversy will only grow. What the gallery sees is the result; what it does not understand is the process. My task is to bring that process forward, so that understanding replaces outrage.

That is why I refuse to stop at the on-field truth. In 2026, when football stopped, I learnt that law and the application of law are two different things. Every restart, every date, every amendment answers a specific need—and without knowing the history of that need, no decision's fairness can be understood. Today that line returns—a protocol before the eyes, and beside it a controversy. Read together, the truth emerges.

Takeaway: The Question Left for Tomorrow

I believe that in the next decade Umpire's Call will disappear entirely from cricket—technology will be so precise that the margin of uncertainty falls to zero. But then a new question is born—if technology makes all decisions, why keep an on-field umpire? The answer is not only in the viewer's hands; it is being written in the ICC's room. Standing at this crossroads, I have one request for the gallery—next time 'Umpire's Call' flashes on the big screen, pause for a moment. Because what you take for a mistake may be one of cricket's most honest decisions—one that says: when not certain, rule in favour of doubt. The game rests on this principle; technology is only its new language.