
Why captains change bowlers when the over count says they shouldn't
A bowler taking wickets gets pulled off anyway. It looks like a mistake on a scorecard and usually isn't.
It's one of the most second-guessed calls in the sport: a bowler is going well, maybe has just taken a wicket, and the captain still takes them off at the end of the over. From the stands or on a broadcast, it can look like panic or overthinking. Most of the time it's neither.
Bowlers have a maximum overs allocation per innings in every limited-overs format, which means every over bowled early is an over that isn't available later — a captain managing a bowling attack is constantly solving for the whole innings, not just the over in front of them. Using a strike bowler's full allocation too early can leave a captain without their best option during the actual death overs, even if that bowler was performing well earlier on.
Matchups matter just as much as form. A bowler taking wickets against the top order might be a much worse option against the batters coming in next — a fast bowler who's just removed two top-order batters can still be the wrong choice to bowl at a set middle-order hitter who scores freely against pace but struggles against spin. The change that looks like abandoning a good thing is often just the captain switching to the matchup that actually matters for the next phase of the innings.


