DRS can turn a close moment into a sequence of evidence, signals, and rule checks. This guide explains how the Decision Review System works, what the on-field and third umpires assess, why Umpire’s Call exists, and how to follow a review during a live cricket match without relying on guesswork. Competition regulations can change, so use the checklist near the end to confirm the current procedures for the match you are watching.
Overview
The Decision Review System, usually called DRS, allows a team to challenge certain on-field decisions. The review is not a general replay request. It is a controlled process in which the on-field umpire makes the initial decision, the captain signals a review when permitted, and the third umpire examines the available technology and match evidence.
Reviews most commonly concern dismissals, such as lbw or caught behind, and some decisions involving whether a batter was caught or whether the ball was legal. The exact scope depends on the playing conditions. DRS does not remove the on-field umpire from the decision: the on-field call remains important, particularly when the evidence falls within an accepted margin of uncertainty.
Three ideas explain most DRS outcomes:
- Clear evidence: The technology or replay shows that the original decision should change.
- Decision supported: The available evidence confirms the original decision.
- Umpire’s Call: The evidence sits within the permitted tolerance around a key part of the decision, so the original decision stands.
For viewers following a cricket scorecard or ball-by-ball commentary, the review icon, decision text, and retained-review indicator may appear before the full explanation. They are useful clues, but the final third-umpire report is the authoritative summary for that delivery.
What to track
1. The original decision and the review signal
Start with the on-field call: out or not out, caught or not out, and the relevant mode of dismissal. In an eligible situation, the captain must communicate the team’s decision to review within the time allowed by the playing conditions. Players cannot usually wait indefinitely for additional information, and a review request made after the permitted window may not be accepted.
The on-field umpire then confirms the review and communicates the matter to the third umpire. Broadcast graphics may show whether the review is from the fielding side or batting side, but graphics are presentation tools rather than the rule itself.
2. The first checks by the third umpire
Before analysing the central question, the third umpire may check whether the delivery was legal and whether the relevant event occurred as described. For a catch, that can include the ball carrying cleanly, contact with the ground, and control by the fielder. For a run-out or stumping, the frame-by-frame replay focuses on the position of the bat or body and whether the wicket was broken while the batter was out of their ground.
A no-ball check can be especially important. If the delivery was illegal, the possible dismissal and the value of the outcome may change. This is why a review can involve more than the incident that first attracted attention.
3. Edge detection and replay evidence
For caught-behind questions, the third umpire uses available replays and sound-based edge-detection technology, often shown through a waveform or audio trace. The aim is to establish whether the ball made contact with the bat or glove before reaching the wicketkeeper or another fielder.
Sound alone is not automatically a dismissal. The timing of the sound, the ball’s path, the bat or glove position, and the relevant law all matter. When the evidence is inconclusive, the original decision may remain in place.
4. Ball tracking for lbw
For an lbw review, ball tracking estimates three key parts of the delivery:
- Pitching: Where the ball pitched in relation to the stumps.
- Impact: Where the ball struck the batter, assessed against the applicable lbw conditions and the original decision.
- Wicket: The projected path of the ball after impact and whether it would have hit the stumps.
The projected path is a model based on the recorded delivery. It is not a camera view of an event that happened after the ball hit the batter. This distinction helps explain why a result can include an uncertainty margin rather than a simple yes-or-no statement.
5. Umpire’s Call
Umpire’s Call applies when a ball-tracking result is close to a defined boundary, particularly for impact or projected contact with the stumps. In that situation, the original on-field decision stands. The term does not mean the technology was ignored; it indicates that the evidence did not clear the threshold required to overturn the on-field call.
Umpire’s Call can therefore produce different-looking outcomes for similar deliveries. An original not-out decision may remain not out when the projection is marginal, while an original out decision may also stand in a comparable marginal case. The practical rule for viewers is simple: read the original decision and the tracking result together.
6. Review retention and decision timelines
A review may be retained or lost according to the result and the competition’s regulations. In many modern playing conditions, an unsuccessful review that ends in Umpire’s Call is treated differently from a review overturned by clear evidence, but the exact retention policy should never be assumed across every tournament.
Review requests also operate within a short time limit. The captain must make the signal promptly, and the third umpire works through the available checks in an ordered sequence. Delays can arise when several angles, a no-ball check, or ball tracking are required. A long delay does not by itself indicate that the decision will change.
Cadence and checkpoints
DRS procedures are best monitored at three levels: before a match, during a review, and after a competition changes its playing conditions.
| Format or setting | What to check before following the match | Why it matters |
|---|---|---|
| Test cricket | Review allowance, innings-specific rules, eligible decisions, and time limits | Long matches may use procedures or allowances that differ from limited-overs cricket. |
| ODIs | Team review quota, review reset provisions if any, and the competition’s DRS scope | Limited overs make retained reviews and late-innings decisions especially significant. |
| T20s | Review quota, time window, eligible dismissal types, and any tournament-specific conditions | A short format can make one lost or retained review strategically important. |
| Major competitions | Official playing conditions rather than assumptions based on another league or international series | Domestic and international competitions may use different review protocols or technology labels. |
During a review, follow this order: original decision, question being reviewed, legality of the delivery, relevant replay or detection evidence, ball-tracking result if applicable, final decision, and review status. This sequence prevents a dramatic graphic from replacing the actual logic of the decision.
For broader match context, pair the review with the guide to reading a cricket scorecard and ball-by-ball commentary. If rain interrupts a match after a review-heavy passage, the DLS Method explanation can help separate review decisions from revised-target calculations.
How to interpret changes
A changed decision means the evidence crossed the required threshold; it does not mean the on-field umpire made an unreasonable call. Umpires decide in real time, often without the slow-motion angles or tracking data available to the third umpire.
When a review is retained, ask which part of the process produced that outcome. A review can succeed because the original decision was overturned, or it can remain available under a rule that treats Umpire’s Call differently. When a review is lost, identify whether the decisive issue was pitching, impact, projected contact, an edge, a clean catch, or the legality of the delivery.
Do not treat ball-tracking graphics as a prediction of what would have happened under every possible contact. The system answers a defined rules question using a projected path. Likewise, do not infer a missed edge solely from the absence of a loud sound; camera angle, timing, and the quality of the available evidence matter.
For match analysis, record the context as well as the decision: score, wickets, batter, bowler, innings, review side, and review status. A single decision can affect tactics, but its importance should be judged alongside the match situation rather than isolated from it.
When to revisit
Revisit this guide before a major Test series, international tournament, domestic T20 season, or any competition that has announced revised playing conditions. A monthly or quarterly check is sensible for a live-score site because review quotas, technology terminology, eligible decisions, and decision timelines can be updated by governing bodies or tournament organisers.
Before the first ball, check the competition’s current playing conditions and note the review allowance, time limit, Umpire’s Call treatment, and any format-specific exceptions. During a controversial moment, pause on the official review explanation rather than relying only on social-media clips. After the match, compare the final decision with the scorecard and commentary so that a retained review, no-ball check, or overturned dismissal is recorded accurately.
Use this quick checklist whenever DRS is shown:
- What was the original on-field decision?
- Was the review requested within the permitted time?
- Was the delivery legal?
- Is the question about an edge, catch, run-out, stumping, or lbw?
- Does the evidence clearly overturn the call, support it, or produce Umpire’s Call?
- Was the review retained or lost under this competition’s rules?
That method turns a confusing review into a traceable decision timeline and makes live cricket coverage, highlights, and post-match analysis easier to understand.
