Timed Out: Two Minutes on the Clock, a Broken Helmet Strap and the Trial of Cricket's Spirit

On November 6, 2026, at the Arun Jaitley Stadium in Delhi. A World Cup league match, Sri Lanka versus Bangladesh. The 24th over of Sri Lanka's innings was drawing to a close. Angelo Mathews was due to walk out next. On the verge of stepping onto the field, he realised his helmet strap had snapped. Batting in a helmet without a strap is not permitted — a safety rule. He turned back towards the dressing room to fetch a new helmet. Before he could, Bangladesh's fielders appealed to the umpire. The third umpire checked the clock — the stipulated two minutes had elapsed. The announcement came: timed out. The first such dismissal in roughly a century and a half of international cricket. That night the debate split in two. One side said, "The spirit of cricket has been wounded." The other said, "The law is the law." But when I looked at the clock's hands instead of the scorecard, the question changed — what exactly were the umpires measuring? The batter's readiness, or merely his time of arrival at the crease? I come from football's VAR room. After being selected in India's first VAR certification programme in 2026, I learned that a decision must be analysed on three levels — what the law says, what the official saw, and what the technology recorded. Those three levels never fully align. In cricket's timed-out controversy, that exact gap came to the surface. The concept of timed out is not new. Law 40.1.1 of the Laws of Cricket, administered by the Marylebone Cricket Club (MCC), states that an incoming batter must be ready to bat within a stipulated time of the fall of the previous wicket. That time was originally three minutes; later, in the faster formats, it was reduced to two. In the playing conditions of the 2026 World Cup, the two-minute limit applied. The law was written on a simple assumption: a professional batter will arrive at the crease, take guard, and be ready. But nowhere does the law say what happens if a helmet strap snaps, if a pad strap comes loose, if something gets in the eye. The clock in the umpire's hand does not measure a batter's safety or equipment failure; it measures one thing only — the time taken to reach the crease. Here is the law's first gap. When it was written, it assumed that any delay by a batter meant deliberate stalling. In reality, a delay can be safety-related, mechanical, even medical. In football I know this problem — a referee can stop play for an injury, because the word "stoppage" is written clearly into the law. In cricket's timed-out law, that word of flexibility is absent. There are precedents for timed out in first-class cricket, though this was the first at international level. The law was not dead; it simply had never been invoked. So on that evening in 2026 it suddenly came alive, bringing with it a controversy the cricket administration was not prepared for. Curiously, the law had almost always lain dormant — umpires generally showed leniency and granted extra time. So the question arises: why such sudden strictness? The MCC's preamble carries a section called the "Spirit of Cricket," stating that it is important to respect not just the letter of the law but the purpose of the game. In the Mathews controversy it was precisely this preamble that was most quoted. Sadly, a preamble issues no verdict; it offers only direction. Now to the real work — examining the decision from inside the game, from multiple angles. Angle one: when did the clock start? The timed-out countdown begins from the moment the previous batter is dismissed. In Mathews's case, it began after Sadira Samarawickrama was dismissed. But there is a subtle point here — how did the umpires know the two minutes were up? There was no visible countdown on the big screen, which a batter could watch to hurry himself along. In other words, the batter did not know precisely how much time remained. In football's VAR, I have seen that every decision carries a time-stamp; in cricket's timed out, that stamp is invisible to the viewer. Angle two: the sequence of the appeal. Timed out is an appeal-dependent dismissal. The umpire cannot give it out on his own; the fielding side must appeal. Bangladesh captain Shakib Al Hasan appealed. The umpires asked him whether he would withdraw the appeal. He did not. The question here is one of morality, not of law — and conflating the two is our biggest analytical error. Angle three: the definition of readiness. The law says the batter must be "ready." But what does ready mean? Standing at the crease, or taking guard, or facing up to the ball? Mathews was not at the crease; he was inside the dressing room. So to the umpires the decision was mechanically clear. But if the definition of readiness had been a little more flexible, the question would arise whether equipment failure counts as a valid reason. In 2026 I analysed 29 VAR reviews and built a framework dividing every decision into "information," "interpretation" and "outcome." In Mathews's decision the information is clear, but at the interpretation level the law is silent. Angle four: the opponent's role. Bangladesh acted entirely within the law. But the unwritten code of sport says that in an opponent's misfortune an appeal is usually withdrawn — especially when the delay is unintentional. Here, the decision not to withdraw was strategic. Shakib later explained that his team's interest came first. I see this not as a moral judgment but as a strategic decision — because in the context of a match, every captain must make that calculation. Angle five: the role of technology. The third umpire's decision came from a combination of television footage and the clock. But television footage does not show time in a single frame; it is a continuous stream. So the question "when exactly did the two minutes end" has no answer in any single frame. Here my referee's-eye habit comes into play: I always look for the time-stamp on a decision, because it tells me how reliable the process is. Angle six: documentation. Every review in international cricket is logged, but for timed out there is no standard record — who ran the clock, at what moment time expired, whether the batter had been warned earlier. After VAR came in in football, we learned that every decision needs an audit trail behind it. In cricket's timed out, that audit trail is missing, and that is what will breed the same controversy again. Placing these six angles together produces a clear picture: the timed-out decision was procedurally valid, but communicatively weak. The batter did not know how much time remained, the viewer did not know the exact moment the clock stopped, and the law contained no clear reference to equipment failure. To me this is not a decision failure but a law failure — a law that never considered an ordinary situation in reality. Now to the part where ordinary analysis stops. Everyone asked, "Is this against the spirit of cricket?" But the real question is different — are being valid and being fair the same thing? In my referee's eye, the answer is no. Validity comes from the law; fairness comes from context. Mathews's dismissal was valid — precise under the rule. But was it fair? Doubt remains, because the cause of the delay was an accident, not negligence. In football I see this distinction daily: a handball is legally a handball, but if the ball deflects off a defender's own hand, the fairness of the decision comes into question. The second misconception: tying this decision to the match result. Mathews's dismissal did change the course of the match, but the correctness of a decision should not be measured by its outcome. A good decision can have a bad outcome, and a bad decision a good one. In 2026 I learned that certification is not the same as certainty — that lesson applies to umpiring analysis too. The third misconception: blind faith in technology. We assume a clock means accuracy. But a clock only tells time, not context. Technology gives us information, not decisions. The human who looks at the clock and gives the batter out is the one actually deciding — and if that human has no clear guidance on equipment failure, then technology only adds confidence, not justice. So what is the way forward? In my view, the timed-out law needs a clear amendment — recognising mandatory equipment-related delays as a valid reason, and introducing a visible countdown for both batter and spectator. In football's VAR room we learned that a good process does not make a decision popular, but at least it makes it explainable. The question before cricket's administrators is now this: do we want to follow the law blindly, or to build a process in which the law and the spirit of the game can survive together? The answer is probably both — but it will come from clear rules, not from the emotion of a single decision.