Timed Out: When Cricket's Rulebook Was Missing a Page

Timed Out: When Cricket's Rulebook Was Missing a Page

November 6, 2026. Arun Jaitley Stadium, Delhi. Bangladesh versus Sri Lanka at the ICC World Cup. Angelo Mathews walks to the crease and stops before facing a ball — the strap on his helmet has snapped. Fetching a replacement helmet and fitting it properly costs time. The two-minute limit expires. Bangladesh captain Shakib Al Hasan appeals — timed out. For the first time in 146 years of international cricket, a batter is dismissed under the timed-out law. Debate erupts after the match: some call it a violation of the game's spirit, others call it perfectly lawful. I opened my five-column decision log that day — minute, offence, review type, outcome, law citation. And right there the question surfaced: when a page of cricket's rulebook is missing, who decides?

Cricket's Laws are written by the Marylebone Cricket Club, and the ICC applies them on the field through its Playing Conditions. The timed-out law has long been among the least discussed clauses in the book. Its core is simple: if an incoming batter is not ready to receive the ball, and the fielding side appeals, the batter can be given out. But where does the phrase "ready" end? The law fixes the time limit clearly, yet it stays largely silent on what happens when a delay is caused by something outside the batter's control — such as a piece of equipment failing.

This is where the MCC Preamble becomes relevant. The Preamble states that cricket is governed not only by laws but also by spirit. That spirit, however, is not a clause or a condition — it is a principle, an intention. Applying an intention on the field requires explicit wording, which the timed-out law lacks. The rulebook had a missing page, and we still played on.

To me, technology and procedure are two different things. At the 2026 World Cup in Russia I watched 32 matches and audited 29 VAR reviews, and there I understood — in Russia I learned that the freeze-frame is a legal witness, but a freeze-frame can never take the place of the spirit. In cricket, DRS, UltraEdge, ball-tracking and the third umpire have documented the game far more thoroughly and made every decision re-verifiable. Yet technology plays no part in a law like timed out. This is not a question of technology; it is a question of procedure. Here the umpire must make a binary call — out or not out — backed only by a clock and an appeal.

Step by step, the Mathews incident yields a definite sequence. Step one: the previous batter, Sadeera Samarawickrama, is dismissed. Step two: the new batter, Mathews, arrives at the crease. Step three: he notices the strap of his helmet is broken. Step four: he waits for a replacement helmet. Step five: the stipulated two minutes elapse. Step six: Shakib appeals and the umpire gives him out. I trust the sequence more than the angle, and the law more than the roar — because each of those six steps is a paper record, a timeline.

Notably, nowhere in those six steps is any clear room for umpiring discretion written down. If an appeal comes and the time has expired, the batter must be given out — that is the obligation of the law. And here the limitation of Law 40 becomes glaring. Compare Law 41 on unfair play, where the fielding side's conduct can be weighed. In timed out, that consideration does not come from the batter's side, because the batter is not the suspect here — he is the victim of an equipment failure. The law protects the batter in one direction and convicts him of negligence in another.

Outside international cricket, timed out has occurred rarely even in first-class cricket; on the international stage it was entirely unprecedented, so the law had never developed an application consistency. There is no live drill for this scenario in umpire training, because it had never happened. Here the absence of precedent itself becomes a precedent — and the decision becomes instant, almost extra-judicial.

The ICC did not revisit the wording of the timed-out law after the incident, nor did it add any exception for equipment failure to the Playing Conditions. Yet the body walked the opposite path in another contested area. In 2026 the ICC moved the non-striker's-end run out — what many call the "Mankad" — out of Law 41 (unfair play) and into Law 38 (run out). That was a deliberate procedural move: pulling the matter from the moral-debate column into the column of process rules. No such step was taken for timed out — the matter still sits in the moral-debate column, even though it poses exactly the same kind of precedent crisis.

Recall the boundary countback rule of the 2026 World Cup final. Then too the champion was decided by the letter of the law, and precisely for that reason the ICC was later forced to change the rule — because readers and players understood that following the letter is not the same as delivering justice. When a rule is amended under public pressure, it reveals that a gap existed in its original text. Timed out now stands in exactly that waiting room.

Here lies my central observation: the real weakness of timed out is not Shakib's appeal but the silence of Law 40 on equipment failure. The law says out when the time expires, but the law does not say what happens when the sole cause of the delay lies beyond the batter's control. That silence forces the umpire into a mechanical decision, and that mechanicalness collides with cricket's own Preamble. The decision was made according to the letter of the law — but was it made according to its intention? That answer is not written in the rulebook, because the page is not there.

Project Restart taught me that emergency rules still demand a paper trail. When the Premier League returned during the 2026 COVID pause, we bound every new protocol — neutral venues, five substitutions, water breaks — into written documents. Because if a decision taken under emergency conditions is not recorded, it cannot later be accounted for. What cricket still lacks on timed out is precisely such a written protocol — one that clearly settles whether the clock stops when equipment fails, and who makes that call.

Now comes the uncomfortable place where emotion and law face each other. Many blamed Shakib Al Hasan, saying he struck at the game's spirit. But a rule written into the Playing Conditions, when applied, is not a personal choice — it is the fielding side's right. A side that must appeal for a decision to follow can be pressed on the morality of appealing, but not on any legal obligation to abstain. The real responsibility here does not belong to a player but to the law-making institution — which kept a rule that left no room for a humane exception. This is the procedural view in which a referee's eye that never leaves the field travels past the boundary and all the way to the drafting table.

So what is the solution? I propose three tiers. First, add a clear exception clause to Law 40 — if the proven cause of the delay is equipment failure or a medical matter, and the batter notifies the umpire immediately, the clock pauses temporarily. Second, a written checklist for the umpire — evidence (helmet), time (scorer and clock), statements (both captains), decision (with the clause cited). Third, a decision log for every incident, recorded through the match referee — exactly as we preserve DRS reviews.

Law first, then the noise. I trust sequence, not angle — and the sequence of this incident says that in that Delhi moment cricket did not merely lose a match; it exposed an administrative weakness. At the 2026 T20 World Cup and in the cycles to come, as cricket is played on bigger stages under more money and more pressure, silences like this will grow more expensive. The question belongs not to a player or a team, but to those who hold the rulebook. If another batter's helmet snaps and the clock does not stop, who is at fault — the cricketer, or the missing page of the law?