Territory planning is the allocation of accounts or geography across salespeople so each has a workable, balanced and coverable patch — traded off against travel time, capacity and the service commitments already made to customers.
Why territory planning matters
Territories are usually drawn once, under conditions that no longer apply, and then inherited. The result is quiet and expensive: one person cannot physically cover their patch while another has spare capacity, and both are measured against the same target as though the difference were effort.
Good territory design improves three things at once — travel time falls, coverage becomes achievable, and performance comparison becomes fair, because the territories being compared are genuinely comparable.
How territory planning works
The core problem is assignment under constraints, and it involves an unavoidable trade-off between two goals that pull against each other:
- Compactness — accounts assigned to one person should be geographically close, or the day disappears into driving.
- Balance — workload should be comparable across people, measured in visits, potential or revenue rather than in area.
Compactness and balance conflict wherever demand is unevenly distributed, which is everywhere: a dense city district may hold more accounts in ten square kilometres than a rural region holds in a thousand. Practical planning also carries capacity limits, shift windows, service duration per stop, and a tolerance for how much imbalance is acceptable before the plan is rejected.
Solving this well is the vehicle-routing problem in disguise — assignment and sequencing interact, since the cost of adding an account depends on the route it joins.
An example
Four reps cover 480 outlets. The inherited split is 150 / 130 / 110 / 90, drawn along administrative boundaries. Re-planned for balance within a 10% tolerance, the split becomes 124 / 122 / 118 / 116, and because the new patches are more compact, total travel falls as well. The rep who previously carried 150 outlets stops being 30% short on coverage every cycle — which had been read as a performance problem for two years.
Common variations
- Geographic territories. Defined by area — postcode, district, pin code. Simple and compact by construction.
- Account-based territories. Defined by customer list, common where account relationships matter more than proximity.
- Segment overlays. Separate coverage for modern trade or key accounts, layered over geographic territories for general trade.
Limitations worth stating
Territory changes have human consequences that models do not price. Reassigning an account breaks a relationship the customer values and the rep built, and moving a strong account away from someone mid-incentive-period is read — correctly — as taking money off them. Optimisers also value only what they are told to: run one on distance alone and it will happily separate a shopkeeper from the rep they have dealt with for six years. This is why territory planning outputs should be reviewed and accepted by a planner rather than applied automatically.
How xMatix supports territory planning
xMatix Field Sales includes a plan-territory action that splits outlets across field staff using a capacitated solver over road-network distances, rather than by drawing lines on a map by hand.
The trade-offs are tenant-level settings rather than hard-coded assumptions: default service minutes per stop, shift start and end times, whether truck-mode routing applies, the balance tolerance permitted between people, whether capacity is enforced, the demand look-back window used to weight accounts, and a solver time limit. Changing those settings changes the plan the solver proposes, so the model can be argued with.
The output is a proposal a planner reviews before it is applied, and it lands as visit routes and stops in the same structures that drive journey plans and day-to-day execution — so a re-plan flows straight into generated visit plans without a separate migration. Stops can subsequently be transferred between routes as territories evolve.
Related: route optimization · beat planning · permanent journey plan
