Timed Out: The Two-Minute Clock, One Appeal, and Cricket's Missing Ledger

What happened at Delhi's Arun Jaitley Stadium on the evening of November 6, 2026, had not been seen in 146 years of international cricket. Angelo Mathews walked in after the sixth wicket fell. His helmet strap snapped. Getting a replacement took time. Two minutes elapsed. Bangladesh captain Shakib Al Hasan appealed. Mathews was out — timed out.

I watched that match from Barishal. The post-match debate was entirely framed as spirit of cricket versus the letter of the law. I got stuck somewhere else. The question was not about Mathews' helmet, nor about his morality. The question was: who was running the clock, and where was that clock's authoritative record written down?

That single question exposes the structural fault line in cricket's decision-making. To see it properly, the incident has to be frozen into a still frame.

Timed out is not a new law. The 1774 records of the Marlborough Cricket Club already mention punishing a batter for wasting time. Law 40.1.1 now states that the incoming batter must be ready to receive a ball within two minutes of the previous batter's dismissal or retirement. In October 2026, MCC cut that window from three minutes to two. And yet, from the first Test in 1877 until November 6, 2026, no one in international cricket had ever been dismissed under it. Not once.

The dry explanation is obvious. The law was always on the books; the pathway to its application had never opened.

That pathway opened because of Law 31. An umpire cannot give a batter out unless the fielding side appeals. Timed out, therefore, is not merely a factual state — it is a procedural lock whose key sits in the fielding captain's pocket. Shakib turned the key. Mathews was stuck.

Add the Preamble to the Laws. It states that cricket owes much of its unique appeal to being played not only within its Laws but also within the Spirit of the Game. The beauty of those two clauses is that neither outranks the other. The controversy, therefore, cannot be settled — it is structurally inevitable.

I first felt that structural inevitability in football, on June 16, 2026, in Kazan. In France versus Australia, referee Andrés Cunha used VAR to award the first penalty in World Cup history — Josh Risdon's handball on Antoine Griezmann. I froze that first VAR penalty for 72 hours until it became a legal precedent. That is where I learned that technology does not change decisions; it changes whose shoulders carry the liability for them.

In World Cup playing conditions the arithmetic gets messier. The tournament regulations lodge the authority over time with the match referee, while the authority over the final decision stays with the on-field umpire. Two authorities, two locations. Delhi showed that split more clearly than any match in years, and almost nobody discussed it.

Freeze the incident and the first layer is simple but overlooked: timed out is not a punishment for a batter's offence. It is a condition precedent. A batter who is not ready to face has, in the eyes of the law, not yet arrived. Occupying the crease is a process, not an event. The bowler at the other end must also be ready, which is why both ends of the preparation matter.

The second layer is more uncomfortable: an appeal is a trigger, not a moral verdict. In cricket culture we read appeals as a measure of sportsmanship. In law, an appeal is only a procedural switch. Had Shakib not appealed, nothing dishonourable would have occurred — the law would simply have lain dormant. That is the real unease: our familiar moral argument rests on a procedural condition that cricket has never openly acknowledged. MCC later confirmed the decision was correct in law. Yet the Preamble exists precisely for moments where correct and just are not the same thing.

The third layer is the burden of proof. Here the umpire is a finder of fact on one question: was the batter ready at two minutes? Football's VAR protocol has a "clear and obvious error" threshold. Timed out has no equivalent threshold. Once the clock starts, the decision is binary — two minutes, or two minutes and one second. At the 2026 Qatar World Cup, three Argentine goals against Saudi Arabia were chalked off in the first half on millimetre-level offside tolerances. Technology manufactured a meaningless precision there, and nobody asked who sets the tolerance band. The same problem exists with time; we simply do not see it.

The fourth layer is the most important and the most invisible: there is no public ledger for the clock. The countdown we watch on broadcast is a television product, not an official record. The official accounting lives on the umpire's wristwatch and in the match referee's head. As a result, there is no time-stamped, publicly verifiable record of the event anywhere. And that record is the only raw material from which a precedent can be built.

This is where the football comparison becomes essential. Football does not publish VAR audio continuously, but it retains it and releases it on request. In cricket we see Hawk-Eye ball-tracking traces on television, but never a trace of the procedural clock. Where football at least left the audit door ajar, cricket never built the door.

One more dimension cannot be skipped — equipment failure and the duty-of-care chain. Mathews' snapped helmet strap was an equipment failure, not an emotional event. The law contains no provision for stopping the clock when equipment fails. The question is who carries that risk: the batter on the field, the team manager who prepares spare kit, the helmet manufacturer, or the match referee who certifies equipment? Silence is itself a decision, and here the law is silent.

I traced the Eriksen collapse from emergency to legal duty — after Christian Eriksen went down in the 43rd minute of Denmark versus Finland at Parken Stadium in Copenhagen on June 12, 2026. There, the question was who owed what to whom, and within what time. Cricket has never written that duty-of-care chain this clearly, because cricket has never fused equipment failure and time failure into a single protocol.

I also think back to July 2026. During the pandemic hiatus, reading the 93-page CAS award that overturned Manchester City's two-year UEFA ban and cut the fine from €30m to €10m, a pattern became clear: the legitimacy of a ruling depends on the precision of the documented record. Because cricket does not want that documentation, it returns to the same argument every time.

The Asian market enters here too. International cricket has DRS and full broadcast systems; Bangladesh's domestic game, the Dhaka Premier League, and the lower rungs of the BPL do not. Yet Law 40 is identical. The same two-minute clock, the same umpiring discretion — but in one place a time-stamped video record exists, and in the other it does not. That is where technological inequality becomes legal inequality. Standing on Bangladeshi soil, this is impossible to miss, because here many decisions rest permanently on unverifiable record.

The debate that evening was framed for us incorrectly. We were told it was spirit of cricket versus law. It was actually record versus memory. What becomes a millimetre argument in football becomes a five-second argument in cricket. Both are the same structural disease: the boundary of a decision is opaque, and the drawing of that boundary has been outsourced to technology.

I learned to read a foul as a fact pattern, not a moral story — and the Mathews incident is exactly that. There is no villain here. The accused is the incompleteness of the written process.

One gap in that incompleteness stands out most. Cricket still does not retain the conversation inside the process. Football at least logs the exchange between referee and VAR studio, even if it is not always released. In cricket, the words between on-field and TV umpires, the exact start and stop of the clock, the sliding definition of readiness — none of it is permanently stored. So if a similar incident produces a different outcome next time, there is no way to prove the inconsistency. A precedent only forms when the record of the earlier event is verifiable.

The question now is whether cricket will write an explicit clock-stop provision for equipment failure, whether it will keep leaning on the fielding captain's appeal forever, or whether it will hand the match referee the power to review these moments on their own motion.

One answer I do know: the game needs a time-stamped, publicly auditable decision ledger. Not a blockchain — an audit trail. A permanent record of when the clock started, when it stopped, when the appeal came, and what the umpire reasoned. The day cricket honestly admits that its name comes from time, timed out will stop being a controversy and start being a precedent.