No Signal: When Cricket's Review System Says 'I Am Not Certain'

The ball-tracking froze. The ball was grazing the outer edge of leg stump, and the machine itself was in two minds. The graphic flashed the word 'clipping'. Thirty thousand spectators rose, expecting a definitive verdict, yet what Hawk-Eye was actually saying was far more modest and honest: 'I am not certain.' Still, the screen displayed 'Umpire's Call', and the on-field umpire's decision survived.

This is the least-discussed yet most important moment in cricket's review architecture. The crowd reads it as luck or injustice; I read it as a deliberately designed null result. When the system says 'insufficient evidence', that is not a failure — it is the system's most honest admission. The whistle is never the story; the story is the angle that was missed — and that angle is today's subject.

I borrow the idea of the null result from data analysis, where the first lesson is that inventing a signal where none exists is the cardinal sin. My seventeen years of match-watching tell me cricket's officiating system has learned this lesson on paper. Whether it holds in practice is what needs testing.

Context: Why caution is the system's default

The Decision Review System, DRS, was first used officially in cricket on July 23, 2026, in the Test between India and Sri Lanka at the Sinhalese Sports Club in Colombo. It began with several technology channels. UltraEdge, or the snickometer, listens for the sound of bat-edge contact; Hawk-Eye ball-tracking projects the ball's path; Hot Spot infrared cameras detect the heat signature of bat-on-pad contact. The third umpire then combines multiple camera feeds to rule.

From the outset a philosophical choice was made that later sat at the centre of every controversy: if the evidence is not 'conclusive', the on-field umpire's decision stands. The system was designed not to change a decision where any doubt existed. Its most familiar expression is 'Umpire's Call'. In LBW reviews, if Hawk-Eye shows that less than half of the ball is hitting the stumps, it is treated as Umpire's Call and the field decision survives.

Around 2026 the 'soft signal' convention arrived — for low catches, the on-field umpire would give a preliminary 'soft' verdict, and the third umpire needed 'conclusive evidence' to overturn it. After long debate, the ICC abolished the soft signal in 2026, because it was stacking uncertainty upon uncertainty.

This caution is not cricket's own invention. Tennis's Hawk-Eye also concedes an error margin and leaves the call unchanged when the ball is shown to land in the same spot. Football's semi-automated offside works with its own line width. Covering VAR in football, I saw the same uncertainty run deeper — because there, intervention requires a 'clear and obvious error'. The question is not about technology; it is whether we acknowledge these limits or hide them.

My biggest lesson as an analyst came from the nature of this cautious principle. 'Conclusive evidence' sounds easy but means something hard: the system does not seek to be perfect, only to avoid clear error. That standard is criticised widely outside cricket — many argue that if technology exists, the right decision should simply arrive. In reality technology serves 'evidence', not 'correctness' — and those are not the same thing.

Core analysis: The geography of uncertainty across three layers

Now to the actual geometry. An LBW review seeks answers to three distinct questions, each with a different degree of uncertainty. First: did the ball hit the bat? Here UltraEdge hunts for a sound spike — but the problem is that bat hitting ground or pad also produces a spike, creating false-positive risk. Second: where did the ball pitch and where was impact? Here Hawk-Eye is relatively certain. Third, and hardest: after impact, would the ball have hit the stumps? Here the system projects the future — not measurement, but prediction. And prediction carries the greatest uncertainty.

This is what I call the 'fog of officiating'. After pitching, spin, seam, wind and pitch friction all bend the ball's path. Hawk-Eye analyses dozens of frames to estimate that bend, but estimation is never perfect. On spin-friendly pitches the uncertainty grows, because the ball turns more sharply in less time. So the half-ball rule of Umpire's Call is really an acknowledgement: at that level of uncertainty, we will not blame the human.

This is my core observation, which I argue is almost absent from public debate. We assume technology arrived to reduce umpiring errors. In truth DRS arrived first to protect the umpire's decision — until the evidence is overwhelming. This 'protection of the null result' is the system's heart. When a review fails, what usually fails is our expectation, not the technology.

