Timed Out: Delhi's Two Minutes and the Silent Gaps in Cricket's Law

On November 6, 2026, at the Arun Jaitley Stadium in Delhi, Bangladesh and Sri Lanka met in the league stage of the ICC Men's Cricket World Cup. Midway through Sri Lanka's innings, Sadeera Samarawickrama was dismissed and Angelo Mathews walked out to bat. Once at the crease, he realised the strap of his helmet had broken. The wait for a replacement helmet began, and during that wait Bangladesh captain Shakib Al Hasan appealed. On-field umpires Marais Erasmus and Richard Illingworth assessed the situation and ruled Mathews timed out. It was the first time in the history of international cricket that a batter was dismissed under this law. A broken helmet strap, an appeal, and a two-minute clock — the convergence of these three produced a decision whose echo has not faded. To me this is not merely a controversy; it is a protocol stress test, where the written law and the reality of the field stood face to face. In Kuala Lumpur I have been logging review-related decisions since 2026; even then the pattern was already there — controversy comes not from the law, but from the consistency of its application. The law first. Under Law 40.1.1 of the MCC Laws of Cricket, after the fall of a wicket or the retirement of a batter, the incoming batter must be ready to receive the ball within three minutes. The ICC reduced that limit to two minutes in the playing conditions for the 2026 World Cup. So the clock ticking in front of Mathews was a two-minute clock. Curiously, this is one of the oldest laws in cricket, yet it had never been enforced in international cricket — until 2026. A comparison is relevant here. Cricket's review machinery — DRS, third-umpire protocols — has become remarkably standardised over the past decade. Ball-tracking, UltraEdge, Snicko: every decision rests on measurable data. In my audit of VAR protocols at the 2026 Russia World Cup, the finding was that where technology exists, consistency of decision-making rises. But laws like timed out lack that technological clarity — here you depend on the umpire's clock and judgement. Let me look at the incident frame by frame. The clock starts from the moment the previous wicket falls. First question: when did Mathews reach the crease, and when was the helmet problem detected? Second question: did the strap break before he was due to be ready, or after he had passed the two-minute limit? Third question: did the umpires ever call Time, which under the law would have stopped the clock? The answers to these three questions form the basis of the decision. There is a subtle but crucial decision gate here — the appeal. Timed out is an appeal-dependent dismissal. The umpire does not dismiss a player on his own initiative; the fielding side must appeal. Until Shakib Al Hasan appealed, the decision was incomplete. This is a unique feature of cricket that does not map onto football's VAR — in football the referee decides himself, without waiting for an appeal. In cricket the appeal is a point of consent, where the morality of the game and the letter of the law are tested together. Mathews' argument was mechanical failure — equipment malfunction. The law contains the phrase reasonable time, but it is unclear what happens in the case of equipment failure. In 2026, when I was logging small review incidents in Kuala Lumpur, I saw that cricket's protocols often ignore a player's human condition. A batter standing mid-pitch adjusting his helmet strap is not a cunning delay; it is an involuntary event. But the law's clock does not stop. The umpires' decision was hard, and they correctly chose the hard path. They followed the law. The question is whether they had any room for discretion. The law says reasonable time, and that phrase itself opens the door to discretion. If the umpire judged the helmet malfunction to be a reasonable cause, he could have extended the time. But the biggest problem here is the absence of consistency — there is no written standard for when something is reasonable and when it is not. Another layer of the controversy is the withdrawal of an appeal. Under the law, the appealing side may withdraw the appeal, and the batter is then not out. The 2026 IPL Mankad dismissal of Jos Buttler raised the same question — legal, but moral? Had Bangladesh withdrawn the appeal, Mathews would have been spared. Shakib did not, and he later said it was part of the law. This is the core difference between cricket's and football's review philosophy — in football decisions are centralised, in cricket they are participatory. In my working method I treat every incident as a decision tree — trigger, review type, final call, and law citation. In the Mathews incident the trigger was Samarawickrama's dismissal, the review type was the on-field umpire's immediate judgement, the final call was timed out, and the law citation was Article 40.1.1. Within this framework one thing is clear — the decision was not wrong, but the path to it was opaque. The significance grows in the context of Asian cricket. Bangladesh, Sri Lanka, India, Pakistan — Asian teams have become markedly mature in DRS usage over the past decade, learning the strategy of conserving reviews. But that maturity is absent in marginal laws like timed out, because here there is no review, no technology — only the umpire's clock. In an Asian cricket culture where emotion over umpiring decisions runs high, such opaque laws will sow the seeds of even bigger controversies in the future. Now to the emotion. Around the world the criticism was about the spirit of cricket. Many said following the law is not the same as justice. But there is a counter-argument here that I consider important. If we relax the law every time we invoke human factors, consistency is lost, and consistency is the foundation of umpiring. In my view the referee's eye is a frame-by-frame threshold test, not a whistle — every decision must be measured against the same standard, or the game descends into chaos. Yet there is another layer many skip — match management. A good umpire does not merely apply the law; he also manages the flow of the game. Had the umpire actively managed the situation while Mathews waited for his helmet — perhaps warning him and extending the time, or clearly communicating the clock — the controversy might never have been born. Here the fault is not the law's; it is the process's. Human factors must also be weighed — fatigue, pressure, the camera's eye. In a World Cup match, in front of a huge crowd, deciding within two minutes is not easy. But that is the reality of umpiring, and that is precisely why protocols need to be clearer, so that umpires are freed from the burden of personal judgement. Looking ahead, my proposal is simple. First, the ICC should create a clear definition of reasonable time, separately addressing equipment failure, medical issues, and safety. Second, a visible clock should be placed on the scoreboard or broadcast so everyone knows how much time remains. Third, the ethics of withdrawing an appeal should be brought into written guidance for players. If cricket truly wants to be a fair game, its laws must not merely be written — they must be transparent, measurable, and equally understood by all. Mathews' dismissal is a historic moment, but it is also a warning. When a law that had never been enforced was enforced for the first time, its gaps became visible. The question now is this — the next time a helmet strap breaks, will the umpire have a clear answer in hand, or will a silent two-minute clock again settle everything?