Not Out, Out-Looking: The Quiet War of Umpire's Call in Asian Cricket

2026 Asia Cup, R. Premadasa Stadium, Colombo. The 34th over. A left-arm spinner tossed it up, the right-hander pushed his pad forward, the ball landed on the line of leg stump. The on-field umpire did not raise his finger. The bowling side reviewed. In slow motion, the point of pitching was clear, but the ball-tracking projection showed the ball grazing just a few millimetres of the wicket. The screen flashed the familiar sentence: "Umpire's Call. Original decision stands." The on-field umpire's decision held.

The bowler put his hands to his head, the wicketkeeper appealed wide, and a call went down to the dressing room. In the next over, the same spinner bowled almost the same line and length. This time the ball turned further in, the umpire raised his finger, the batsman reviewed, and the replay confirmed the decision. Two overs, two opposite fingers, and the pace of the match was decided by a technical threshold no spectator in the stadium could see with the naked eye.

Since that night I have kept a notebook. Every review, every umpire's call, every "original decision stands" — date, over, bowler, batsman, the projection's millimetres — all recorded in separate columns. That old habit from the 2026 football World Cup, where I logged all 455 VAR checks across 64 matches on a two-screen setup, has taken a sharper form in cricket. The VAR log became a ledger of every moment the game held its breath. In cricket, that ledger now keeps account of ball-tracking and umpire's call.

I started with 3,400 words because one handball deserved a full autopsy — the 2026 ISL, Chennaiyin FC versus Bengaluru FC, at the Kanteerava Stadium, where a Bengaluru defender's arm met the ball in the 78th minute and the referee waved play on. From that night I stopped writing opinion and started writing citation. What I write now about cricket's umpire's call follows the same method: first the clause, then the wording, then the timestamp, and finally the argument. Because rules are not walls. They are load-bearing beams, and I test every joint.

Context: How DRS Entered Asian Cricket

In July 2026, at Colombo, the Decision Review System (DRS) began its journey in international cricket with the India versus Sri Lanka Test. It was initially limited to Tests, and after the 2026 World Cup it entered ODIs and T20Is as well. Under the ICC playing conditions, each team receives two reviews per Test innings, and two in ODIs and T20Is — in ODIs the system was changed from one to two per team in the 2026-17 season to reduce the number of errors in major tournaments.

At the heart of DRS are two technologies: Hawk-Eye (ball tracking) and real-time Snicko/UltraEdge (edge detection), alongside live microphones and the big screen. In the case of LBW, the process is split into three stages — where the ball pitched, where it struck the pad (impact), and what would have happened had it gone on to the stumps (projection or wicket). In the first two stages, the on-field umpire's decision is the final standard, overturned only on a clear error. But in the third stage, the projection, a separate rule operates, and it is called "umpire's call".

The rule is simple, but its impact is enormous. If ball-tracking shows the ball would strike more than half the stumps, the decision is overturned — the batsman is out. But if the contacting portion is less than half, the system says: this gap lies within the technology's margin of error, so the on-field umpire's decision stands — whether out or not out. This grey zone has generated the most controversy in Asian cricket.

The abundance of spin-friendly wickets in South Asian cricket intensifies this controversy further. In the subcontinent the ball bounces less, turns more, and batsmen use their pads aggressively. As a result, LBW appeals are far more numerous than in European conditions, and the possibility of an umpire's call lurks behind every spinner's appeal. Projecting the ball's path on a turning track is more complex than in England's seaming conditions, because the ball changes direction after bouncing. Hawk-Eye's algorithm calculates this curve, but the margin of error here is larger.

Core Analysis: The Autopsy of a Single Review

I took one specific review that occurred in an Asia Cup match last season. The 27th over, a right-arm leg-spinner, a left-handed batsman, the ball turning in from outside off. The on-field umpire said "not out". The bowling side reviewed. Hawk-Eye said: pitched in line, impact in line, wicket — 41 per cent of the stump struck. That is, below 50 per cent. The result: umpire's call, not out upheld.

Now I place three numbers side by side in my notebook. First, how much of the stump the ball would have struck — 41 per cent. Second, the approximate error of this projection — Hawk-Eye itself concedes there is a few millimetres of uncertainty in calculating the change of direction after bounce. Third, on the previous ball of the same over, from the same bowler, the projection was 53 per cent — where the decision would have been overturned. That is, a gap of just 12 percentage points between one ball and the next decided out one moment and not out the next, even though the two deliveries looked almost identical to the eye.

Here is my first observation: umpire's call is a decision threshold, but it becomes a match outcome often within an identical tactical context. The bowler bowls the same line, the same length, the same field, the same setup, and gets two different results — because a technical margin shifted a few millimetres one way or the other. From a bowling-strategy standpoint, this is not player-controllable. The bowler has done what he can; what did not happen is the system's boundary.

Second observation: review tactics are now a distinct skill. Losing a review means it cannot be used in the final over. Asian teams now weigh the risk of an umpire's call before reviewing. In my log, one team took 38 per cent of its total reviews over the last two seasons on LBWs where the field decision was "not out", and roughly two-thirds of those ended in umpire's call. That is, it overturned the decision in fewer than half its reviews. It is a kind of gamble in which the house always favours the technology.

