The Ball Hits the Stumps, Yet It Stays Not Out: DRS 'Umpire's Call' and Cricket's Silent Transfer of Power

The Referee's Eye

The Ball Hits the Stumps, Yet It Stays Not Out: DRS 'Umpire's Call' and Cricket's Silent Transfer of Power

Hook

The red dot on the ball-tracking screen stopped dead on the outer edge of leg stump. Twenty-two yards away, the batter was still on the crease, helmet on, a question in his eyes. The giant stadium screen looped the replay again and again — the ball pitched outside leg, struck the pad in line, then bent inwards. The red ball was hitting the stumps; nobody was disputing that. Yet the reply that came back through the third umpire's headset carried cricket's two most contested words: 'Umpire's Call.' The on-field decision stood. The batter walked.

I watched that scene from a small flat in Kuala Lumpur, on the far side of the screen, and immediately opened my old spreadsheet. Because the scene was not new. In 2026, I began logging VAR incidents in Kuala Lumpur; the pattern was already there. VAR in football, DRS in cricket — the technology differs, but the question is identical: who actually makes the decision, and why do we accept that decision as 'truth'?

Law & Decision

Applicable law: ICC Men's Test Match Playing Conditions, Player Review (Appendix D). The three LBW gates — pitching, impact, wicket-hitting. Instruments: ball-tracking, UltraEdge, HotSpot. Decision layers: on-field umpire → player review → third umpire → ball-tracking projection → umpire's call threshold. My confidence levels: high on the pitching gate, medium on impact, low-to-medium on wicket-hitting.

Context: Law, Machine, and a Quiet Compromise

DRS began officially in July 2026 with the India–Sri Lanka Test in Colombo. Since then the system has stood on three different instruments — ball-tracking, UltraEdge (audio-based snicko detection), and HotSpot (thermal imaging). The story of umpire's call is really a story about the error margins of these three machines.

The ICC Playing Conditions set out the Player Review system in Appendix D. Put simply: in Tests, a team gets two reviews per innings; a successful review is retained, a failed one is lost. The number differs in ODIs and T20s, but the principle is the same.

LBW asks three questions. Did the ball pitch in line with the stumps? At the moment of pad contact, was the ball in line? And the final question — would the ball have hit the stumps? The first two answers are binary: either in line or not. But it is the third question that gives birth to umpire's call. When ball-tracking says the ball would have hit the stumps, but the margin is so small that less than half the ball would have struck, the technology's prediction is treated as 'not certain,' and the on-field decision survives.

A subtle compromise hides here. The technology does not always say 'out' or 'not out'; it says 'probable path.' The law then places a confidence band over that probability. The question is whether the viewer, watching that red ball on the screen, ever gets to see that band. The answer: no.

My experience has taught me that the 2026 Kuala Lumpur incident log and the 2026 Russia World Cup VAR Protocol Audit both delivered the same lesson: the technology's decision and the technology's presentation are never the same thing. In football, VAR draws an offside line; in cricket, ball-tracking draws the ball's path. In both, the screen shows a certain truth that is, on paper, only a probability.

Core Analysis: Dissecting One Decision Across Four Layers

The Mathematics of Half a Ball

At the centre of umpire's call sits a geometric boundary. When ball-tracking predicts the ball would have hit the stumps, the question becomes: how much of it would have hit? The whole ball? Half? A sliver? In the language of the law, if less than half the ball would have struck the stumps, it falls on the 'edge of timing,' and the on-field decision survives. This half-ball-width band is the true geography of umpire's call.

When I ran the VAR audit across Russia in 2026, I saw that subjective handball decisions were overturned most often — because there is no geometric band there, only human interpretation. Cricket is the reverse: the band exists, measured in numbers, but where the band sits is the real subject of dispute. The technology measures, the law draws the boundary, and the human searches for meaning inside it.

Same Ball, Two Verdicts: The Architecture of Asymmetry

This is where DRS hides its most under-discussed structural feature. The same ball-tracking projection — the same red dot, the same path — stays 'out' if the on-field umpire said out, and stays 'not out' if the umpire said not out. The technology's output is identical, but the final decision depends on the first on-field call.

Think about it. If the ball grazed the edge of the stump by a hair, an on-field 'out' sends the batter back, while an on-field 'not out' lets him survive. The technology is saying the same thing in both cases — 'the ball was almost hitting the stumps.' But the system translates that same uncertainty into two different outcomes. This is not a flaw; it is a deliberate legal choice to preserve on-field authority. Yet the result is a system that can confirm human error but was never designed to correct it in the marginal zone.

This is why the Referee's Eye is a frame-by-frame threshold test, not a whistle. For every review, I measure three questions separately: what the technology says, what the law permits, and what the on-field call was. The real decision emerges from the intersection of all three — technology alone never decides.

Who Reviews, and Why

