What DRS is for
The Decision Review System exists to correct clear on-field umpiring errors, not to give a second opinion on every close call. Each team gets a limited number of unsuccessful reviews per innings, which is why captains are cautious about using one on a decision that is only mildly doubtful.
The technology behind it
Three tools do most of the work. Ball-tracking software predicts the path a ball would have taken after hitting the batter's pad, used mainly for leg-before-wicket decisions. UltraEdge, an audio-based system, picks up the faint sound of bat or glove touching the ball, which is often invisible to the naked eye at full speed. Slow-motion replays from multiple camera angles handle everything else — whether a catch carried, whether the bat was grounded, whether the ball touched the boundary rope.
Why "umpire's call" exists
When a review is about leg-before-wicket, the ball-tracking prediction is checked against two thresholds: whether the ball was hitting the stumps clearly, and whether the point of impact was close enough to the edge of the zone that reasonable umpires could disagree. If the tracking shows the ball only just clipping the stumps, the on-field umpire's original decision stands — this is called umpire's call. It exists because ball-tracking is a prediction, not a certainty, and the system is built to trust the human umpire when the margin is genuinely too fine to call.
Why a review can still fail
A review fails, meaning the team loses that review, whenever the technology supports the original on-field decision — including every umpire's call outcome. This is why teams sometimes look certain to succeed on television replays and still lose the review: the difference between "probably out" and "out beyond reasonable doubt" is exactly the gap DRS is built to respect.
How many reviews a team gets
In most formats, each side is allowed a fixed number of unsuccessful reviews per innings, commonly two in Test cricket. A review is only deducted if it is unsuccessful — a correct review does not use up the team's count, which is why sides sometimes review more often than the raw number would suggest.
The bigger picture
DRS was never meant to make cricket officiating perfect. It was built to remove the small number of decisions that technology can prove wrong beyond reasonable doubt, while leaving the genuinely marginal calls with the umpire, exactly where the system's designers intended them to stay.
The players making those close calls are themselves shaped by decisions made well before a ball is bowled — see how IPL player auctions build the squads in the first place. For more, browse our full Cricket section.
