From Two Minutes at Timed Out to Half a Ball at DRS: Auditing Cricket's Rule Gaps

On 6 November 2026, at the Arun Jaitley Stadium in Delhi, Sri Lanka's Sadeera Samarawickrama fell in a World Cup group game against Bangladesh. Angelo Mathews walked in, worked at a snapped helmet strap, pulled at a glove, and never faced a ball. The third umpire's screen carried a clock that had already expired. International cricket had its first timed out dismissal in almost a century and a half.

The immediate theatre matters. The Delhi crowd roared, the Sri Lankan dugout protested, the commentary box fumbled for language. Mathews spoke to the umpires before he left. The decision could not change the result of the match, but it changed what the match meant, because the incident became history on the spot.

I did not sit with the scorecard that evening; I sat with the umpire's decision tree. The questions were not simple: whose clock held the two minutes? When did it start — at the fall of the wicket, or when the incoming batter crossed the rope? And where exactly does 'ready' begin? Timed out is almost the only law in cricket whose outcome rests not on the on-field umpire's perception but on a third party's clock and log. That is why this episode is not a morality debate about the spirit of the game; it is a data-governance question.

The law is not new. Timed out sits in the MCC code at Law 40.1.1, which requires the incoming batter to be ready to face the next ball within two minutes of a dismissal or retirement. From 1 October 2026, the MCC's revised code cut the window from three minutes to two.

Law-making in cricket runs on two floors. The MCC writes the Laws, which apply directly to Tests and first-class cricket. The ICC writes Playing Conditions, the white-ball and tournament-specific layer. The two documents rarely move together, and controversy nests in the gap. The same 2026 revision moved the non-striker run-out out of 'unfair play' (Law 41.16) and into Law 38.3 — the act became legitimate, not unsporting. In 2026 the ICC made the stop clock permanent: sixty seconds between overs, with a five-run penalty for repeat breaches.

The video room was moving too. DRS debuted in July 2026 in the India-Sri Lanka Test at the SSC in Colombo. Today it is a three-layer evidence chain: ball-tracking, UltraEdge, real-time snicko. Each team gets two reviews per innings in Tests and ODIs and one in T20Is; in Tests the reviews are topped up after 80 overs.

My own notebooks hold two decades of this pattern. In 2026, watching Milorad Mažić's four-minute VAR review in Chile versus Cameroon, I forgot the scoreboard entirely and spent 72 hours writing a 4,200-word timeline built clause by clause on the 2026 IFAB VAR protocol. That piece is where 'The Referee' began. In 2026 I watched Néstor Pitana award the Perišić handball penalty in the World Cup final and spent eleven days logging 29 VAR reviews and 20 changed decisions across all 64 matches. In 2026, through empty stadiums and five substitutions, I built a spreadsheet of 500 referee decisions. In 2026, when semi-automated offside cut checks to about 25 seconds in Qatar, the lesson landed: controversy did not shrink, it relocated — from the pitch to the video room, from the decision to the wording. Cricket has done exactly the same thing, only it calls it DRS.

So let us replay Delhi frame by frame. First, the clock: the law says time runs from the fall of the wicket or the retirement. Second, the keeper of the clock: after the on-field umpires signal, the TV umpire, with an official timer and the scorers' log. Third, what 'ready' means — and this is the real gap. A snapped helmet strap, a glove malfunction, grit in the eye: are these legitimate reasons for not being ready? The MCC clause carries no such exemption, and no injury-stoppage or medical-timeout equivalent exists. Fourth, the decision: the on-field umpire rules, the match referee turns the pages of the code of conduct, and nobody asks where the clock was logged or who operated it.

One trap must be avoided here — cricket's DRS and football's VAR cannot be filed together. VAR is referee-initiated; DRS is player-initiated. Football's standard is 'clear and obvious error'; cricket's is 'the on-field decision stands unless the evidence is conclusive'. Football gives the referee no explicit benefit-of-the-doubt zone inside the protocol, while cricket does: umpire's call, where the on-field verdict survives if less than half the ball is striking the stumps.

Many fans do not know that a review is retained when the outcome is umpire's call. Timed out runs the opposite logic: no on-field perception is involved at all, so there is no margin for doubt. Where a human judges, there is room for doubt; where a clock judges, there is none — and yet nobody asks who ran the clock or where its log lives.

One thing kept surfacing in that 500-decision spreadsheet from 2026: identical incidents produced different outcomes in different competitions because the protocol language was not the same. Timed out carries a sharper version of that risk. The MCC code's 'two minutes' and the ICC Playing Conditions' 'two minutes' are the same words, but the method of running the clock is not uniform. Where a tournament has a TV umpire, timestamps are recorded; where a domestic competition does not, the field umpire's wristwatch and memory are the final evidence.

The Bangladeshi context sharpens this. From the BPL to the National Cricket League, the same two minutes and the same half-a-ball arithmetic apply, but who stores the timing data, and where, changes from competition to competition. Two applications of one law mean the law is not really one law — the written version and the applied version diverge.

Look for precedent and you land on 25 March 2026. The storm over R Ashwin running out Jos Buttler at the non-striker's end in the IPL revolved around the same question: spirit, or statute? Three years later the MCC wrote the answer into the code: statute. Mathews' dismissal is the next step on that road.

To my eye, the most neglected part of timed out is metrology — the measurement itself. Football has argued for years about stoppage time, but at least the added minutes are announced. In cricket, where is the two-minute window announced? On the umpire's screen, out of the crowd's sight. A sanction the spectator cannot see is a sanction whose legitimacy the spectator cannot accept — that is the built-in weakness of any clock-driven law.

One more observation, logged across years of watching: in white-ball cricket, the decision to review is often taken at the speed of emotion and team pressure, on the captain's belief rather than the ball-tracking trend. Protocol holds only when the review decision is made against a standard fixed in advance.

The instinctive reaction is: why was the appeal not withdrawn? Read the law and the obligation disappears — withdrawal of an appeal is a courtesy provision, not a duty (Law 31.4). The question nobody asked matters more: which device ran the clock, who operated it, and was that timestamp attached to the match referee's report? The variable here was not morality; it was metrology — the reliability of measurement.

A second blind spot: we reach for the vague clause of the spirit of the game. Yet the MCC Preamble frames that idea in the language of honest play and respect for the opponent, not as a licence to rewrite a result. By skipping the clock's precision and going straight to character, we drag the referee's eye down to the spectator's eye and turn a decision into a vote of the moral thumb.

A third problem is structural. Clock-driven laws apply evenly only when every competition keeps timing logs of the same standard. ICC tournaments carry smart timers and logs; domestic leagues often do not. The question is therefore direct: in a domestic match with no TV umpire, against whose standard is the two minutes measured? No answer is ready, because I cannot recall anyone asking.

Three things to watch in the 2026-27 cycle. First, whether the ICC fixes a single timed-out clock protocol for domestic competitions, with timestamps mandatory in the match report. Second, whether the half-a-ball band for umpire's call is re-parameterised at all, since tracking technology has grown more precise while the band has stayed old. Third, whether boards publish review-success data; if anonymous throw-away reviews stay secret, pressure for protocol reform never builds. Cricket's next controversy will live or die not on heroics in the middle but in the version numbers of clocks and rulebooks. The question stays open: those who write the rules — will they write the measuring instrument too?