Auditing Cricket's Review Protocol: Delhi's Timed Out, Lord's Six Runs and the End of the Soft Signal

A helmet strap snapped at the Arun Jaitley Stadium in Delhi. On 6 November 2026, in a World Cup group match between Bangladesh and Sri Lanka, Angelo Mathews walked out to bat, found the strap broken, sent for a replacement, and crossed the time limit written into the tournament's playing conditions. Bangladesh appealed. The umpire raised his finger. Mathews became the first batter in the long history of international cricket to be dismissed timed out — off zero balls, for zero runs.

A new block went into my incident ledger that day: match ID, over, applicable clause 40.1.1, trigger (opposition appeal), outcome (out), confidence level (high). The last column stayed empty — human factors. That empty cell is the subject of this piece. In Kuala Lumpur, I began logging VAR incidents; the pattern was already there, and it says this: the more precise a protocol becomes, the more human pressure accumulates at its edges.

Cricket's review architecture is older than football's and built in layers. The third umpire arrived in the early 1990s for run-outs; in July 2026, at a Test in Colombo between India and Sri Lanka, ball-tracking was first combined with a player-initiated review, later branded DRS. In between came Umpire's Call, the soft signal, and the arithmetic of losing a review.

The layers have to be separated, or analysis piles up without producing a verdict. Trigger: who asked for the review — a player, an umpire, or the protocol itself. Threshold: what standard of proof overturns a call, and in what unit is it measured. Cost: what an unsuccessful review costs — the review itself, time, or the rhythm of the match. Record: where the decision is written down, and who can alter it afterwards.

At the 2026 Confederations Cup I logged 12 reviews across 12 matches; four goals were overturned, and the Chile–Cameroon and Portugal–Mexico incidents took three weeks of frame-by-frame work. The conclusion was blunt: five decisions rested on the subjective reading of the word handball. The following year I widened the same spreadsheet across all 64 matches of the Russia World Cup, cataloguing 29 penalties and every VAR review; the 12,000-word VAR Protocol Audit broke 20 overturns into law categories and added average review times. Each incident ran through a decision tree: trigger, review type, final call, law citation.

One limit belongs up front. Cricket's ball-tracking is a modelled projection with its own error band; football's offside line is closer to geometry, though frame-rate error lives there too. Handball and the soft signal are comparable as principles, not as verdicts. So I compare rules, not scorelines. And since 2026, no rule claim leaves my desk without three independent sources behind it.

Block one — Lord's, 14 July 2026.

The World Cup final, England against New Zealand. A throw from Martin Guptill headed for the boundary in the final over; it struck the running Ben Stokes' bat, changed direction and crossed the rope. The umpires awarded six runs. Those six runs took the match to a tie, then to a Super Over, then to a boundary-countback regulation that decided the trophy.

My audit splits the question into two gates. First: had the batters crossed for the second run when the throw was released? Under MCC Law 19.8, when a boundary results from an overthrow, completed runs are added to the boundary allowance — two plus four makes six if they had crossed, one plus four makes five if not, and the strike also changes. Second: did the ball come off the bat? That does not alter the overthrow arithmetic, but it alters the language of the argument. The MCC later confirmed the umpires had applied the law correctly.

The important finding is not about umpiring but about rule design: what broke at Lord's was not the on-field decision but the tiebreaker written into the playing conditions. Boundary countback was an administrative clause, and its authors had not audited the distribution of outcomes it could produce. In October 2026 the ICC Board scrapped it in favour of repeated Super Overs. The class my 2026 Russia audit created — frame the rule before you frame the replay — has no cleaner example.

Block two — Delhi, 6 November 2026.

Under MCC Law 40.1.1, an incoming batter must be ready within the stipulated time after a wicket falls, or be out. Mathews faced two decision gates. First: had he exceeded the limit — a question of measurement rather than interpretation. Second: was the delay beyond his control — a snapped helmet strap is not literally his fault, but the law was written to stop time-wasting by the batting side, not to cover equipment failure.

The structural limit of written law shows up here. Cricket's timed out is a strict-liability provision: the question is not whether sympathy is deserved but whether the condition was met. Football's VAR is the opposite architecture, hunting proportionality through a threshold called clear and obvious error, whose unit of measurement has never been published. Cricket issues verdicts; football negotiates them.

