Umpire's Call: The Threshold Technology Draws for Itself

On August 25, 2026, at Headingley, England's chase was down to its last pair on the fourth day of the third Ashes Test. A Nathan Lyon delivery struck Ben Stokes on the pad. The on-field umpire did not raise his finger. Australia reviewed. On the big screen the tracking line crept forward, and the ball was shown grazing the outer edge of leg stump. Umpire's call — the not-out decision stood. England went on to win by one wicket, Stokes unbeaten on 135.

I watched that review from my home in Chattogram with a stopwatch and a notebook beside me. I have been watching cricket for 52 years, and that single frame keeps dragging me back to one question: when the ball is going on to hit the stumps — when the condition for out is being met — why is the decision still not overturned? The answer is not in the technology. It is in the process, where the burden of proof and the margin of measurement are two separate things.

Let us go to the tape, slowly, and let the frame speak.

The rule at work that day sits inside the ICC Playing Conditions. DRS tests three things — where the ball pitched, where it struck the pad, and whether it would have hit the stumps. On pitching, human judgement gets no allowance at all. A ball pitching outside leg means not out; a ball pitching outside off is simply a fact, and what the on-field umpire thought is irrelevant. The other two stages carry a threshold. If less than half the ball is inside the relevant zone on impact or on the projected path to the stumps, it is umpire's call — the on-field decision survives, and the reviewing side keeps its review.

DRS was first trialled in international cricket during the 2026 Sri Lanka-India series, and it took more than a decade and a half to travel from that trial to domestic franchise leagues. Two unsuccessful reviews per innings (three in Tests, with a top-up after 80 overs) is now common knowledge in every living room. Then, from June 1, 2026, the ICC abolished the soft signal for low catches: the third umpire no longer decides under the shadow of the on-field umpire's tentative call, but decides alone. That was an admission of something important — in the name of respecting the human call, the system had blurred who was actually responsible for the decision.

Now to the substance. In my tape notebook, one review means three separate frames, each with its own accountability. The first frame covers the bowling position and the pitch of the ball; it is almost purely factual. The second covers the point of impact on the pad; here the first human allowance appears. The third is the projection towards the stumps, the curved line we all recognise on screen. That is where the deepest doubt lives, because the line is not a measurement — it is a model, a mathematical extrapolation built from the handful of frames before impact. The direction of the seam, the amount of grass on the pitch, whether the ball changed direction fractionally in the air: all of it lives inside that model.

Umpire's call is not a measurement at all; it is the minimum threshold of proof. The question was never whether the ball was hitting the stumps. The question was whether the model carried enough certainty to declare it. Once that distinction settles in the mind, the whole argument changes tone.

And this is my strongest objection. When the same machine says the ball pitched outside leg stump, it is treated as unalterable truth — nobody splits it into half-outside and half-inside. Yet at the very next stage, an artificial threshold is clamped onto that same machine's verdict. Identical claims of precision, two different standards of treatment. If the technology can call pitching accurately, its projection towards the stumps deserves to speak in the same language. And if the projection really is an estimate, why is the threshold 50 per cent — why not 30, why not 70? That number rests on no published calculation. It is simply installed inside the protocol.

The retention rule is the other disputed clause. Umpire's call returns the review; a proven error costs it. The consequence is straightforward: reviewing a marginal call is a gamble with no stake. In my own tagged sample of more than three hundred reviews, a large share sit right on that boundary, where the outcome depends on a small calibration drift. A side that reviews only marginal calls risks little. A side that believes the technology is flawless only loses.

Match management has shifted too. Once an umpire looked for protection inside his own experience. Now he knows that whatever he gives on a marginal call will return to him as umpire's call on the screen. Whether umpires are drifting towards not out is no longer a new debate at ground level. The way VAR's 2026 World Cup debut reshaped the decision equation for referees, DRS has added the same kind of umpire-dependent layer to cricket.

Part of the noise runs on emotion — that we were robbed. Before dismissing it, one thing must be conceded: the law was applied correctly in that Headingley frame. My referee's eye does not change the rule along with the team. A Bangladesh review and an Australian review get the same three frames, the same half-ball calculation, the same burden. When I began the Referee's Eye show on Facebook Live in 2026 over a disputed penalty in Chattogram, the rule I set for myself was this — read the clause before raising the claim. It still holds.

The most overlooked lesson comes from the 2026 VAR debut, where 17 of 29 reviews overturned the on-field call. The number dazzles, but the lesson sits elsewhere: the legitimacy of a review system never rests on the precision of the technology. It rests on how the threshold was set. More technology does not reduce controversy; it reduces only invisible errors, while multiplying visible ones that cannot be corrected. Today we can all see the ball sitting on the boundary line, and we are still not allowed to intervene. Visible helplessness breeds more anger than invisible bias.

My proposal is simple, and it belongs at the end of a tournament. First, the error margin of the tracking system should be published after every major event. Second, the umpire's call threshold should be announced in the same breath as that published figure, so everyone knows how heavy the burden actually is. Then the umpire will know where the protection of his call ends and where the technology's responsibility begins. Whether technology will ever speak the last word, time will tell. For now the question is this: when a decision is visible to the entire stadium at once, who carries the responsibility for defending it — the umpire, the technology, or the people who wrote the rule?