DRS Explained: Umpire's Call, Ball-Tracking, and Why Reviews Get Lost

Nothing in cricket generates more argument than three words on a big screen: umpire’s call.

The Decision Review System has been part of international cricket since 2008, and after nearly two decades a large share of the audience still misreads what it is for. It is not a system for getting every decision right. It is a system for removing the ones that are obviously wrong — and that distinction explains almost every controversy it produces.

What DRS actually consists of

Three separate technologies, used for different questions.

Ball-tracking (Hawk-Eye and equivalents). Multiple high-speed cameras track the ball’s trajectory and project where it would have gone had the pad not been there. Used exclusively for LBW.

Edge detection (UltraEdge, Snickometer). A stump microphone synchronised to super-slow-motion footage. A spike in the audio waveform at the exact frame the ball passes the bat indicates contact. Used for caught-behind and bat-involvement in LBW.

Thermal imaging (Hot Spot). An infrared camera showing friction heat where the ball struck. Used inconsistently — it is expensive, and many boards do not pay for it.

The third-party umpire also has plain high-frame-rate replay for run-outs, stumpings, boundary catches and no-balls, which is a separate process from a team review.

How many reviews you get

In international cricket:

• Tests: three unsuccessful reviews per team per innings, replenished after 80 overs.
• ODIs and T20Is: generally two unsuccessful reviews per team per innings.

The key word is unsuccessful. A successful review — one that overturns the on-field decision — is not deducted. Get it right and you keep it.

Umpire’s call outcomes also retain the review. This is the compensation for the umpire’s call rule and it is more significant than it sounds: a team that reviews a marginal LBW and gets umpire’s call keeps its review, which means the true cost of reviewing a genuinely close decision is zero.

Umpire’s call, properly explained

This is the concept that causes the arguments, so it is worth being precise.

Ball-tracking is a prediction, not a measurement. It knows where the ball was before it hit the pad and models where it would have gone afterward. Like any prediction, it carries a margin of error.

The ICC’s response is to define a zone of uncertainty. For an LBW to be overturned from not out to out, ball-tracking must show:

• More than half the ball pitching in line
• More than half the ball striking in line
• The ball hitting enough of the stumps to clear the margin of error

If the projection shows the ball merely clipping the stumps, the technology is not confident enough to overrule a human being. The on-field decision stands — whatever it was.

This is the part people get wrong: umpire’s call cuts both ways. The identical ball-tracking output produces out if the umpire gave it out, and not out if the umpire gave it not out. That is not a bug. It is the entire design. The system is deferring to the umpire in the zone where it cannot claim to know better.

The alternative — treating a clipping projection as definitive — would mean the technology overturning human decisions on evidence that is, by its own admission, within its error bar.

Why teams lose reviews they should have kept

Three failure modes recur constantly, at every level of the game.

Reviewing on hope with the tail in. A team eight wickets down burns a review on a delivery that pitched outside leg, because the alternative is accepting the innings is over. Understandable, and still a waste.

Deferring to the batter at the striker’s end. The striker has the worst view of an LBW of anyone on the field — they are side-on to their own pad and have no view of where the ball pitched. The non-striker has a far better angle on the line of the delivery. Teams that consistently review well are teams where the non-striker’s opinion carries weight.

The fifteen-second rule. Reviews must be requested within roughly fifteen seconds of the decision. That is not long enough to consult the dressing room, and attempts to look up at the balcony are precisely how sides end up rushing a bad review or missing a good one.

What DRS has actually changed

Its effect on the game is larger and more specific than “fewer mistakes.”

The front-foot no-ball. Third-umpire checks on every dismissal caught a category of error that used to go entirely unnoticed. Wickets are now routinely rescinded for no-balls the on-field umpire missed.

Spin bowling to the pads is viable again. Before ball-tracking, umpires were reluctant to give LBW to a ball pitching outside off and spinning in, because they could not be sure of the trajectory. Hawk-Eye demonstrated that a great many of those deliveries were hitting the stumps. Umpires now give them, and off-spinners bowling into the pads have a mode of dismissal they had effectively lost.

Pad-play is finished. Kicking away a ball outside off stump used to be a low-risk defensive technique. Ball-tracking made it a liability.

Sweeping got riskier. Playing across the line and missing is now much more likely to be given out than it was in 2005.

Where it is not used

DRS costs money — cameras, operators, licensing — and not every board can afford it. It is standard in most international cricket and in major franchise leagues, but it is absent or partial in much of the domestic game and in a good deal of Associate cricket.

That gap matters more than it might appear. A team that plays its home fixtures without ball-tracking and then arrives at a World Cup Qualifier where every decision is reviewable is playing a subtly different sport, and adjusting to it is a real disadvantage on top of every other one those sides carry. It is one of the quieter inequalities in the game, alongside the financial ones we covered in how Associate cricketers earn money.

The honest verdict

DRS was never designed to produce perfect decisions. It was designed to eliminate the howler — the plumb LBW given not out, the thick edge given out, the dismissal that changes a match and that everyone in the ground can see is wrong.

Measured against that goal it has worked, comprehensively. Measured against the goal people imagine it has — that every decision should now be objectively correct — it will keep disappointing, because the technology’s own error bars make that impossible.

Umpire’s call is the honest admission of that limit. It is not the system failing to decide. It is the system declining to pretend it knows something it does not.

More explainers: the DLS method explained · best bowling figures in cricket history · greatest world records in cricket