DRS Review Strategy Explained: When to Review, How Many Reviews Are Left, and the Best and Worst DRS Decisions
Decision Review System (DRS) strategy — each team gets 2 reviews per innings (Tests) or 1 review per innings (ODIs/T20Is). When to review (and when not to): captains must decide in real time. Famous DRS moments: India's initial refusal to use DRS (the 'UDRS' controversy 2009-2012), MS Dhoni's 'not out' T-signal, the worst reviews ever taken, and the review that won the 2019 World Cup Final for England.
The Decision Review System (DRS) gives each team a limited number of reviews per innings to challenge on-field umpire decisions — bringing in technology (Hawk-Eye for LBW trajectory, UltraEdge/Snicko for edges, Hot Spot for contact zones) to assist the third umpire in overturning or confirming the on-field call. DRS strategy — knowing when to review, when to save a review, and how to read the in-match situation — is a significant tactical element of modern Test, ODI, and T20I cricket. Teams that use DRS reviews wisely gain an advantage; teams that waste reviews on hopeless causes are exposed in later tight decisions.
DRS Allocation Per Format
DRS review allocations: (1) Test cricket: each team has 2 unsuccessful reviews per innings. If a review is successful (the umpire's decision is overturned), the review is retained. If unsuccessful (the decision stands, either by clear umpire correctness or 'umpire's call'), the review is lost. With 2 reviews over 90-200 overs, Test teams must be conservative — using reviews for genuine edge or LBW uncertainty rather than hopeful attempts; (2) ODI cricket: each team has 2 unsuccessful reviews per innings (since 2019 ICC ODI Playing Conditions update). Previously, ODIs had 1 review. The expansion to 2 reviews brought ODI DRS usage closer to Test cricket; (3) T20I cricket: each team has 1 unsuccessful review per innings. With only 20 overs per innings, 1 review must be used extremely carefully — often teams defer their review to the death overs when the match is on the line; (4) Successful review retention: when a review succeeds (the decision is overturned), the team retains their review. This means a team can theoretically maintain 2 reviews for the entire innings if both of their reviews succeed. In practice, teams use 1-3 reviews per innings across their run.
DRS Strategy: When to Review
Decision framework for DRS reviews: (1) The batsman's knowledge: a batsman given out LBW knows whether they hit the ball with the bat (if so, not out under LBW laws — the ball must not have hit the bat before the pad for LBW to apply). If the batsman is certain they hit the bat first, reviewing is correct. If genuinely uncertain (an inside edge or bat-pad contact that the batsman cannot feel clearly), review probability is lower; (2) The fielding team's appeal confidence: when the bowling team reviews a not-out decision, the players and captain must quickly assess: did the ball hit the pad in line? Does the trajectory prediction suggest hitting the stumps? Was there an audible edge (not caught by UltraEdge)? Experienced captains (Ricky Ponting, Virat Kohli) develop strong DRS instincts based on their read of the ball's flight; (3) The tactical review: late in a Test innings with wickets needed and few overs remaining, teams sometimes make speculative DRS reviews — hoping for 'umpire's call' luck even when the chance is low. This is accepted as risk management when reviews would expire unused; (4) Never wasting the last review: with 1 review remaining in a Test innings (T20 with 0 reviews, the review is gone), the value of a review rises. Teams should only use their last review for high-confidence decisions — 'near certainties' where technology is expected to confirm an edge or clear LBW.
Famous DRS Moments
Iconic DRS decisions in cricket history: (1) 2019 World Cup Final — England vs New Zealand: in the Super Over after the tied match and tied Super Over, England won on boundary count. But during the Super Over itself: Martin Guptill's run out (and subsequent boundary count) was resolved by DRS technology in confirming the run out. The match's final resolution involved multiple third umpire decisions — though technically the final outcome was the boundary count rule, not a DRS review; (2) MS Dhoni's famous DRS 'saves': Dhoni (India captain, 2008-2017) became known for DRS decisions — whether to review or not. His assessment of whether to use India's review was frequently praised for accuracy in the 2012-2015 period when India adopted provisional DRS in away series; (3) Stuart Broad not out (Ashes 2013): at Trent Bridge, Stuart Broad (England) edged to first slip and was caught — a clear edge by UltraEdge standards. Australia's captain did not review the not-out decision (they had no review remaining). Broad went on to score 65 in a partnership that swung the match. This is the most famous DRS 'non-review' — Australia had failed to review a clear edge because they had exhausted their reviews earlier in the innings; (4) The umpire's call controversy in T20 World Cup 2022: multiple 'umpire's call' LBW decisions in the 2022 T20 World Cup semi-finals caused significant controversy — teams used their single T20 review on LBW decisions that resulted in 'umpire's call' (standing), leading to match-deciding moments being determined by the umpire's original on-field call rather than technology.
Frequently asked questions
How many DRS reviews does each team get?
DRS review allocation by format: Tests — 2 unsuccessful reviews per innings per team; ODIs — 2 unsuccessful reviews per innings per team (since 2019); T20Is — 1 unsuccessful review per innings per team. A successful review (decision overturned) is retained — the team keeps their review count. An unsuccessful review (decision stands, including 'umpire's call') reduces the count by one. In Tests, with 2 reviews over a 90-200 over innings, teams must be selective. In T20Is, 1 review per innings means teams typically save the review for death overs or high-stakes moments.
What was India's objection to DRS?
India's BCCI refused to use DRS in bilateral home series from 2009-2012, with captain MS Dhoni and BCCI officials citing concerns about the accuracy of Hawk-Eye ball-tracking technology. Dhoni specifically questioned whether Hawk-Eye's trajectory prediction (extending the ball's path beyond the point of impact) was reliable enough to override umpire decisions. India also objected on the grounds that the technology was not universally available at all Test venues. The BCCI's refusal created a two-tier DRS system — DRS was used by all other teams but excluded from India home bilateral series. India accepted DRS from 2016 onwards. The BCCI position was partly driven by national board politics and partly by genuine technology skepticism.
Why did Stuart Broad not get given out in the 2013 Ashes?
Stuart Broad (England) was not given out caught at slip off an edge during the 2013 Ashes at Trent Bridge — he clearly edged the ball to first slip but on-field umpire Marais Erasmus did not give it out. Australia had no DRS reviews remaining at that point — they had used both reviews earlier in the innings. Under DRS rules, with no reviews left, Australia could not challenge the decision. Broad batted on, scoring 65 in a partnership that significantly changed the match result in England's favour. The incident became the most famous example of the importance of review management — Australia's earlier unsuccessful reviews meant they could not challenge the crucial Broad not-out.