DRS in Asian Cricket: The Umpire's Eye, the Pixel and the Geometry of the Law

On the evening of March 19, 2026, at the Melbourne Cricket Ground, Bangladesh met India in a World Cup quarter-final. In the 40th over, a Rubel Hossain delivery travelled toward Rohit Sharma; many analysts felt it sat near waist height. Umpire Aleem Dar gave no no-ball signal. Rohit Sharma went on to make 137, India won by a wide margin to reach the semi-finals, and Bangladesh's World Cup run ended.

Ten years have passed, and the argument has not. But if we argue only about whether the umpire was wrong, we lose the real story. At the centre of a decision there is rarely one person; there is a system, an angle, an uncertainty. In my view, the whistle is never the story; the angle that was missed is the story.

Context: What the law asks, what technology can give

DRS, the Decision Review System, arrived not to replace the umpire but to assist him. After a first experimental use in 2026, it was gradually established across international cricket between 2026 and 2026. It rests on three pillars — ball tracking, UltraEdge and HotSpot. Each has its own error margin, and those margins create the controversy.

Under the rules, a Test side gets two reviews per innings, renewed after 80 overs; ODIs and T20s allow one. That number alone shows how limited the right to decide really is.

The most contested part of DRS is "umpire's call." When ball tracking shows the ball clipping the edge of the stumps, the decision returns to the on-field umpire. In other words, the technology does not give a certain answer; it says, "We are not certain enough, so the person on the field is final." That rule is not an accident — it is a conscious admission of uncertainty.

In Asian cricket, DRS carries a different weight. On subcontinental pitches the ball bounces lower, spin dominates, and the projected path is harder to estimate. The uncertainty in the ball-tracking model rises — and as uncertainty rises, so does the number of umpire's calls.

Core analysis: the five layers of one decision

This is where my interest lies. What does the law ask, and what can the camera see — and what happens in the gap between them? I want to split a decision into five layers.

The first layer is the geometry of LBW. It is a three-dimensional problem. When the ball strikes the pad, its path, bounce and spin together form a probability envelope. Ball tracking can locate the centre of that envelope, not its edge. That edge is exactly what "umpire's call" is. Technically, the ball-tracking error margin is roughly half a ball's width — a small margin. Yet small margins decide matches.

The second layer is the umpire's viewpoint. He stands about 22 yards away. A ball at 140 km/h reaches him in roughly 0.4 seconds — within which eyes, brain and decision must all finish. Conscious human reaction time is usually 0.2 to 0.3 seconds. The arithmetic leaves almost no time at all.

The third layer is occlusion. The bowler's arm, the batter's leg, the wicketkeeper's body — together they hide part of the ball's path from the umpire. A camera can watch from twelve angles; the umpire watches from one, and partially. Here my favourite line applies: it is not an eye problem, it is a geometry problem.

The fourth layer is pressure. In a packed Asian stadium, amid the noise of a hundred thousand fans, a decision at a defining moment is never easy. After a knee injury ended my semi-professional career in 2026, I began referee analysis — and learned there that the decision of the person standing on the field is not the decision of the viewer on the sofa. Authority and perspective change when you stop playing and start adjudicating.

The fifth layer is the broadcast interface. On television the viewer sees the final ball-tracking image, which looks utterly certain. But that image is the centre of a probability envelope, and the uncertainty around it never appears on screen. So the viewer concludes, "The technology knows; the umpire does not." That is the deepest illusion.

From my seventeen years of watching the game, I would say this: DRS does not settle controversy, it relocates it. Once the argument was about the umpire's eye; now it is about the tracking margin, the camera frame rate and the umpire's-call rule. The question stays the same; only its address changes.

One statistical reality is worth keeping in mind. Across recent international matches, a large share of reviewed decisions — in my rough estimate, 30 to 40 per cent — end in umpire's call. The technology often cannot decide by itself. I hold a reasonable confidence here: reducing the ball-tracking error margin would lower that figure, but never to zero. Uncertainty is not a flaw in the technology; it is part of reality.

In the Asian context there is another dimension — team strategy. Sides such as Bangladesh, Pakistan and Sri Lanka often review on emotion, while Australia or England frequently calculate. On Asia's spin-friendly pitches, LBW reviews pay off more, because bounce uncertainty is greater in a spinner's tracking.

The contrarian angle: emotion versus law

Now to the part that is usually skipped — emotion versus law.

Fans want a certain answer. They want technology to declare: out, or not out. But cricket's law is written in the language of probability. The law never says "the ball will hit the stumps"; it says whether the ball was likely to hit the stumps. That distinction is the most neglected of all.

Another contested idea is that "the umpire was blind." It is easy, and it is wrong. The umpire is not blind; he is watching from a limited angle. The angle he did not have, the camera did — and the camera showed it. Here lies the question of responsibility: where the system draws a limit, the individual's duty is to make the best decision within that limit. Unless we separate the system's limit from the individual's error, we can never judge fairly.

I would draw a comparison here. Football has lived the same story with offside. Semi-automated offside arrived at the 2026 Qatar World Cup, yet it did not end every argument — because the line, the frame and human interpretation still leave questions. Cricket's DRS walks the same road.

One more thing deserves thought: is DRS's benefit equal for all teams? In much of Asia, especially for smaller boards, the cost of the technology is a major barrier. Where technology exists, decisions are more accurate; where it does not, people must be trusted. Fairness in the game becomes entangled with the unequal distribution of technology.

Not a conclusion, but a direction

Looking forward, I have one clear view. The next step for DRS should be transparency — showing the viewer the uncertainty envelope in ball tracking, publishing the statistics of every review, and explaining the umpire's-call rule more clearly.

If technology is truly to help the umpire, then its uncertainty must be made public too. A system that does not know its own limits does not help the umpire; it adds pressure.

I leave the final question open: if the uncertainty of the ball-tracking model is proven, then whose decision is final — the person on the field, or the pixel? Cricket has not yet answered that.