Skip to content
PlayGridAll stories
Cricket

DRS and Umpire's Call: A Field Guide to the Review System

The Decision Review System sparks more arguments than it settles, mostly because fans don't know what it's actually designed to do. Here's the logic.

The PlayGrid Desk·Apr 9, 2026·3 min read
DRS and Umpire's Call: A Field Guide to the Review System

No feature of modern cricket generates more confusion, and more furious living-room arguments, than the Decision Review System. Most of the heat comes from a misunderstanding of what DRS is for. It isn't there to make every decision perfect. It's there to erase the obvious mistakes while leaving the on-field umpire in charge.

What DRS actually is

DRS lets teams challenge an umpire's decision a limited number of times per innings. When a player reviews, a third umpire re-examines the call using technology:

  • Ball-tracking to predict the path of the ball for leg-before-wicket (LBW) decisions.
  • Edge detection — audio and thermal-imaging tools — to see whether the ball touched bat or glove.
  • Slow-motion replays for catches, run-outs and no-balls.

Each side gets a set number of unsuccessful reviews. Get a review right and you keep it; waste it on a hopeful punt and you're down one for the innings. That scarcity is the whole game within the game.

The part everyone argues about: Umpire's Call

Here is the concept that causes the most outrage, and it's actually the most sensible part of the system.

For an LBW review, ball-tracking predicts where the ball would have gone. But that prediction isn't perfect — there's a small margin of uncertainty. So the rule says: if the ball is only just clipping the stumps, the original on-field decision stands, whether that was out or not out. That's Umpire's Call.

Umpire's Call isn't the technology being indecisive. It's an honest admission that a prediction with a margin of error shouldn't overturn a human decision when the two barely disagree.

This produces the situation fans hate: two identical-looking deliveries, one given out and one not, purely because the on-field umpire made different original calls. It feels inconsistent. But it's internally consistent — the technology is only allowed to overrule the umpire when it's confident, and "barely clipping" isn't confident.

Why the reviews are limited

People sometimes ask why every close call isn't just checked automatically. The answer is design philosophy. Unlimited reviews would slow the game to a crawl and, more importantly, would shift authority entirely to the video umpire, undermining the person in the middle. By giving teams a small, precious number of challenges, DRS forces a strategic decision — is this the moment to spend one? — and keeps the on-field umpire as the default authority.

That scarcity creates genuine tactical drama. Burning both reviews early on marginal shouts can leave a team defenceless when a genuine howler goes against them later. Good captains treat reviews like a resource to be conserved, not a toy.

How to watch a review like an insider

When a decision goes upstairs, ask three quick questions. Was there a clear edge? Did the ball pitch in line and hit the pad in line? And is it hitting the stumps convincingly, or just clipping? If it's clipping, expect Umpire's Call and expect the original decision to survive. Understand that, and the system stops looking like chaos and starts looking like what it is: a carefully bounded way to fix the mistakes that matter without pretending the game can be officiated to perfection.

#drs#rules#explainer
Share
More stories