The Millimetre Verdict: Auditing Cricket's Review Protocol from Soft Signal to Stop Clock

Hook

On 14 July 2026, at Lord's, Martin Guptill's throw deflected off Ben Stokes' bat and ran away to the boundary. The on-field umpire signalled, the TV umpire confirmed, and six runs went onto the scoreboard — two completed by running, four as an overthrow allowance. The gap between the written text of Law 19.8 and what actually happens on grass opened up that evening, and not only decided a World Cup final; over the next three years the law itself would be rewritten twice. I opened a new spreadsheet tab that night and named it “Boundary Overthrow Protocol.” Much of my later cricket review audit grew out of that tab.

Supporters tend to shrug and call it fate. In my logbook it is not. It is a decision gate — a point where written law, the tolerance limits of technology and human perception fuse into a single verdict. This is a story about millimetres and percentages.

Context: the frame inside which verdicts are born

The review system began in 2026 as a trial during the Sri Lanka–India series. It became permanent in Test cricket from October 2026 and entered ODIs at the 2026 World Cup. Teams started with one review per innings and now hold two; in T20Is, two reviews have been available since October 2026. The change matters tactically: a review is no longer a last resort but an instrument of over-management.

The technology stack is where the verdict is actually manufactured. Hawk-Eye projects the ball through pitching, impact and wicket. Ultra-Edge and Real-Time Snicko capture the sound of bat meeting ball. Hot-Spot reads heat. Slow-motion cameras test whether a catch was clean or whether the ball touched grass. The third umpire is, in effect, reconciling three different evidence streams against one standard.

The phrase “umpire's call” is widely misread. In simple terms: if the projection shows less than half the ball hitting the stumps, or if more than half the ball is outside off stump at impact, the technology upholds the on-field decision. Alongside sits the three-metre rule — if the batter is more than three metres from the stumps, the projection is not used to judge the point of impact.

From mid-2026 the ICC withdrew the “soft signal.” On-field umpires no longer offer a provisional verdict on catches; the third umpire reaches a conclusion directly from the evidence. Then, from December 2026, the “stop clock” was trialled in ODIs and T20Is — the fielding side must be ready to bowl within 60 seconds of the previous over ending. Earlier, in 2026, the non-striker run-out was moved out of Law 41.16 (Unfair Play) and placed under Law 38 (Run out). The 2026 ODI World Cup introduced an in-match slow over-rate penalty, placing an extra fielder inside the 30-yard circle when a side falls behind.

None of this framework is new to me. In Kuala Lumpur, I began logging VAR incidents in 2026; the pattern was already there. What football calls a review protocol, cricket calls playing conditions and third-umpire procedure. Both ask the same question: how much of a decision is technology, how much is human, and who carries the blame when it goes wrong.

Core Analysis

The decision gate: four questions, one verdict

