How The Decision Review System Handles Umpire's Call

Umpire's call is the most argued-about element of cricket officiating, and most of the argument comes from misunderstanding what it is for. It is a statement about measurement confidence, not about fairness.

Ball-tracking predicts rather than records

The cameras record the ball up to the point of impact with the pad. Everything after that point is a projection of where the ball would have gone.

That projection is built from the observed trajectory, the bounce characteristics and the distance travelled before impact. It is a physical model, and models carry error.

The error is small but not zero, and it grows with the distance between impact and stumps. A ball struck well forward has a longer predicted path and a wider uncertainty band.

The margin is expressed as a proportion of the ball

Rather than publishing an error figure, the system encodes uncertainty as a requirement about how much of the ball must be shown hitting the stumps for a decision to be overturned.

A marginal clip of the outside of leg stump falls inside that band. The system cannot distinguish between that and a ball passing just outside, so it declines to contradict the umpire.

When the projection shows a clear strike on the middle of the stumps, the margin is comfortably exceeded and the on-field decision is overturned regardless of what it was.

The same delivery can produce two outcomes

This is the feature that generates most complaints. An identical trajectory results in a dismissal if the umpire raised the finger and a not-out if the umpire did not.

That is consistent rather than arbitrary. Inside the margin the technology is not asserting the correct answer, so authority remains where the laws place it by default, with the standing umpire.

Removing the margin would not eliminate uncertainty. It would transfer every marginal case to the model and treat a prediction as though it carried the certainty of a recording.

Review economics change how captains use it

Teams hold a limited number of unsuccessful reviews, and an umpire's call outcome usually preserves the review rather than consuming it. That asymmetry shapes when sides go upstairs.

A fielding captain with a marginal shout has a reasonable case for reviewing, because the downside is often only a retained decision rather than a lost review.

Batting sides face the opposite calculation. Reviewing a plumb-looking dismissal to check for an inside edge costs a review outright if no edge exists, which makes the threshold higher.

The system was built to remove howlers, not adjudicate millimetres

The original purpose was correcting obvious errors that changed matches. Marginal adjudication came later, as tracking improved and broadcasters began displaying projections to viewers.

The visual presentation drives much of the friction. A graphic showing the ball clipping the stumps looks definitive on screen, which makes a retained not-out appear perverse.

What the graphic omits is the confidence interval around the line it draws. Umpire's call is that interval, made into a rule.