Take a real example. On July 14, 2026, the World Cup final at Lord's. England and New Zealand tied, and the Super Over tied too. By the rules, boundaries were counted — England 26, New Zealand 17. The trophy went to England. The players did nothing 'wrong'; the rulebook decided. This is the most dramatic form of the null result: when neither side loses within the game itself, the system settles it.

Consider another angle — the success rate of reviews. Historically, only about a quarter to a third of reviewed cases are overturned, because the system strictly demands 'conclusive evidence'. Many read this low success rate as technological weakness; I read it as proof of how high the evidentiary bar is.

There is another layer, which may be called the 'economy of reviews'. Each innings has a limited number of reviews, forcing teams to be strategic. A curious consequence follows: teams often review cases they believe are certain and lose, because the field angle and the tracking projection differ. In several matches I have noted batsmen feeling pad contact and feeling confident, while Hawk-Eye showed the ball missing. That gap between sensation and geometry is the system's most honest lesson.

Add one more thing. Inside DRS, the 'impact in line' question is also geometric. Whether the ball landed in line with the stumps depends on the pitching position and the bend. When an off-spinner pitches outside the stumps and turns, line determination becomes harder still. This is why the same delivery can be out in one match and Umpire's Call in another — not a failure of consistency, but the natural product of geometric uncertainty.

A review's decision tree is actually simple, but every step demands humility. First — was the delivery legal? Second — was there bat contact? Third — did the ball pitch in line with the stumps? Fourth — was impact in line? Fifth — would it have hit the stumps? The first four steps are answered with near-certainty by Hawk-Eye and UltraEdge; but at the fifth step the system reaches inference. And the whole decision rests on that inference. As a referee-analyst, I always isolate that fifth step, because that is where the system concedes its own limits.

There is a less-discussed effect on the rhythm of the game. Every review takes time, and a stadium waiting on the third umpire sinks into a strange silence. The delay not only worsens the over rate; it breaks players' mental rhythm. The batsman who had already walked off assuming 'not out' is summoned back not from the pavilion, but from the big-screen graphic. This psychological layer is part of systems analysis too, because a decision must not only be right, it must arrive on time and legibly.

Taken together, the review system works with three layers of truth: what can be measured, what can be inferred, and what can never be certain. Successful officiating means telling these three layers apart — and staying humble on the last.

Contrarian angle: The problem is not the technology, it is the presentation

Now the uncomfortable question. The loudest complaints about Umpire's Call come from spectators — 'the ball was hitting the stumps, yet not out?' Here I say the problem is not the technology; the problem is the language of broadcast.

When Hawk-Eye draws the ball's path on the big screen, the viewer reads it as final truth — though the projection is one probable path among many. Had the broadcaster shown '51 percent probability of hitting the stumps', the same decision would have become comprehensible rather than controversial. This 'theatre of certainty' is the real offence.

Second, the question of accountability. Behind the null result, let us not hide the human too. If technology says 'not certain', then the on-field umpire's original call is final — meaning a human judgement remains, delivered in a fraction of a second. Viewers often forget that an umpire's reaction time is only 0.3 to 0.4 seconds. Pressure, fatigue, obstructed sight — analysing without this foggy layer makes the system look far cleaner than the field, which is unreal.

Yet yes, there is one fair complaint: when the same Umpire's Call rule consistently denies a bowler, procedural inconsistency erodes trust. Consistency is not the technology's job, it is the administration's — and the ICC's duty does not end there.

Takeaway: Showing uncertainty is the next step

As semi-automated offside and ball-tracking spread, one question grows more urgent: do we want to display perfect certainty, or honest uncertainty? My seventeen years tell me cricket's next big reform is not in technology but in presentation. Showing probability margins instead of the word 'clipping', placing the system's uncertainty beside the umpire's call — that is what will restore trust.

So I leave the question to the ordinary viewer: when the machine clearly says 'I am not certain', why do we insist a human be certain instead? A system that can admit its own ignorance is, in the end, the most trustworthy.