DRS Explained: How the Decision Review System Works in Cricket

The Decision Review System (DRS) is cricket's technology-assisted review process — allowing batting and fielding teams to challenge on-field umpiring decisions using ball-tracking cameras, thermal imaging, and audio analysis. Introduced in international cricket from 2008 onwards, DRS has fundamentally changed how umpiring decisions are made and contested, significantly reducing the number of incorrect decisions that stand in international cricket.

Ball-Tracking Technology

Ball-tracking (Hawk-Eye) is the core technology behind DRS — a system that uses multiple high-speed cameras to track the ball's trajectory and predict where it would have continued after hitting the batter's pad. For LBW decisions, ball-tracking shows whether the delivery would have hit the stumps if the pad had not been in the way: a ball tracked to hit the stumps changes the umpire's 'not out' LBW decision; a ball tracked to miss the stumps upholds an umpire's 'out' LBW decision. The tracking prediction is most accurate for deliveries that pitch on a good length near the stumps, and less accurate for deliveries that pitch very full or very short.

Edge Detection: Snickometer and Hot Spot

Two technologies detect whether the ball has edged the bat. Snickometer (or Ultra-Edge) analyzes audio — detecting the acoustic 'nick' sound of the ball hitting the bat edge via a microphone embedded in the stumps. Hot Spot uses infrared thermal imaging: the friction from the ball hitting the bat or pad creates a heat mark visible on the infrared camera, providing visual evidence of contact. Used together, Snickometer and Hot Spot can determine whether a ball touched the bat, the pad, or both — resolving caught-behind and LBW decisions where the ball's path was ambiguous.

Umpire's Call

Umpire's call is a DRS outcome where the technology shows the decision is too close to overturn — the ball is tracking to hit a portion of the stumps (for LBW) or the audio/thermal evidence is inconclusive (for edges). When umpire's call applies, the on-field umpire's original decision stands regardless of whether the review team believes the technology supports an overturn. If umpire's call applies to a review, the reviewing team does not lose one of their reviews — their review count stays the same, acknowledging that the decision was genuinely marginal.

How Reviews Are Used Tactically

Each team has a limited number of reviews per innings — typically two in Test cricket, one in ODI and T20I. A failed review (where the technology confirms the umpire's original decision) costs the team one review. Teams must be strategic about when to use reviews: saving them for crucial wicket-falling or LBW decisions in the final overs, rather than wasting them on marginal decisions early in the innings. The best batters and captains have developed an instinct for when a review is likely to succeed — assessing in seconds whether the technology will reveal an error in the umpire's call.