After the Soft Signal: Why the Third Umpire's Burden Grew in Catch Disputes

The Oval, day five, 11 June 2026. India batting in their second innings. Shubman Gill pushes into the gully region; Cameron Green dives full length to his right; whether he has taken it cleanly is the only question in the ground. The on-field umpire says out. Third umpire Richard Kettleborough studies the screen. My notebook entry that day ran to three lines: incident — low catch, channel — gully, verdict — out. What followed was hours of argument, and the real reason for it was procedural, not technical. That match was the first serious Test after the soft signal was abolished, and it was the first time we saw where the burden lands once the old certainty is taken away. The monitor does not lie; the angle does.

Referee's Eye + VAR Pilot Log | Scenario: post-soft-signal catch review

First, what the soft signal actually was. Introduced into international cricket in the middle of the last decade, it required the on-field umpire to give a provisional call — out or not out — on marginal low catches, with the third umpire needing clear and conclusive evidence to overturn it. In March 2026 the ICC Cricket Committee recommended its removal; the recommendation was ratified in May, and it took effect from the World Test Championship final beginning 7 June 2026 (source: ICC announcement, May 2026). The logic was clean: if the on-field call sets the standard of proof, then the standard of proof becomes a lottery rather than a law.

In Asian conditions the change casts a more complicated shadow. An English Test venue runs more than 30 cameras, with parallax-controlled slow-mo rigs and ultra-motion. Many grounds in the subcontinent and across Asia run six to eight, with low boundary cameras and floodlight flare breaking off gloves and ball edges. Same law, same second-by-second remote review, different angle budget. It shows up most sharply in the Asia Cup or domestic T20 leagues, where the third-umpire roster rotates but the frame count does not increase.

This is where my seven-point checklist from 2026 becomes relevant again. I built that log at Stockley Park: 38 Premier League matches, 47 checked incidents, 12 overturns, and three missed calls that became training clips. The seven points were angle, offence, point of contact, speed, offside line, restart, communication. Because every point had a pre-agreed answer, average review time fell from 84 seconds to 52. I used the same checklist to brief 20 referees at St George's Park. The time came down not because of technology, but because of sequencing.

Referee's Eye + VAR Pilot Log | Core analysis: the three questions of contact

A catch decision is really three physical questions.

One — did the ball touch the ground.

Two — were the fingers under the ball, meaning was control established.

Three — at the moment control was established, what was the fielder's body doing in relation to the boundary rope.

None of the three is visible to the naked eye. At a 50 frames-per-second broadcast feed, one frame is 20 milliseconds, while the whole contact event in a diving catch lasts 40 to 80 milliseconds — two to four frames. Anything more precise comes only from ultra-motion cameras, which not every Asian venue carries. Review speed has improved; review picture quality has not.

There is a second trap here, one I see constantly. Ball-tracking and edge-detection tools produce numbers that get treated as final truth. But ball-tracking does not measure catch contact at all; it measures the ball's path, and that too through a predictive model. The model carries its own error band, and the error band is not shown on screen. So the data and the interpretation must be read separately: what is the frame rate, what is the pixel density, what is the prediction error. Without those three answers, any graphic is just a picture.

Now the actual procedural change. With the soft signal in place, the default outcome on a 50-50 catch was the on-field call. With it gone, the default became conclusive evidence — a standard that cannot be measured, only interpreted. In my log, the pattern is consistent: on the same kind of ambiguous frame-set, cases that previously stayed out are now drifting to not out, because when the evidence is unclear the cost of changing the decision falls on the third umpire, and he does not want to carry it. The old bias favoured on-field certainty; the new bias favours third-umpire denial. The reform changed, the direction of the bias changed, the bias itself did not end.

Review log | Format: minute — incident — verdict — law

1. The Oval, 11 June 2026 — low catch at gully, Shubman Gill — out — Law 33 (caught)

1. Same review — on the frame showing point of contact, ball and glove merge into the same pixel

1. Pattern one — short explanation, long wait; spectators remember the duration longer than the decision

1. Pattern two — where crowd and commentary pressure is highest, the third umpire's announcement becomes shorter still

1. Training note — mandate a single timestamp reference for every marginal catch

Now the proposal. I call it the Frame Threshold Protocol, seven points. One, a published frame-rate list per tournament, so spectators know which camera runs at which frame rate. Two, a parallax statement on every review. Three, a single timestamp for point of contact, cited by umpire and commentator together. Four, ball speed compared against frame capability, with weak evidence declared weak when speed is high. Five, a written definition of control — fingers against palm. Six, who restarts play and within how many seconds. Seven, a verbal verdict within twelve seconds, no more than five sentences.

My old communications work applies directly here. In 2026 I joined the Premier League's behind-closed-doors task force and analysed 92 empty-stadium matches, finding that whistle-to-signal delay rose by 0.8 seconds — with the crowd gone, referees were losing their internal sense of timing. That is when I standardised phrases such as check complete and on-field decision stands; the league credited the protocol with an 18 per cent reduction in communication errors. Empty stadiums made the audio protocol louder than any crowd. Catch reviews have exactly the same problem today: the decision exists, the language of the decision does not.

From Russia, with a remote desk and a five-second delay. At the 2026 World Cup I reviewed all 64 matches from a remote desk and logged 22 reviews, including a decision tree that compressed the France-Croatia final handball review into three minutes. One lesson still holds: on a remote screen you see the frames, but you do not feel the delay — the delay that 40,000 people in the ground are living through. In catch reviews, the gap between the umpire's decision and the spectator's experience is a gap in time, not in evidence.

Referee's Eye + VAR Pilot Log | Contrarian angle: emotion against law

Lord's, 2 July 2026. Jonny Bairstow walks out of his crease, Alex Carey breaks the stumps, and the verdict is out. The law is clear, the emotion is raw, and the Long Room argument at the Marylebone Cricket Club becomes famous. Catch disputes repeat exactly this structure: a gap between what the law says and what the eye wants to believe.

This is my most uncomfortable observation. LBW has a formal uncertainty band called umpire's call — a small ball-projection error is tolerated, because the system admits the eye can err. Catches have no such band, no published pixel or frame tolerance. One law book, two standards. A system that admits uncertainty on one clause and denies it on another is questioned by its own rules.

History says the same. In my notebooks from 2026 to 2026, handball and catch reviews are written in the same mould: minute, angle, verdict, law. At Euro 2026 in 2026 I covered 51 matches and five VAR overturns; the Denmark-England semi-final penalty review ran two minutes ten seconds, and it is the duration, more than the decision, that audiences still remember. What cricket needs now is the language of that duration, not another verdict.

There is also an invisible cost in catch reviews that never appears on a table. A losing side does not merely lose a review; it learns to abandon reviews. Across regular-season matches I am seeing a collective reluctance to challenge marginal low catches, because players know the decision will almost never change. The review survives on paper, not on the field. The cost lands on weaker teams — fewer cameras, smaller support staff, one video analyst. A strong side loses a review and moves on; a weak side loses one and rewrites its innings plan.

Takeaway

A major legal overhaul of catch reviews is unlikely in the next cycle, because the law itself is fine. What is not fine is the declaration of measurement. If conclusive evidence is going to remain the phrase on the field, its definition has to be written down off it — which frame rate, which parallax, which point of contact. Otherwise every marginal catch is judged not on evidence but on the strength of interpretation. So the question is simple: do we want justice from the technology, or do we want to load responsibility onto the technology and hide our own uncertainty behind it?

— Root: 2026 Premier League VAR Pilot Log