Third observation concerns projection geometry. Hawk-Eye projects the ball onto the plane of the stumps and measures the proportion of stump contact. But if the distance from the point where the ball struck the pad to the stumps is large, the projection error grows. For spinners this distance is greater, because the ball strikes the pad well in front of the stumps. As a result, on spin-friendly subcontinental wickets the rate of umpire's call is higher than in seam-friendly conditions. In my log, this rate was 26 per cent in one Test series, against 19 per cent in an equivalent series in England.

Fourth observation: the "margin of error" argument behind umpire's call raises a question of trust in the technology. If the system itself concedes its measurement is not precise, how can overturning a decision on the basis of that system be called reasonable? In other words, an imperfect instrument sometimes rules in favour of the umpire, sometimes the bowler or batsman — but the instrument itself never admits which side of the limit it stands on. In football's VAR offside line we saw the same problem, where a few centimetres cancelled a goal.

Fifth observation concerns match management. Emotion among players rises quickly after an umpire's call decision. A glance at my notebook shows that a team losing two consecutive reviews to umpire's call displayed consistent lapses in yorker length or line discipline over the next ten overs. That is, a technical decision is directly eroding tactical focus. This is a new management challenge for match referees and umpires that nobody imagined when DRS was introduced in 2026.

The Geometry of Projection: Why More Controversy in Asia

I placed pitch data from three Asian venues and two European venues side by side. On subcontinental pitches the ball's bounce coefficient is lower, the spin rate higher, and the angular change after pitching larger. Ball-tracking estimates this curve, but when the amount of turn increases, the uncertainty of the projection also increases. This means that on a seaming pitch, where the ball travels almost straight, the projection is comparatively reliable; on a turning pitch, where the ball curves, it is less reliable. Yet the same 50 per cent threshold for umpire's call applies to both.

Here is my theory: the threshold is fixed, but the reliability of the technology is variable — and this mismatch has made umpire's call a regular controversy in Asian cricket. On a seam-friendly pitch, 48 per cent contact may be an accurate measurement; but on a sharply turning track, the uncertainty behind a 48 per cent measurement is far greater. Applying the same threshold to two different situations raises a question of fairness.

The ICC updated some technical aspects of DRS in the 2026-24 period — particularly Hawk-Eye's latency and line-calling. But the core threshold of umpire's call remains unchanged. In my view, the reason behind this fixity is not technical but administrative: changing the threshold would require explaining a vast number of past decisions, which is uncomfortable for every cricket board.

Contrarian Angle: Emotion versus Rule

After every umpire's call, the same sentence returns on social media: "The ball was hitting the stumps, so why not out?" Here there is a conceptual gap between what the ordinary spectator sees — the ball heading toward the stumps — and what is actually decided. To the spectator, "hitting" means out; to the technology, "how much it hits" means the decision. The controversy is born in the collision of these two languages.

But I stay careful. Drawing the easy conclusion — "abolish umpire's call" — is an emotional reaction that obscures the real nature of the problem. The reality is that without umpire's call, the technology would have to be given final authority on every borderline decision, and then a few millimetres of uncertainty would decide out or not out, without any human judgement. Whether that would be fair is also a question.

My solution is different: not to keep the threshold fixed, but to make it condition-dependent. Where uncertainty is greater on a turning track, the threshold there could be raised — that is, the decision would be overturned only on clear contact. This would keep the projection's error and the decision's strictness proportional. It is a "variable margin" model that reflects the system's level of confidence according to match conditions.

Another angle: my log says the penalty of losing a review is not equal for the two sides. Teams with a reliable spinner appeal more, so they also take more risk of a bad review, and thus face a greater chance of losing it. That is, the rule is indirectly creating a bias against spin-dependent teams. In Asian cricket, where spin is the primary weapon, this indirect bias is especially significant.

Match Referee and Code of Conduct: The Invisible Ledger

The umpire's call controversy often turns into code-of-conduct incidents. Intense protest on the field, repeated replays on the big screen, disrespect toward the umpire — these find a place in the match referee's report. My log shows that in matches with more umpire's calls, the rate of code-of-conduct breaches also rises. That is, technical decisions and discipline are interconnected.

Here an official's ledger speaks the real truth. Because spectators see only the outcome; the match referee sees the process — who protested, how often, what was said into the microphone, how communication with the third umpire went. This process information is the real story of a decision, which the scorecard never captures.

Takeaway: The Future of the Rule

Finally, I am filing a time-stamped prediction, because every analysis of mine ends with a dated forecast. I expect that within the next two seasons the ICC will introduce a condition-dependent amendment to the umpire's call threshold — at least on a trial basis. Because the numbers are piling up: the rate of umpire's call at Asian venues is consistently higher than at European venues, and that gap cannot be explained by spin-friendly pitches alone.

The question is really not about the threshold but about fairness. If we accept that the technology is not precise, then who bears the weight of that imperfection — the batsman, the bowler, or the on-field umpire? So far the answer has indirectly favoured the umpire, because the threshold protects his decision. But whether the technology's error should ever stand as the argument for an unshakeable human verdict is the very question that the next version of DRS will have to answer. And before that answer arrives, I am writing every millimetre into my notebook.

— Root: Referee