August 28, 2026 — ny_wk
▶ What Is DRS Umpire's Call, Really? | Subscribe to @explorenystream
Disclosure: some links above are affiliate links — if you buy through them I may earn a small commission at no extra cost to you. Thanks for supporting the channel!
DRS Umpire's Call is the most misunderstood decision in modern cricket — and once you understand the three separate checks behind every LBW review, the logic that once seemed maddening starts to look like the only honest option the game has. Here is exactly how it works, why it exists, and why scrapping it would actually make things worse.
Picture the scene. A packed stadium. A bowler has beaten the batter, the ball has crashed into what every pair of eyes in the ground insists is the middle of middle stump, 80,000 people are already in the air — and then the replay rolls, the tracking confirms the impact on the stumps, and the on-field umpire raises a finger to say: not out. Nothing has broken down. No one has made an error. That is Umpire's Call doing precisely what it was designed to do, under conditions the game's lawmakers anticipated in full.
The fury is understandable. The logic, once laid out completely, is airtight. Here is every layer of it.
An LBW decision is not a single question. It is three questions asked in a fixed order, and an appeal can fail at any one of them before the final check is ever reached. Understanding this structure is the foundation of understanding DRS — because most of the public debate around Umpire's Call skips straight to the third check without acknowledging the first two.
Before anything else, the ball tracking system evaluates where the delivery landed. Under the Laws of Cricket, a ball that pitches outside the line of leg stump cannot be given out LBW, regardless of where it strikes or where it was heading. This is a matter of pure geometry. The cameras that feed the ball-tracking model — typically six or more high-frame-rate units positioned around the ground — have enough data to resolve this with high confidence. If the answer is "outside leg," the appeal dies immediately. No further checks. Decision upheld.
If the ball pitched in a valid zone, the second check asks whether it struck the batter in line with the stumps — or outside off stump when the batter was playing a shot. Again, this is a factual question about a point in space. Camera data can answer it with high precision. If the impact was outside the line of off stump and the batter was playing a shot, the appeal fails here.
Both of these first two checks share an important property: they are measurements of something that actually happened, at a known moment, in a fixed location. The technology excels at them. When it overturns the on-field decision on either of these two grounds, there is no ambiguity — the camera data says what happened and the decision changes.
This is where Umpire's Call enters. The third check is categorically different from the first two, because the ball never actually reached the stumps. A leg — or a pad, or a boot — got in the way. So the system has to predict where the ball would have gone if that leg had not been there. It extrapolates the delivery's trajectory, accounts for deceleration and any seam movement already observed in the delivery, and produces a probability map of where the ball would have crossed the stumps' plane.
That prediction is very good. Ball-tracking technology used in international cricket is calibrated against thousands of deliveries per series and independently validated. But it is still a prediction, and predictions carry error margins. That margin is small — often described as in the range of a few millimetres in any direction — but it exists, and the entire architecture of Umpire's Call is a direct response to it.
The threshold for overturning an on-field decision on the trajectory check is this: the ball-tracking model must show that at least 50% of the ball would have struck the stumps. That is the boundary between "clear enough to overturn" and "Umpire's Call."
The choice of 50% is not arbitrary. A cricket ball is approximately 72 mm in diameter. The stumps together span 228 mm. A ball that clips the very edge of off stump — with just a sliver of its circumference overlapping — is not the same kind of clear-cut dismissal as a ball crashing into leg stump with the centre of its trajectory. The 50% rule distinguishes between those two situations in a principled way.
When the model shows more than half the ball on the stumps, the technology is expressing a high-confidence verdict. The margin of error in the prediction is not large enough to flip the outcome. Overturning the on-field umpire in that case is statistically justified — you would be wrong to keep the original call.
When the model shows less than half the ball on the stumps, something different is happening. The technology is saying: this is close, and my margin of error is not small enough to be certain which way this goes. In that narrow band of space — effectively the edge of the stumps — the model's prediction uncertainty overlaps with the boundary between out and not out. Making a definitive call in that zone would mean pretending the model is more precise than it actually is.
This is the core of the entire rule. False precision in international sport is not neutral — it is actively harmful. If a system that carries a known margin of error is allowed to overturn human decisions by 1 mm, then it is not the tracking that is deciding matches. It is the noise floor of the model's measurement.
When the trajectory check returns a result in the Umpire's Call zone, the rule does not split the difference. It does not flip a coin. It does something more principled: it treats the question as unresolved, and hands it back to the human who was standing at the best angle, in real time, with the full sensory context of the delivery.
That means the same delivery, with the same ball-tracking output, can produce two opposite final decisions — and that is not a bug. If the on-field umpire gave "out," it stays out. If they gave "not out," it stays not out. The DRS review has been run in full; it has concluded that the technology cannot improve on the human call; and the original decision stands.
This is the feature that generates the most frustration among fans, because it violates an intuitive assumption: that reviewing a decision with technology should always produce the same result regardless of what the umpire said first. That assumption would be correct if the technology were perfect. It is not. The rule is designed for the world as it is, not the world as viewers wish it were.
There is a second part of this that almost nobody knows, and it is genuinely important for team strategy. When a review is referred and comes back as Umpire's Call, the challenging side does not lose their review. The system treats the outcome as genuinely ambiguous — the technology did not say the appeal was wrong, only that it could not determine the answer with sufficient confidence. Burning a review on a close call that the technology cannot resolve would be a punishment for the wrong thing. So the review is retained, and the team can challenge again later.
This distinction matters more than it might initially seem. In a tight Test match, teams typically have two reviews per innings. Keeping a review after an Umpire's Call can be the difference between being able to challenge a clear edge that the on-field umpire misses in the final session, or having no recourse at all.
The case for removing Umpire's Call from DRS is not absurd, and anyone who tells you it is has not engaged seriously with the opposition argument. Here it is at full strength: ball-tracking technology has improved enormously since DRS was introduced. The margin of error is smaller than it used to be. If the model shows any part of the ball hitting the stumps, why not trust it and overturn? Every "not out" in the Umpire's Call zone is a wicket the bowler earned but did not get, or a dismissal the batter survived when the tracking says they should not have. The rule protects a human error rather than correcting it.
That argument has force. But it runs into two problems that cannot be dismissed.
The first is measurement honesty. No ball-tracking vendor has published a verified margin of error below a few millimetres across all ground conditions, all ball types, and all camera configurations. The model is re-calibrated at each venue, but calibration is not perfection. Asking any model to render a decisive verdict on a question that falls within its own error bars is epistemically dishonest — and in sport, epistemically dishonest rules produce injustice, not precision.
The second problem is asymmetric consequence. Every run of data eventually produces an outlier. A tracking prediction that is wrong by 3 mm on a ball that clips the very edge of the off stump is an error of a kind the naked eye cannot catch and the laws cannot correct after the fact. In a format where single wickets determine series outcomes, that is not a theoretical risk worth accepting in exchange for eliminating Umpire's Call.
Keep Umpire's Call and you protect the game from false precision in the edge case where the technology is genuinely uncertain. Remove it and you get a cleaner-looking rule at the cost of turning measurement noise into match outcomes. The current rule, for all its appearance of inconsistency, is the more intellectually rigorous of the two options.
Reading about DRS and watching it unfold in a live stadium are completely different experiences. There is nothing quite like being in the stands when a captain walks out to the square, signals the review, and a packed ground waits for the third umpire to run through all three checks on the giant screens.
Test cricket's great venues offer very different atmospheres. Lord's in London remains the sport's spiritual headquarters — the Long Room alone is worth the visit if you can get a seat in the Pavilion, though members' access is restricted on big match days. Book well in advance; Lord's Test tickets for England matches sell out months before the series begins.
The Sydney Cricket Ground (SCG) and Melbourne Cricket Ground (MCG) give you the Boxing Day and New Year's Test experience that Australian cricket fans treat as a national rite. The SCG's Heritage Listed grandstands and the MCG's capacity for 100,000 make both worth a trip if you are ever in Australia during an Ashes summer.
In the subcontinent, the Eden Gardens in Kolkata and the Narendra Modi Stadium in Ahmedabad — the largest cricket ground on earth by capacity — offer an intensity that has no parallel in world sport. The noise alone when a review is referred during a tight LBW appeal is something that does not translate on television.
Umpire's Call is the outcome of a DRS LBW review when the ball-tracking model shows that less than 50% of the ball would have struck the stumps. Because the prediction falls within the technology's margin of error, the system treats the question as unresolved and the original on-field decision — whether out or not out — stands.
Because when the ball-tracking falls in the Umpire's Call zone, the technology is explicitly saying it cannot determine the correct outcome with confidence. In that case, the on-field umpire's call becomes the tiebreaker. The same tracking output therefore produces different final results depending on what the umpire said — which is the intended behaviour, not an error.
No. When a review is referred and the third umpire returns an Umpire's Call verdict on the trajectory check, the challenging side retains their review. The ICC treats Umpire's Call as a genuinely inconclusive result rather than a failed challenge, so no review is lost.
Without Umpire's Call, any ball-tracking result showing any part of the ball on the stumps could overturn a human decision, even when the projected impact falls within the model's own margin of error. This would mean that measurement noise — tiny inaccuracies inherent in any predictive model — could directly determine match outcomes at the highest level of the sport.
Every cricket fan has shouted at a screen over an Umpire's Call. Knowing the three-check system — and exactly why that 50% threshold exists — does not make those moments less dramatic. It makes them more so, because you can see precisely what the technology is communicating and why the game's lawmakers chose this answer over every alternative.
Watch the full animated breakdown — What Is DRS Umpire's Call, Really? — on @explorenystream. A new rule is broken down on the channel every week. Subscribe so you never miss the next one.
