Field Positions Explained: How Fielding Strategy Changes by Match Phase

Watch the field at the 3rd over of a T20 innings and a fielding chart at the 18th over can look like two different sports. Same eleven players, same 30-yard circle, same boundary rope — but almost nothing else in common. Captains aren't just moving bodies around a diagram; they're solving a different equation every few overs, one that shifts with the required run rate, the batter on strike, the number of wickets in hand, and even the size of the ground. At the beginning, you might see slips, a packed ring and fielders waiting for a mistake. By the time the death overs arrive, almost everyone is standing on or near the boundary, with only a few players inside the circle.

The players haven't changed. The pitch hasn't changed. But the purpose of the field has changed completely.

That's one of the most fascinating parts of cricket. Fielding isn't simply about putting eleven players in eleven sensible positions. The captain is constantly making decisions based on the batter, bowler, pitch, match situation, required run rate and the number of wickets remaining.

So, what is actually happening when a captain moves a fielder from point to deep cover, or brings fine leg up?

Let's break it down what to actually look for the next time you're watching a match — or building one out yourself in the Field Visualizer.

The Basic Battle: Save Runs or Take Wickets?

Almost every fielding decision comes down to one basic question:

Are you trying to stop runs, or are you trying to create a wicket?

Of course, captains want both. But you can't always have both.

A fielder inside the circle can cut off singles and put pressure on the batter. A fielder on the boundary can prevent a four, but that extra protection comes at the cost of leaving another area of the field open.

And a catching fielder is an even bigger statement. The captain is essentially saying:

"I'm willing to give up some runs because I think this is where the wicket is going to come."

That balance changes throughout an innings.

Powerplay: When Captains Attack

The Powerplay is one of the most interesting phases of limited-overs cricket because the fielding restrictions force captains to take risks.

In a T20, the first six overs allow only two fielders outside the 30-yard circle. In an ODI, the restrictions work differently across the innings, but the opening phase still gives the batting team an opportunity to exploit gaps in the field.

With fewer fielders available on the boundary, the captain has a choice.

What you'll typically see:

• Slip and/or gully in play for pace bowlers, especially with a new, harder ball that carries more
• Point and cover positioned squarer to cut off the drive, rather than deep to save boundaries
• A single fielder patrolling each straight boundary (long-on/long-off), often the only two fielders back

The reason attacking fields make sense here is simple: the new ball offers the best chance of getting an early wicket, while the fielding restrictions make boundaries harder to prevent anyway.

A wicket in the Powerplay can be hugely valuable.

Get an opener out and suddenly a new batter has to walk in and face a relatively new ball, often with attacking fielders waiting for a mistake.

That's why opening batters are so aggressive during this period. They know the fielding restrictions won't last forever.

The Powerplay is essentially a battle between the batter's freedom to attack and the bowler's opportunity to strike.

Middle Overs: Where Fielding Gets Personal

Once the fielding restrictions ease (overs 7–15 in T20, roughly 11–40 in ODIs), the field spreads out and the game becomes about pressure accumulation rather than single moments. This is where things get really interesting.

In T20 cricket, the middle overs are generally where spinners come into the game and captains start building fields around specific batters. The aim isn't necessarily to produce a wicket every ball. It's about creating pressure.

What you'll typically see:

• Five fielders permitted outside the circle, typically split to cover both straight boundaries and the batter's strongest hitting arc
• Spinners introduced, often with a deep point/deep square leg pair specifically set for the sweep and slog-sweep
• A "save-one" field — fielders positioned to turn a certain boundary into a single, rather than trying to stop the single itself

A right-hander who loves hitting through mid-wicket may see a deep mid-wicket, deep square leg and long-on protecting the leg side. A batter who scores heavily through cover might find an extra fielder protecting that region.

Sometimes the captain isn't even trying to stop the single. They're trying to stop the boundary. That's where the idea of a "save one" field becomes important.

If a batter can still take a single but can't turn that shot into four, the fielding side may consider that a win. One run isn't necessarily a problem. Four runs are the actual problems if 5 singles and one boundary come, it becomes 9 runs in that over.

