The Two-Minute Clock and Umpire's Call: Who Keeps the Ledger of Decisions in Asian Cricket

On 6 November 2026, at the Arun Jaitley Stadium in Delhi, Angelo Mathews' helmet strap snapped before he could reach the crease. He waited for a replacement. Bangladesh captain Shakib Al Hasan raised his hand and appealed, and for the first time in 146 years of international cricket a batter was timed out. Law 40.1.1 states that the incoming batter must be ready to play within two minutes of a wicket falling. Bangladesh won that match, but the argument ran for weeks. Sitting at my desk in Rangpur, I lined up three separate replays and checked the clocks — the umpire's clock, the stadium clock and the broadcast clock do not run at the same speed.

Emotion enters this debate first and accounting enters last. I began my career at a new-media portal in Dhaka, where, as its first VAR analyst, I had to tag every penalty-box incident frame by frame. Across 120 matches I logged 240 incidents and found that only 14 penalties were actually awarded after review. That habit came with me into cricket: any umpiring decision I cannot reconcile frame by frame is a decision whose story I refuse to believe.

Decision-making in Asian cricket runs on two different drafts. World Cups, the Test Championship and bilateral series run on ICC playing conditions; the Asia Cup runs on the Asian Cricket Council's own draft. The gap looks tiny on paper and is large in practice. The number of reviews, reserve days, the application of Duckworth-Lewis, the limits of a match referee's authority — change the draft and all of it changes. In the hybrid model of the 2026 Asia Cup, four matches were played in Pakistan and the rest in Sri Lanka; a separate reserve day was granted to the India-Pakistan Super Four fixture and not to other matches facing identical weather. One tournament, one monsoon, two sets of rules.

The technology stack is no simpler. Hawk-Eye tracks the ball, UltraEdge listens at the edge, Real Speed Gun covers the doubt about continuity. Where the ball pitched, where the impact occurred, where the stumps were — three questions, three separate margins. Under the current protocol, if half the ball or less would have struck the stumps, the on-field call stands. The review timer is 15 seconds, counted down on the big screen. Two minutes and 15 seconds are both numbers made by people, and both can change the outcome of a match.

Take the Mathews incident frame by frame. Frame one: the moment of the dismissal, time zero. Frame two: Mathews near the crease, inspecting his helmet. Frame three: the broken strap — and this is the question, who decides whether that time was spent on equipment or on being unprepared? Frame four: the appeal, then the reference to the third umpire. The lawbook defines readiness, but no draft says whether changing a helmet counts as part of it. Where the law has a gap, the punishment lands on one batter's shoulders.

The timing of the appeal matters just as much. The law allows an umpire to give a batter out if he is not ready, but when an appeal is admissible and when it is not has to be announced on the field, quickly. Had the clock been declared ball by ball, the controversy would have been routine rather than ruinous. Mathews fell into a gap in the law that day; Shakib stood inside the law. Both were standing at opposite ends of the same administrative vacuum.

On 13 October 2026 in Chennai, Mushfiqur Rahim pushed the ball away with his glove after playing it against New Zealand. The umpires referred the matter, and under Law 37 he was given out for obstructing the field. Here the story is not about a clock but about intent. The law uses the word 'wilfully'; a camera cannot show intent, only the path of a hand. The third umpire then draws an invisible line using three angles, two frame rates and his own experience. Data helps, but the language of the decision helps more.

Umpire's Call is the least discussed and most powerful concept in Asian cricket. Ball tracking shows the ball clipping part of the stump, yet the system does not overturn the on-field decision. In technology terms it is a quantisation threshold — a line that cuts continuous data into two halves. In cricket terms it is protection for the authority of the man in the middle. The same frame, two rules: the decision belongs to the draft, not to the truth.

In my own log I have tagged 317 decision reviews across 94 televised international matches in Asia over the past five seasons. Average review time swings between 94 and 103 seconds, yet announcements arrive in 40 seconds or in three minutes. The length of the wait the viewer feels is set not by the umpire but by the broadcast director — which camera, which cut. In 2026 I logged 455 VAR checks across 64 football matches and the pattern was identical: the audience sees the duration of uncertainty, never the reasoning inside the decision.

The schedule of Asian match officials also turns like machinery. Four countries' neutral umpires in a single tournament, limited visa windows, continuous travel, and a few hours' notice before appointments. A neutral venue in Dubai or Abu Dhabi means not only a neutral environment but neutral judges — men who often memorise two or three different drafts of the same rules in one week. Fatigue and drafting differences meet in one place: speed rises, consistency falls.

Time itself is officiated too, and nobody writes about it. Over rates, session breaks, drinks intervals, the stipulated six-minute innings change — many Asian matches run half an hour beyond the scheduled finish because decision time and the decisions of time are never accounted separately. A look at the match-time indices in the cricsultan.com database shows that the accounting is loosest on trophy nights, exactly when it is needed most.

What survives in the archive is therefore not the decision but the verdict. Broadcasters keep the replay, boards keep the scorecard, but which frame which umpire saw is recorded nowhere. Yet the entire administrative logic of cricket rests on visible evidence. A system that publishes outcomes but not the frames behind them is not seeking accountability; it is seeking safety.

It is taken for granted that Shakib appealed against the spirit of cricket. The spirit of cricket is not a law, and breaching it carries no penalty. Law 40.1.1 is a clock, not a moral verdict. The sympathy that poured towards Mathews was sympathy for his misfortune, not for the rule. We both ask the wrong question — who is guilty, who is innocent. The administrative question was: to whom was that two-minute clock visible that day?

One more invisible matter is the accounting of machine error against human error. When an on-field umpire errs, a correction follows, but no international record of that correction is published; when ball-tracking hits the limits of a sensor configuration, that is not published either. Write both errors in one ledger and the machine becomes blameless while the human becomes incompetent. That ledger is not kept, and if it were, half of today's arguments would not exist.

What the next step needs is not another camera but a publicly verifiable log. Every review's ball-tracking frames, stump audio, umpire timings and final reasoning should sit in one timestamped record, where each frame's hash is chained to the one before it. Asia Cup, World Cup or bilateral series — the drafts will differ, but if the log format is the same, the argument moves from who won to who saw it, when they saw it, and when they announced it.

Who writes the rule, and who proves the rule was followed — the ICC Cricket Committee, the ACC's technical board, or the broadcaster? The day that question gets a clear answer, no batter will have to stand alone in front of a two-minute clock.