Umpire's Call: Who Really Controls the DRS Margin on Asian Pitches?

A night one-day match at Mirpur's Sher-e-Bangla Stadium. The 34th over. A left-arm spinner releases, the batter pushes forward, the ball thuds into the pad. The on-field umpire raises the finger. The batter signals for a review. Thirty thousand pairs of eyes swing to the giant screen. The tracking unfolds slowly: impact in line, wickets — umpire's call. The on-field decision stands. A collective groan rolls around the ground, and in the dugout a batter sits down with his helmet off, cursing under his breath.

I have watched that clip forty-eight times. Not to watch the delivery. To watch where the decision was actually manufactured — on the pitch, inside the ball-tracking software, or in a clause of the playing conditions. Because in modern cricket the question is no longer 'was it out'. The question is who writes the definition of out, and who sets the margin of that writing.

DRS arrived in Asia in 2026, at Colombo's SSC ground, in the Sri Lanka-India Test where the player-review system was first used. In its early years India was the harshest critic of the system, questioning the reliability of tracking and avoiding DRS for years, before fully accepting it during the 2026-17 home season against England. Since then the story has been double-edged for Asia: reviews are now inseparable from the game, yet the decisions still depend on the cameras and calibration of venues whose ownership and data sit outside Asia.

The rule looks simple. Two reviews per team in Tests, one in limited-overs cricket, retained if successful, with fifteen seconds for players to decide. The third umpire checks in a fixed order: front-foot no-ball first, then bat-pad contact, then impact, then the stumps. In LBW the three stages are assessed separately: where the ball struck the pad, the point of contact between ball and pad, and the projection — where the ball would have hit the stumps. If impact or contact is marginal, the on-field call stands; for projection, the 2026 clarification spelled out the half-ball threshold — the ball must be projected to hit the stumps by more than half its width to overturn a not-out, otherwise it is umpire's call and the field decision is final.

In June 2026 the ICC removed the soft signal entirely from catch decisions. The on-field umpire no longer offers a provisional verdict; the third umpire decides directly. Together, these two changes produced a large transfer of authority that is rarely discussed in Asia. As the field umpire's discretion shrank, the studio monitor and the software's internal threshold grew. The question is to whom that threshold answers.

To me DRS was never merely technology; it is a distribution system — an account of how the right to decide is split between the field, the studio, the algorithm and the playing conditions. The rule was never the point; the rule was the flashlight — the thing that shows us where the shadow falls. And on Asian pitches the shadow falls somewhere else entirely.

The first shadow is time. Ball-tracking projects from the point of impact to the stumps. On subcontinental pitches the ball is slower, bounces lower, spins more — meaning it takes longer to travel from impact to stumps, and in that extra time it curves more. The slower and more sharply the ball turns, the longer the projection window and the wider the envelope of uncertainty. The same tracking system, the same software — yet the certainty available on a Perth wicket does not hold on a slow turning Dhaka surface. The strange part is that this envelope is never shown to the audience. We see a clean green-and-red line; we do not see the variance behind it.

The second shadow is geometry. Tracking accuracy depends on the number and placement of cameras, frame rate and calibration. Major Asian venues now have international-standard camera networks, but not all venues are equal — in regional series, age-group tournaments or domestic matches where tracking does not exist at all, 'umpire's call' is a theory, not a reality. And where tracking does exist, calibration reports are not public. No board knows the average deviation of the tracking system at its own ground last season.

The third shadow is review economics. A review is a finite resource, so every review is a gamble — and who now makes that gamble in the dressing room? The profession that entered cricket late is the performance analyst. Many teams now consult data before reviewing: which umpire, at which venue, has what percentage of decisions overturned. The decision shifts from the eye's belief to a probability calculation. The data is not wrong here, but the data does not know the rhythm of a match — when saving a review is worth more than winning one is something no spreadsheet can tell you.

