Two Minutes, One Broken Strap, and Cricket's Decision Frontier

Two Minutes, One Broken Strap, and Cricket's Decision Frontier

Arun Jaitley Stadium, Delhi, the evening of 6 November 2026. Angelo Mathews walked down the dressing-room steps with a helmet in his hands. On the very edge of the field, the strap snapped — and the strap is the only part of a helmet that actually does a job. A replacement helmet arrived from the dugout. Its strap would not fasten properly either. Behind him a clock was counting and nobody was talking. Two minutes expired. Shakib Al Hasan appealed. The third umpire was asked a question. The big screen gave the answer. Mathews was out, zero off zero balls — the first timed-out dismissal in 146 years of international cricket.

I was on my sofa at home that evening with a notebook on my knee. When the match ended, the notebook had one line in it: the strap against the clock — which one is truer? In seven years of writing about officiating I have filed more than two hundred pieces, and this one put me in front of a question no law book answers. The question is not about timed out. The question is how much jurisdiction conscience retains when a clock and a law sit in judgment together.

Law 40.1 is mercilessly simple. After a wicket falls, the incoming batter must be ready to receive the ball within two minutes, failing which he is timed out. Law 40.2 leaves a crack of an exception open, but no clause says how wide that crack is. A broken strap, an unfastened pad buckle, a sore finger inside a glove — none of it is separately provided for. The law speaks of being ready, never of the process of getting ready. Mathews was legally out; I have no doubt about that part. The question is how deep the water is between legal and legitimate.

Look at the history. Test cricket began in March 1877, the first ODI came in 2026, the first T20I in 2026. In all that time nobody had been timed out — the law slept for 146 years. A sleeping law wakes on one particular evening when a player stumbles over a clause supporters have never touched. That is my decision-first view of the game: a match report may start with a wicket, mine starts with the decision, because spectators remember scoreboards while decisions are what actually carry a match.

Consider Lord's, 14 July 2026, the World Cup final. England needed fifteen from the last over — fewer than a strap needs. Off the fourth ball Ben Stokes hit towards deep midwicket, ran two, and Martin Guptill's throw deflected off Stokes's bat and reached the boundary. England were credited six. Law 19.8 said the boundary added to the runs already completed depended on whether the batters had crossed; the replays showed they had, so six was correct. The decision was legally immaculate, and the world still felt uneasy that night. Unease does not stop when a decision is right — that is the central truth of decision science.

In March 2026 I was one of eleven candidates selected for India's first VAR certification programme. Reviewing 72 hours of tape from the Bengaluru FC versus Mohun Bagan ISL semi-final, I logged fourteen marginal offside calls and three penalty-area incidents and produced a 28-page decision audit that FIFA's officiating team later requested for its Asian development archive. That is where I learned that certification is not the same thing as certainty. A certificate says I know the process; certainty says I know the outcome. Cricket's DRS debate confuses the two constantly.

The architecture of cricket technology stands on three levels. The first is UltraEdge, built on sound. The second is ball-tracking, a physical model of the future. The third is the soft signal, the umpire's intuition. From June 2026 the ICC scrapped the soft signal for most caught-behind decisions after trials. That was real reform: previously, if the on-field umpire signalled out and the replay was inconclusive, the field decision survived. Now there is no signal, only evidence. The result is slower decisions — and slow is not the same as accurate, because different umpires interpret the same pictures differently across tournaments.

On sound I carry an old caution. The camera misses what the ear catches, but the ear is not a perfect witness. Stump-mic feeds, broadcast compression, the faint brush of bat on grass, the layer of crowd hum — all of it shifts with time and venue. I write the same line in my own notes: an UltraEdge spike is an indicator, not a witness. If you do not check the sync, a spinner becomes a seamer. A spectator who reaches a verdict from a viral clip without that caution is often simply reacting to edited presentation.

Ball-tracking numbers are odder than the tracking itself. DRS projects how much the ball will deviate after pitching and whether it will hit the stumps — but the tolerance of that model is not announced every series. Manufacturers claim millimetric accuracy, yet an independently verified figure never appears in a match report. When we say umpire's call, we mean that if less than half the ball is hitting the stumps the field decision stands. Where did that line come from? How do we know 50 per cent is the right threshold? Culturally the answer is that it is a negotiated boundary, not a research finding. That should be published rather than denied.

I must also admit the limits of my own jurisdiction. During the 2026 World Cup in Russia I logged all 29 video-assisted reviews across 64 matches remotely, and built a 47-slide framework categorising each review by decision type, response time and outcome accuracy. It was later published as The VAR Ledger. Anything standing outside those slides still sits in an 'uncertain' column in my notebook. Cricket still does not routinely publish review response times. That silence is my loudest complaint.

Here is the collision I call the umpire's sweat. From the 2026 World Cup the ICC introduced an in-game penalty in ODIs: if the fielding side is not in position in time, an extra fielder must come inside the circle for the remainder of the over. Every review costs time, and time carries the risk of team punishment. The umpire weighing an appeal is quietly calculating that reviews belong to the two teams while the clock sits on his shoulders. Rushed decisions breed errors, and errors are then covered by reaching for technology. Technology stops being a measure of truth and becomes a risk-management device. That is my least-discussed finding.

The other face of the argument is the Preamble, which states that cricket is played not only within the Laws but within the Spirit of Cricket. Supporters cited that sentence over Mathews. My notebook says otherwise: a preamble is not a clause, and jurisdiction does not grow out of a preamble. The power in an umpire's hand comes from the final article, not the introduction. Shakib was entitled in law to do what he did; however aggrieved Mathews felt morally, a court does not sit in the preamble. Learning to separate the legal verdict from competitive legitimacy is the real lesson of that evening.

There is one more layer, and it is the least discussed. Each side gets a limited number of reviews — two per innings in ODIs and T20Is, two in Tests with a top-up after 80 overs. That number does not make the process transparent; it makes it strategic. A captain now asks whether to spend a review or bank it for a future need. The system turns truth-seeking into an exercise in priority management. The review count has barely changed for years, and a formal decision audit has never been made public.

I want the ICC to publish a decision audit alongside its report for every tournament. When my 28-page audit listed categorised decisions, response times and overturn rates, English football asked for the document. Cricket shows outrage, not data. We need to know which categories of catch became more error-prone after the soft signal was abolished, or on which surfaces ball-tracking became most ambiguous. Without that information, reform does not happen and mystery survives.

Think again about Mathews's strap. Had the law stated that equipment failure earns an extra sixty seconds administered by the third umpire, Mathews might not have walked back for a duck, and the hinge moment of cricket history might have stayed an ordinary Monday. The law does not need permission from anyone; the law supplies the clock. The clock is still in human hands, but nobody has yet signalled who will read it aloud. Not since Mathews.

Cricket no longer needs to ask how accurate the technology is. It needs to ask who will publish each instrument's tolerance, and by what process that tolerance will be honoured.

The clock and the camera are both human-made. The question is not about the machines. The question is who sets the tolerance and who announces it. Until that answer is found, the next broken strap may not cost a wicket — but the game will be poorer for it.