The Third Umpire Without a Soft Signal: Cricket Accepts 3.57 Centimetres of Doubt on LBW, Then Demands Certainty on a Catch

11 June 2026. The Oval, World Test Championship final, fourth day. In a flat in Manchester it was 2:47 in the morning, and I had the notebook open before I opened the laptop. The habit has not changed since the 2026 World Cup: every referral gets three columns — minute, camera angle, law citation. What happened at The Oval that evening was not a story about a low catch. It was the first serious examination of a protocol that had just been abolished.

Shubman Gill was batting. At gully, Cameron Green dived to his right and came up with the ball. Whether it had touched the ground beneath his fingers was never as certain on screen as it felt inside the stadium. The third umpire stayed with out. Social media erupted.

The anger pointed the wrong way. People were asking, "Did the ball touch the ground?" The question should have been, "Who supplies the evidence of ground contact, and who sets the standard for that evidence?"

Because in May 2026 the ICC's Chief Executives' Committee decided to remove the soft signal, effective 1 June. The catch at The Oval was therefore the new system's first big test. The system did not pass — and the failure was institutional, not personal.

What the protocol actually was, and what exactly changed

The soft signal was never a Law. It was an administrative device inside the ICC Playing Conditions. When a low catch, a boundary catch or a stumping was doubtful, the on-field umpire first gave a preliminary verdict — out or not out — and then referred it. The third umpire could overturn that only on "conclusive evidence."

That was the flaw. The umpire with the worst view — seventy metres away, two eyes, one angle — ended up holding the highest authority. Technology did not dismantle that; it protected it. For nearly two decades cricket lived with the discomfort, because if a camera cannot resolve depth, the human read on the field is the last currency available.

In 2026 cricket threw that currency away. And that is where the story leaves cricket. In the player-movement market we call this "regulatory alignment," and in cricket officiating it barely exists. While this piece was being written, the IPL, SA20, ILT20, BSL and The Hundred were all processing movement — NOCs, drafts, trade windows. A player flies out next month and finds the same Law but a different review protocol. The technology is often the same brand. Who decides, how fast, and against which evidentiary standard changes from series to series. That inconsistency never appears on anyone's price list.

The first page of the notebook: the evidence of frames

I opened the notebook before I opened the replay because I knew I had to do the frame arithmetic myself. This is where the least-discussed number hides.

Broadcast frame rates run at 25 to 50 frames per second depending on territory, and 30 or 60 in the North American pattern. Take 50 frames per second. The gap between two frames is 20 milliseconds.

Now the ball. A ball leaving the bat at 140 km/h is travelling at roughly 38.9 metres per second. In one millisecond it covers about 3.89 centimetres. In twenty milliseconds — one frame — it covers about 78 centimetres.

Seventy-eight centimetres. In the gap between two frames. So how exactly is the instant of ground contact supposed to be captured? It is not. What we see are two different frames: in one the ball is under the fingers, in the next it has been released. The audience fills in the space between. Not the camera.

Hawk-Eye's tracking cameras reportedly capture several hundred frames per second, up to about 340 fps, far finer than broadcast. Even at that rate the interval is roughly three milliseconds — at 150 km/h, eleven or twelve centimetres of ball travel. The gap shrinks. It does not vanish.

Then add parallax. The third umpire is looking at two-dimensional images. A shadow beneath the ball can, across several frames, look exactly like ground contact. The relationship between camera angle and ball trajectory decides whether the gap is even visible. And when a finger, a palm or the brim of a cap covers the ball, it disappears from the screen entirely. A verdict is still required.

So I wrote in the notebook: every frame is a witness, but not every witness tells the whole story. In a catch referral a frame is not a conclusion. It is a probability. And when a Law demands a final verdict from a probability, the fault lies with the Law, not the frame.

Ball-tracking: where cricket admits its own doubt

Now the real comparison — and it is not a theory, it is arithmetic.

In the ICC Playing Conditions for LBW reviews there is a mechanism called Umpire's Call. The logic is simple: if the on-field umpire said not out, and ball-tracking predicts the ball would hit the stumps, the decision still stands unless the ball is hitting with enough margin. The standard is half a ball's width.

A cricket ball's lawful circumference is 22.4 centimetres, giving a diameter of roughly 7.13 centimetres. Half of that is about 3.57 centimetres. The stumps are 22.86 centimetres wide and 71.12 centimetres tall — and inside that box cricket has calmly written roughly three and a half centimetres of uncertainty into the letter of the Law, and called it Umpire's Call.

I do not call that a scandal. I call it honesty. The ball is pitching, seaming, spinning, bouncing unpredictably; the path after bounce is a projection, not a measurement. The system acknowledges its own limit and returns the decision to the human on the field.

Here is my test. In the same match, the same innings, cricket runs two entirely different philosophies of proof. On one side, LBW: the technology's own uncertainty, 3.57 centimetres, is written into the protocol. On the other, a low catch: across a 20-millisecond gap between two frames — which for a ball at 140 km/h is about 78 centimetres of darkness — a single umpire's eye is asked for perfect certainty.

