The Blind Spot of Umpire's Call: Where the Replay Stops, Truth Does Not

I have seen this match from three angles, and the truth is still in the replay. But the replay has a blind spot of its own — and that blind spot sits at the exact centre of the DRS argument in Asian cricket.

Hook: The ball that is not actually a ball

An LBW review. The on-field umpire says not out. On the ball-tracking screen, the ball clips the inside edge of the stumps and moves away. The big screen flashes: "Umpire's Call — Original decision stands." The stadium erupts, and within two hours the clip is everywhere. Almost nobody watching that replay and passing judgement knows that the ball they are being shown grazing the stumps is not a real ball. It is a prediction — a future drawn mathematically out of camera frames. That is precisely why umpire's call generates so much anger and so few real questions. The question nobody asks is the only one that matters: what is the camera actually seeing, and what can it never see?

I have watched this game for fifty years — as a player, as an official, then as a broadcaster. In that time I learned something no textbook teaches: controversy never rests on truth. It rests on protocol. And protocol is written by people, not machines.

Context: Where DRS came from, and who draws its limits

DRS formally entered the field on 23 July 2026 at the Sinhalese Sports Club in Colombo, in the India-Sri Lanka Test. It began as a Test-only tool, moved fully into limited-overs cricket around 2026-11, and reached T20 cricket later still. The system stands on three pillars: ball-tracking (Hawk-Eye and its cousins), edge detection (UltraEdge/real-time Snicko), and the older infrared Hot Spot, which many broadcasters no longer use at all.

The law looks simple. In practice it is not. In LBW, umpire's call operates in two places. First, if there is doubt about the line of the stumps before the ball hits the pad. Second — and this is the most contested — if the prediction says the ball will hit the stumps but the centre of the ball is less than half a ball's width inside the outer edge of the stump, that prediction is set aside and the on-field decision survives.

Then there is the 3.6-metre rule. If the point of impact is 3.6 metres or more from the stumps, the ball-tracking prediction is discarded entirely — only the point of impact is judged. The logic behind it is honest: from that distance, projecting the ball's path is beyond what the technology can reliably do.

Each side gets two reviews in ODIs and T20Is, three in Tests, with a top-up after 80 overs. But the number is not the real story. The real story is that every stage of this system — camera frame rate, the sensor that catches the ball's touch, the tolerance of the prediction algorithm — is written down nowhere public. The viewer sees a blue line and a green ball and assumes it is truth. That is where the trouble begins.

Core: Three angles, and the limit of each

My habit is to view any decision from three angles. I do it here too.

First angle — the television broadcast. Here we see smooth graphics, a perfect path, and a verdict. But broadcast ball-tracking is built from a fixed number of frames per second, and the path between them is interpolated — the moment between two images is estimated. When a ball travels at 130 kilometres per hour, the path hidden in the gaps between frames is never seen. For spinners it is harder still, because the ball changes its axis when it pitches. On low-bouncing subcontinental pitches, that estimate is more fragile than anywhere else.

Second angle — UltraEdge or Snicko. When the ball touches the bat's edge, there is a sound, and that sound appears on screen as a wave. But sound does not always come from the bat. Ball on pad, bat tapping the ground, even an umpire's sleeve can produce a spike. I have seen spikes sold as bat edges, and genuine edges dropped because the microphone's sampling missed the frame.

Third angle — the ball-tracking prediction. This is the biggest gap. From the moment the ball hits the pad to the stumps, nobody has actually seen the rest of the path — the machine draws it, using a trajectory model. Post-bounce speed, amount of spin, effect of wind: all assumed. So when the screen shows the ball grazing the stump, we are watching a model's opinion, not evidence.

This is the real meaning of umpire's call. It is not a rule to protect the umpire. It is a rule that admits the limit of the technology. Where the machine is not certain, the human decision on the field survives — and that is fair. The problem is that this subtle logic never reaches the viewer. The viewer sees "not out given, though the ball was hitting the stumps" and concludes it is an injustice.

I have seen this match from three angles, and the truth is still in the replay — though honestly, the replay is itself an interpretation, not proof.

Now to the Asian context. Subcontinental pitches are slow, bounce low, the ball spins more. In this environment, LBW reviews are mostly about spinners, and for spinners the ball-tracking estimate is weakest of all. When a ball grips and turns, its subsequent path is barely predictable to a model. So in Asian matches, umpire's call may appear more often than elsewhere — because the technology is uncertain, and the protocol hands that uncertainty back to the on-field decision.

One thing must be added here that no calculation captures — the player's memory. My older experience tells me a batter or bowler deciding on a review trusts his own eye and habit, not numbers. Dressing-room chemistry, which umpire a player trusts, which bowler keeps burning the team's reviews — no data model holds these. Yet matches are often decided by exactly these invisible things.

Contrarian: The anger is aimed at the law, but the fault is the protocol

My biggest objection here: the anger fans and pundits show over umpire's call is aimed at the wrong address. They think the umpire is wrong, or the technology is biased. What actually happens is that three separate questions get merged: was the process right, was the protocol applied correctly, and was the final decision correct.

Until these are separated, the argument never ends. The process can be right, the decision can stand by protocol, and the outcome can still be wrong — because the data itself is limited. The reverse is also true: a weak process can produce a correct outcome. Cricket society resists this nuance because we want a clean villain.

Second contrarian point — the broadcast-room effect. From 2026 I started making weekly reviews in a small room of my own, with a bought microphone and a ring light. I learned that when a clip travels without context, it becomes a weapon instead of evidence. Remote studios, second-screen commentary, and clipped replay debates together have turned DRS into a new courtroom, where the jury sits on the sofa and the verdict is based on views.

One more thing belongs here. In 2026, when I was walking the path from studs to whistle, and whistle to microphone, I learned a lesson that still applies: there is a gap between what a player feels and what the law says. My job is to explain that gap. In the DRS argument the gap is wider, because a third party has entered — the technology. And what technology says must be translated into the language of law, or the viewer just sees a blue line and stays confused.

Takeaway: The limit of the technology must be written down

My demand is simple. If ball-tracking is a model, then that model's tolerance — how many millimetres of uncertainty, what frame rate, what assumptions — must be shown on the broadcast. As the accuracy of service-line calls is public in tennis, so it should be in cricket.

This demand is not only for transparency. It is for the future of the game. As long as viewers believe a replay equals truth, every umpire's call will remain a betrayal of faith. The day they understand that a replay is an interpretation, and that it too has limits, they may stop being angry at the umpire and start asking how much the machine really knows.

In fifty years I have learned only one thing — the game is not perfect, and never was. Umpires, players, technology: none are perfect. The question is not about perfection. It is about honesty — bringing the limit into the open instead of hiding it. When the next Asia Cup or World Cup produces a ball-tracking line grazing the stumps, and the stands erupt, someone may finally ask the question nobody asks today: who drew that line, and how much certainty was in their hand?