The Third Umpire's Stopwatch: Review, Rule and the Accountability Gap in Asian Cricket

Stopwatch starts: 00:00. The big screen still reads, "Third umpire checking." Two batters stand mid-pitch, the wicketkeeper has pulled off his gloves, the fielding captain is setting a field from mid-on. At 01:47 the first replay appears. At 03:09, UltraEdge. At 04:12, the decision. Four minutes and twelve seconds — one of the longest waits in my log from an Asian match.

The time was spent on the field, but the decision was manufactured in an edit room. In that room sat the third umpire, beside him a broadcast director, on his screen ball-tracking software, in his ear a specific version of the ICC playing conditions. Then came the announcement, the camera turned away, the commentator explained it. But one question was never written down: which frame turned the decision, and who owns that turn.

I started this third-umpire log from Dhaka because in our cricket decisions get argued about, but the steps inside a decision never get discussed. Since my days as a volunteer match-data recorder in Rangpur, my habit has been to timestamp every incident. As a statistics student I began tagging review frames — what was seen at which second, what was dropped how many seconds later. There was no video budget, only a spreadsheet and stubbornness.

The rule comes first, the technology second

DRS entered Asian grounds in July 2026, at Colombo's Sinhalese Sports Club, through the India-Sri Lanka series. Since then every controversy has had the same root: humans write the rules, technology only measures them. The MCC writes the Laws, the ICC Cricket Committee fixes the playing conditions, and the Asian Cricket Council runs its own version in its own tournaments.

The gap between those three layers opens in three places. First, playing conditions are tweaked before every tournament — sometimes the umpire's-call threshold, sometimes the soft signal on catches. In May 2026 the ICC announced the soft signal would be scrapped, effective from June. The result: the same kind of catch is out in one season on the on-field umpire's hunch, and not out the next season on camera evidence alone.

Second, technology is not uniform across venues. The camera set-up at a neutral venue in Dubai or Sharjah is not identical to Mirpur or Pallekele. High frame-rate cameras, UltraEdge sensors, ball-tracking calibration — all are configured before a match, and the person who configures them never appears on a broadcast.

Third, time. Teams get a limited window to decide on a review, usually 15 seconds. Since 2026, over-rate shortfalls carry in-match penalties — five runs per over, plus fielding restrictions. But there is no written limit on how long a third umpire may take.

Where the decision is actually made

My log's first column is time, the second provider, the third frame number. After three years of keeping it, five things became clear that nobody outside the ground is supposed to know.

The first is the clock. When the on-field umpire looks at the captain, and the captain looks at the dressing room, it is often unclear who is running the 15-second timer. Some broadcasts show an on-screen timer; some do not. Among the matches I logged where no timer was shown, one review was clearly taken after 20 seconds — and nobody questioned it. When the rule is invisible, its application is invisible too.

The second is the big screen. The third umpire watches a monitor, but the replays he sees are chosen by a broadcast director. Which angle arrives when, when the spin-cam is used, how quickly the snickometer is shown — the umpire has no say in any of it. The broadcast director is effectively an unofficial umpire whose name never reaches the scorecard. In my log, a certain type of catch-behind review averaged four angles, while an identical review elsewhere showed six — the difference driven by the match's importance, not by the rules.

The third is ball-tracking. This is where the biggest misunderstanding lives. Ball-tracking does not decide, it predicts. If the projection of the ball hitting the stumps after pitching is below the threshold, the decision reverts to the on-field umpire — umpire's call. The final call therefore comes from an earlier human estimate, not from the machine. Technology predicts; technology does not judge. As long as umpire's call exists, DRS is really a system for checking a human verdict with cameras, not a system for machines to deliver verdicts.

The fourth is the post-soft-signal world. Previously, on catches, the on-field umpire signalled his hunch and the third umpire respected it. With the system scrapped, the third umpire decides alone. On paper this increases clarity. In practice it relocates responsibility rather than expanding it — before, a wrong call could be blamed on a wrong soft signal; now the full weight sits on one person, and the reasoning behind the error is stored nowhere. Responsibility increased; the accountability record did not.

The fifth is the Asian ground reality. From March to June, temperature, humidity and light quality do not stay constant in this region. Evening dew makes the ball skid, which feeds into ball-tracking projections. Across a Test Championship cycle, travel schedules can put one umpire in three matches in Dubai in a week, while another series goes without an experienced hand. Change the venue and the rule does not change, but its application does. That is the rule-instability map — one law, different edges.

In Bangladesh, a review is an asset

I keep Bangladesh's matches separate in my log, because here a review is not just technology — it is a scarce resource, like a timeout. On Asia's spin-friendly pitches, reviews are spent most heavily against LBW, and in a large share of the matches I logged, those reviews were gone inside the first ten overs. The cost lands in the second half of the match, when the pitch begins to break and a review is genuinely needed — and none is left.

It matters to separate a batter's failure from a captain's error here. The captain takes the review decision, but that decision depends on the voices of the wicketkeeper, the close fielder and the senior player at slip. In Asian teams this decision chain is culturally more deference-based — whoever is senior carries more weight. The more technology the review system acquired, the more cultural the review decision became.

One pattern held consistently in my log: when a team falls behind in a match, its review usage changes shape — more defensive, less planned. The review becomes an emotional decision rather than a tactical one. And under ICC rules, a review that survives is not carried into the next innings; the resource resets each innings, exactly as a session resets with a new ball.

The crowd's anger is landing in the wrong place

This is the uncomfortable part. When a controversy erupts on the field or on screen, the anger goes at the umpire. My log says a large share of the errors are not a matter of umpiring skill but the product of a system where each step of a decision sits with a different actor, while the blame sits on one neck.

Consider it. The broadcasters choose the replay angles, a match-setup team handles ball-tracking calibration, the playing conditions set the threshold, and one umpire delivers the final announcement. We attach the combined output of four separate organisations to one person's name. As technology grew, trust in cricket did not grow; the place where trust is missing simply moved from the field to behind the screen.

And one gap goes almost unnoticed — the archive. Where does the third umpire's audio and video footage go after a match, how long is it kept, can anyone see it on request? To my knowledge there is no obligation to release this footage in the public interest. So when an argument breaks out, we see the replay but not the process. The frame that turned the decision was on air tonight and is gone tomorrow. If an archive is not for accountability, what exactly is it for?

The question nobody has asked yet

The fix is not more technology but a visible process. If the third umpire's audio log were published within 24 hours of a match, if the playing conditions' version number appeared on the scoreboard, and if the three decisive frames of every review were permanently preserved, what would cricket actually lose? Probably nothing. It would gain one thing that is now rarest in Asian cricket — the names behind the decision.