Umpire's Call: When DRS Becomes a Legal Document in Asian Cricket

That line from the review log is still stuck in my notebook — the ball-tracking showing 49.8 percent of the stumps, the third umpire's screen flashing green, and the decision unchanged. Umpire's Call upheld. The ground was boiling; the batter was pulling off his helmet, someone was rising in the dressing room, the commentator's voice was climbing — this should have been out. I sat beside my laptop, hunting for the clause that turns this ruling from a judgement into a procedural outcome. Across a decade of review logs in Asian cricket, I keep seeing the same thing: the argument is about emotion, the resolution is about percentages, definitions and timestamps.

DRS was not a single-day invention. It began its international trial with the India-Sri Lanka Test in July 2026, and the ICC adopted it as a standing system the following year. Since then every review is really a three-step mini-trial: first the on-field umpire's original decision, which carries a kind of foundational recognition inside DRS; then ball-tracking; then UltraEdge or Snicko to verify bat-on-ball contact. The ICC Playing Conditions and the MCC Laws together write the whole process — when a review can be taken, who can take it, and how often.

In Asia the picture gets more tangled. Two reviews per innings in Tests, fewer in limited-overs cricket — that ceiling decides when a team gambles and when it folds its hands. Bangladesh, India, Pakistan, Sri Lanka each carry a different review culture, because each carries a different domestic administration. When I watch Dhaka's domestic cricket alongside an English county match, I understand it: the same law produces two different behaviours, because law is written at the centre and applied at the edges.

There is another side to this system, and it lives off the field — cost. Ball-tracking, UltraEdge, stump mics; every technology carries a large bill and needs trained operators. In ICC-sanctioned matches the host board absorbs much of it, but domestic cricket works differently. In domestic leagues in Bangladesh or Sri Lanka where a full DRS setup is not present at every match, players learn how to take a review for the first time only when they reach the international level. That is a preparation gap no coaching camp can fill.

Let us take the ruling apart. For LBW, DRS asks three questions: did the ball pitch in line with the stumps? Was the impact in line? And would the ball have hit the stumps? If any of the three carries uncertainty, the decision returns to the on-field umpire. That is where Umpire's Call is born. Its threshold is half the width of the ball — if more than half the ball would hit the stumps, it is out; if less, it is Umpire's Call.

That half-a-ball margin is in fact the least discussed yet most powerful legal clause in cricket. It admits that technology is not perfect either. Ball-tracking is a projection, a prediction — and prediction carries a margin of error. So the ICC decided: where the technology itself is unsure, the human on the field speaks last.

From 1 June 2026 the ICC scrapped the soft signal for catches entirely. Previously the third umpire gave a kind of priority to the on-field umpire's initial decision before even watching the replay — if there was doubt, that decision stood. The scrapping is a constitutional shift: evidence first, assumption after. In my review log I have seen that after this change the average resolution time of catch controversies fell, because a decision no longer hangs across two layers.

Every review is really a limited resource, and in Asian cricket managing that resource changes the tempo of a match. A wasted review does not just burn one chance — it blinds a team tactically for the next two hours. For a side like Bangladesh, with comparatively fewer experienced reviewers, one weak call can shake the mental balance of an entire innings. Yet when the bigger Indian or Pakistani sides have the best technology and analysts on hand, the review becomes part of the plan — not a reflex of emotion.

Across every Asian Test and limited-overs match I have tracked since 2026, one pattern keeps returning: teams take their first review in the most emotional moment, and save the last one for the most necessary moment. The arithmetic in between is really the coach's and the analyst's job. A team that keeps timestamps of its reviews knows who reviewed, when, and under which clause — and that is what shapes the next match's decisions. Experienced cricketers like Bangladesh's Shakib Al Hasan also sway between emotion and arithmetic at the moment of a review, and that very sway sets the success rate.

One more thing is clear in my log: most failed reviews come in two situations — UltraEdge catches in the early overs, and LBWs in the death overs. In the first, emotion wins; in the second, time pressure wins. A team that recognises these two traps carries a far higher review success rate than others. This recognition is no secret — it is all public data, but nobody keeps the count, so the pattern escapes the eye.

A tournament is really a legal document, written in over-by-over chapters. Asia Cup or a bilateral series, every review there is a footnote — some read it, some do not, but the count remains. And that count decides which team clears the group stage and which team flies home.

There is an ethical question about the technology too. Ball-tracking shows where the ball would have gone, but that is a projection — wind, pitch friction, the seam position, all rest on assumption. When the ICC keeps Umpire's Call alive, it is really admitting: we give the right to question technology, but we do not make technology God. That is a clause of restraint, and that restraint is what keeps DRS credible.

Now the part where I first accept the conventional reading, then overturn it. The conventional reading is: home umpires are biased, so Asian matches need more reviews. It sounds reasonable, but my log says otherwise. The problem is not bias — the problem is the gap between the standard of a decision and its application, and that is not the fault of any single umpire but a structural matter.

I have seen the same LBW become Umpire's Call one day and out the next — on a few centimetres of ball-tracking. Spectators cannot see that difference, so they think the rule changed. But the rule did not change; the ball went somewhere else. That is my biggest lesson — be angry at the on-field umpire, but the final decision was written on a screen in a trial chamber, in a room of percentages. I keep a review log for esports rulings too, because pixels can foul as well; cricket's pixels are bigger, but the logic is identical — evidence first, ruling after. — Root: Referee

I opened the 2026 VAR ledger again, and the same clause was staring back — only the field and the game's name had changed, the method was the same. When I watch county championship cricket from London, I see something else: in almost every match a written courtesy code operates between umpires and players — less argument about decisions, more discussion about process. Yet in Dhaka, the same situation escalates fast, because both spectators and players believe the review is a lottery. The same MCC Law, two cultures, two outcomes. That is my Diaspora Rulebook experience: one law at the centre, many applications at the edges.

I have built reviews on timestamps from the start, never on hot takes. In 2026, when I was building the football VAR ledger, I learned: write the time and the clause beside every decision, and the argument quiets down later. In cricket that habit pays even more, because decisions per innings far outnumber football's. The Asia Cup review log taught me that a tournament is really a legal document written in over-by-over chapters.

The team that does best next season will not take the most reviews — it will keep the best accounts. The question is no longer whether DRS is ruining cricket; the question is who will learn to read this system best. The law always stays the same; those who do not memorise it but understand its rhythm are the ones who win.