Bangladesh's appeal was lawful. Sri Lanka's grievance was legitimate. Both sentences can be true at once, and that is exactly where written law runs out of language. I left the human-factors cell empty in that day's entry — in an audit, a blank is not a mistake, it is a finding. An on-field umpire counts seconds inside 30,000 voices, a third umpire has no camera aimed at a helmet strap, and no decision sheet prints a confidence level.

Block three — the end of the soft signal, 2026.

Midway through the year the ICC removed the soft signal from its protocols. Previously the on-field umpire gambled on a provisional call, and if the third umpire could not find conclusive evidence, that provisional call survived. Absence of proof became a decision. With the practice abolished, the geometry of the incident feeds the verdict directly.

When a review protocol admits its own defect and deletes it rather than expanding its powers, it does not weaken — it strengthens. That lesson is legible for football. Football's VAR is centralised and free to trigger, so a vast number of marginal incidents enter the system and each gets a subjective hearing. Cricket's DRS is player-initiated and finite: lose two reviews and you are unarmed. That economy of cost keeps cricket's review culture far more disciplined.

Cricket did keep Umpire's Call, an authority doctrine sitting inside a review system. The honest defence is that ball-tracking is a projection with an error band, and inside that band technology has no right to overturn a human. The argument is sound, but cricket has never published the size of the band. Cricket publishes laws, not error bars.

What happens when technological uncertainty stays hidden, I examined from another angle in 2026. In the Silent Pitch study I analysed 81 behind-closed-doors Bundesliga matches after the May restart against a control group of 225 pre-shutdown matches. Home penalties per match fell from 0.29 to 0.18, home win rate from 43.3 per cent to 33.3 per cent, and I tracked 1,200 foul calls to test for referee bias. The conclusion was simple: crowd noise is a variable outside the protocol, but its pressure enters the decision. Cricket has its own such variable, and it is time — a three-minute review erases a spell of pressure.

Now the part of the protocol no heatmap shows. A player-initiated review is a depleting asset; two failures mean an unarmed final over. Skilled captains bank reviews by arithmetic, not hope. The deeper effect is on style of play. Because Umpire's Call survives, marginal lbw calls are hard to overturn against the bowler, so the rational bowling plan becomes a straight line at the stumps, where the call usually holds. Batting responds in kind: deeper in the crease, sweeps, a shifted impact line, altered footwork.

A position deserves stating plainly. A review protocol does not merely adjudicate; it redistributes advantage. It is pushing bowlers toward one sanctioned line and slowly homogenising the game — much as the modern inverted winger has erased the touchline winger, a threshold-friendly delivery is swallowing varied bowling. No spreadsheet catches this, because a heatmap records where the ball went, never why it was bowled.

So I keep the ledger. Every entry carries time, match ID, law citation, trigger, camera frames, outcome, confidence level and revision history. The lesson of a blockchain is not technological but procedural: nobody can quietly rewrite yesterday's verdict. A decision that can be edited afterwards is not a decision — it is a draft. My own scoring is part of that discipline; imposing a 24-hour delay before publication cut my correction rate by roughly 70 per cent.

The stands ask: was the umpire right? The audit asks: was the decision auditable? Two different questions, and most argument never leaves the first. The darkest room is not the decision but the clock. Review protocols are sold as accuracy machines; they operate as rhythm machines. Much of the fury fans store up is not aimed at technology but at waiting. Nobody has ever costed how much pressure a single review absorbs from a contest.

One more uncomfortable point. The anger after Delhi was not really a complaint against the law; it was a complaint that no one assigned intent. Law does not search for intent, it does arithmetic. The fix is not more technology but published thresholds: the size of the error band, the confidence level, the weight given to human factors. Cricket holds an asset football lacks — a published law book. Football's VAR still runs on a threshold whose unit has never been written down. The sport that invented the offside line has yet to write the measurement of a decision.

In the coming season, every tournament should publish an open review ledger: each decision a block, carrying law, trigger, camera frames, error band and confidence level. Then a wrong call stops being a scandal and becomes a row in a table. Which changes the question entirely — if nobody can edit the verdict afterwards, what exactly are we arguing about? The umpire's call, or our habit of reading it?