And when several dot balls are mixed with those singles, the pressure begins to build. Eventually, the batter may feel compelled to play a shot that isn't really there.

That's when the field does its real work. It doesn't always take the wicket.

Sometimes it simply creates the conditions for the wicket to happen.

The Batter Matters More Than the Diagram

One of the biggest mistakes people make when looking at cricket fielding is assuming that a captain is using a fixed template. They're not. The field depends heavily on who's batting.

Imagine two right-handed batters facing the same spinner. The first batter is excellent against the sweep and slog-sweep. The second prefers hitting straight and through cover. The captain shouldn't necessarily use the same field for both.

• Against the first batter, you might see protection deep on the leg side.
• Against the second, the field could shift towards cover, long-off and the straight boundary.

The bowler matters too.

A spinner who gets significant turn may encourage a completely different field from a fast bowler who is attacking the stumps.

This is why experienced viewers can learn a lot simply by watching where the captain moves the fielders before the ball is bowled. The field often tells you what the bowling side expects the batter to do.

Death Overs: You Can't Stop Everything

In the final overs (16–20 in T20, 41–50 in ODIs), fielding restrictions are fully lifted, and the calculus flips entirely. At this stage, the batting team is looking for boundaries almost every ball. As the fielding restrictions are largely gone, so the captain can put most of the team on the boundary.

But that doesn't mean the captain can simply cover every possible shot. There aren't enough fielders. The job is now damage control.

A captain studies the batter and asks:

• Where is this player most likely to hit?
• What shot is the bowler trying to prevent?
• Which boundary is bigger?
• Where is the mis-hit most likely to go?

What you'll typically see:

• All or nearly all fielders on the boundary, often set specifically to the batter's known hitting zones based on pre-match data
• A short third man or fine leg brought up if the batter has shown a tendency to miscue the scoop or ramp
• Bowlers targeting yorkers and wide slower balls specifically because the field is set to cover length-ball hitting areas — the field and the bowling plan are designed together, not separately

Death-overs fields are frequently built off analytics — a specific batter's scoring heat map against a specific bowling style — rather than general cricketing principles. It's also why a genuinely world-class death bowler (someone who can consistently hit a yorker under pressure) is so much more valuable than raw pace: the field can only do its job if the ball actually arrives where it's supposed to.

A fast bowler who can't control their length can actually make a carefully constructed field irrelevant. But a bowler who consistently hits their intended areas gives the fielding captain a much better chance of controlling the damage.

At this stage, a boundary isn't necessarily a failure. If the field prevents a six and turns a potentially huge shot into a two or four, the field has done its job.

Test Cricket: A Different Sport Entirely

It's worth a quick note on the longer format, because Test cricket doesn't have phases in the same rate-driven sense — but it has something arguably more interesting: fields built around dismissal patterns rather than run-rate.

A Test captain might crowd the leg side for hours to induce one specific mode of dismissal against one specific batter, sacrificing containment completely because time, not overs, is the resource being spent. Slip cordons expand or contract not by over number but by pitch conditions, ball age, and how many overs are left in the day. It's the clearest illustration of the run-prevention-vs-wicket-taking trade-off, just stretched across a much longer canvas.

The captain isn't necessarily asking:

"How do I stop the next boundary?"

Instead, the question may be:

"How do I get this batter out?"

That's a completely different mindset.

In Test cricket, the age of the ball, pitch conditions, time remaining in the day and the batter's weaknesses can all influence the field. The game moves more slowly, but the strategic battle can be even deeper.

Why This Matters Beyond Just Watching

Understanding field-by-phase logic changes how you watch a game. Instead of seeing "a field," you start seeing a decision — a captain reading the required rate, the specific batter, the pitch, and the bowler's skillset, then picking a side of the containment/wicket-taking trade-off. The next time a captain brings a fielder up from the boundary in the 14th over, or crowds the off side for a left-arm spinner, it's worth asking: which side of that trade-off are they betting on, and why now?

You can build out any of these fields yourself — Powerplay, middle-overs, or death — using the Field Visualizer, and compare how a single change in fielder position shifts the balance between the two.

Try the GameOnField Field Visualizer