Cricket DRS Explained: Reviews, Umpire’s Call, Ball Tracking and Decision Timelines
DRSCricket RulesUmpiringBall TrackingMatch Technology

Cricket DRS Explained: Reviews, Umpire’s Call, Ball Tracking and Decision Timelines

CCricbuzz News Editorial Team
2026-11-17
7 min read

Understand cricket DRS, umpire’s call, ball tracking, review deadlines, retained reviews, and the third umpire’s decision process.

Cricket’s Decision Review System can turn one delivery into a detailed technical examination. This guide explains how a review is requested, what the third umpire checks, why umpire’s call remains important, how review time limits work, and which details to monitor when following a live match.

Overview

The Decision Review System, commonly called DRS, gives teams a controlled opportunity to challenge an on-field decision. It does not replace the on-field umpires. Instead, it allows the third umpire to review available evidence and advise the on-field umpire when the technology clearly supports a change.

A DRS decision normally combines several forms of evidence. Replays can show whether a catch was clean, UltraEdge or another approved edge-detection tool can help establish contact with the bat, and ball-tracking technology can assess the likely path of a delivery for leg before wicket decisions. The precise technology and playing conditions can vary by competition, so the match regulations remain the final reference.

The basic principle is simple: the original decision stands unless the review produces sufficient evidence to overturn it. This is why a review can show that an on-field call was close without changing the result. The most familiar example is umpire’s call on an LBW review.

What to track

1. Whether the decision is reviewable

Teams generally use DRS for significant decisions such as caught behind, catches, LBW, and some run-out or stumping situations. A review is not a general replay request for every delivery. The exact list of reviewable incidents is set by the relevant playing conditions.

Before interpreting a review, identify the original call: out or not out, caught or not caught, LBW or not LBW, and so on. The third umpire is testing that specific decision, not starting the entire passage of play again.

2. The timing of the review request

The fielding captain or batter must request a review promptly after the decision. In many international playing conditions, the teams have a short window, commonly 15 seconds, to signal their choice. The request usually needs to be made before the next ball and must be clearly communicated to the on-field umpire.

A team can discuss the decision briefly, but excessive delay can make a review invalid. Broadcast graphics may show a review being requested, accepted, or sent upstairs, but the umpire’s acknowledgement is the key operational step.

3. The evidence sequence

The third umpire usually works through the relevant evidence in a logical order:

  • Fair delivery: Was the ball legal, including checks for a no-ball where relevant?
  • Contact: Did the ball touch the bat, glove, pad, or another part of the batter first?
  • Edge or catch: If a catch is involved, is there clear evidence of contact and control?
  • Impact: For LBW, did the ball strike the batter within the permitted zone?
  • Ball tracking: If required, would the ball have hit the stumps?

For a caught-behind review, UltraEdge may help identify a spike as the ball passes the bat, but the timing of the sound or signal still has to be assessed alongside video. For a catch, the third umpire considers whether the ball touched the ground and whether the fielder had control under the applicable laws.

4. What umpire’s call means

Umpire’s call is most commonly discussed in LBW reviews. Ball tracking may show that the ball is close to the edge of an allowed impact or projected-stump zone. If the tracking result falls within the defined margin associated with the original on-field decision, the decision remains unchanged.

This does not mean the technology has failed or that the review was pointless. It means the system recognises a zone in which the on-field judgement has priority because the available evidence does not establish a clear error. An original out decision can therefore remain out, while an original not-out decision can remain not out, under umpire’s call.

5. Whether the review is retained

Teams receive a limited number of unsuccessful reviews, with the allowance determined by the competition’s playing conditions. A review that overturns the decision is normally successful. An outcome involving umpire’s call or inconclusive evidence is commonly treated differently from a straightforward failed challenge, but readers should check the rules for the specific match or tournament.

Do not assume that every review shown on television has the same effect on a team’s remaining allowance. The broadcast review counter and the official match communication are useful checkpoints, particularly late in an innings.

6. Not-out decisions

A not-out decision can be reviewed by the fielding side when it believes a dismissal should have been given. The process remains the same: the third umpire looks for clear evidence that the original decision was incorrect. If there is no conclusive evidence, the not-out decision stands.

For a batter’s review of an out decision, the batter must communicate the request through the on-field umpire rather than directly to the third umpire. Teams should also remember that a review cannot normally rescue a decision after the permitted time has expired or the next delivery has begun.

Cadence and checkpoints

Use the following workflow whenever a review occurs during a live match:

  1. Record the original call: Note whether the decision was out or not out and which dismissal was involved.
  2. Check the request: Confirm that the captain or batter requested DRS within the permitted window.
  3. Watch the decision tree: Follow no-ball, bat-pad, edge, impact, and ball-tracking checks in that order where applicable.
  4. Separate evidence from conclusion: A visible spike, a clean catch, or a tracking image is evidence; the third umpire’s final call is the decision.
  5. Update the review count: Check whether the team retained or lost its review under the match regulations.

The broad procedure is similar across formats, but the operational details may differ:

FormatWhat to checkPractical note
Test cricketReview allowance, time limit, and session-specific playing conditionsLong matches make review management and late-innings allowances especially important.
One-day internationalsAvailable reviews, review retention, and tournament regulationsA review can influence a short innings quickly, so the countdown and match situation matter.
T20 cricketCompetition-specific review rules and compressed decision windowsTeams must balance the value of a challenge against the limited time and remaining wickets or balls.

This comparison is a monitoring guide, not a substitute for the official playing conditions. Domestic leagues and franchise tournaments may use different review allowances, technologies, or procedures.

How to interpret changes

The strongest review decisions are not always the most dramatic. A clear UltraEdge spike can settle a caught-behind question, while a faint or badly timed signal may leave the third umpire with insufficient evidence. Similarly, ball tracking is a projection of the delivery’s path, not a recording of an alternate physical reality.

When reviewing an LBW decision, separate three questions: where the ball pitched, where it struck the batter, and whether it would have hit the stumps. A delivery can pass one test and fail another. The original on-field decision becomes especially important when one of these elements reaches an umpire’s-call zone.

Review strategy should also be judged in context. A team may challenge a marginal call because the batter or bowler is a key player, because the innings is nearing its end, or because the review allowance is about to reset under the competition rules. A failed review is not automatically poor captaincy; the quality of the information available at the moment matters.

When to revisit

Revisit this guide whenever a major series, league, or tournament publishes revised playing conditions. A monthly or quarterly check is useful during an active cricket calendar, while a pre-season review is sensible before following an IPL campaign, international tour, or major global event. Pay particular attention to changes in review allowances, review-retention rules, approved technology, terminology, and decision timelines.

During a match, use this article alongside the live score and ball-by-ball commentary. After the review, note the original decision, the evidence shown, the final outcome, and the team’s remaining reviews. That four-part record makes it easier to understand later controversies without relying only on a headline or social-media reaction.

For wider match analysis, pair the DRS record with the confirmed playing XI and squad news, the scorecard, and the relevant pitch report. The practical takeaway is straightforward: identify what was called, follow each technology check, confirm whether the evidence was conclusive, and then verify how the decision affected the team’s remaining reviews.

Related Topics

#DRS#Cricket Rules#Umpiring#Ball Tracking#Match Technology
C

Cricbuzz News Editorial Team

Senior Cricket Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.