In the Shadow of Umpire's Call: The Fairness Ledger Nobody Keeps in Asian Cricket

In the Shadow of Umpire's Call: The Fairness Ledger Nobody Keeps in Asian Cricket

Hook

On 14 July 2026, at Lord's, England and New Zealand played a World Cup final in which both sides made 241 in their 50 overs and both scored 15 in the Super Over. According to the ICC's official record, a single sub-clause settled the champion: the boundary count. England had hit more boundaries, so the trophy went to them. Ball-tracking, UltraEdge and the third umpire were all present—the entire battery of modern technology. But the champion was decided by a numerical calculation that had no direct relationship with the cricket played that night.

Since that night a question has lodged itself in my head and never left: what exactly do we use to measure fairness in cricket? Technology, numbers, or the umpire's conscience? Sitting in a small room in Liverpool, spreadsheet beside me, I kept circling that question—notes on 29 VAR reviews, frame rates of ball-tracking, and three words written on a blank sheet: 'clear and obvious'. In Asian cricket the question is sharper still, because here the ball turns, the bounce is low and the pitch is slow. Where ball-tracking is itself an estimate, a grey zone called 'umpire's call' is born—a zone where the law says one thing and the screen says another. And in that gap every Asia Cup, every Asian duel ends with an uneasy feeling: the decision may be lawful, but is it fair?

Context

The Decision Review System began in 2026, in a Test series between India and Sri Lanka. At first it was experimental, a source of player suspicion and umpire discomfort. Today it is integral to almost every major tournament. But its internal architecture needs understanding, because on Asian soil that architecture often sags.

DRS stands on three pillars. Ball-tracking—usually Hawk-Eye—which estimates the ball's path. UltraEdge or Snicko, which detects the bat's edge. And HotSpot, which detects heat on the pad at contact. For LBW, ball-tracking answers three questions: where did the ball pitch, where did it strike the batsman, and would it have hit the stumps.

The first problem is here. Ball-tracking does not tell the future; it estimates it. Camera frame rate, the ball's seam position, friction on the pitch, wind speed—all combine into a mathematical model that says where the ball would have gone. That model is as accurate on a green, damp English pitch as it is inaccurate on a dry, turning pitch in Chennai or Mirpur. In England the ball lands on the seam and deviates slightly, predictably. In the subcontinent the ball grips, spins, and changes path in every frame—a nightmare for any model.

And the most contentious part of the law is 'umpire's call'. Under the rule, if ball-tracking shows the ball hitting less than half of the stump, the on-field umpire's decision stands. That is, when the technology is not certain, it returns the call to the umpire. Per IFAB and ICC playing conditions, the rule rests on one argument: the technology is not 100 per cent accurate, so the benefit of the doubt belongs to the human in the middle. But the question is whether that argument actually increases fairness or merely increases unease.

Asian cricket has an extra layer—slow over rates, frequent spinners, long fielding sessions. In this environment umpires must decide quickly, often with barely a second to read line and length. Yet that one-second decision is later protected by technology through 'umpire's call', even when the ball clips a millimetre of the stump's edge. This reality is what manufactures the umpiring controversy in Asian cricket.

Core Analysis: The Physics of Ball-Tracking

Whenever I watch an LBW review, I freeze the moment—I freeze the movement, I go frame by frame. Ball-tracking technology is in essence a continuous estimate, an attempt to derive a future path from a few fixed frames. The more frames the camera captures before the ball pitches, the more accurate the estimate. But if the ball turns on pitching, or changes direction through spin or seam movement, the model expresses a probability, not a certainty.

On Asia's dry pitches, ball-tracking is most likely to err, because spin and low bounce destabilise the estimate. A delivery that bounces 60 centimetres in England may bounce 40 in India or Bangladesh—and the final segment of the ball's path shifts according to stump height. When ball-tracking says the ball hits 'less than half the stump', it is in fact confessing its own uncertainty. The question is: why should the batsman pay for that confession?

The Umpire's Call Paradox

The idea of 'umpire's call' looks simple but is complex. If the on-field umpire says out and ball-tracking shows the ball hitting less than half the stump, it stays out. If the on-field umpire says not out, the same evidence keeps it not out. The same ball, the same data—but the decision depends on what was said in the middle first. This is an uncomfortable truth in the age of technology: the final decision belongs not to the technology but to a compromise between technology and the human in the middle.

To me, this is the great fault line. If the technology is not certain enough to decide, it should not decide—it should gather more data, not protect the old on-field decision. The current system is essentially a compromise: the technology tells the truth, the law gives it half-power and sends it away. So a player who wins a review feels robbed, and one who loses feels foolish. In both cases, trust in umpiring falls.

In tournaments like the Asia Cup this paradox is starker, because teams differ in their review strategy. Some take only 'safe' reviews; some gamble. That strategic inequality eventually affects outcomes, even though every team is equal before the law.

Spin, Low Bounce and the Limits of Estimation

Subcontinental cricket is largely a game of spin. Mirpur, Chennai, Colombo, Galle—everywhere the pitch is slow, the turn modest but low. In this environment ball-tracking's job is harder, because the ball's final path often raises the question of stump height. Because of low bounce, a delivery that looked to be going over the stumps might have gone under—or the reverse.

