DRS Review Strategy for Batsmen: When and Why to Review
Every batsman has access to team reviews under the DRS system — and the decision of when to use or preserve a review is one of modern cricket's most consequential in-game choices. This article explains how batsmen make review decisions and what happens when reviews run out.
How the DRS Review Works for Batsmen
The Decision Review System (DRS) allows each team a limited number of reviews per innings — typically 2 in Test cricket, 1 in ODIs, and 1 in T20Is: when a batsman disagrees with an on-field umpire's decision (most commonly an LBW out decision or a caught-behind decision when the batsman believes they didn't hit the ball), they can request a review within 15 seconds of the decision; the team captain or the batsman at the crease can call the review (specific rules vary by ICC format — in some formats only the dismissed batsman can call the review); the third umpire then examines available technology (ball-tracking for LBW, Hot Spot or Snickometer for edge detection) and either upholds or overturns the on-field decision; and if the review is unsuccessful (the original decision is upheld), the team loses one review — successful reviews retain the review count.
Batsman Decision-Making Under DRS
The batsman's review decision must be made in 15 seconds — a very short time for what can be a complex assessment: the batsman must assess the LBW probability (did the ball hit the pad in line with the stumps? was it pitching in line? would the ball have hit the stumps?); the edge probability for caught-behind decisions (did they hit the ball? was the deviation after the ball passed the bat genuine edge or pad?); and whether a review is worth using (if the batsman is 90% sure the umpire's decision was wrong, reviewing is clearly correct; if only 60% sure, preserving the review for a higher-probability situation may be better). Batsmen who are genuinely uncertain tend to look to their batting partner for a reaction — a partner who clearly didn't hear an edge is strong evidence that no edge occurred, while a partner who grimaces suggests the edge was audible.
The Consequences of Running Out of Reviews
When a batting team uses both reviews unsuccessfully, they have no further recourse: incorrect on-field decisions stand for the remainder of the innings; batsmen who are 'out but not out' (umpire errors that go against them) have no mechanism to challenge; and the batting team must absorb the psychological impact of knowing a potentially incorrect decision cannot be appealed. The strategic importance of preserving reviews is most acute late in a close Test innings — a batting team on their last wicket with no reviews remaining is particularly vulnerable to on-field LBW errors because there is no challenge option. Teams specifically coach batsmen to be conservative in review usage early in an innings (when the full 15-second window allows for deliberate assessment) and to preserve reviews for situations where the confidence in the challenge is very high.
Frequently asked questions
Can the batting partner influence the review decision?
Yes — the non-facing batting partner has a specific role in DRS decisions: they are positioned at the non-striker's end and may have a clearer view of whether the ball hit the bat (for edge-related reviews) or whether the LBW trajectory was in line with the stumps; the batting partner can indicate their assessment through gesture or communication with the dismissed batsman; but only the dismissed batsman (in some format-specific rules) or the team captain can formally call the review — the batting partner's input is advisory. In practice, a batting partner who urgently signals 'yes review' or 'no don't review' carries significant weight because they often have a clearer viewing angle for the key element of the decision. Teams who communicate well about DRS decisions (established batting partnerships with good DRS communication) preserve their reviews more efficiently than newly-formed pairs.
What does 'umpire's call' mean and why does it matter for reviews?
Umpire's call is a DRS category specifically applied to marginal decisions: in LBW reviews, the ball-tracking technology identifies whether the predicted trajectory of the ball would hit the stumps; if the ball is shown to be hitting the stumps, the batsman is out; if the ball is shown to miss the stumps, the batsman is not out; but if the ball's trajectory is 'on the edge' — the ball's predicted path is partially hitting a stump but not clearly fully hitting or fully missing — the decision is 'umpire's call'; in umpire's call situations, the original on-field decision is upheld regardless of the technology's marginal result; and the reviewing team retains their review even when umpire's call is the verdict — the review is not wasted when the technology is inconclusive. Umpire's call ensures that marginally incorrect ball-tracking predictions don't override on-field umpires when the technology's uncertainty margin is larger than the wicket's size.
Are there situations where it is clearly right to use a review even with only one remaining?
Yes — specific situations make review usage clearly correct: a batsman who knows with very high confidence (90%+) that the on-field decision was wrong should always review (preserving the review to use later when the decision might be less certain is inefficient — using the high-confidence review now may save the batsman's wicket, which is more valuable than any future review); when a key batsman is dismissed by an on-field decision at a critical match moment (a key batsman at the crease in a close chase being wrongly given out LBW should always be reviewed if the team still has a review); and when the ball-tracking camera coverage is available and the ball appears clearly outside the stumps (the technology provides a definitive answer for clearly-missed balls). The only time to preserve the review is when confidence in the challenge is moderate (60-70%) and a later, higher-confidence challenge is reasonably anticipated.