The fourth shadow is the first frame on the producer's monitor. Whatever the third umpire sees first shapes his initial hypothesis. If the producer starts the replay from the angle that creates doubt, the decision tilts that way too. The referee's eye sees the foul before the crowd feels it — but which frame the studio referee sees first is chosen by the producer.

The fifth shadow is power. After the soft signal was withdrawn, the on-field umpire no longer supplies a 'provisional truth' on catches. The third umpire must now find evidence and deliver a verdict at the same time — yet the limit of that verdict, the point at which evidence becomes 'sufficient', is nowhere written down. Where the threshold is unwritten, the threshold is set by habit, pressure and the aura of the venue. In matches involving smaller teams I routinely see that limit applied more strictly than in matches involving the giants — hard to prove, because nobody keeps the data.

The sixth shadow is the dual nature of the margin. Fans split into two camps: the batting side believes the system has wronged it, the bowling side believes the batter survived on technology's back. Both are the wrong question. Nobody 'erred' on the margin; the margin was designed deliberately, so that the benefit of uncertainty returns to the on-field umpire. Umpire's call is not a bug, it is a policy decision.

This is where my 2026 Russia ledger returns to me. I kept a ledger of every VAR decision in Russia, and the margins told a story — not of how 'correct' the decisions were, but of who was granted the right to make them. Cricket's umpire's call tells the same story in a different language.

My 2026 silent study adds the weight of the crowd to that distribution. Across 83 Bundesliga matches played behind closed doors during the pandemic, home win rate fell from 43.3 per cent to 33.7 per cent and average added time rose by 1.4 minutes. In the silent study the whistle stopped, and the game finally spoke — part of every decision is always written by crowd pressure. Umpire's call gives that invisible writing a legitimate frame, though the frame never admits what it is covering.

The seventh shadow is audio. With UltraEdge we always assume a spike means contact with the ball. But a spike can come from the bat hitting the ground, from a glove brushing the pad, from the faint graze of ball on stump. When, on slow-motion replay, the spike and the visual frame do not align, the third umpire faces a philosophical problem — which is truer, the sound or the picture. There is no formal rule for that conflict.

The eighth shadow is the front-foot no-ball. In the review process the TV umpire checks the no-ball first; if a no-ball is found, a batter given out on review survives. It looks like a small correction, but it says the review is a package — the batter is not merely challenging an LBW, he is challenging the whole decision chain.

The ninth shadow is league economics. The IPL, BPL or PSL play with a single review, where the pressure of pace and entertainment is different. Smaller leagues have smaller production budgets, fewer cameras, so the same law is applied to different standards of evidence. The same law, a flashlight of different quality — and where the light is weaker, the shadow grows longer.

Now to the place where the popular complaint aims at the wrong target. When fans groan at umpire's call on the screen, their anger goes at the technology, as if the tracker were conspiring. It is not. The tracker does honestly what it does; the problem is that we ask it a question beyond its capacity to answer. 'Would the ball have hit the stumps' has a probabilistic answer, not a certain truth. We ask technology for a picture of the future while judging it by the standard of present certainty.

Second, a simple fix is often proposed: abolish umpire's call and every decision becomes 'correct'. Wrong. Abolishing it would not reduce error, it would move the error line. A ball projected to clip the stump by one millimetre would then be out — the controversy would be reborn elsewhere, not diminished. Anyone who truly wants reform must stop arguing about the margin and start making the uncertainty disclosure transparent.

Third, I want to concede that the crowd's emotion is not unreasonable. The review wait has become part of the match — three minutes staring at a screen, a team's joy left hanging, breaks the flow of play. That delay is itself a cost, and it never appears in any calculation of raising or lowering a threshold. This is where I part company with analysts who compute review success percentages but never compute the damage to a match's rhythm.

Looking ahead, my proposal is simple but uncomfortable: Asia's cricket boards should open a public review ledger — the tracking calibration deviation at every venue, the distribution of review outcomes each season, and the umpire's-call rate, all published as open data. A system that cannot show its own uncertainty concentrates power through silence. And the question remains: who will judge the technology that judges the game?