How Umpires Make Decisions: The Judgement Process Behind Every Call
The mental and technical process behind umpiring decisions — how on-field umpires judge LBW (trajectory, impact, bat-before-pad), how caught-behind decisions are made from sounds and visual cues, how run-outs are timed, the protocols for consultation between two umpires, and what happens when a DRS review contradicts the on-field decision.
The On-Field Umpire's Information
The on-field umpires make their decisions in real time without the benefit of replay, slow motion, or ball-tracking technology — relying entirely on what they can observe from their standing position at the bowling end (for most calls) or the leg umpire's position at square leg. The umpire at the bowling end is responsible for: LBW decisions, front-foot no-balls, run-outs at the striker's end, caught decisions (for balls hit toward the wicketkeeper or in the air), and calling dead ball. The square-leg umpire assists with: stumpings (they are positioned to see whether the ball has passed the stumps before the keeper removes the bails), run-outs at the non-striker's end, and no-balls when the striker-end umpire is unsighted.
The umpire's judgement on LBW decisions — the most complex call in cricket — requires three simultaneous assessments: was the ball pitched in line (not outside leg stump); did the ball hit the pad before hitting the bat (not bat-before-pad); and would the ball have hit the stumps if the pad had not been there (trajectory assessment). Each of these three checks must be answered 'yes' for the batsman to be given out — and each assessment is made from a single viewing angle in real time at speeds up to 145 km/h.
Caught-Behind: The Sound Cue
Caught-behind decisions — where an edge from the bat is caught by the wicketkeeper — are among the most difficult in cricket because the visual cue (the ball appearing to flick the edge) is often ambiguous at bowling-end umpire viewing angle. Experienced umpires develop a specific skill: listening for the sound of ball-on-bat before making a caught-behind decision. A nick from the bat produces a distinctive sound — different from the sound of ball-on-pad, ball-on-glove, or ball passing the bat without contact. Umpires with high caught-behind accuracy typically rely on the sound cue rather than the visual cue alone.
The most contentious caught-behind situations involve ultra-thin edges — 'feather edges' where the ball barely grazes the outside edge of the bat. These produce virtually no sound and leave no visible mark on the ball or bat. DRS's Snickometer (audio waveform) and UltraEdge (in advanced broadcast setups) can detect these edges from their acoustic signature, which is why on-field umpire Not Out decisions for caught-behind are frequently overturned on review when a Snickometer spike is visible at the moment of ball-bat proximity.
Consultation Between Umpires
The two on-field umpires can consult with each other on difficult decisions — either before making a decision or when genuinely unsure about an aspect of the play. Common consultation scenarios: a run-out where neither umpire had a definitive view of whether the bat grounded before the bails were removed; a caught-at-the-boundary where the fielder may have touched the rope; or a no-ball where the front-foot position was borderline. Consultation is a permitted protocol under the Laws — it is not a sign of weakness but good procedure. The umpires' consultation does not prevent a DRS review of the decision they subsequently make.
Frequently asked questions
Can an umpire change their decision after raising the finger?
Yes — an umpire can revoke a decision before the next ball is bowled. This rarely happens in practice (it requires the umpire to immediately recognise they made an error) but is not prohibited by the Laws. Consulting with the co-umpire and then correcting an out decision to not out (or vice versa) is permitted without a formal DRS review being required. In most practical cases, the DRS review system has replaced informal decision revision — a team would typically review the decision rather than expecting the umpire to self-correct.
How do umpires signal different decisions?
Umpires use a standardised set of signals: index finger raised (out); both hands extended horizontally (no ball); one hand raised (wide, when held to the side); both arms crossed at the waist (dead ball); both hands rotated above the head (six); single hand sweeping across the body (four); arm raised and pointing to the crease (bye); fingers touching the forearm (leg bye); finger pointing to the helmet (penalty runs). These signals are communicated to the scorers, who record them, and are recognised internationally.
What happens if an umpire makes a mistake that DRS cannot correct (e.g., calling a wide)?
DRS only covers four decision types: LBW, caught behind/edge, caught (including boundaries), and run-out/stumping. Other umpiring decisions — wide calls, no-ball calls (except front-foot), fair/unfair play decisions, boundary calls (except relay-catch situations) — cannot be reviewed through DRS. If an umpire incorrectly calls a wide that wasn't wide (or misses a wide), the decision stands. This is a recognised limitation of the current DRS framework, and some cricket administrators have proposed expanding DRS to cover wide calls in the future.