The Two-Minute Constitution: From 'Umpire's Call' to Mathews' Timed Out — Cricket Now Runs on Default Settings

On 6 November 2026, at Delhi's Arun Jaitley Stadium, the 25th over of the Bangladesh-Sri Lanka World Cup match had just ended. Sri Lanka's score was wobbling, and out walked Angelo Mathews at number six — the man around whom two nations' crowds have built a decade of stories. On his way in, his helmet strap snapped. A new strap arrived, was fitted, and the clock kept running. The umpires checked their watches. Bangladesh captain Shakib Al Hasan appealed. And for the first time in 146 years of international cricket, a batter was dismissed timed out.

That night I logged the line in my notebook the way I used to log things when I started the VAR protocol ledger in 2026: Law 40.1.1, limit two minutes, exemption for equipment failure: none. I opened the 2026 ledger again, and the same blank cell was staring back at me. That is not a hot take. That is a drafting flaw.

What followed was almost inevitable. The debate centred on Shakib's morality, on the spirit of cricket. Nobody opened the conditions document. And at almost exactly the same time, two far bigger and far less discussed changes were reshaping how cricket is governed.

Start with the law. MCC's Law 40.1.1 says that after a wicket falls, the incoming batter must be ready to face within two minutes in men's cricket, and one minute thirty seconds in women's cricket. For years that limit was three minutes. The 2026 code revision cut it to two. The clause is numerically clean and interpretively merciless — there is no exemption written for being absent, for changing equipment, or for being held up on the way to the middle.

ICC event playing conditions normally lift MCC's laws verbatim, adding event-specific tweaks where needed. For timed out, no such tweak exists. On 6 November the umpires had no door of discretion to open. They had a watch and they had a clause.

Now the second page of the ledger. From January 2026, the ICC introduced in-match over-rate penalties in T20Is and ODIs. The mechanism: for every over the fielding side fails to complete in time, one fielder must be brought inside the 30-yard circle, and that penalty carries for the rest of the innings. No hearing, no assessment of intent, no allowance for wickets, injury breaks or DRS consultations. A pure, mechanical debit.

Test cricket works the other way. There, slow over rates are punished after the match — match fees docked, and World Test Championship points deducted. The same offence is judged in two entirely separate jurisdictions: in white-ball cricket inside the ground, in red-ball cricket after the ledger closes.

The third layer is DRS. White-ball teams get two reviews per innings; Test teams get two, refreshed after 80 overs. If ball-tracking shows the ball would have hit the stumps but less than half the ball would have been inside the stump line, the on-field call stands as umpire's call. The crucial detail: the team that reviewed loses that review anyway.

Here is the core of it. Cricket is running two contradictory philosophies at once. On one side sits mechanical severity — the two-minute timed-out limit, the in-match over-rate penalty. On the other sits uncertainty-tolerant deference — umpire's call, where the limits of a prediction technology are given legal protection. The problem is not that both exist. The problem is that which one applies is decided by drafting convenience, not by any stated principle.

The Russia World Cup review log taught me that a tournament is a legal document written in over-by-over chapters. So I went looking for how often cricket's other laws grant relief when equipment or external factors cost time. The answer: rarely. Umpires can change intervals for rain and light. Concussion replacements exist as a medical carve-out. But when a batter's kit fails inside the ground, no clause covers it — and the batter pays for it alone.

On umpire's call, the biggest misconception is that it protects the umpire. It does not protect the on-field umpire; it protects the predictive error margin of ball-tracking. Whether the ball would hit the stumps is a forecast, not a measurement. Only if more than half the ball enters the stump line does the decision change. One number — half a ball — is effectively a legal boundary today.

Across recent seasons I have kept my own tally in the Lord's and Oval press boxes: which reviews failed, and why. The clearest pattern is that catch-behind reviews generate little argument, while the half-ball tracking zone generates the most. The first is an event. The second is a forecast. The law judges events, but the sanction is delivered by a forecast.

Over-rate penalties hit the captain, not the scoreboard. Losing an outfielder means abandoning the plan — the fielder kept back to save boundaries in the death overs has to come in. My observation is that teams react in two ways: they set defensive fields and concede fewer runs, or they shorten spells and change lengths. Neither was the original plan.

On enforcement culture, I have watched both markets. In Dhaka's domestic and club cricket, time-related laws are applied loosely — umpires usually give a few extra seconds for a strap or a pad, because nobody is auditing the pace of play. In English county and club cricket, umpires hold the watch in hand, and protecting the innings rhythm is close to an institution. The same law produces two different games.

Then there is the documentary record. At the 2026 ODI World Cup, Virat Kohli scored 765 runs — the most in a single edition, past Sachin Tendulkar's 673. Mohammed Shami took 24 wickets in just seven matches, the most by an Indian bowler in one tournament. Travis Head made 137 in the final and was named player of the match; roughly 92,453 people watched at the Narendra Modi Stadium in Ahmedabad. Australia won their sixth ODI World Cup. These numbers do not require an argument. They require a ledger.

Taken together: since 2026, cricket's governance has shifted from post-match adjudication to automatic in-match defaults. Decisions are now produced by a watch, a clause number and a prediction model. The umpire's judgement sits third or fourth on that list. That is the real lesson of the Mathews affair, where everyone watched Shakib's finger and nobody read the clause.

Now the conventional reading, then the reversal. The standard argument holds that Shakib's appeal damaged the spirit of the game and Bangladesh's image. But the right to appeal was his, it is written in the laws, and there is no obligation to decline. What is genuinely true lies outside the appeal: the 2026 code shortened a time limit without adding a relief clause. A law that closes a gap in the safety belt while leaving no light where the belt is lost produces accidents that are the failure of the law, not of the driver's character.

The second reversal concerns umpire's call. The usual defence is that it shields umpires from challenges. The ledger cuts the other way: it shields the technology's prediction error, not the umpire's decision. And when half a ball decides the outcome, the umpire no longer carries the whole responsibility either. Responsibility is split among a watch, a clause and a machine — and split responsibility never fully belongs to anyone.

The third reversal concerns the spirit of cricket. The preamble names it, but no umpire can use it to override a specific clause, and neither can a match referee. The sharpest weapon in emotional argument is the bluntest in legal argument. That gap is the game's current weakness: there is no bridge between its public severity and its private flexibility.

So what comes next? Two changes look likely. First, the next MCC code revision should add a limited exemption for equipment failure to the timed-out law — the incident has already entered match referees' training conversations. Second, the white-ball in-match over-rate penalty will probably reach Test cricket, because counting from the boundary is far cheaper than counting a team's finances.

My real question sits elsewhere. Do we want a game fully determined by a clock and a clause? Or a game where the law draws the limit and the person standing in the middle interprets it? The first is good for bookkeeping. The second is what makes it cricket.

— Root: Referee