Loading field map
Every cricket captain faces the same practical question: where should each fielder stand, and how should those positions change as the game unfolds? The answer has shifted dramatically over 150 years, driven not by changes in the Laws of Cricket but by the format being played, the bowling attack being used, and—most recently—the availability of ball-by-ball tracking data. Field setting theory is the study of these shifting placement logics, and it can be organized into four authoritative frameworks that emerged in sequence but now coexist in live tension.
For nearly a century, field settings were designed for one overriding goal: taking wickets. In Test cricket, where matches lasted five days and run rates hovered around two or three an over, captains placed fielders where the bowler was most likely to generate a catch. A fast bowler attacking the top of off stump would expect a slip cordon of two or three fielders, a gully, and a short leg—all positioned within ten metres of the bat, ready to catch edges. A spin bowler flighting the ball outside off stump would be supported by a short leg, a silly point, and a backward short leg, all crouching close to the pitch. Deep fielders were a last resort, used only to save runs when the ball passed the infield.
This placement logic was inseparable from the bowling theories of the era. The Fast Bowling School relied on the slip cordon to convert edges into wickets; the Spin Bowling Attack depended on close catchers to turn bat-pad nudges into dismissals. A captain setting a traditional Test field was effectively saying: the bowler will attack the stumps or the corridor of uncertainty, and the field will back that plan by covering the most probable catching zones. Deep positions—long on, long off, deep square leg—were reserved for defensive phases or for containing a batter who had begun to dominate. The framework was not written down as a formal theory; it was passed from captain to captain as craft knowledge, refined by the slow pitches and patient rhythms of five-day cricket.
The introduction of One-Day International cricket in 1971 created a new constraint: a limited number of overs, which meant a limited number of balls to take wickets and a pressing need to restrict runs. Traditional Test settings, with their cluster of close catchers, left large gaps in the deep that a batter could exploit for boundaries. The One-Day framework responded by pulling fielders out of the close catching positions and spreading them around the boundary. The ring field—a circle of infielders placed on the edge of the thirty-yard circle—became the standard, with two or three boundary riders patrolling the ropes.
Fielding restriction rules formalised this shift. In the early overs, only two fielders were allowed outside the thirty-yard circle, forcing captains to keep their best catchers close while still protecting the boundary. After the Powerplay, the number of permitted outfielders increased, and captains would move fielders to the deep to defend against big hitting in the death overs. The priority had changed from wicket-taking to run-restriction: a single saved in the deep was now worth more than a possible edge in the slips. One-Day settings did not abandon Test placements entirely—a slip might still be posted for the new ball—but they narrowed the catching cordon and thickened the boundary ring. The framework coexisted with Traditional Test settings because the formats were separate, but it absorbed the older logic only where it did not conflict with the run-rate imperative.
Twenty20 cricket, launched in 2003, compressed the game into three hours and made boundary-hitting the primary scoring mechanism. One-Day settings, which balanced run-restriction with wicket-taking, were too conservative for a format where a single over could swing a match. T20 Aggressive Field Settings inherited the ODI ring but inverted its purpose: instead of using the ring to save singles, captains used it to force batters to take aerial risks. The deep positions were no longer a last resort but a permanent feature, with fielders stationed at long on, long off, deep midwicket, and deep square leg from the first ball.
Match-up targeting became the defining innovation. A captain would place a deep point for a batter known to slog-sweep, a deep backward square leg for a puller, and a short third man for a batter who regularly edged cutters. The field changed ball by ball, not just over by over, as bowlers and captains responded to the batter's stance, the pitch condition, and the required run rate. This was a direct reaction to the T20 Batting School, which had turned batting into a power-hitting discipline; field settings had to anticipate where the batter would try to clear the infield. The framework discarded the close catching cordon almost entirely—slips became rare, short legs vanished—and replaced them with a flexible ring of boundary riders and a handful of infielders positioned to cut off singles. It remains the dominant framework in T20 cricket today, but it now coexists with a newer, data-driven approach that challenges its reliance on captain intuition.
From 2010 onward, the availability of ball-by-ball tracking data—Hawk-Eye, ball-by-ball feeds, wagon wheels, and heat maps—made it possible to test field placements against actual batter behaviour. Analytical Field Placement Theory treats every earlier framework as a set of hypotheses to be validated or refuted by evidence. Instead of asking "where do fast bowlers usually want a slip?", it asks "given this batter's edge probability against this bowler on this pitch, where should the fielders stand to maximise dismissal probability?"
The method is straightforward in principle but complex in execution. Clustering algorithms group a batter's scoring shots into zones—cover, midwicket, fine leg, third man—and calculate the expected runs per ball for each zone. A model might reveal that a batter scores at twelve runs per over through midwicket against pace but only four through cover, prompting the captain to place a deep midwicket and a wide long on while leaving the cover region unprotected. Machine learning models go further, simulating thousands of field configurations to find the arrangement that minimises expected runs or maximises wicket probability for a given bowler-batter matchup.
Analytical Theory does not discard the earlier frameworks; it tests them. Traditional Test settings often hold up for the first few overs of a Test match, when the ball is new and batters are cautious. One-Day settings remain useful for the middle overs of an ODI, when run rates are moderate. T20 Aggressive settings are broadly confirmed by data for power-hitting phases, but the models frequently suggest small adjustments—moving a fielder two metres to the left, or swapping a boundary rider for an infielder—that a captain relying on intuition might miss. The framework is still young, and its adoption varies widely across teams, but it has already changed how professional sides prepare field plans.
Today, the leading frameworks are T20 Aggressive Field Settings and Analytical Field Placement Theory, and they are in a state of productive disagreement. T20 settings are captain-driven, reactive, and shaped by experience; Analytical settings are data-driven, proactive, and shaped by models. The two agree on the fundamental goal—minimise runs while maximising wicket opportunities—but they disagree on how to achieve it. A captain might trust his gut that a deep square leg is needed for a particular batter, while the analyst's model shows that the batter rarely pulls and that the fielder would be better placed at deep midwicket.
Most professional teams now blend both approaches. The captain sets the initial field based on the match-up and the format, and the analyst provides real-time adjustments using live data. The division of labour is clear: intuition handles the unpredictable—a batter's body language, a bowler's confidence, the pressure of a close finish—while analytics handles the probabilistic—expected runs, zone vulnerabilities, historical match-up data. Traditional Test settings and One-Day settings remain in use for their respective formats, but they are increasingly informed by analytical insights rather than passed down as unexamined tradition.
The central tension in field setting theory today is not between old and new but between two kinds of knowledge: the tacit knowledge of a captain who has read the game for twenty years and the explicit knowledge of a model that has processed millions of balls. Neither has won, and neither is likely to. The frameworks coexist because they answer different parts of the same question: where to stand, and why.