The Bowler's End Umpire: Responsibilities, Signals, and Decision-Making
The bowler's end umpire — also called the 'striker's end umpire' — stands at the end from which the ball is bowled, positioned behind the bowling crease to one side of the stumps. This umpire has the primary responsibility for decisions requiring the closest view of the delivery: no-ball calls, wide-ball calls, LBW decisions, bowled/hit wicket dismissals, run-out decisions at the bowler's end, and counting the balls per over. The bowler's end umpire's positioning and decision-making framework is governed by the Laws of Cricket and is one of the most demanding officiating roles in any sport.
The bowler's end umpire's position and why it matters: the bowler's end umpire stands 2-3 metres behind the bowling crease, to the side of the stumps opposite the side from which the bowler runs in (if the bowler runs in from the left side of the crease, the umpire stands to the right, and vice versa). This positioning allows the umpire to: (1) Watch the bowler's action and delivery point: the umpire must observe the bowler's front foot landing position to determine no-ball (front foot crossing or landing on the batting crease, ahead of the popping crease). This is done by peripheral vision — the umpire watches the batsman and the ball but simultaneously tracks the bowler's front foot. From 2016 onward, ball-tracking technology (DRS) provides TV-based front-foot no-ball checking as a support tool. (2) Judge the ball's legality: the umpire must determine whether each delivery is a legitimate ball, a wide (outside the wide-ball crease), a no-ball (front foot overstepping, ball above waist height when the batsman is in batting stance, ball bouncing more than twice, etc.). (3) Make LBW decisions: LBW requires the umpire to assess three simultaneous criteria — (a) did the ball pitch in line with the stumps (or outside off without leg-spin), (b) did the ball make contact with the batsman's pad on the leg side of the stumps, and (c) would the ball have hit the stumps if the pad was not there? All three criteria must be satisfied. The bowler's end umpire is the primary LBW decision-maker — the square leg umpire is not positioned to make LBW calls. (4) Counting balls: the umpire tracks each legal delivery and calls 'over' when 6 legal deliveries have been bowled. Wide balls and no-balls do not count — an over can contain 8-10 actual deliveries if wides and no-balls are bowled. Umpires use counters (small counters held in the hand, one moved between hands per ball) or pebbles/coins moved from pocket to pocket to maintain the count. Losing count of the number of balls in an over has occurred at Test level — the most famous being the 7-ball over bowled in the 2001 Ashes at Headingley when umpire Steve Bucknor miscounted.
The No-Ball Judgment — Peripheral Vision Challenge
Why front-foot no-ball detection is one of umpiring's most difficult tasks: the bowler's end umpire must watch the batsman's body position, the ball's delivery point, and the bowler's front foot simultaneously — but these three elements are in significantly different visual fields. The challenge: (1) The ball is released at the bowler's arm height (2-3 metres above ground). (2) The front foot lands at ground level, approximately 6-8 metres in front of the batsman. (3) The batsman is at the umpire's eye level, 20 metres away. To observe all three simultaneously requires a peripheral vision strategy that takes years to develop: most senior umpires report watching the ball from the bowler's hand release through to the batsman (primary focus), while using peripheral vision to track the front foot's landing — listening for the 'thud' of the front foot's landing as an additional cue. Research on umpire performance shows that front-foot no-ball detection rates are significantly lower than 100% even for elite on-field umpires — particularly for bowlers with deceptive actions where the front foot landing is disguised or subtle. ICC's DRS intervention from 2016 onward specifically addressed this limitation: TV cameras track the front foot automatically and notify the third umpire if an overstepping occurs. The third umpire communicates with the on-field umpire via earpiece — and the on-field umpire calls the no-ball accordingly. This DRS front-foot check does not apply at all levels of cricket, only in matches with the full DRS technology package.
Signals and Communication
How the bowler's end umpire signals decisions and communicates with the square leg umpire: the bowler's end umpire is responsible for the primary official signals for: (1) Out (index finger raised): used for all modes of dismissal that the bowler's end umpire has adjudicated — LBW, bowled, caught (confirmed after consultation with the square leg umpire if needed), hit wicket, and run-out at the bowler's end. (2) Wide ball (arms extended horizontally): signalled after a delivery that is outside the defined wide-ball crease (in Tests: outside the off-stump crease or behind the leg stump line for balls down the leg side). In T20, the wide crease is defined more strictly than in Tests. (3) No-ball (arm extended horizontally with hand open, palm down): signalled for any delivery that is illegal under Law 21. (4) Over (wave of the hand): signals the end of the over after the 6th legal delivery. (5) Dead ball (both hands extended downward): signals that the ball has become dead due to a specific event (e.g., the bowler breaking the wicket before delivery, the ball lodging in the batsman's clothing). Communication with the square leg umpire: for potential run-out decisions at the striker's end (batsman run out while taking a run to the bowler's end), the square leg umpire has the closer view and typically adjudicates. If there is doubt (both umpires unsure), consultation between umpires is permitted before the signal. For DRS match conditions, the third umpire communicates via earpiece during reviews.
Frequently asked questions
What is the bowler's end umpire responsible for in cricket?
The bowler's end umpire (standing behind the bowling crease) has primary responsibility for: (1) No-ball calls — front foot overstepping, waist-height full tosses, balls bouncing more than twice, etc. (2) Wide-ball calls — deliveries outside the defined wide crease. (3) LBW decisions — requiring simultaneous assessment of pitch line, pad line, and stump-line trajectory. (4) Bowled and hit-wicket decisions. (5) Run-out decisions at the bowler's end. (6) Counting balls per over — calling 'over' after 6 legal deliveries. The bowler's end umpire makes the primary decisions for all these events; the square leg umpire primarily handles run-outs at the striker's end and provides additional perspective on catches.
Why is it so difficult to call no-balls in cricket?
Front-foot no-ball detection requires the umpire to simultaneously watch the ball from the bowler's hand (at arm height, ~2.5m above ground) while tracking the bowler's front foot (at ground level, 8m away) and monitoring the batsman's position. These three visual elements are in different vertical and horizontal positions — no single focal point captures all three. Elite umpires use a peripheral vision strategy (focusing on ball-to-batsman path while detecting front foot via peripheral vision and sound cues) but accuracy is below 100% even for experienced international umpires. DRS front-foot checking (introduced from 2016) uses TV camera tracking to supplement on-field umpire judgment in matches with full DRS technology.
How do umpires keep track of balls in an over?
Bowler's end umpires use physical counting devices to track balls per over: the most common method is holding 6-8 small objects (stones, coins, or purpose-made plastic counters) and moving one between hands per legal delivery — after 6 objects have been moved, the over is complete. Wides and no-balls do not count toward the 6 — the counter is not moved for non-legal deliveries. Umpires also develop an intuitive sense of over length, but physical counters are used as the primary record to prevent miscounts. Historically, 7-ball and even 8-ball overs have occurred at Test level due to counter mismanagement — now extremely rare due to better training and the availability of technology assistance.
What is 'umpire's call' in DRS for LBW decisions?
In DRS LBW reviews, 'umpire's call' is applied when ball-tracking technology shows the ball clipping the edge of the stumps within a defined margin of uncertainty — the outer edge of the ball passing within a specific pixel zone of the stumps. In this 'marginal' zone, the original umpire's decision stands regardless of the DRS ball-tracking projection. The rationale: both the umpire's judgment and the ball-tracking projection have inherent uncertainties at the margins; when the ball-tracking is in the marginal zone, it cannot definitively overturn an umpire's judgment. The consequence: a batsman can be given 'out LBW' by the umpire with the DRS confirming 'umpire's call' (ball clipping the stumps marginally) — the decision stands as out even though DRS does not definitively confirm it would have hit.