Beyond Umpire's Call: DRS, Asian Cricket and the Verdict No Rule Can Deliver

In April 2026 I left a salaried commentary-production job in Manchester and gave the whole IPL season to logging reviews. Sixty matches, 214 DRS decisions, and every row carrying seam position, the ball-tracking projection, the umpire's-call margin and the seconds between appeal and referral. On the night of 21 May in Hyderabad, Mumbai Indians beat Rising Pune Supergiant by one run; that final became an entry in my logbook that changed the tone of every analysis that followed.

I logged 214 decisions before I learned to distrust the obvious angle. Every appeal on a cricket field is a claim, and every claim is a kind of bet — the on-field umpire's bet. The review system promises to re-examine that bet, but the re-examination becomes another bet the moment the ball's path is projected and the verdict hangs inside five or six centimetres.

India's attitude to DRS was, for a long time, one of deferral. In 2026 India rejected it — questions over ball-tracking accuracy and, inside the BCCI, a lack of trust in the technology. Five years later, from the 2026-17 England series, India adopted it almost wholesale. The technology had not changed that much; the power equation had. That difference shaped the Asian review culture in a way that has been badly under-examined: trust in technology was not built through testing it, but through the confidence of the board that adopted it.

Meanwhile the tracking system did change. The gap between today's ball-tracking logs and the first versions a decade ago did not come from a controversy report; it came from calibration work. Yet whenever DRS comes up in an Indian context, the argument almost never reaches calibration. It stops at umpire's call.

One way to understand umpire's call is to treat it not as an admission of error but as a line of tolerance. When the ball is projected to settle within the stumps or the padline on a limited margin, tracking says whether the verdict falls inside or outside that limit — but the system's own uncertainty works across that line. A verdict that just brushes the edge is filed as 'umpire's call.' In that process the rulebook says nothing; a human draws the line, and that human is invisible.

This is the real emptiness of DRS — every review is filled by a residue no clause can absorb, and that residue must be answered by the same umpire the technology left behind on the field.

I kept a separate column in the logbook: 'possible reversal.' That is, the decisions that fell inside the umpire's-call margin and where a second angle was theoretically possible. How many of the 214 they were seemed important then; today I think the more important question was who was accountable for those decisions. The answer is not clean, and that clean answer was what I wanted — because when a decision has no owner, everyone can point their phone at it.

Nine pages of protocol taught me how much judgment a rulebook cannot hold. I wrote that protocol in 2026 in the International Broadcast Centre in Moscow, after starting to classify that year's 29 penalties — not by outcome but by process error. Two federations asked for the document; I sent it free. Cricket has never built an approved version of that exercise, and that is the largest gap of all. In cricket, three different questions about a review system usually get crammed into one column: was the ball on target, was the tracking reliable, and did the umpire judge the line correctly. The first is a question of law, the second of technology, the third of tolerance. All three should get separate ratings in a report — and no report does it.

The root of that gap is structural, not intentional. The money and the broadcast noise around Asian cricket's decision-making come from the Indian market, which carries a very large share of global cricket revenue. When one market grows large enough that its opinion is the centre of the news cycle, the demand for technical improvement turns into a demand to 'avoid controversy.' The real question here is not how powerful a board is; it is who pays for that power — which domestic competition, which layer of the pyramid, which journalist's livelihood.

IPL 2026 was a clerk's audit for me, precisely because I was producing a five-minute weekly segment for an outlet that held no broadcast rights that season. Whoever holds the rights does not need to collect data; only the person who does not, counts. Three lessons from that audit hold even more strongly in today's pseudo-data age. First: the biggest deception in a review is not the outcome but the ball-tracking's opening frame — the frame before the frame is where most decisions are actually made. Second: the seconds between appeal and referral measure the cost of indecision; the longer the wait, the more of the game stands frozen in a low-emotion segment. Third: the silence after a retainer is cancelled is also data — when Mumbai Indians beat Delhi Capitals in Dubai, on-field umpires in crowdless matches appeared to take 3.4 seconds longer on average before sending decisions upstairs, and stump-mic audio overtook replay as the primary evidence.

Those 3.4 seconds open the whole case. With crowd noise, an umpire decides quickly under collective pressure; without it, the same umpire begins to hear his own voice and waits. The crowd does not just amplify celebration; it sets the pace of review. And if the crowd sets the pace, then the hosting economy of Asian cricket enters the pace of umpiring too.

This is where a more uncomfortable question arises. Long reviews are breaking the rhythm of the match — that is not merely a spectator's complaint, it is a technical fact of match management. Even a two-minute wait cools the celebration that builds with a wicket, and a cooled celebration creates an insurance-level psychology: players no longer trust the celebration first, they look at the screen first. That shift came not from any single outcome but from the length of the process.

Here a counter-intuitive angle appears, and I often pause on it. What we demand most from DRS is the one thing it cannot give: emotional certainty. When a star player is dismissed, we want justice from the review; when the same review goes against another team, we point a finger at the same system. The law does not differ, the principle of umpire's call does not differ — only the emotional accounting does. I stopped asking who was right and started asking who was watching. Because a decision that does not come from the law comes from the trust of the watcher — and that trust has no public ledger.

The absence of that ledger is not confined to big matches. It shows more in domestic cricket, where review facilities are not available at every match, and where the part of the game that produces no highlights quietly disappears from coverage. When my main broadcast retainer was cancelled by a single email in April 2026, I put some of the shutdown into what is least watched — timing 92 Premier League fixtures frame by frame. Coming back from that to cricket umpiring, one deception became clear: we discuss the decisions that get replays. The ones that get no replays drop out of the argument entirely, even when their impact is equal.

When the retainer was cancelled, I started timing the silence in empty stadiums. Today that habit tells me that the real challenge for DRS in Asian cricket is not the technology but the reporting structure that narrates it. We have precise ball-tracking data, but no public document of the human impact of the umpire's-call margin. We have a count of reviews, but no accountable home for that count. And when accountability has no home, trust is built and broken by the taste of a single broadcaster.

This difference is not only about numbers. On one side are matches with the full review setup; on the other, competitions where an innings ends before a player even gets the right to review. It is easy to file that inequality under 'uneven development,' but it shows whose service the technology is in. DRS looks strongest where the media money is largest; and at its most sensitive point — the tolerance line of umpire's call — it is most often invoked in matches where the cost of applying it has been least recovered.

This may sound like an old refrain, but the numbers taught me exactly this. When we call a decision 'wrong,' we are really calling a process 'incomplete' — and the parts of a process are not equally accountable. A calibration failure is answered by technology. An umpire's failure is answered by a rating. But a failure inside umpire's call is answered by no one, and that is the most expensive gap. The day it is filled, DRS in Asian cricket will move from argument to ledger.

The next stage is not the one we expect. The real front is not semi-automated offside-style technology — that has already arrived — but the public ledger of the umpire's-call margin. The day every review records which part of the margin a verdict fell into and who tolerated it, trust will stop depending on technology. Until then, the question left after every big appeal is not cricket's — it belongs to the system that decided which decisions should be recorded and which should not.

My logbook has 214 rows. Some of them still wake me at night, but the question is no longer the same. The question is not what the umpire saw — it is who drew that line, and who kept its accounts after it was drawn. Until accountability's name is printed on that line, every big review will remain a piece of theatre — a full stage and half a truth.