Two Minutes, One Helmet Strap, and Cricket's First Timed Out

On November 6, 2026, at the Arun Jaitley Stadium in Delhi, a group-stage match of the ODI World Cup: Bangladesh versus Sri Lanka. On paper a routine fixture, in history a permanent one. Midway through Sri Lanka's innings, Sadeera Samarawickrama was dismissed. Out walked Angelo Mathews — experienced, combative, his team's last hope. At the crease, it emerged that the strap of his helmet had snapped. He waited for a replacement. Meanwhile, another clock was running: the clock of the law. The two-minute limit expired. Bangladesh captain Shakib Al Hasan appealed to the umpire. The umpire declared Angelo Mathews timed out. The first such dismissal in the history of international cricket. A helmet strap and a two-minute limit — together they produced one of the most controversial and, at the same time, least-examined legal moments in the game's history. For many years I have logged cricket and football officiating decisions in four columns — minute, incident, law, verdict. At the 2026 World Cup in Russia, I watched all 64 matches twice and recorded 455 VAR checks and the 20 decisions ultimately changed. That ledger taught me that to judge any decision, you must first reconstruct the incident with a cool head and a stopwatch. So I took this incident back to the whiteboard — to see where the clock first learned to bend. You have to understand the law, because judging a decision without understanding the law is judging nothing but emotion. Law 40 of the MCC's Laws of Cricket — Timed Out. Simply put: after the previous batter is dismissed, the incoming batter must either be in position to take guard, or his partner must be ready to receive the next ball, within two minutes. If this condition is not met, and the opposing side appeals, the incoming batter is out Timed Out. Notice two phrases. First, in position to take guard, or his partner ready to receive — the law speaks not of one batter but of the pair's readiness. Second, on appeal — the dismissal is not automatic; it demands an active claim. The law was written for a slower game, when the only defence against making crowds wait was this clause. No one imagined that a clause dormant for a century and a half would one day wake over a broken strap. This is not a new law. Before Mathews, in roughly 150 years of international cricket, no one had ever been dismissed under it. In first-class cricket its use is almost nil. It is one of those rare laws that lives on the page, not the field. The older the law, the less it is used — and the less it is used, the less clearly its application is defined. Here is the first crack. By 2026, cricket measured every line of bowling, batting and fielding with millimetre-accurate technology — ball tracking, UltraEdge, split-screen replays. But time? Time was measured by the clock inside one person's head. It never glowed on a screen, was never verified by any review process, never gave testimony through a timestamp. In Asian cricket this ambiguity is more complex still. In this region's cricket history, decisions, power and technology have always circled the same question: who gets the benefit of the doubt, and who is placed under the microscope. Whether DRS or a third-umpire review, behind every use of technology there is a key held in someone's hand — who operates it, who audits the auditor, and how clear clear really is. From Lord's to the ICC to Dhaka, the question is the same. So the Mathews incident is not merely a Bangladesh-versus-Sri Lanka matter. It is a case study of power, process and technology in Asian cricket — and at its centre lies a question nobody asked: who decides on time? I reconstruct the incident with a stopwatch. The clock starts when Samarawickrama is dismissed. Mathews arrives. The helmet strap snaps. He signals for a new helmet. It takes time for the helmet to come from the dugout. The two-minute limit passes. The umpire gives him out. Now the question: at which moment within those two minutes was Mathews ready or not ready? The law says he must be in position to take guard. Without a helmet he could not face a ball — but is wearing a helmet mandatory under the law? This is the subtle point. The law says the batter must be ready; but whose fault is a failure of a batter's protective equipment — his own, or the game's? The law does not answer, because the law assumes the equipment will be fine. I recall working on the 2026-17 IFAB deliberate-play amendment, analysing 63 disputed decisions, each with a law number, a minute, a decision and a verdict. There I learned that every word of a law is a door — open or shut, depending on who pushes it. The word ready is that door here. Who determines who is ready and who is not? The on-field umpire. Not a clock, not a third umpire, not a TV replay — only the on-field umpire's judgement. Yet in 2026, every run-out is seen by the third umpire, every no-ball checked by ball tracking, every catch by soft signal and replay. But a decision on time? No. Time remains one of the rare decisions where technology is not called. The second door: the appeal. The law is clear — timed out requires an appeal. Shakib Al Hasan appealed. The question here is not morality but process: was the appeal made within the laws? Yes. The law permits it. But assuming that what the law permits always matches the game's character is a mistake. Law and character are two different things, and cricket's problem is that we routinely confuse them. The reaction was immediate and fierce. Mathews called it disgraceful. Many fans and former players called Shakib's decision against the spirit of the game. Some said it was unfair to a senior player. Social media split in two — one side for the law, one side for courtesy. I understand the reaction, and I accept its strongest form: cricket is a game of courtesy, where informal tolerance often matters more than formal law — as when batters are spared because of bad light, an injured opponent is let off, or a doubtful run-out goes to the batter. This custom has saved the game many times, and it is what distinguishes cricket from football. But here lies the counter-intuitive truth. If everyone in that match had followed the unwritten custom of courtesy, the decision would never have come. So is the blame Shakib's alone? No. The blame belongs to the process — to a system in which, standing in 2026, the most basic element, time, hides inside one person's head. Consider it: cricket now calls technology into every decision, yet where technology is most needed — a clock — it is absent. Had there been a visible clock on the field, had the third umpire been able to verify time, Mathews would have known how long he had. There would have been no controversy, because the decision would have belonged to the clock, not to judgement. And a clock never takes sides. I notice a pattern here. In Asian cricket, controversy tends to centre on the player's decision, not on the process's weakness. Yet it is the process that produces the decision. At the 2026 World Cup in Russia I saw that controversy did not diminish after VAR arrived — because the controversy lay not in VAR's decisions but in VAR's thresholds: who defines clear and obvious, who may request a review, and who delivers the verdict. Cricket's DRS stands in exactly the same place. Who calls it clear evidence on UltraEdge, who calls it umpire's call — these definitions are the true centre of controversy, not the decision itself. Mathews's timed out is the same kind of definitional gap: what does ready mean, and who decides? There is no answer, because the law never placed that question before us. The helmet question adds another layer. Modern protective equipment is mandatory — helmet, arm guard, pads. In Mathews's case the equipment itself was faulty. The question: is the fault of faulty equipment the batter's, or the game's? The law says he must be ready; but if readiness is disrupted by a cause beyond his control — a snapped strap — should the law apply the same way? Here the blindness of the law surfaces. The law measures people equally but does not measure circumstances. This is the central problem of timed out: it is a binary law — either ready or not ready — while reality is never binary. Mathews was not unprepared by choice; he was unprepared by accident. The law cannot tell the difference, because the law does not recognise people, only conditions. I translate the lesson from my football VAR ledger into cricket's language. In football, offside was once a decision of feeling; now it is a line, a frame, a timestamp. In cricket, the arrival of ball tracking did the same — from out seemed to out proven. But time is still at the stage of feeling. Mathews's case shows cricket has spread technology everywhere except the simplest place. The clock's decision is still a decision of feeling. And a word on the ethics of the appeal. Many say Shakib's appeal was legal but disrespectful. I am uncomfortable with that sentence, because it puts law and morality on the same scale. If a law yields a disrespectful decision, the blame belongs to the law — not to the person who follows it. Shakib did what the law allowed. If that feels wrong, change the law; do not blame the player. That is my whiteboard verdict: whether the timed-out law itself is right is a matter for debate; but as the law is written, the decision was correct. The third door: who watches the clock? No one. The two on-field umpires manage the match, count balls, handle DRS calls, and juggle a hundred small decisions. One of them must also count time — in his head, amid other work. This is not something a human can do accurately. And why is a task humans cannot do accurately being left to humans? Here genuine reform is needed. The third umpire should have a visible timer, as the VAR has a replay monitor in football. Time, too, should be a verifiable element — with a timestamp, a screen, a record. Cricket has already proven it can do this: ball tracking, UltraEdge, snicko all solve the same kind of problem. And here the question of Asian cricket returns. Who will run this clock, and whose decisions will fall under the microscope? Complaints about decisions in Asian teams' matches are nothing new — sometimes true, sometimes an excuse. But if the process is opaque, the boundary between complaint and evidence blurs too. A visible clock would make the decision transparent — and transparency is equal for both sides; that is its value. Now to the counter-intuitive angle that overturns the dominant note of the debate. Throughout the controversy everyone asked: was Shakib's appeal right? But the real question was different: who allowed such a situation to arise? Did the umpires warn Mathews? The law carries no obligation to warn, but sound match management should. Had an umpire told Mathews you have one minute left, the helmet might have arrived and the controversy never been born. That is match management — not the letter of the law but the spirit of its application. In football, referees warn players in exactly this way — also unwritten, yet part of the craft of running a match. So my whiteboard verdict reads: a lawful decision, poor management. The law was right; the process failed. And that distinction is one cricket often fails to see. One more thing is notable. After the incident, the MCC stated clearly that the umpires had made the correct decision under the law. But correct and good are not the same. A decision can be lawful and still be damaging to the game. Cricket's governing bodies routinely forget this distinction, because to them law means justice. But the biggest lesson here is different. The Mathews incident proves cricket still swings between technology and custom. On one side, DRS, ball tracking, UltraEdge — millimetre accuracy. On the other, time, courtesy, spirit — all vague, unwritten, informal. Controversy is born in the collision of these two worlds. And the victim of the collision is the player — who wants to play by one world's rules, only to find his fate decided by another's. Mathews, trying to fix a strap, became the victim of a law that wakes once a century — but wakes precisely at the moment someone least needs it. My 47 years of observation tell me that in sport, controversy does not diminish when laws change; it diminishes when the process becomes transparent. In football, offside controversy fell after the line was drawn, not before VAR. In cricket, no-ball controversy fell after ball tracking. So how will time controversy fall? When time becomes visible. So looking forward, I propose three things. First, let there be a visible time clock on the field — seen by batter, crowd and commentator alike, just as tennis has a serve clock. Second, let the third umpire have the power to verify time, as with DRS. Third, let timed out become a reviewable decision, so a side can spend a review to have it checked. These are not fantasies. Cricket has already made every decision verifiable — except time. Only one place was left out. And because that one place was left out, Angelo Mathews walked into history — with a snapped strap and a two-minute clock in hand. Had the clock been visible on the field, that day in Delhi would not have written cricket history — only a match. That is the real question: do we want decisions to come from human feeling, or from the ticking of a clock? Cricket has not yet answered. Mathews perhaps has — he said the game has changed, and he cannot accept it. But whether the game has changed is not my question. Mine is: in changing, where has cricket put its clock?