One dimension is almost always overlooked in DRS debates: who takes the review. In my log, batters' reviews and bowlers' reviews are two different risk structures. Batters usually review an 'out' decision, hoping ball-tracking will show the ball missing or the impact outside the line. But because the on-field 'out' survives inside the umpire's call band, a batter's review often dies at the margin. Bowlers review 'not out' calls, and their path to success runs through different gates.

A pattern returned again and again in my spreadsheet: most reviews fail, and a significant share of those failures stop right at the umpire's call boundary. This is not a batter's misjudgement — it is the protocol's design. When the law says 'if uncertain, the on-field call stands,' the person reviewing is not betting against the technology but against his own luck.

Here the 2026 Kuala Lumpur incident log served me well. In football, the same problem appears at VAR's subjective gates — the referee decides, VAR 'assists' him, but the final word often stays with the referee. Cricket's machine is more neutral, yet the centre of power stands in exactly the same place: on the field.

The Red Ball on Screen and the Invisible Confidence Band

Now to the image millions see on every review. The ball-tracking graphic — a red ball, white stumps, a clean path. The batter thinks it, the crowd thinks it, the commentator says it: 'Look, the ball hit the stumps, that's out.' But the picture on screen is a point prediction; the confidence band behind it never appears.

An old frustration returns here. I have written many times about heatmaps — they hide a player's real role; they are an average, an impression, not the truth. The red ball in ball-tracking is much the same. The machine draws a probable path, then compresses an uncertainty band, and we take that compressed band as 'proof.' The technology is not wrong; we are reading its language wrongly.

A structural difference between football and cricket becomes clear here. Many of VAR's gates are subjective — whether a 'clear and obvious error' occurred is a human call. Cricket's gates are far more measurable — pitching, impact, wicket-hitting. Yet both systems share one thing: the image presented to the viewer conceals the complexity of the decision. In my 2026 Russia World Cup VAR Protocol Audit, I saw exactly this pattern — the screen's certain picture and the decision's uncertain reasoning never matched.

Caution is needed here. Cricket's DRS and football's VAR cannot be compared directly. DRS's gates are nearly binary, resting on a physical model of the ball; many of VAR's gates are interpretive. So I compare principles, not processes. Their one real similarity: when technology enters the heart of decision-making, it also shifts the balance of power — who speaks, and who listens, both change.

The Tax of Time

One cost is nearly invisible: time. Each review stretches from moments to minutes — projection, snicko check, in-line verification, the third umpire's communication. One or two reviews may be negligible; but five or six across a Test day affect the match's rhythm, the over rate, and the bowlers' freshness.

When I worked on the 2026 Empty Stadiums: Silent Pitch Study, I learned one thing — when external noise changes, the game's internal rhythm changes too. Reviews work in reverse: when external technology enters, the game's internal rhythm is disrupted. This tax of time is the hidden price we pay in the name of making a decision 'perfect.'

Contrarian Angle: Umpire's Call Is Not a Flaw — Its Presentation Is the Crisis

The easy path is to make umpire's call the villain — 'the technology says out, yet it stays not out, what a foolish law.' I reject that. Umpire's call is in fact a prudent compromise: where the technology's prediction is weakest, it trusts the human on the field. It is an honest admission of the technology's limits.

But my real objection lies elsewhere. The system preserves the human umpire's authority precisely in the zone where the human umpire is least reliable — that is, whether the ball grazed the stump by a hair, who can possibly judge that with the naked eye? Seen this way, we have retained the human exactly where his eye is weakest. And the technology's greatest service — covering that weakness — we have rejected in the name of legal courtesy.

Deeper still is the problem of presentation. The law admits uncertainty, but the screen conceals it. So when the viewer sees 'the red ball hit the stumps' while the system says 'this is an uncertain zone,' the clash of two truths erodes the viewer's trust, breeds anger at the umpire, and deepens distrust of the technology. The real misfortune is this: the law is honest, the technology is skilled, but the communication is dishonest.

My football experience offers a warning. After I began the VAR log in Kuala Lumpur in 2026, I saw that viewers' anger often landed not on the protocol but on the referee. The same can happen with DRS in cricket — if someone showed the uncertainty of umpire's call on screen, people would stop blaming the umpire. The problem is not in the technology but in the transparency.

Takeaway: Toward Sight

The next step, to my mind, is clear — tiered transparency. Show the confidence band on the ball-tracking graphic, make every review's decision log public, and standardise the umpire's call boundary across formats. When technology has entered the heart of the decision, its uncertainty belongs there too.

The ball that hits the stumps yet is not out is a symbol of cricket's silent transfer of power. The question is no longer, 'Is the technology right?' It is now, 'Who will see the technology's uncertainty, and who will accept it?' If the answer stays hidden on the far side of the screen, then in every review we lose not just a decision, but people's trust in the game itself.