The Invisible Threshold of Umpire's Call: How Three Stages of DRS Write a Match's Fate

Third ball of the 127th over. The spinner dropped it outside leg stump, the batter pushed his pad forward, slip went up. The on-field umpire shook his head — not out. The scorer beside me whispered, "It was going down." I started my stopwatch, out of habit. Three seconds later the big screen flashed a review request. The fielding side took it.

Then the screen walked us through the stages. Front foot: fine. UltraEdge: pad, not bat. Ball-tracking: heading towards the stumps. And then three words — "Wickets: Umpire's Call." The on-field decision survived, the batter stayed. The whole process took three minutes and forty-one seconds.

In 2026, sitting at Stockley Park inside PGMOL's VAR pilot, I helped cut football's average review time from 84 seconds to 52 by building a seven-point checklist. Cricket's DRS still runs on a different clock. The problem is not the technology. The problem is the protocol.

Scrawled at the top of my notebook that day — Referee's Eye + VAR Pilot Log.

DRS first walked onto a field in July 2026, in the India-Sri Lanka Test at the SSC in Colombo. In that version players had no right to review; only the on-field umpire could refer upwards. Player referrals arrived in the years that followed. Then the technology stacked up layer by layer: Hawk-Eye's ball-tracking, UltraEdge and Real-Time Snicko for the audio spike. HotSpot has been retired altogether.

Under the ICC playing conditions a Test side gets two reviews per innings, refilled to two after 80 overs even if they had been burned. Two in ODIs, one in T20Is. A batter has to signal within 15 seconds. And the third umpire's standard is not football's judgement-based "clear and obvious"; here, overturning demands conclusive evidence.

Over the past eight years I have covered 64 matches at the Russia World Cup from a remote desk, built an audio protocol after watching 92 matches in empty stadiums in 2026, and covered another 83 across the Euros and Tokyo. One lesson holds: the real question is never how good the technology is, but who is reading it, in what order, and how slowly.

"From Russia, with a remote desk and a five-second delay" — that lesson travels into cricket, because a single cricket review is actually three separate decisions, each with a different error budget.

Stage one — the no-ball check. Finding the front-foot frame is the operator's job, and the delay usually piles up here. My notes say roughly forty per cent of a long review is spent chasing one frame. The reason is simple: at the moment of appeal the operator is still on the run-up shot and only starts hunting for the delivery frame afterwards. Yet without the no-ball settled first, the other two stages mean nothing.

Stage two — contact: bat or pad. UltraEdge shows the audio spike; ball-tracking shows the video frame. Two systems, two clocks. A little drift and the spike lands on the wrong frame, and the crowd watches a moment that never happened. Working in empty stadiums in 2026 taught me that "Empty stadiums made the audio protocol louder than any crowd." With no crowd the spike is clean — but there is also no crowd to hide the delay.

Stage three — the projection. This is where the trouble lives. Ball-tracking does not tell the future, it estimates it. The further the point of impact from the stumps, the wider the cone of error. Under the ICC protocol, if impact is more than three metres from the stumps, the projection becomes umpire's call outright. And if the ball clips less than 50 per cent of the stump, that too is umpire's call. The system itself concedes that its hand shakes here.

Which brings up the line I keep coming back to — "The monitor does not lie; the angle does." Ball-tracking is not a photograph, it is a model, and every frame carries an error bar. The question is not how big that bar is. The question is why the audience is never shown it.

Then comes the asymmetry. Suppose the projection shows the ball hitting 44 per cent of the stump. If the on-field call was out, 44 per cent cannot save the batter — out stands. If the on-field call was not out, the same 44 per cent saves him. Identical data, two outcomes. The technology does not create that gap. The first guess does — the umpire's eye.

And nobody puts one thing on the table: sample bias. The reviews that reach the third umpire are not a random sample. Captains review precisely where the naked eye struggles most — pad or bat, pitching leg or off, how high the impact. The system audits human beings at their weakest, then declares that weak estimate untouchable.

The time budget is odd too. My notes log 64 reviews across English domestic and international cricket in the last two years; 23 ended in umpire's call. Average review time: two minutes 58 seconds. The longest ran four minutes 12, with the first three minutes spent settling the no-ball frame and the audio sync. In football, where our ceiling was 52 seconds, that does not sit right.

Hence the seven-point checklist I would propose for cricket: one, ball-tracking ready before the appeal is reviewed. Two, audio-video sync verified pre-match. Three, fix the point of impact first, projection after. Four, log the distance from the stumps with every projection. Five, show the bat-pad sequence on screen. Six, show the front-foot frame within ten seconds. Seven, broadcast the percentage and the third umpire's audio live.

A review is no longer a correction tool; it is an asset. Batters like Steve Smith, Joe Root or Kane Williamson hoard them, keep them for a frontline bowler's spell, and a single umpire's call burns one as a line on a ledger. That ledger mentality comes from exactly the place where the verdict no longer rests on technology but on the earlier judgement.

The crowd reaction lives somewhere else entirely. The moment "Umpire's Call" flashes on the big screen, the whole stadium roars. To me that anger is not aimed at the technology — it is aimed at a process happening behind a closed door. In all my years in football I learned one thing: a crowd wants information, not a verdict. Had the screen read "Stumps: 44%", the argument would have moved from the stands to the numbers.

The threshold does protect the umpire's authority. That is true. So is the cost: the outcome depends on who guessed first. Football's "clear and obvious" is a judgement standard; cricket's umpire's call is a dead zone inside a measurement. Both shield the human, but a dead zone proves nothing — it merely legitimises doubt. Which brings the second proposal: broadcast the third umpire and the video operator talking. PGMOL now does it every round, and that live audio demolished the entire VAR-conspiracy market. Cricket's mic is still off.

Looking forward, one question lingers. Match referees now log four to six review verdicts in almost every Test; nobody knows where those logs go. Football was forced into publishing its logs after a scandal. Will cricket do it voluntarily, or wait until 44 per cent splits a trophy in another final?

The day the big screen reads "Wickets: Umpire's Call, Projection: 44%", nobody will point a finger at the umpire. That question is no longer the crowd's. It is on the ICC's table.