The Decision Review System: what actually changed and what didn't
DRS gets blamed for almost every controversial dismissal, but most of the real controversy sits in one specific rule: umpire's call. Here's how the system is built and where its edges are.
Three technologies, one decision
A DRS review combines three separate readings: ball-tracking (a camera-array system that projects the delivery's likely path past the point of impact), edge detection (audio/thermal tools used to judge bat-pad or bat-ball contact), and standard slow-motion replay for run-outs and stumpings. For an LBW review specifically, ball-tracking has to clear three checks in sequence — where the ball pitched, where it struck the batter, and whether enough of it was hitting the stumps — before an on-field "not out" can be overturned to "out," or vice versa.
Where "umpire's call" comes from
Every ball-tracking prediction carries a margin of error, because it's a projection past the point of impact, not a measurement. To account for that, the system defines a buffer zone around the stumps and the batter's front pad. If the projected path falls inside that buffer — close enough that the technology can't be fully certain — the on-field umpire's original decision stands, win or lose, as "umpire's call."
This is the single biggest source of DRS controversy, and it's a rule, not a technology failure. Viewers see a graphic showing the ball clipping the stumps and assume "clipping counts," but the system is deliberately built to defer to the human decision inside that margin rather than treat a marginal projection as gospel.
Review allocations differ by format
Test cricket allows each side two unsuccessful reviews per innings; ODIs and T20Is allow one. The asymmetry reflects how much time is available to review the decision on the field, and how much a wrongly burnt review can cost a side across a much shorter run of overs.


