Umpire's Call: Inside the Grey Zone of DRS Where the Decision Becomes the Question

Melbourne Cricket Ground, March 19, 2026. A World Cup quarterfinal. Bangladesh against India. Rubel Hossain's delivery arrives above waist height; umpire Aleem Dar signals a no-ball. Rohit Sharma stays at the crease. He goes on to make 137. India 302/6, Bangladesh 193—India win by 109 runs and reach the semifinal. Afterwards, the Bangladesh Cricket Board sends a formal protest to the ICC.

That night, nobody asked the most important question loudly. The question was not, "Did the umpire make a mistake?" It was: why could that decision not be reviewed? The answer is simple. The no-ball was not covered by DRS. The technology was in the stadium; the door was shut. I began with 1,058 incidents, and the anomaly was hiding in plain sight: the decisions that generate the most argument are often the ones least open to review.

DRS—the Decision Review System—entered cricket slowly. A first trial in 2026, then gradual adoption between 2026 and 2026. The architecture has three layers: the player review, the third umpire, and ball-tracking or replay technology. Two reviews per innings in Tests; one or two in ODIs and T20s depending on format and tournament—the limit itself has been changed by the ICC more than once. A successful review is retained in some formats; a failed one is lost.

For an LBW review there are three elements: where the ball pitched, where it struck the batter, and whether it would have hit the stumps. If any one of them carries doubt, the decision survives. This is where "umpire's call" lives—under the ICC framework, if ball-tracking shows the ball would have hit the stumps but the calculation falls inside the technology's margin of error, the on-field umpire's original call stands.

That margin is not only a technical limit; it is a conscious decision. Somebody decided how much uncertainty is tolerable. The ICC's explanation is that DRS was introduced to catch the "clear howler," not to deliver perfect justice. The logic is clear: protect the umpire's authority, keep the game moving. But a logic that holds at the institutional level does not hold in the stands.

It is worth understanding the gap between what ball-tracking manufacturers claim and what happens on the field. A system like Hawk-Eye tracks the ball's path from several cameras and projects its future—at millimetre range. Millimetre range does not mean perfect. If the ball spins, if the bounce changes, if the ball blurs in a frame, the projection shifts. Umpire's call hides inside that projection.

Behind ball-tracking sit multiple high-speed cameras recording hundreds of frames per second. Each frame is used to mark the ball's position and estimate its path. The problem is that when the ball pitches, dust, grass or shadow make marking difficult. The uncertainty of those few frames returns later as the margin.

Impact carries its own uncertainty. How far in front of the crease the batter stood is calculated from ball-tracking and pitch maps. A decision taken on one side or the other of a boundary line means two different outcomes from the same contact—one rule, two interpretations.

The problem is not accuracy; the problem is visibility. On the big screen the fan sees a box reading "Umpire's Call," but not how far the ball was from the stumps, or where exactly the margin was drawn. The information that decides the call stays hidden from the eyes that care most. My objection is here—not against the rule, but against the opacity of the process.

The rulebook gave me a verdict; the freeze-frame gave me a question. The freeze-frame showed the ball heading toward the stumps—but "how much" stayed open. Who decides how much is enough? The on-field umpire? The third umpire? The technology provider? Or the person who wrote the rule?

There is a less-discussed angle here, and I want to separate incompetence, incentive and conspiracy. Ownership of ball-tracking technology and broadcasting often sit under the same corporate roof. A supplier can also be tied to broadcast interests. I am not claiming results are manipulated—I have no evidence of that, and accusation without evidence is not my method. But when a commercial relationship supplies the instrument of judgment, transparency in setting its margin should be its strongest defence. That transparency is the scarcest thing of all.

Bangladesh's experience sharpens the question. Since Melbourne in 2026, many DRS moments have accumulated in the memory of Bangladesh's fans—a review lost to umpire's call on an LBW, the frustration of a review never taken. In every case the feeling is the same: "The ball was hitting the stumps, so why is it not out?"

A double standard operates here, but not inside the rules—inside feeling. When a decision goes the fan's way, the technology is praised; when it goes against, the technology is doubted. DRS was never a neutral machine, because a person operates the machine and an institution wrote the rule.

There is a neglected angle around review limits. A limited number of reviews forces every captain into calculation: on which decision do I take the risk? That calculation is not a field decision; it is a game of probability, in which the likelihood of umpire's call floats in the air. When a captain reviews, he is not deciding; he is betting. And when the bet loses, he loses not only a decision but an asset.