3.57 centimetres and 78 centimetres. Both numbers sit in the same book of Laws, inside the same game, on the same evening. On LBW cricket is humble. On catches cricket is arrogant. There is no technical reason for that. There is an institutional comfort. LBW failure can be measured against tracking frames; catch failure cannot be measured, because the unit of measurement was never built. Admitting the limit of something unmeasurable is administratively awkward. So it is not admitted.

One further point matters. The uncertainty in projection is not uniform either. If the ball has hit the pad, the impact point is itself a projection. How much of the stump it would strike is a projection stacked on a projection. So 3.57 centimetres is not one layer of doubt; it is several added together. Cricket still concedes it. On catches we do not see a tenth of that concession.

The evidence of sound, and what the empty stadium taught

Here my second notebook opens. In 2026, when the world stopped, I took on a side project alongside my degree: listening to closed-door matches. The Bundesliga returned on 16 May, the Premier League on 17 June. I later extended the log through Euro 2026 and the Tokyo Olympics, adding 51 reduced-crowd matches. Cricket had its own version: in July 2026, international cricket returned in a bio-secure environment at Southampton, and the stump microphones caught sounds the crowd normally swallows.

That is the sentence I wrote down: the empty stadium taught me to hear what the crowd hides.

UltraEdge, or Snicko, is a waveform. When ball meets bat, a spike appears. But a spike is not an edge. Ball on pad produces a spike. Ball on the splice, on the helmet, a boot scuffing the pitch, even a gust across the stump mic — all produce small transients. The spike must be aligned to a frame. If the audio track drifts a fraction against the video track, the spike lands on the wrong frame, and the final verdict changes with it.

The empty stadium exposed both sides of this. With crowd noise gone, a genuine edge was far clearer; the third umpire could hear more. By the same token, a boot brushing the pitch sounded like an edge. Silence does not add proof. Silence only makes small sounds loud.

This is where I police myself. Acoustic overreach is an easy trap. When a fan shouts "there was a noise," I write in the notebook: a noise is not a contact. So I always pair audio with image — which frame the spike sits in, how wide the gap between bat and ball was, how many degrees the bat had turned. Sound alone cannot deliver a verdict. Sound only sends a question to the image.

The layer of Law: where numbers are honest because the object is slow

I have an old fascination with front-foot no-balls, because it is the rare case where cricket is genuinely millimetre-precise.

The popping crease line sits 1.22 metres in front of the bowling crease. At delivery, some part of the bowler's front foot must be behind that line. The third umpire checks it in real time and reports within seconds. A single centimetre generates argument.

But notice: a foot does not arrive at 140 km/h. The bowler plants the foot, then releases; the front edge approaches that line and stays there for a few milliseconds, effectively static. Where the object being measured is slow, the Law can genuinely be fine-grained — and that is real measurement, not sleight of hand.

Where the object is travelling at 140 km/h, claiming the same precision from 50-frame broadcast footage is evidentiary self-deception. That is the fundamental difference between the no-ball check and the low catch. We call both "millimetres," but one millimetre is real and the other is rhetorical.

There is another piece of case law in my notebook, and it is relevant. On 25 March 2026, in the IPL, Ravichandran Ashwin ran out Jos Buttler at the non-striker's end. Under the Laws of the day the act sat inside the Unfair Play chapter. The argument would not die. The result was structural: from 1 October 2026 the ICC moved the dismissal out of Unfair Play and into the run-out Laws.

That is the lesson. Cricket does not change a Law when its technology is weak. It changes the Law when the culture can no longer defend it. The 2026 World Cup boundary-countback clause died the same way. The abolition of the soft signal was not the fruit of a technical upgrade; it was a reputational concession. Nobody can claim that in May 2026 the cameras suddenly learned to resolve 78 centimetres. The capability did not improve. The discomfort did.

The contrarian read: not transparency, but a transfer of liability

The removal of the soft signal was sold as a victory for transparency. I do not believe that, and my dated notebook entries support me.

Previously the verdict came from a named on-field umpire — a face, an attributable call, a record that could be reviewed and a man who could be dropped next match. Now the verdict comes from a third umpire who takes no initial position, sitting inside a set of frames supplied by a private technology vendor. Which angle loads first, which frame is discarded, where the spike is aligned — none of it appears in the book of Laws.

So liability did not disappear. It became invisible. The phrase "conclusive evidence" exists neither in the Laws nor in any published interpretation. An umpire can therefore call almost any decision conclusive, and almost any decision inconclusive. There is a word called protocol. There is no document called protocol.

And when the audience howled, I would argue their instinct was not wrong. What they were watching genuinely was undecidable. The error was believing the technology was at fault. The fault lay with a legal architecture that demands a final verdict from evidence incapable of supplying one.

Takeaway: publish the frame log

Cricket already measures player depth, builds rankings and publishes indices across the world. If the same industry can measure a player through frame-by-frame data, it can publish the data behind a verdict.

I want a public review ledger. Every referral should carry the list of angles used, the frame rate, the timecode, the audio file relied on, the reasoning for the kick-point selection, and the operator's note. If every decision has that document behind it, tomorrow's argument will stop asking whether the ball touched the ground and start asking: show me your frame log.

Otherwise, the biggest decisions of the next decade will not be settled by a protocol at all. They will be settled by which frame loaded first — and by which broadcaster's contract decided it.