Half a Ball, a Whole Argument: Who Reads DRS in Asian Cricket?

In July 2026, India and Sri Lanka were playing a Test at the Sinhalese Sports Club in Colombo, and for the first time in Test history the players had the right to review. Nobody in the stands knew that the ball shown crashing into the stumps on the big screen would not change the decision — a clause called Umpire's Call would hand ownership straight back to the man in the middle. I watched that series from a flat in Liverpool with a notebook open, logging every review: who asked, how long it took, what came back. That was the day I understood that DRS is not a technology contest. It is a reading contest.

The notebook is still with me. When football adopted VAR, I tracked its protocol the same way. Reading the two documents side by side, my position is plain: most of the argument about DRS in Asian cricket is not about the machine. It is about who reads which clause, and who is allowed to decide.

In Test cricket each side gets two reviews, topped up by two more once 80 overs are bowled. In limited-overs cricket, two reviews, none returned. The window to signal is 15 seconds; miss it and the review is gone. Hawk-Eye projects the ball's path, UltraEdge detects contact with the edge of the bat, Real-Time Snicko listens for sound. The whole apparatus sits under the ICC's match playing conditions and their appendix — a document most spectators have never opened.

India took its time. Full adoption came with the series against England in November 2026. Pakistan, Sri Lanka and Bangladesh had entered the trial earlier. Yet the heaviest review traffic is in Asia, where spin, low slow pitches and giant screens work together. I watch Asia Cup matches from Liverpool, keeping a separate sheet: how many seconds each review took, and how many ended in Umpire's Call. My own sample, not an official one — but a sample seen with my own eyes.

One reality is discussed far less. Hawk-Eye and UltraEdge are not operated by the ICC. The host broadcaster runs them, under its own cameras and its own calibration. In England that duty stays with one company across years. In Asia the host broadcaster changes every series. The machine stays the same; the continuity does not.

I opened the playing conditions appendix again. The Umpire's Call explanation is the least-read chapter in the book. Put simply: if ball-tracking shows more than half the ball hitting the stumps, the decision changes. If less than half is hitting — the ball clipping and moving on — the on-field call stands. That 50 per cent line is the most contested boundary in Asian cricket, because a few millimetres of uncertainty decide who owns an entire decision.

The second clause: a review corrects a decision; it does not create one. The third umpire must ask whether the video evidence is conclusive. The word conclusive carries no millimetre definition. Two matches, the same frames, two different outcomes — and the crowd reads it as bias, when the problem lives in the language of the clause, not in anybody's intent.

The third clause: the frame log. Every review's frames, timestamps and camera angles are stored somewhere. Technically this behaves like a ledger — each entry recorded, no old entry quietly edited. But a ledger only works when somebody can audit it. In cricket, nobody does. Calibration, frame rate and camera selection all sit with the host broadcaster.

The fourth clause: 15 seconds. The most undervalued rule in the sport. Eleven people decide, in under twenty seconds, under pressure. The weight falls on captains like Kohli or Babar Azam, but the information arrives from a coach and an analyst behind glass — information and authority are never in the same pair of hands. My own log shows a lower success rate for reviews taken in the last ten overs than in the first ten. Those late reviews are made from fear, not from data.

The fifth clause: cricket and football took different roads. Cricket gave the player the right to refer; football did not — in VAR the referee walks to a monitor or the review room signals. Cricket trusts the projection of ball-tracking; football trusts the on-field eye and then checks it on a screen. Even the law-makers differ: MCC and ICC in one sport, IFAB in the other. The technology is nearly identical; the process is not, because each sport parks its doubt in a different place.

When the big screen shows the ball hitting the stumps and the result comes back not out, anger is understandable. My objection lies elsewhere. All the noise around Umpire's Call hides the real gap.

The real gap is the vagueness of conclusive evidence, and the extra burden placed on the third umpire since the soft signal was retired. A low catch now asks one person to judge whether the video is sufficient. Same frames, same frame rate — the outcome rests on one human's sense of what is enough. Two umpires watch the same clip with different mandates and so read it differently. Technology does not make decisions; it moves the accountability of a decision from one room to another.

Some will say VAR and DRS suffer the same flaw, so comparison is pointless. I disagree, with one condition: compare processes, not just machines. Cricket hands the player a referral right; football does not. In cricket the decision belongs to a projection; in football it belongs to the umpire's eye. Same cameras, different distribution of power — so the argument erupts in a different place.

Semi-automated offside is already in football; automated ball-tracking is coming to cricket. Automation does not erase the question, it sharpens it: the quieter the machine, the heavier the human announcement on top of it. If Asian boards agree to publish an independent calibration and review log, separate from the host broadcaster, then at the next Asia Cup we can all read a controversial review together, from the same evidence. The question is no longer about technology. It is about transparency.