Over recent years I have noticed that 'umpire's call' verdicts are relatively more common in matches played in the subcontinent. One reason is the spinners' angle of attack—they often bowl at the stumps, so the probability of hitting is high, but exactly how much remains an estimate. The second reason is the pitch: on a slow pitch, if the ball turns, the prediction becomes even less certain.

A vital question arises here: if the uncertainty of ball-tracking depends on the nature of the pitch, should the same threshold (50 per cent) apply equally at every ground and in every country? Or does the subcontinent demand more caution? The law now uses a single number, but when the ground changes, the reliability of the technology changes too. This is a silent problem of fairness that nobody measures.

The Disappearance of the Soft Signal

In 2026 the ICC abolished the 'soft signal'. Previously, when a catch was in doubt, the on-field umpire gave a 'soft' signal—out or not out—and the third umpire gave that signal primacy. This practice generated years of controversy, because often the on-field signal won even when clear evidence existed. From June 2026, ahead of the World Test Championship final, the ICC scrapped the soft signal—meaning the third umpire now decides independently on the evidence.

The change is welcome, but it exposes a larger truth. What we had long thought of as 'the technology's decision' was in fact a hybrid of technology and the on-field decision. Even after the soft signal's abolition, 'umpire's call' survives, because it operates at a different level—in LBW rather than catches. So the reform is half-done, and the paradox half-remains.

To my mind, the soft signal's abolition is a lesson for Asian cricket. It shows that old practices can be changed if the decision is clear. Then why is the same clarity not needed for 'umpire's call'? I leave the question open; time will answer.

The Inequality of Review Data

Review-usage statistics reveal a pattern. Top teams often take good reviews, because they have analyst teams, ball-tracking forecasts and experienced players. Smaller teams take reviews with more risk, and therefore err more. This inequality has grown in the technology era, because a 'guessing process' now operates before any decision, and in that process resources and experience matter greatly.

In Asian cricket, DRS is essentially a contest of skill, not merely an instrument of fairness. The team that can read technology gains an advantage; the team that cannot makes bad reviews and loses momentum. This reality prevents technology from being neutral—it creates a new inequality. One might ask: if teams had more reviews instead of a limited number, would technology-literacy matter more than talent? Probably yes.

Premise versus Pixel

In my personal spreadsheet I have logged every contentious decision for years. A pattern returns again and again: the clear and obvious error was not in the pixel; it was in the premise. That is, the problem is not the accuracy of ball-tracking but the question we are asking it. We ask, 'Did the ball hit the stumps?' But the real question should have been, 'In this environment, how reliably can technology answer that question?'

'Umpire's call' is born from this error of premise. We have made an uncertain estimate the standard of decision, then returned to the umpire to settle that uncertainty. In doing so, responsibility is not shared between technology and human—it hangs in the air. A player does not know whom he is appealing against: the pixel or the umpire.

I call this gap 'the shadow of the law'. The law is clear, the technology is clear, but at their meeting point a shadow forms where the decision stays unclear. In Asian cricket this shadow is darkest, because here the reliability of the technology is itself in question.

The Rhythm of Fairness

I have long believed fairness is measured not only in big decisions but in small concessions. Over rates, drinks intervals, minor allowances in the field—this accumulated ledger decides whether a match feels just by its final hour.

In Asian cricket, over rate is a chronic problem. Spinners bowl slowly, fielders set up slowly, and matches routinely run beyond time. This slowness increases pressure on umpires and lowers the quality of decisions. A match's fairness lives not only in LBW verdicts but in its overall rhythm—and that rhythm often breaks in Asian cricket.

I think this rhythm problem also sits behind the DRS controversy. When a match drags, when the fielding side plays slowly, umpires tire, and a tired umpire's decision is later protected by the shelter called 'umpire's call'. That is, a large part of the technology controversy is really a controversy about human fatigue.

Contrarian Angle

Now an unpopular word. Many believe 'umpire's call' is a defect that should be abolished. I disagree—conditionally. 'Umpire's call' is in fact technology's honest confession. When ball-tracking says 'I am not certain', protecting the on-field decision is a realistic choice. If we erase this grey zone and treat every estimate of ball-tracking as final truth, we will commit greater injustice—because then a wrong estimate at 49 per cent would also be imposed as out.

But here is the condition. 'Umpire's call' is fair only when ball-tracking's reliability is equal at every ground. On the subcontinent's spin-friendly, low-bounce pitches it is not equal. So my contrarian position is this: before abolishing umpire's call, we need to measure the reliability of the technology—and if that yardstick varies by ground, the definition of umpire's call should vary by ground too. Without this, we are imposing a single standard on a shape-shifting game.

I also concede that my position may be wrong. If evidence emerges that ball-tracking is as accurate in the subcontinent as in England, I will change my mind. But that evidence has not yet reached my hands.

Toward a Conclusion

That night at Lord's, on 14 July 2026, taught me one thing: technology never guarantees fairness; it only makes a decision clearer. Clarity and fairness are not the same. The boundary count was clear—but was it fair? Ball-tracking's number is clear—but fair? Asian cricket will have to answer this question in the future.

The day cricket's lawmakers understand that the reliability of technology must be measured ground by ground, 'umpire's call' will cease to be a problem—it will become an honest confession, equal for all. Until then, every contentious review in every Asia Cup will remind us that a rule is only a hypothesis, and cricket's memory tests that hypothesis continuously.