Tactics
Cricket captaincy explained: the last job with real power
How cricket captaincy works: fields, bowling changes, the declaration, the follow-on, reviews, over rates, the coach relationship and captaincy by format.
By CricketTaken EditorialPublished Tactics20 min read
A cricket captain can move all nine of his fielders between deliveries, change the bowler at the end of every over, decide the innings is finished while his batters are still scoring, and hand the opposition a first-innings deficit or not, entirely as he chooses. Nobody on the field can overrule any of it. The coach is in the dressing room, several hundred metres away, watching on a screen like everybody else.
No other team sport gives one participant that much authority while the game is actually being played. A football captain wins a toss and shouts. A rugby captain chooses between a kick and a scrum. Cricket captaincy explained properly is the story of a job that still carries genuine in-play power at a time when every other sport has moved that power to the touchline.
The power comes with a cost that is rarely stated plainly. Every decision is visible, most of them are reversible only by making another one, and the record keeps score of the outcome rather than the reasoning. A captain who makes eight good decisions and one bad one is remembered for the ninth.
The field is the clearest statement a captain makes
Start with the thing that happens most often and gets explained least. Between every ball, a captain has nine fielders to place, and where he puts them is a public declaration of what he thinks is about to happen.
A field is a distribution of probability made physical. A slip cordon says: this batter will edge before he scores. A sweeper on the cover boundary says: I have decided I would rather concede one than risk four. A short leg says: I think the ball will pop, and I am willing to put a young player in physical danger to catch it.
The constraints are few and they matter. No more than two fielders may be behind square on the leg side, a restriction in the Laws that exists because of a bowling tactic the game decided it did not want. In limited-overs cricket the playing conditions add circles and phase-by-phase caps on how many fielders may be outside them, which is why a Twenty20 field looks nothing like a Test field even when the same captain sets both. The full vocabulary of where those positions sit, and why they have the names they do, is worth knowing before anything else.
Read the two columns as two theories of the same problem. The Test field spends almost everything on the chance of a wicket in the next few overs and accepts that anything past the ring goes for four. The Twenty20 field has given up on the wicket, is protecting the boundary, and is trying to make the batter take two rather than six. Neither is more aggressive. They are aggressive about different things.
The subtler part of field setting is what a captain does when nothing changes. A field left unaltered for six overs tells the batter he has been read correctly and can settle. A field that moves one fielder five yards squarer between deliveries tells him somebody is thinking about him specifically, and it costs nothing. Good captains fidget with purpose.
The most common error is the field that hedges. A ring of fielders half-saving the one and half in catching positions is a field that will neither take a wicket nor stop runs, and it usually means a captain has decided not to decide. A defensive field set honestly is better than an attacking field set nervously, because at least the bowler knows what he is being asked to do.
Which points at the real function. A field is a message to the bowler as much as a trap for the batter. Set three slips and a gully and you have told a fast bowler to bowl full and attack the edge. Push everything back and you have told him you want dot balls. A bowler bowling to a field he does not believe in bowls badly, which is why captains talk to their bowlers before setting rather than after.
Bowling changes, and the bowler who wants one more over
The bowling change is the decision a captain makes most often after the field, and it is the one where his authority collides most directly with another player's judgement.
A fast bowler in the middle of a good spell will always want another over. He can feel the rhythm, he thinks the batter is close to a mistake, and he is not thinking about the two hours after tea. The captain has to think about the two hours after tea, because there is nobody else who will.
The arithmetic is a resource problem with no clean answer. Overs from a fast bowler are finite in a way that overs from a spinner are not. A bowler pushed for two extra overs in the morning may have nothing left by the close, and the wicket that comes at five o'clock is worth exactly the same as the one that would have come at noon. Against that, momentum in cricket is real and short-lived: a bowler who has beaten the bat three times in an over is more likely to take a wicket in the next one than a fresh bowler is in his first.
The judgement is about which of those two facts is operating. And the honest version is that a captain often cannot tell, so he uses proxies. How is the bowler's speed holding up. Has his line drifted. Is he still landing the ball where he was five overs ago, or is the batter suddenly leaving with more comfort. Is he asking for another over because he is bowling well, or because he does not want to be seen to be tired.
The senior bowler complicates this further. A captain telling an experienced strike bowler he is finished for the session is a young captain overruling a man with twice his caps, in front of a crowd, and it has to be done in about four seconds between overs. Handled badly it costs a relationship. Handled by not doing it at all, it costs a Test match on the fifth afternoon when the fast bowlers have nothing left.
Then there is the change nobody wants to make: taking off the bowler who is bowling beautifully and getting nothing, in order to bring on the one who is bowling moderately and might get lucky. Wickets in cricket are not distributed in proportion to quality over short periods, and a captain who only bowls whoever looks best is following a signal with a great deal of noise in it.
Rotation across a day has a shape most captains follow. Short sharp spells with the new ball, longer holding spells in the middle when the ball is old and the batters are set, and then a deliberate reserve kept back for the last hour, when a tiring batting side is at its most vulnerable and a fresh fast bowler is worth twice what he was at two o'clock. In the shortest format the same instinct becomes an over-by-over calculation, and getting it wrong at the back end of a Twenty20 innings is unrecoverable.
Cricket captaincy explained by the declaration, which no other sport has
Here is a decision genuinely unique to cricket: a captain may choose to stop his own team from scoring.
The Laws let the captain declare an innings closed at any time while the ball is dead. There is no minimum score, no required lead, no committee. He can do it after one over or after two days. It is one of the very few provisions in any sport that allows a team to voluntarily give up a resource it is still successfully using.
The reason it exists is that a Test match has two resources and only one of them can be converted into the other. Runs can be accumulated indefinitely. Time cannot. A side that bats until it is bowled out may find it has built an unassailable lead and left itself fifty overs to take twenty wickets, which is worth exactly nothing. The declaration is the mechanism by which a captain converts surplus runs into the time needed to use them.
The trade is unforgiving because both quantities move at once. Every additional over batted adds runs to the lead and subtracts an over from the time available to bowl.
- Lead in runs
- Overs left to bowl
A constructed example with round numbers. The batting side is assumed to score four an over with fifteen overs bowled per hour, starting from a lead of 320 with 130 overs left in the match. No real match, score or result is being described.
Show the numbers
| Item | Lead in runs | Overs left to bowl |
|---|---|---|
| Declare now | 320 | 130 |
| After one more hour | 380 | 115 |
| After two more hours | 440 | 100 |
| After three more hours | 500 | 85 |
Look at what the two lines do. The lead climbs steadily and the overs fall steadily, and somewhere in the middle they cross a threshold that only exists in the captain's head: the point where he believes the lead is already enough. Past that point, every run scored is worthless and every over lost is expensive. The whole skill is in locating a line that nobody can see.
Several things push the answer around. The pitch matters most, because a surface that is deteriorating makes twenty wickets cheaper and lets a captain declare earlier, while a flat one means he needs a bigger cushion and more time. Weather matters, since a forecast of rain on the last day removes overs that have not been lost yet. The strength of the bowling attack matters, because a captain with four bowlers who can run through a side can afford a smaller lead than one relying on part-timers.
And then there is the asymmetry that shapes the behaviour of almost every captain in history. Declaring too early can lose a match that was already won. Declaring too late merely draws one that might have been won. Those two outcomes are not punished equally. A captain who declares and loses is accused of arrogance for the rest of his life; a captain who bats on and draws is described as cautious, which is a much shorter sentence. Rational actors respond to that gradient, which is why declarations across the sport skew late. The individual mechanics of the decision, including the odd cases where a captain declares behind, deserve their own treatment.
There is also a version of the declaration used to buy an entire day, where a captain closes an innings cheaply on a rain-hit fourth morning to manufacture a result out of a match heading nowhere. That requires the opposing captain to co-operate, usually by forfeiting an innings of his own, and it is one of the few moments in professional sport where two opponents openly negotiate the shape of the contest in order to produce a game worth playing.
The follow-on is a right captains increasingly decline
The follow-on is the declaration's mirror image. A side leading by a defined margin after the first innings may require the opposition to bat again immediately, which saves time and stops the leading side batting when it does not need to. The margins are in the Laws and they scale with the length of the match, with 200 runs the figure for a Test of five days or more.
Nothing obliges a captain to use it, and modern captains increasingly do not.
The stated reason is bowler workload, and it is a real one. Enforcing the follow-on means the fast bowlers who have just spent a day and a half in the field go straight back out with no batting innings in between to rest their legs. On a hot ground with a flat pitch, that is a genuinely large ask, and a fast bowler who breaks down in the third innings is unavailable for the fourth, which is when the match is decided.
The second reason is risk elimination, and it is the honest one. A side that bats again cannot lose. It builds a lead so large that no fourth-innings chase is plausible, and it converts a match with three possible results into a match with two. A side that enforces the follow-on has kept the small but real possibility of the opposition batting for two days and then chasing something modest, which has happened often enough to live in every captain's imagination.
The third reason is the pitch. Enforcing the follow-on on a surface that is about to start turning square means bowling the opposition out on the good day and batting last on the bad one. Declining it means the captain takes the good batting conditions for himself and leaves the ruin for the fourth innings.
Against all that sits the argument that keeps the option alive: a side bowled out cheaply once, with its confidence gone and its bowlers idle, is at its most vulnerable in the next hour, and giving it a day and a half off to recover is a strange way to press an advantage. Captains who enforce it are usually captains who trust their attack and think the psychological moment is worth more than the rest. Both positions are defensible, which is why the decision keeps being argued about.
- 200Lead needed to enforce the follow-on
- 2Fielders allowed behind square on the leg side
- 60Seconds allowed between overs under the stop clock
- 1Championship points lost per over short
Rule-defined figures rather than performance statistics. The follow-on margin is the one for a match of five days or more; shorter first-class matches use smaller margins. The stop clock and over-rate penalties are set by the ICC playing conditions and Code of Conduct.
Reviews are a budget, and the captain is the one who spends it
The review changed captaincy more than any other modern addition, because it converted a moment of pure umpiring into a resource management problem the captain owns.
The mechanics are simple enough. When the fielding side wants to challenge a decision, the captain signals, and only the captain. The batting side's review belongs to the batter at the wicket. Each side has a limited number of unsuccessful reviews per innings, and the exact allowance is set by the competition's playing conditions rather than by the Laws, which is why it has changed more than once and differs between formats.
What makes it a captaincy problem is that the captain almost never has the best information. The bowler knows what the ball did. The wicketkeeper has the clearest view of an edge and the best angle on height. The slip fielder heard the noise. The captain, standing at mid-off or mid-on, has the worst seat in the ground and about fifteen seconds to synthesise three excited opinions into a decision.
So the skill is not judging the delivery. It is judging the people. A wicketkeeper who is certain and a bowler who is hopeful are two very different inputs, and a captain who cannot tell them apart burns his allowance in the first hour. Experienced captains develop a hierarchy: the keeper's opinion on an edge outranks everyone, the bowler's opinion on his own delivery is discounted for enthusiasm, and any appeal where nobody sounded convinced at the time is not reviewed regardless of what the replay might show.
The budget produces genuinely interesting decisions later. Reviews do not carry over between innings, so an allowance untouched at the end of an innings has been wasted, which makes speculative reviews late in an innings rational rather than desperate. Meanwhile a captain with one review left and a long batting order still to come has to decline appeals he privately believes in, which is the sort of decision that looks stupid in retrospect exactly half the time. What the system does and does not adjudicate is a subject in itself.
Over rates are a penalty the captain carries personally
Every decision above happens under a clock, and the clock has teeth.
A fielding side must bowl a minimum number of overs in the time available, and falling short is punished. The ICC Code of Conduct sets a fine of five per cent of the match fee for every over a side finishes short, capped at half the fee, and the World Test Championship playing conditions remove a championship point for each over short. Those are not small numbers over a two-year cycle, and they arrive weeks after a match in which nobody noticed the problem happening.
From the 2025-27 championship cycle, Test cricket also carries a stop clock. The fielding side must be ready to bowl the first ball of the next over within sixty seconds of the previous over finishing, and after two warnings in a block of eighty overs, a third offence costs the fielding side five penalty runs. The warnings reset when a new ball becomes available.
Put those together and a captain is managing an invisible resource on top of everything else. Long field-setting conferences cost time. Frequent bowling changes cost time. Extended discussions about whether to review cost time. Bowling spinners is faster than bowling seamers, so a captain behind the clock has an incentive to bowl the wrong bowler at the wrong moment for reasons that have nothing to do with taking wickets.
That is the part worth understanding. Over-rate rules do not merely penalise slowness after the fact, they change the tactical choices being made while the game is in progress. A captain who is four overs behind at tea is a captain whose options have narrowed, and the narrowing happened for administrative reasons. Whether that is a sensible way to run a sport is a genuine argument, and the penalty structure is the place to start it.
- Decide what result is still availableBefore anything else, the captain establishes whether a win is realistically in reach, whether a draw is the ceiling, and whether losing is still possible. Those three answers set the entire frame, and they change with every session.
- Count the overs, not the hoursTime is only useful as overs. The captain works out how many overs remain in the match, subtracts what the change of innings will cost, and treats what is left as the budget for taking ten wickets.
- Estimate what ten wickets costs on this pitchA deteriorating surface with rough outside off stump needs fewer overs than a flat one. This is the largest input and the least measurable, and it is why the same lead can be plenty on one ground and thin on another.
- Decision point, is the lead already enoughIf the opposition cannot realistically chase the current lead, every further run is worth nothing and every further over is expensive. If they can, batting on is still buying something. This is the crossing point the whole decision turns on.
- Check the weather and the lightOvers lost to rain on the last day are overs the captain never gets to spend. A poor forecast pulls the declaration earlier, sometimes dramatically, because a draw becomes the default rather than the fallback.
- Check the state of the bowlersTen wickets have to be taken by people. A captain with two fit fast bowlers needs more overs and a bigger cushion than one with four, and a bowler who has already bowled thirty overs in the match will not deliver what the plan assumes.
- Weigh the two ways of being wrongDeclaring early can lose a won match. Declaring late draws a winnable one. These are punished very differently by everyone watching, which is why most captains err late and know they are doing it.
- Declare, and accept it is now unreviewableThe Laws allow the declaration at any point when the ball is dead, and there is no mechanism to take it back. Everything after this is the opposition's move, and the captain spends the next two days being told what he should have done.
The steps are a decision sequence rather than a formula. The Laws set no minimum score or lead, so every input here is a judgement the captain makes and defends afterwards.
A good Test captain can be a poor Twenty20 captain
The formats look like the same sport and ask for different people.
Test captaincy is a game of accumulation. The captain is building pressure across sessions, and most of what he does produces no visible result on the day it is done. He sets a field that will pay off in an hour, keeps a bowler back for the last session, and spends long periods deciding not to change anything. The core skill is knowing the difference between patience and passivity, and the two look identical from the boundary.
Twenty20 captaincy is a game of allocation under a hard constraint. There are only twenty overs, no more than four from any bowler, fielding restrictions that change at fixed points, and a batting side actively trying to attack specific bowlers. Nearly every decision is a matchup: which of my bowlers is least bad against this batter, right now, given who I have left. The consequence arrives within six balls and it is usually large.
The instincts pull in opposite directions. A Test captain's default is to protect the situation and wait for the mistake, which in a Twenty20 innings means bowling a defensive over to a set batter and losing eighteen runs. A Twenty20 captain's default is to force the issue, which in a Test means attacking fields that leak runs on a flat pitch for two sessions and a bowling attack with nothing left.
Format also changes the volume of decisions. A Test captain makes perhaps a few hundred meaningful choices over five days, most of them reversible. A Twenty20 captain makes a much smaller number of larger ones, all of which are final. Getting one bowling change wrong in a Test is a bad half-hour. Getting one wrong in the eighteenth over is a defeat, and franchise leagues have made that a specialist job, which is one reason the auction market values captaincy the way it does.
The one-day international sits between them and is arguably the hardest of the three, because the middle overs require Test-style patience and the last ten require Twenty20-style aggression, and the captain has to switch between the two without losing his nerve in either direction.
The captain, the coach, and who is actually in charge
Cricket's coaching structure is odd, and the oddness is what preserves the captain's power.
A coach cannot be on the field. He watches from the dressing room or the balcony, and the game does not stop often enough for him to intervene meaningfully. Drinks breaks, the fall of a wicket and the intervals are the only reliable channels, plus whatever a twelfth man carrying gloves can plausibly say on his way past. The result is that the person with the most tactical preparation is systematically unable to apply it at the moment it matters.
This produces the sport's characteristic division of labour. The coach owns preparation, selection input, analysis, training and the parts of the plan that can be decided in advance. The captain owns execution and everything that could not be predicted. When those two things align, nobody notices there is a boundary. When a match goes somewhere neither man anticipated, the captain is on his own with a plan built for a different day.
Limited-overs cricket has narrowed the gap. Frequent breaks in play, formal timeouts written into some competitions' playing conditions, and the sheer volume of pre-match matchup analysis mean a Twenty20 captain is often executing a script rather than writing one. That is a genuine shift in where the authority sits, and it is why franchise cricket sometimes looks more coach-driven than international cricket does.
Test cricket has resisted, mostly because five days generate too many unscripted situations for any amount of preparation to cover. The captain on the fourth afternoon, with a pitch behaving differently from the forecast and two bowlers unavailable, is making it up in a way that has essentially not changed in a century.
There is one more thing the Laws hand to the captain and not the coach. The Preamble makes the captains responsible for ensuring the game is played within the Spirit of Cricket, which is the only place in the entire code where a specific individual is held accountable for the conduct of others. Whatever anyone thinks of that as a legal instrument, it means the captain is the person who has to walk to the umpire when something happens that the rules cover badly. The wider framework he is enforcing sits in the Laws themselves.
What the job costs the player doing it
Cricket captains are playing members of the team, which is unusual for a role with this much responsibility, and the two jobs interfere with each other in ways the sport has never resolved.
A batter who is captain has spent the fielding innings making a hundred small decisions, managing bowlers, watching the clock and absorbing whatever went wrong. He then has to walk out and bat, which requires a completely different mental state: narrow, present, uninterested in anything except the next delivery. Getting from one to the other takes time that the fall of an early wicket does not provide.
A bowler who is captain has the opposite problem. He is the one player who cannot bowl a spell and then switch off, because every over bowled by anybody else still requires his input, and he has to assess his own bowling honestly enough to know when to take himself off. Selecting yourself for one more over is a decision no captain is well placed to make.
The workload extends past the ground. Captains front the press before and after every match, sit in selection discussions, deal with players who have been dropped, and carry the public account of every defeat. That is a substantial amount of cognitive and emotional load spread across a tour, and the player carrying it is expected to keep producing the performances that got him picked in the first place.
Whether captaincy costs form is one of the sport's oldest arguments, and it is not settled, partly because it cannot be. Some players are demonstrably better with the job, because responsibility focuses them and the extra involvement suits the way they think about the game. Others fall away, and the fall is usually blamed on captaincy whether or not it caused it. There is no control group. The same player cannot both captain and not captain the same series, which means every claim about the effect is an inference from a sample of one.
What can be said with confidence is that the sport is aware of the risk and now manages it. Split captaincy across formats, where different players lead in Tests and in white-ball cricket, exists mainly to stop one person carrying all of it. So does the practice of naming a vice-captain who genuinely shares the fielding-innings decisions rather than merely standing next to the captain. Both are responses to a workload the game has decided is too large for one player across a full calendar.
Cricket captaincy explained by watching a captain when nothing is happening
Coverage points its cameras at the ball, which means most of what a captain does is off screen. The interesting parts happen in the gaps.
Watch him between overs. A captain who walks straight to the bowler at the end of every over is either coaching or reassuring, and which one it is usually shows in who talks first. A captain who instead walks towards the wicketkeeper is gathering information rather than giving instructions, and the keeper is the best source on the pitch he has.
Watch what he does after a boundary. The lazy response is to move the fielder the ball went past. The considered response is to leave that fielder alone and change something else, because a batter who has just hit a four through cover is now expecting a fielder at cover, and giving him one confirms his read.
Watch the fielder he moves when nothing has happened at all. Small, unprompted adjustments between deliveries are a captain running a plan several balls ahead, setting up a shot he wants the batter to play. If a fielder moves and two balls later the ball goes exactly there, that was not luck.
Watch him look at the scoreboard clock. Over-rate pressure shows up as a captain hurrying his bowlers between deliveries, cutting conferences short and preferring the quicker bowling option. Once you know it is there, it is visible in almost every long innings.
And watch the last hour before a declaration or a new ball. That is when a captain is doing arithmetic in his head that nobody has told the commentators about, and it is where the difference between captains who are running the match and captains who are reacting to it becomes obvious. The rest of how the game is put together, and the rules that shape every one of these decisions, is collected in the cricket archive.
Common questions
What does a cricket captain actually decide?
Almost everything that happens while the ball is in play. The captain chooses at the toss whether to bat or bowl, sets and moves every fielder, decides which bowler bowls each over and for how long, chooses when to take a new ball, calls for reviews, and in the longer format decides when to declare an innings closed and whether to enforce the follow-on. There is no coach permitted on the field to overrule any of it.
When should a captain declare an innings?
A declaration is a trade between runs and time, and the correct moment is when one more over of batting adds less to the lead than it takes away from the overs available to bowl the opposition out. The Laws let the captain close the innings at any point while the ball is dead, which means the decision is entirely his and there is no formula. Declaring too early risks losing, declaring too late guarantees a draw, and the second mistake is criticised far less than the first.
Why do captains often not enforce the follow-on?
Because enforcing it commits the bowlers to a second consecutive innings in the field with no rest, on a pitch that is usually still good, and modern schedules make fast bowlers a resource a captain is reluctant to spend. Batting again also removes any possibility of losing, which matters more to a captain than the extra time saved by following on. The margin required is set out in the Laws, but nothing in the Laws obliges a captain to use it.
Who decides whether to review a decision in cricket?
The fielding captain decides for the bowling side, and the batter at the wicket decides for the batting side, in both cases within the time allowed after the umpire's decision. The captain will listen to the bowler and the wicketkeeper, who have the best evidence, but the signal has to come from him and the allowance is his to manage across the innings. Umpire referrals for run outs and stumpings are a different procedure that costs the teams nothing.
Why can a good Test captain be a poor T20 captain?
Because the two jobs reward opposite instincts. Test captaincy is about building pressure over hours, holding a plan when nothing is happening and knowing when patience becomes passivity. Twenty20 captaincy is a rapid sequence of resource allocations under fielding restrictions, where a single bad matchup costs twenty runs and there is no time to recover. A captain whose strength is the long game can be genuinely slow at the short one, and the reverse is just as common.
Filed under Cricket·cricket · test cricket · captaincy · tactics · laws