Skip to content
Foundation5 min

How Bowling Teams Calculate Wickets Needed to Win

A bowling team's target isn't just restricting runs — it's taking wickets. This article explains how bowling teams think about the wickets they need to win, how wicket probability changes through an innings, and why some overs are more wicket-likely than others.

Written by GeoCric EditorialUpdated Invalid Date
ShareShareWhatsAppFacebook

The Wicket Calculation

In every format, the bowling team needs to take 10 wickets to dismiss a batting innings: in Test cricket, the calculation is spread across potentially 150+ overs (each wicket attempt — each aggressive delivery — must be balanced against the run rate being conceded); in ODI cricket, the calculation is compressed into 50 overs (taking wickets early in the innings restricts the batting team's total — each wicket of a set batsman is worth more than a wicket of a new batsman because the set batsman's future run-scoring is eliminated); and in T20 cricket, 20 overs makes wicket probability even more compressed — a single over that produces 2 wickets completely changes the match equation, while an over without a wicket still has its impact measured in the run rate it conceded. The bowling captain tracks wickets remaining versus overs remaining throughout the innings as a continuous match-state indicator.

Wicket Probability by Innings Stage

Statistical analysis of match data shows that wicket probability is not uniform across an innings: the first 5-10 overs produce the highest wicket probability per delivery (new ball, swinging conditions, batsmen not yet calibrated — the period of maximum bowling-side advantage); the middle overs (15-35 in ODIs) produce the lowest wicket probability (set batsmen, flat ball, predictable field — the batting team's most productive and least risky phase); the final 10-15 overs produce elevated wicket probability again (attacking shots, yorker-length deliveries, fielders on boundaries making run-saving diving attempts — the chaos of death overs produces wickets from misplaced attacking shots); and in Tests, the pre-lunch and pre-tea sessions produce slightly elevated wicket probability due to the batting team's mental adjustment to restart-of-session conditions. Bowling captains use this non-uniform distribution to plan their most aggressive bowling attacks for the periods of highest wicket probability.

Planning Wicket Bursts

Bowling captains specifically plan for 'wicket bursts' — clusters of wickets within a few overs that rapidly shift the match balance: a wicket burst requires the bowling team to maintain their most aggressive configuration even after taking a wicket (a team that celebrates a wicket and then reverts to defensive bowling loses the batting team's vulnerability window, which is typically 5-10 deliveries after a wicket falls when the new batsman is most at risk); the new-batsman risk window is specifically prepared for in training (bowling coaches train bowlers on 'first ball plans' for specific batsmen — the delivery designed to get the incoming batsman before they are settled); and the 'bowling in pairs' tactic (keeping two aggressive bowlers on in consecutive overs to maintain pressure across the wicket-fall period) is specifically designed to extend the wicket burst window rather than losing the advantage through a bowling change.

Australia vs England Ashes 2013-14 wicket burst: The 2013-14 Ashes series produced one of cricket's most famous wicket bursts — Mitchell Johnson's spell at Brisbane where England collapsed from 132/3 to 136/8 (5 wickets in 11 balls) as Johnson's extreme left-arm pace under the Brisbane afternoon conditions produced both genuine difficulty and panic-induced bad shots from England's batsmen. Australia's captain Michael Clarke specifically maintained Johnson's bowling in consecutive overs rather than taking a break — exploiting England's vulnerability window rather than giving them a break to recover. The burst effectively ended England's resistance and produced a result in a match that was otherwise competitive.

Frequently asked questions

What does 'bowling to take wickets' vs 'bowling to restrict runs' mean?

The distinction represents two fundamentally different bowling strategies: bowling to take wickets means deliberately bowling in ways that maximise the probability of dismissal — even if it costs runs; this includes posting slips (reducing outfield coverage), bowling the fuller length that risks being driven for four but also produces edges, and using swing or spin aggressively to create chances rather than boring the batsman out; bowling to restrict runs means prioritising the prevention of boundary and high-scoring shots over the wicket attempt — this includes plugging gaps with outfield fielders, bowling short of a good length to cut off the drive, and using line-and-length to produce dot balls. Most captains blend both strategies across an innings — aggressive wicket-seeking in high-probability phases and restrictive containment in low-probability phases.

Does the bowling team's plan change if a particularly dangerous batsman is at the crease?

Yes — the bowling plan explicitly adjusts for the specific batsman's strengths: against a batsman known to score prolifically through the off side (a drive-dominant player), the captain sets more off-side fielders and instructs bowlers to bowl middle-and-leg stump — removing the drive but potentially opening up on-side scoring zones; against a batsman who averages very high (a quality batsman), the captain may accept lower wicket probability and focus on containment (reducing scoring rate to pressure them into taking risks they wouldn't otherwise take); and against a known weakness — a batsman who struggles against very short-pitched bowling or very full-pitched bowling — the captain may specifically exploit that weakness even if it costs more runs in the short term, because the dismissal probability is worth the cost. This specific-batsman adjustment is called 'setting a plan' and is prepared before the match through video analysis.

How does the bowling team respond when they cannot take wickets?

A bowling team that goes 30+ overs without a wicket in Test cricket faces specific strategic challenges: their bowlers are tiring and the batting team's confidence is building — the 'pressure' element of wicket-probability is reversing (the batting team now has the psychological advantage); the captain must decide whether to accelerate the bowling (throw more aggressive deliveries at the risk of more runs) or maintain containment and wait (hoping the batting team makes an error rather than creating one); and the captain may make a bowling change specifically to introduce a fresh perspective rather than because the new bowler is necessarily better — a new bowler's change of pace, angle, and delivery type provides new information that the batting team must recalibrate to. The 'trying something different' bowling change is a specific strategic acknowledgement that the current approach isn't producing the needed wicket probability.