Field placement is where captaincy meets tactics. A well-set field can restrict runs, create dot balls, and force wickets in critical moments.
Powerplay Field
The first six overs in a T20 innings carry the highest strategic weight — only 2 fielders are permitted outside the 30-yard circle. How those fielders are positioned determines whether the batting side can build momentum or is forced into early consolidation. We typically see these standard configurations in the powerplay:
- Cover point + backward point — close off drives through the off side
- Third man + fine leg — cover the glance and the edge
- Forward short leg + backward square leg — catching positions for short-pitched bowling
- Mid-off + mid-on — contain straight-batted boundary shots
- Long-on + long-off — boundary riders for the big over
Middle Overs (7-15)
The fielding restrictions relax once the powerplay ends — up to 5 fielders can now be placed outside the 30-yard circle. This is the phase where smart captains make the biggest impact. We observe three distinct strategic modes used by top T20 teams during the middle overs:
- 3-4 catchers in the inner circle — maximise the chance of a run-out or miscued shot being held
- Deep boundary riders saved for high-risk zones — prevent the six while accepting singles
- Choke pressure applied by shrinking the gap — force the batsman to go over the top
Death Overs (16-20)
The final five overs are where matches are won and lost, and field placement at the death is the most technically demanding aspect of T20 captaincy. Every fielder position must balance saving runs against preventing sixes. Our analysis of successful death overs performances consistently shows this setup:
- 5 fielders positioned along the boundary in the deep — maximum protection against sixes
- Long-on, long-off, deep midwicket, deep extra cover — the four corners of the death field
- Sweeper at square leg — covers the lofted drive over midwicket
- Wicket-keeper + slip retained for any pace bowler operating in the channel
For Specific Bowlers
Yorker Specialist
When a bowler has demonstrated the ability to land yorkers consistently at the death, the field should open up completely. All 5 fielders can be placed on the boundary, allowing the bowler maximum freedom. The philosophy here is simple: if the yorker lands, runs are already restricted — the fielder placement is purely for the occasional mis-hit six.
Slower Ball Bowler
A bowler operating with a well-disguised slower ball changes the geometry of the pitch. The field should compress inward — mid-off, cover, and point all inside the ring. Deep fielders are pulled back because batsmen typically chip slower balls rather than hitting them for six. The objective is to force singles and prevent the boundary while the slower ball does its work.
Wicket-taking Bowler
When a bowler has been consistently generating edges and false shots, the field should maximise the catching area. Slip, gully, and point form a catching chain behind the bat. This is the highest-risk field setup — it leaves large uncovered gaps on the leg side — but it is designed for wickets, not dot balls. Use it when the match situation demands a wicket rather than a run freeze.
Match-ups Based Field
Modern T20 captains build their fielding plans around specific player match-ups rather than applying the same template to every batsman. We track these match-up patterns as part of our tactical analysis — the data consistently shows that match-up-specific field settings outperform generic plans by a measurable margin:
| Batsman Type | Recommended Field |
|---|---|
| Left-handers vs leg-spin | Deep cover deployed, no slip — the natural angle of leg-spin into a left-hander eliminates the off-side edge |
| Right-handers vs off-spin | Slip, gully, and backward point set — off-spin's natural angle produces edges on the off side |
| Power hitters (boundaries-focused) | Boundary riders on all four sides — trade singles for the six-stop |
| Anchor batsmen (rotation-focused) | Attacking inner-circle field — force the accumulator to play risky shots for runs |