Umpire's Call: The DRS Rule That Splits Every Cricket Crowd

Few three-word phrases can silence a stadium and start a thousand arguments quite like Umpire's Call. The ball-tracking graphic shows the red ball clipping leg stump, the bowler is already wheeling away, and then the big screen flashes a result that keeps the batter exactly where they were. Half the ground cheers, the other half throws up its hands. This is the single most misunderstood part of the Decision Review System (DRS), and once the logic clicks, it stops feeling like a robbery and starts looking like a sensible piece of design.

This is a guide to what actually happens in those long seconds while the third umpire works through a review — what the technology is measuring, why a ball shown hitting the stumps can still be not out, and how captains decide whether to spend a review at all.

What DRS is really doing

DRS arrived in international cricket in 2008, in a Test between India and Sri Lanka, and it has been refined almost every season since. It is not one camera or one gadget. It is a stack of tools the third umpire consults in sequence:

• Ball-tracking (Hawk-Eye or Virtual Eye), which reconstructs the delivery's real path and predicts where it would have gone after hitting the pad.
• Edge detection — the audio spike of UltraEdge or Snickometer, synced to the exact frame the ball passes bat or pad.
• Hot Spot, an infrared layer that shows a bright mark where the ball touched something, used in some series but not all.

The on-field umpire makes a decision first. DRS exists only to correct the clear mistakes, not to re-referee every ball from scratch. That single idea is the key to the whole Umpire's Call debate.

The three checks behind every LBW review

An LBW review is the one that produces the most drama, and it runs through three gates in a fixed order. Miss any gate and the verdict is settled before the next one matters.

1. Pitching. Where did the ball bounce? If it pitched outside leg stump, the batter is not out, full stop — no matter how plumb it looked. This is a hard line with no grey area.
2. Impact. Where did the ball strike the pad? It must be in line with the stumps, or outside off stump only if the batter was not offering a shot. Strike the pad outside off while playing a genuine stroke, and it is not out.
3. Wickets. Was the ball going on to hit the stumps? This is where ball-tracking makes its prediction, and this is where Umpire's Call lives.

A batter can be beaten all ends up and still survive on the first or second gate. That is why a delivery that looks dead straight on the replay can come back not out — it pitched a fraction outside leg, and nothing else gets a vote.

Why the ball can hit the stumps and still be not out

Here is the part that breaks people. On the impact and wickets gates, the technology has a built-in margin of error, because predicting the future of a moving ball can never be perfect. Hawk-Eye is extremely good, but it is still an estimate.

So the rule-makers drew a tolerance zone. For the wicket to be overturned to out, the prediction must show enough of the ball striking the stumps — in practice, the centre of the ball must be hitting within a zone bounded by the outer edge of off and leg stump and the bottom of the bails. If the ball is only shaving the surface, with less than roughly half the ball overlapping the stumps, the system declares the call too tight to be certain. It then hands the decision back to the human who made it. If the umpire gave it out, it stays out. If not out, it stays not out.

That is why the same graphic — ball kissing leg stump — can mean out for one batter and not out for another. The graphic is identical; the original on-field decision was different. Umpire's Call is not the technology being indecisive. It is the technology admitting the margin and refusing to overturn a defensible human decision on a coin-flip.

The bit that protects your review

There is a practical upside that often gets lost in the outrage. Since a 2017 change to the playing conditions, an Umpire's Call result lets the reviewing team keep its review. You only burn a review when the original decision was clearly right.

So the accounting works like this:

• Decision overturned in your favour: review retained.
• Result comes back Umpire's Call: review retained.
• Decision clearly upheld against you: review lost.

This matters at the death of a tight chase, when a captain is guarding a single review like a last bullet. A marginal LBW shout that returns Umpire's Call costs nothing, which quietly encourages teams to roll the dice on the 50-50s.

Edges, snicks and the caught reviews

Not every review is an LBW. Caught-behind and bat-pad referrals lean on the audio and infrared tools instead of ball-tracking. The third umpire lines up the UltraEdge waveform with the frame the ball passes the bat. A spike exactly as bat and ball meet means contact; a spike a frame too early or late usually means bat hitting pad or ground.

These are often cleaner than LBW calls, but they have their own grey zones — a faint flicker on the trace, or pad and bat so close that the audio can't separate them. When the evidence is genuinely inconclusive, the principle is the same as Umpire's Call: no clear proof, so the on-field decision survives.

How many reviews you get, and the smart way to spend them

The allocation depends on the format, and it is worth knowing before you scream at a captain for wasting one.

• Tests: three unsuccessful reviews per innings per side.
• ODIs: two per innings.
• IPL and most T20 leagues: two per innings — and in the IPL these can now also be spent challenging wides and height no-balls, not just dismissals.

That IPL expansion changed the strategy. A review is no longer sacred to the big LBW shout; a team might burn one disputing a waist-high full toss or a tight wide down leg in a last-over chase. The flip side is the familiar groan when a side wastes both reviews early on hopeful appeals and then has nothing left for a genuine howler at the death.

The golden rule that good captains follow is simple: review the decisions you are confident are wrong, not the ones you wish were wrong. Trust the bowler and keeper for edges, trust your own eyes for pitching outside leg, and leave the desperate hail-mary appeals alone.

Where the argument goes next

Umpire's Call remains cricket's most reliably divisive rule. One camp wants it scrapped — if any part of the ball hits the stumps, give it out and be done. The other camp points out that doing so would hand a prediction algorithm absolute authority over deliveries it cannot judge to the millimetre, and would make the standing umpire almost irrelevant on LBWs.

The game's lawmakers have so far chosen to keep the human in the loop and let the margin protect both batter and bowler. Meanwhile DRS keeps creeping into new corners — height no-balls, off-side wides, and richer ball-tracking — which means more reviews, more graphics, and more chances for a packed ground to split down the middle. The next time that phrase lights up the screen, you will at least know it is not the system dodging a decision. It is the system telling you the call was simply too close to take out of the umpire's hands.