Timed Out: Cricket's Law vs Emotion on the Two-Minute Line

Arun Jaitley Stadium, Delhi, November 6, 2026. A group-stage match of the ICC Men's Cricket World Cup between Bangladesh and Sri Lanka. The fourth wicket fell at the top of the 24th over of Sri Lanka's innings, and the veteran Angelo Mathews walked to the crease. What followed had never happened in the 146-year history of international cricket. The strap on Mathews's helmet snapped, and as he fussed with a replacement, he crossed the two-minute boundary. Shakib Al Hasan appealed, and on-field umpire Marais Erasmus raised his finger. Timed out — the first in international cricket. I will state the verdict up front: the umpires were correct under the written law, but the protocol that should have surrounded this ruling did not exist. That is where the real problem hides.

Understand the law first, because two layers of rules are working together here. MCC Law 40.1 states that after a batter is dismissed or retires, the incoming batter must be in position to take guard, or have a partner ready to receive the next ball, within three minutes of the dismissal or retirement. That clause entered the Laws in 2026. But the ICC Playing Conditions reduce that window to two minutes in ODIs and T20Is. One framework, two applications — in my seven-point review checklist (angle, offence, point of contact, speed, offside line, restart, communication), this layer distinction matters most.

When I built the Premier League VAR Pilot Log at Stockley Park in 2026, I audited 38 matches, logging 12 overturns, 47 checked incidents and 3 missed calls. The first lesson there was simple: a decision can only be legitimate if it sits inside a measurable process. Timed out fails exactly at that point, because what gets measured is the clock, and a clock never explains why the delay happened. In Asian cricket — especially in Bangladesh, Sri Lanka, India and Pakistan matches — this collision of emotion and law is not new. This time, though, the collision happened in the middle of the field, in front of everyone.

Let me break the timeline down the way I broke down every review from the remote desk at the 2026 Russia World Cup — from Russia, with a remote desk and a five-second delay. First, when did the clock start? At the moment the batter was dismissed, not when he retired. Mathews reached the crease within the allotted time. Second, what happened next — the helmet strap snapped and he busied himself with a replacement. Third, whether Shakib appealed before the two minutes expired, which was decisive. Timed out is an appeal-driven dismissal; the umpire cannot give it on his own, the fielding side must ask.

Fourth, what did the umpires actually see before ruling? Here sits the most important fact — timed out is not covered by DRS. Unlike a catch, an LBW or a stumping, there is no route to the third umpire. The monitor does not lie; the angle does — but in this incident there was no monitor at all, only a stopwatch. And a stopwatch never says why two minutes slipped away.

The text of the law is even narrower. It says the batter must be in position to take guard, yet the word ready has no definition. If equipment failure like a snapped strap occurs, does that time count? The Playing Conditions do not answer this. In my 2026 checklist, I flagged exactly this gap under the heading communication — if a decision and its reasoning are not logged together, they can never become training material.

The match context matters enormously. Sri Lanka were bowled out for 279, and Bangladesh chased it down by three wickets with 53 balls to spare — Najmul Hossain Shanto made 90 and Shakib Al Hasan 82. One timed out sent Mathews back for a duck and cracked Sri Lanka's middle order. That moment, which turned the match, became the headline — because the term timed out is rare, and rarity drives traffic.

This is where emotion meets law. Many players, especially in the Sri Lankan camp, called it contrary to the spirit of cricket. But my years of watching tell me the problem is not Mathews's resolve or Shakib's decision; it is the incompleteness of the protocol. In the VAR world we practise a threshold called clear and obvious error; in timed out, no such threshold is written anywhere. A clock is as sincere as it is merciless — and in this equipment-driven collision, the law cannot recognise the equipment's own gap.

Core observation: the real weakness of timed out is not the umpires' call, but the absence of any exception clause for equipment failure.

There is another layer I understood more clearly while working in empty stadiums in 2026 — empty stadiums made the audio protocol louder than any crowd. Delhi had a crowd, but as a player struggled with his gear at the centre of the field, the two-minute clock felt nothing. The communication principle we introduced in VAR — explaining the reason before announcing the outcome — is simply missing from timed out.

Looking forward, my prediction: the ICC will soon add an exception clause to the Playing Conditions, recognising extra time for equipment failure. Before that clause arrives, though, a seven-point timed out checklist is needed: time of the wicket, entry to the crease, condition of equipment, the starting point of the clock, the moment of appeal, umpire communication, and the written reason for the decision. The question now belongs to the ordinary viewer: does the game want to protect the letter of the law, or the spirit of it — and when the two collide, who stops the clock?