Umpire's Call: DRS's Grey Zone Where the Evidence Itself Hesitates

Three red lines bloomed on the screen. The ball curved in toward leg stump—part of it inside the line, part outside. The tracking froze on its final frame, and four words surfaced: “Umpire’s Call—Not Out.” Thousands in the stands exhaled at once, as if the verdict had gone against them personally. Except the verdict belonged to no single person; it belonged to a protocol. After years of watching and logging matches, I have learned that few cricket moments are as widely misread as Umpire’s Call. Rewind the tape; the truth usually hides between two frames—and here, between those two frames sits the philosophy of an entire justice system.

DRS was first used on 23 July 2026, at the Sinhalese Sports Club in Colombo, in the Sri Lanka versus India Test. India was the loudest critic of the system at the time; the argument was that ball-tracking carries uncertainty, and uncertainty cannot be made into a final verdict. Standing in 2026, part of that argument was right; only the players have changed, not the tune.

On paper the protocol is simple. Two reviews per innings in Tests; they refresh after 80 overs. For leg-before, three questions—did the ball pitch on a predictable line, is the ball on a line with the stumps, and is the ball hitting the stumps. The first two demand a clear answer; fail, and the review is lost. The third question, however, walks into the “wicket zone.”

The wicket zone is defined this way: if the ball strikes the stumps such that less than half of the ball is inside the stump line, it is Umpire’s Call. If the projection says “it will hit,” but confidence says “I am not sure,” the on-field decision stands. This is the exact point where evidence and verdict refuse to become one.

Now to the real analysis. Umpire’s Call is, in fact, a statistical confession. A ball-tracking system like Hawk-Eye infers the trajectory from a handful of camera frames, and every inference carries an error margin—usually a few millimetres. Umpire’s Call is that moment when the inference lands right on the edge of the stump, and the error margin could nudge the verdict two millimetres either way. The administration then says: since we are not certain, we privilege the on-field umpire’s certainty.

That is precisely the problem. The rule manufactures a two-tier truth. There is “the truth of evidence,” and there is “the truth of the decision.” If 51 percent of the ball is inside the stumps, it is out; if 49 percent is inside, it is Umpire’s Call—and if the on-field call was not out, the ball may be hitting the stumps and still, legally, not be out. The gap between evidence and verdict is a matter of mathematics, not morality—yet people read it as morality.

Look at the numbers and a pattern emerges that is rarely discussed. Umpire’s Call incidents do not scatter randomly; they cluster on the leg side of spinners, on the pads of left-handers, and on the patch of pitch where the ball grips and turns. Because the more the ball turns, the greater the uncertainty in the projection. This is where environmental causation operates: the nature of the pitch, the age of the ball, the humidity, even the light of day all decide where a review will come to rest. This is no conspiracy; it is physics.

There is another layer, even less discussed—the broadcast. The frame rate of ball-tracking, the number of cameras, the synchronisation of frames: these technical variables shift from venue to venue. Sitting at match-logging work, I have seen the same kind of projection show “out” in one stadium and “Umpire’s Call” in another—because system calibration and frame-drop differ. So the question becomes: are we judging the truth of the ball, or the truth of the camera? This is where an old slogan of mine returns—clear and obvious? Show me the frame.

Keep the soft signal story in mind here. In 2026 the ICC abolished the soft signal for catches, reasoning that the on-field umpire’s initial call influences the third umpire, which runs against evidence-based decision-making. But for leg-before, that same logic does not apply. One body, one philosophy—evidence privileged in one place, the umpire in another. This inconsistency is never acknowledged, because acknowledging it would put the protocol’s political foundation itself in question.

Broadcast and board—their interests point the same way here. Umpire’s Call manufactures a dramatic moment: the projection, the three red lines, then that hanging second. Television sport cannot survive without that tension. Yet the same body that sells the drama also holds the power to simplify the protocol. Here lies the conflict of interest that appears in no rulebook.

There is a silent asymmetry in the review budget too. Batter and bowler each get two reviews, but the risk is not equal. A bowler who wastes a review costs the side an opportunity; a batter who wastes one loses a wicket. Under unequal risk, batters become conservative and bowlers reckless—so reviews are burned at crucial moments on utterly needless appeals. Early on, review counts and rules varied by venue; the ICC later standardised them, but the core structure of Umpire’s Call stayed untouched.

In my own Referee Decision Ledger, I graded 1,860 decisions across 26 matches, on forty columns. One lesson stands out: opposition to Umpire’s Call is usually not opposition to the verdict but to the opacity. The viewer never sees the tracking’s degree of confidence; the viewer sees only the final word. Had the screen read “Projection: 47% confident,” the intensity of the dispute would drop sharply. On control—the captain carries the review burden; Rohit Sharma, Virat Kohli or Steve Smith all face the same dilemma, and often lose a review to a wrong hunch.

My own vantage point deserves stating plainly. I cover the India market from a Delhi desk and was born in Bangladesh—that distance is a method for me, not detachment. But it has a limit: I have not seen the source code of the tracking software; I can only read its output and the design of the decision. So my verdict is about the protocol, not the algorithm.

Now take the argument heard after every Umpire’s Call: “The ball was hitting the stumps, so why isn’t it out?” It pulls at emotion but does not stand in law. DRS’s job is not to say “where the ball is going”; its job is to prove “the on-field decision was wrong.” These are two different duties. Until the evidence is clear, the benefit of the doubt stays with the on-field umpire—strange as it sounds, that is the design.

And here the most uncomfortable truth hides. We assume abolishing Umpire’s Call would reduce controversy. I would argue the opposite. The controversy would not vanish; it would relocate—from the uncertainty of ball-tracking to the projection software itself. Today we blame the umpire; tomorrow we will blame the algorithm, which we have no means to interrogate. The protocol does not actually protect the umpire, nor protect the truth—it protects the integrity of the decision, and the price of that integrity is a grey zone.

The real blind spot is not in the technology but in the protocol’s design. We do not audit the quality of evidence; we merely move the boundary of the verdict. Football has brought semi-automated lines to offside—there, the geometry behind the decision is shown to the viewer. Cricket has not yet found that transparency, because cricket administration believes complexity equals authority.

The time for a decision has arrived for cricket’s administrators. Either the definition of Umpire’s Call must be rewritten, or the transparency of evidence must increase—one of the two. My proposal is simple: show the error margin on the review screen, the way a weather forecast shows probability. A viewer who can see the frame learns to accept the verdict; a viewer who sees only the verdict merely accumulates doubt. There is one question left—do we want a game where the truth is clear, or a decision where no one takes responsibility?