DRS Explained: Ball-Tracking, UltraEdge and Umpire's Call

How DRS works: when a player wishes to challenge an on-field umpire's decision, they make a T-shape signal with their hands within 15 seconds (the 'review' gesture). The third umpire then examines the relevant technology to determine whether the decision should be overturned. The key DRS technologies: (1) Ball-tracking (HAWKEYE / Hawk-Eye / Virtual Eye): uses multiple cameras positioned around the ground to reconstruct the 3D path of the ball from the moment it leaves the bowler's hand to impact point and beyond. Used for lbw reviews — the system predicts where the ball would have gone if the batsman hadn't been in the way, and whether it would have hit the stumps. (2) Edge detection (UltraEdge / Snickometer): detects whether the ball has nicked the edge of the bat. The Snickometer uses an audio waveform (spike in sound at the moment of contact) correlated with the ball's position relative to the bat. UltraEdge is a more sophisticated version that also uses Hawk-Eye data. Hot Spot uses infrared cameras to detect friction heat from bat-ball contact; however, Hot Spot is not always available at all grounds (it requires specialist equipment). (3) Impact analysis: determines where the ball pitched and where it impacted the batsman — key for establishing whether the ball hit within the relevant zones for lbw.

The Three Lbw Checks'

For an lbw review, the third umpire checks three things in sequence: (1) Pitched outside leg: did the ball pitch outside leg stump? If yes, the batsman cannot be out lbw (Law 36) — even if the ball would have hit the stumps. DRS outcome: if the on-field umpire gave 'out' and the ball pitched outside leg, the decision is overturned. (2) Impact: did the ball hit the batsman in line with the stumps (or at least outside off stump if the batsman was playing a shot)? If the ball impacted outside the line of off stump AND the batsman was playing a shot, they cannot be out lbw. (3) Going on to hit the stumps: would the ball have hit the stumps? Hawk-Eye generates a 3D trajectory prediction — showing what percentage of the predicted ball path would have hit the stumps. The system shows a 'red/green' zone indicating the margin of uncertainty around the prediction. Umpire's call: when the ball-tracking prediction shows the ball clipping the edge of the stumps (within the uncertainty margin), the system returns 'umpire's call' — the on-field umpire's decision stands. If 'out' was given on field and DRS shows 'umpire's call', the batsman remains out. If 'not out' was given on field and DRS shows 'umpire's call', the batsman remains not out. The player's review is NOT lost when 'umpire's call' is returned — because the decision was genuinely uncertain.

DRS Strategy and Team Usage'

Review allocations: in Test cricket, each team starts with 2 reviews per innings. Reviews are lost only if the player's challenge is unsuccessful (the original on-field decision stands after review). Reviews retained after umpire's call returns: the review is NOT lost — only unsuccessful challenges (where the technology clearly shows the on-field umpire was correct) cost a review. Review allocation reset: in Test cricket, reviews reset after 80 overs — each team gets 2 fresh reviews for the next 80-over block. This prevents teams from running out of reviews late in long innings. In ODIs: each team gets 1 review per innings; T20Is: 1 review per innings. DRS strategic use: good DRS strategy involves: (1) never wasting a review on something you're not confident about — if there's no clear edge and the ball looked plumb lbw, save the review. (2) Knowing when NOT to review — if your fielders did not go up for a catch appeal initially, reviewing via DRS while the ball is still live suggests the fielders themselves weren't confident about the edge. (3) Captains sometimes use DRS to 'reset' a partnership — reviewing a close not-out decision mid-morning when reviews will be replenished at the 80-over mark anyway costs nothing in strategic terms. Teams that use their final review without conviction (trying a 'nothing to lose' review in the final over of a Test when reviews won't reset) may waste it and regret it if a genuinely reviewable decision comes up shortly after.

DRS availability: DRS is not universally available. Grounds in Associate Member nations often lack the camera infrastructure required for Hawk-Eye and UltraEdge. The ICC mandates that Full Member bilateral Test series use DRS; however, some series have been played without DRS when one board (historically the BCCI) opted out. India's BCCI resisted DRS for several years (citing concerns about Hawk-Eye accuracy on turning Indian pitches) — India vs England in India was played without DRS until the mid-2010s. DRS vs Hot Spot: Hot Spot (infrared edge detection) is the gold standard for bat-edge detection but requires expensive equipment (2 infrared cameras per end) that is not always deployed. At venues without Hot Spot, UltraEdge (acoustic spike correlation) is used instead. UltraEdge's limitation: it detects sound spikes near the moment of impact, but cannot always distinguish bat-edge contact from pad contact or other nearby sounds (bat hitting pad, bat hitting ground) at the same instant. Contested Hot Spot dismissals: the Ashes 2013 'Hot Spot non-edge controversy' — Australia's Brad Haddin appeared to not get a genuine edge but Hot Spot showed what appeared to be a mark; subsequent analysis was inconclusive. The ICC continues to review DRS technology improvements after each cycle.