I split every review into four gates. Gate one — trigger: is the incident reviewable at all (wides and no-balls remain outside the scope, the field umpire's power reserved). Gate two — evidence gathering: which camera, which frame, which audio channel. Gate three — standard application: which clause, which tolerance. Gate four — final verdict and its reasoning.

I used exactly this four-gate model in my 2026 VAR audit, where every review across the 64 matches in Russia was slotted into four columns: trigger, review type, verdict, law citation. In cricket the model works more cleanly because the technology outputs a number. In football “not sufficiently clear” is a sentence; in cricket it is “51 percent of the ball outside the line.”

The politics of tolerance: one incident, two verdicts

Here is the paradox. Ball tracking predicts the ball will hit the stumps, but less than half of it. If the on-field umpire said not out, the review result is not out. The identical projection, had the umpire said out, results in out. One physical event, two completely different outcomes — divided only by the first call.

The logic is that where evidence is not beyond doubt, the field decision stands. The mathematical consequence is that technology makes no decisions at all; it only sets the boundary of doubt. For bowlers this is a source of real grievance, because to a leg-spinner “49 percent versus 51 percent of the ball” produces no different reality on the field. The wicket does not fall.

In my Kuala Lumpur log I have noted that broadcast presentation amplifies the anger. When viewers see a graphic where the ball clearly strikes the stump and the result is still not out, they blame the technology. The fault is not in the technology but in the communication. If “umpire's call” were shown on screen as a distinct category with a distinct colour and a distinct label — “evidence insufficient, on-field call stands” — anti-umpire sentiment would fall.

Abolishing the soft signal: the problem moved, it did not disappear

The 2026 change deserves credit, because the soft signal was essentially a device for avoiding accountability. An early on-field call always left the third umpire with a “favoured” decision to lean on. But the change did not solve the whole problem.

The third umpire now faces two sequential questions — first, did the ball touch the ground or the bat; second, was it a clean catch. Both are visual judgements. Camera angles can deceive; the frame between ball and grass can be lost entirely. With the soft signal, that uncertainty was absorbed into the on-field call. Now it lands squarely on the third umpire. Uncertainty has not decreased; responsibility has merely been transferred. In accountability terms this is progress. In psychological terms it is not.

Audio-visual collision: the limits of Ultra-Edge

The limits of technology are most visible with bat-pad catches. A ball can brush the bat without any sound at all — a faint touch off the grip, contact with the pad strap. Conversely, bat hitting the ground produces a click that Ultra-Edge often renders indistinguishable from bat on ball.

I have tracked these incidents since 2026 and use a simple test I call the frame-by-frame threshold check. A referee's eye is a frame-by-frame threshold test, not a whistle. Three questions: does the ball's trajectory deviate? Does the bat's trajectory deviate? Do the sound and the moment of deviation align on the timeline? Only when all three answer yes is bat-on-ball contact reliable enough to decide on.

The problem is that protocol often treats “sound” as primary evidence while the picture is secondary — whereas in my 2026 VAR audit I found the opposite principle: visual evidence deserves priority, because sound transmission depends heavily on stadium acoustics and microphone placement. Crowd decibels, spike-mic distance, the producer's audio filters — all of these can change what the technology reports.

The third umpire's psychology and the pressure of time

Laws are implemented by people. In 2026, analysing 81 matches behind closed doors, I saw that when external pressure changes, so does the pattern of decisions. In cricket that pressure takes a different form — not crowd noise, but time.

A catch review must be decided within two to three minutes, usually under pressure from the producer, the broadcast schedule and forty thousand waiting spectators. When I log review durations, a pattern keeps returning: doubtful catches take longer, obvious dismissals faster. Where evidence is weak, the verdict is slow — and slowness tends to favour the on-field call.

That slowness has a cost. The flow of play breaks, the bowler's rhythm is lost. If the on-field umpire is not helpful, the third umpire fights alone. So I would argue for a graded evidence standard: Tier one, clear visual, verdict within 30 seconds. Tier two, audio-based signal, additional angles required. Tier three, insufficient evidence, on-field call stands, with the reason displayed on the scoreboard.

The stop clock and over rate: governance's new instrument

The stop clock introduced in December 2026 is a major moment in cricket governance, because for the first time the burden of over-rate control was placed entirely on the fielding side. Previously a slow over rate was punished after the match — fines or suspensions. Now the sanction arrives inside the match: an extra fielder inside the circle.

For me the tactical consequence is no smaller than the technical one. When the batting side knows that, in a given over, the fielding captain is forced to keep an extra fielder inside the circle, hitting to the short boundary becomes harder, rotating strike becomes easier, and captains pre-plan how to split their bowling resources so they can accelerate later. A change in the penal code directly rewrites tactical logic.

But there is a standards problem here. The stop clock counts to 60 seconds — but from when? From the over-end signal, from the moment the ball becomes dead, or after a DRS review concludes? These edge cases need to be spelled out in every condition, or two sides in the same match will be held to different standards.

The Kuala Lumpur log: the same pattern at regional level

I have documented this process in the Malaysian context for roughly a decade. In domestic and regional tournaments, the scarcity of technical resource is a major factor — Hawk-Eye is not everywhere, there is no Snicko, available angles are limited. Two things stand out in that environment.

First, in a low-technology setting the meaning of “umpire's call” shifts. Where there is no ball tracking, the decision rests on the field umpire's perception and the third umpire's solitary judgement. One law, different standards.

Second, inconsistent training often produces inconsistency in how the law is applied. If a soft signal is permitted in one match and withdrawn in the next, participating teams cannot predict the standard. Without predictability there is no trust. Without trust there is no framework.

Cricket to football: the limits of comparison

I often read the two review systems side by side, because the questions are articulated more clearly in cricket — time limits, evidential standards, error classification. In football “clear and obvious error” is a subjective standard; in cricket “half the ball” is physical.

But the limits of comparison must be stated. First, cricket is naturally stop-start — one ball, then a gap — while football reviews occur inside a continuous flow. Second, cricket caps reviews in numbers (two); football's ceiling is effectively unlimited. Third, in cricket the field umpire's call is a linked gate within the review, whereas in football the referee's verdict is often wholly replaced.

So comparison travels at the level of principle, not tactics. What I borrow is classification — error type, error cause, path to correction. Cricket's decision-gate model can be applied to football's VAR debate; football's flow-of-play logic cannot be transplanted into cricket.

Contrarian Angle: this is not emotion, it is ecosystem

The biggest realisation of my recent work is this: it is easy to cast the umpire at the centre of a review controversy as a villain; the harder task is to see him as one node in a system.

One common argument runs that umpires are redundant, technology is perfect, and removing the human hand solves everything. Reality is otherwise. Technology makes no ruling — it sets a boundary, and that boundary is drawn by people. Why half a ball? Why three metres? The answer is in the law, not in the science.

The largest unspoken truth is that technology does not reduce umpiring error so much as relocate it. Responsibility used to rest finally on a person. Now it is distributed across producer, camera operator, ball-tracking system and law-maker. In other words, the scope to deny responsibility has expanded. That is technology's most unfavourable outcome: accountability disperses, and the point at which to ask questions becomes impossible to locate.

There is a less comfortable point too: technology creates new inequalities. The team with the larger production budget plays in a match with more angles. The league without Hawk-Eye plays to a lower decision standard. Technology does not deliver equality; it distributes scrutiny according to capability.

When cricket entered its technology era, these questions were not on the table. They are now.

Takeaway: three signals to watch over the next three years

First, whether the stop clock's method of timing is written into the laws in precise language. Without clear wording, the same incident will receive two interpretations in two matches.

Second, whether “umpire's call” is presented to viewers as a distinct category — a verdict that has crossed a threshold of doubt, labelled “evidence insufficient” rather than merged into the general result.

Third, whether DRS standards are defined for regions with thinner resources. When the law is one, the procedure is one, but the technology differs, the standard of accuracy differs too.

A referee's eye is not a passive gaze — it is an active question. And cricket's decision gates keep asking the same thing: what is the evidence, where is its limit, and who draws the line.

Methodology note: every incident and decision in this piece has been checked against the relevant ICC playing conditions and MCC Laws. Where event data differs by regional edition, the boundary has been stated separately. My post-2026 notebooks and third-umpire timing spreadsheets remain the source record behind this analysis.