The analysis runs at three levels. The first is technology: what ball-tracking can and cannot say. The second is rule: how the ICC set the margin, the review limit, and the definition of "clear error." The third is use: how the decision reaches the fan in the stadium, on the screen and on the broadcast. Of the three, the third is the most neglected.

From years of watching matches, one thing is clear: DRS's biggest failure is not the wrong decision—it is the unexplained decision. The umpire never announces on the field why a call stood. In the stadium the fan sees only text, not reasoning. In football, at least some announcements follow VAR; in cricket, even that is absent.

With catches, the "soft signal" question is more complex. When the third umpire must decide without conclusive proof, the grey zone widens. The contact point of hand, ball and ground is not always clear on camera. In that uncertainty, too, the on-field call survives—the same pattern: doubt means the field decision wins.

Is the ICC open about the limits of its technology? Do ball-tracking companies publish detailed methodology for their accuracy? Not all of it. Some claims appear in the media; the detail does not. Where the evidence in a system of judgment is partly hidden, suspicion is natural—and not unreasonable.

In tennis, Hawk-Eye is used differently: the screen shows the ball's mark and the boundary together, and the fan can see for themselves whether the ball was in or out. In cricket, that is not shown. The same technology, two kinds of transparency—this is not a limit of technology but a limit of decision-making.

Criticism of the umpire's call margin is not new. Coaches, captains, commentators—all have at times demanded the margin be reduced or removed entirely. Each time the ICC has given the same argument: technology has limits of accuracy, and deciding beyond them creates a new injustice. The argument is partly true, but the question remains—who measures that "limit"?

On the broadcast, the decision arrives in a few seconds of graphics. The fan has no time to ask. Debate spreads on social media, but it is information-poor, because the information is never fully disclosed. So the argument is not about technology; it divides by team.

Cost is another layer. Not every cricket board can afford DRS—smaller associations are often left out. The same game therefore runs under two systems of judgment: one where technology exists, one where it does not. The question of equality appears here too.

Now the other side. Suppose the ICC removed umpire's call tomorrow and let ball-tracking decide everything. Would fans be happy? For a while. Then a new complaint would arrive: "The tracking is showing it wrong." Because perfect technology does not exist; only claims of perfection do. And the ICC's core objection is valid: the game is run on umpires, and technology is only a tool to correct clear errors. Remove umpire's call and the umpire's role itself comes into question.

So the real conflict is not technology against umpire—it is secrecy against accountability. My lesson from football: VAR arrived promising transparency, and ended up confusing fans further, because the process was never explained. Cricket is walking the same road, only more slowly.

Another counter-intuitive point: umpire's call may be protecting the game by accident. If every millimetre-based decision were final, batters would live in uncertainty on every delivery, and review breaks would destroy the pace of ODIs and T20s. Uncertainty here is not the product of bad technology—it is an unstated decision to protect the rhythm of the game.

In the Bangladesh context there is another layer—emotion. Since 2026, suspicion has settled in the mind of the fan in every big match. That suspicion is not groundless, because it was born from experience. But suspicion is never judgment. The referee's eye means evidence, not feeling—and that is the hardest lesson of all.

Still, the process can be improved, and must be. Three proposals, in order of importance. One: show the real ball-tracking calculation on the big screen—how far the ball was from the stumps, where the margin sits—so it reaches the fan. Two: the ICC should publish ball-tracking accuracy data regularly, with methodology. Three: the third umpire's decision should come with a brief reason announced on the field.

An ideal system adds two more steps: publishing the complete ball-tracking data after every review—pitch point, impact point, projection; and independent audits, in which accuracy is tested regularly and results are made public.

A final thought on the future. For front-foot no-balls, automated checking is already in use in some series—the third umpire watches directly, no player review needed. This model may be the next step: where the machine is certain, the decision belongs to the machine; where it is uncertain, transparent explanation follows.

Transparency in decisions does not weaken them. It is the reverse—an institution that can admit its own limits earns more trust. A hidden margin destroys trust, and no system of judgment survives without trust.

Cricket is still learning how to run technology and human judgment together. In this learning phase the greatest risk is treating technology as infallible. What the machine shows is evidence; what the machine cannot show is a limit. Fail to understand that difference, and umpire's call will remain a name for controversy forever.

The referee's eye is less a gift than a burden of proof. In cricket that burden still rests on the fan's shoulders, and the question stays open: if technology judges, who answers for the judgment?