Skip to content
Rules5 min

DRS Reviews and Umpire's Call: The Decision Review System

The Decision Review System allows players to challenge on-field umpiring decisions using Hawkeye, Snickometer, and Hot Spot technology in Test and limited-overs cricket.

Written by GeoCric EditorialUpdated Jul 3, 2026
ShareShareWhatsAppFacebook

The Decision Review System (DRS) allows players to challenge on-field umpiring decisions using ball-tracking (Hawkeye), edge-detection (Snickometer and Hot Spot), and replays. Introduced experimentally in 2008 and standardised in 2011, DRS has reduced umpiring errors significantly while adding a strategic dimension to the game — teams must use reviews wisely, as wasting them leaves no recourse later in an innings.

How Reviews Work

Each team has two DRS reviews per innings in Tests and one per innings in limited-overs cricket. A review is retained if the decision is overturned; lost if it is upheld. The third umpire examines multiple technologies: Hawkeye for LBW predictions (showing the ball's projected path after pitching), UltraEdge/Snickometer for inside-edge detection (a thin edge not visible to the naked eye), and DRS-approved ball-tracking for impact point and height. The third umpire's recommendation is sent to the on-field umpire, who makes the final call.

Umpire's Call

When Hawkeye predicts that the ball would have hit the stumps but part of the ball clips the edge of the zone — within 50% of the ball's width hitting the stumps — the on-field decision stands. This is 'Umpire's Call'. If an LBW was given out and Umpire's Call is applied, the batter is out. If not out was given and Umpire's Call is applied, the batter stays not out — and crucially, the reviewing team retains their review. This asymmetry is a source of ongoing debate.

Hawkeye ball-tracking is accurate to within 2.5 mm for impact predictions. The Umpire's Call zone — where the model's margin of error is high enough that the on-field decision is deferred to — covers approximately 25% of all LBW predictions.

Strategic Use of Reviews

Experienced captains and wicketkeepers develop skill in reading when a review is worth burning. Common rules of thumb: do not review unless at least two of the three technologies support overturning (edged to keeper, clear missing leg, obvious impact outside off). Wasting reviews in the first 10 overs leaves a team with no protection against genuine umpiring errors at the end of a session. Some captains keep reviews for the final session, knowing that a wicket or a saved wicket in the last hour of a Test day can change the match.

Frequently asked questions

What is Umpire's Call in DRS cricket?

Umpire's Call occurs when Hawkeye predicts the ball would clip the edge of the stumps within the model's margin of error. The on-field decision stands, and if the reviewing team was told 'Umpire's Call', they retain their review.

How many DRS reviews does each team have in a Test?

Each team has two unsuccessful DRS reviews per innings in Test cricket. A review is retained if the on-field decision is reversed. In limited-overs cricket, each team has one review per innings.