Understanding the Decision Review System makes a live cricket match easier to follow when an appeal becomes controversial. This guide explains how a review is requested, what ball tracking and edge detection can show, why umpire’s call exists, how reviews are retained or lost, and which rules to check across Tests, ODIs, and T20s.
Overview
The Decision Review System, usually called DRS, allows a team to challenge certain on-field decisions. It does not give players unlimited opportunities to question an umpire. Reviews are controlled by format-specific playing conditions, are available only for eligible decisions, and must normally be requested within a short time after the decision.
A review is assessed by the third umpire, who may use available technology such as video replays, edge detection, and ball-tracking graphics. The third umpire then advises the on-field umpire, who announces the final decision. The review process is designed to correct clear errors while preserving the authority of the on-field officials.
DRS is most commonly discussed after an lbw decision, a caught-behind appeal, or a disputed catch. However, not every part of an incident can be reviewed in the same way. Technology may be able to answer whether the ball hit the bat, but it may not remove every uncertainty about the ball’s future path or the precise point of impact.
What to track
The review workflow
- On-field decision: The umpire gives a decision, such as out or not out. A team can consider whether the decision is important enough to challenge.
- Captain signals for a review: The fielding captain usually signals for a review when challenging a batter’s dismissal appeal. A batter may request a review when given out. Players must do so within the permitted time and in the manner set by the playing conditions.
- Third umpire checks the incident: The review begins with available video and technology. The third umpire may first establish whether the delivery was legal and whether the relevant event occurred before moving to the main decision.
- Evidence is assessed: Replays, edge detection, and ball tracking are considered where relevant. The evidence must meet the standard required by the competition’s review protocol.
- Decision is communicated: The third umpire recommends whether the original decision should stand, be changed, or be cancelled. The on-field umpire then confirms the result.
Technology and decision areas
Ball tracking reconstructs the ball’s projected path after pitching. For an lbw review, analysts generally consider where the ball pitched, whether it struck the batter in line with the stumps, and whether it would have hit the stumps. The system is a prediction based on recorded data and modelling; it is not a view of a ball continuing through the batter.
Edge detection, including systems commonly referred to as UltraEdge, compares audio and video around the moment the ball passes the bat or glove. A spike can support the conclusion that contact occurred, but the third umpire still considers timing, bat movement, and the relevant laws.
Impact zone describes where the ball struck the batter in relation to the stumps. This matters mainly in lbw reviews. A projected trajectory may be decisive, may support the original decision, or may leave the call within the permitted margin of uncertainty.
Umpire’s call applies when the available ball-tracking evidence falls within a defined margin on a key lbw element. In that situation, the original on-field decision remains in place. This is why a review can show a marginal projected result without overturning the umpire’s call. It is not the same as the technology declaring that the batter was definitely out or definitely not out; it recognises the limits of the evidence and the benefit of the original decision.
Comparison of review rules and evidence
| Area | What to understand |
|---|---|
| Review limits | Each format and competition sets a permitted number of unsuccessful reviews per innings or other playing period. International Tests commonly use a different allowance from limited-overs cricket, while domestic and franchise competitions may set their own conditions. Check the match regulations before relying on a number. |
| Reviewable decisions | Reviews generally cover dismissal decisions and certain related incidents, subject to the competition’s protocol. Not every on-field call can be challenged. |
| Ball tracking | Used mainly for lbw questions to assess pitching, impact, and projected contact with the stumps. |
| Edge detection | Uses replay and sound evidence to assess whether the ball touched the bat or glove before reaching the wicketkeeper or fielder. |
| Impact zones | The location of contact between ball and batter is considered against the stumps and the requirements of the lbw law. |
| Umpire’s call | A marginal tracking result may leave the original decision unchanged. The review is commonly retained in this situation, but the exact treatment should be confirmed in the applicable regulations. |
| Retained reviews | A successful review is normally retained. A review involving umpire’s call is also commonly treated differently from a fully unsuccessful challenge. Competition rules determine the precise accounting. |
| Tests, ODIs, and T20s | Review allowances, timing, technology availability, and special conditions can differ. Use the official playing conditions for the specific match rather than assuming every format or league follows the same framework. |
Cadence and checkpoints
During a live cricket match, monitor the review count shown on the broadcast or score overlay, but treat it as a guide rather than the sole authority. A scorecard or match centre may distinguish between reviews lost, reviews retained, and reviews affected by umpire’s call. If the display is unclear, the competition’s official match information is the safer reference.
At the start of a series or tournament, check four items: the number of reviews available, whether unsuccessful reviews are charged in the same way across innings, which technologies are in use, and whether special playing conditions apply. These checks matter particularly when moving between a Test match, an ODI, a T20 international, and a domestic T20 league.
For post-match analysis, record the original decision, the reason for the review, the evidence shown, and whether the review was retained. This produces a more useful review of captaincy than simply counting successful challenges. A captain may make a reasonable review that fails because the evidence supports the umpire’s original decision.
How to interpret changes
A review result should be read in stages. First ask what the original decision was. Next identify the specific question: bat or pad, legal delivery or no-ball, catch carried cleanly or not, or projected path of the ball. Then separate evidence from interpretation. A visible mark on a replay may settle contact, while ball tracking may still leave an lbw element within umpire’s call.
Do not treat a retained review as proof that the team was correct about the entire appeal. Retention can reflect the rules governing marginal evidence rather than a completely successful challenge. Similarly, a lost review does not automatically mean the captain acted irresponsibly. The quality of a decision depends on the match situation, the batter involved, the wicket’s value, and how much reliable information was available at the time.
For a fuller match assessment, connect DRS decisions with the scorecard: the over, score, batter, bowler, field setting, and remaining reviews. You can then judge whether a team preserved its reviews for high-value moments or used them on low-confidence appeals. This approach complements a cricket scorecard review and a broader post-match analysis workflow.
When to revisit
Revisit this guide before a major tournament, at the beginning of a new season, and whenever a competition publishes revised playing conditions. Review allowances, technology terminology, review timing, and the treatment of marginal decisions can change between competitions. A rule that applies in an international match may not apply identically in a franchise league.
Before the next match, open the fixture or match centre and check the format, competition regulations, review allowance, and available technology. During play, note each review and its outcome. After the match, compare the broadcast explanation with the official scorecard and record any unfamiliar terminology. This simple routine will help you interpret the next controversial decision without relying on assumptions carried over from another format.
For related context, compare DRS decisions with format-specific player statistics, venue information from the pitch and venue checklist, and the match schedule in the fixtures guide. Always confirm the latest competition-specific rules before treating a review count or decision outcome as definitive.