Skip to content
Shyenova

GIS & Spatial Analysis

Route & Territory Design

Territories are usually inherited, unbalanced, and defended fiercely by whoever has the easy one.

Territory and route structures decay quietly. A beat plan is drawn when a distributor is appointed and is still running six years later, after the market has doubled in one direction and thinned in another. Reps in dense areas cannot cover their list; reps in sparse ones spend half their week driving. Nobody redraws it because redrawing it is politically expensive and the analysis is thought to be hard.

It is not especially hard. Territory design is a well-understood optimisation with two objectives that pull against each other (balance the workload, minimise the travel) plus contiguity so the result is operable. The genuine difficulty is not the mathematics. It is producing an answer the field organisation will accept, which means modelling their actual constraints rather than the idealised ones.

How the work runs

Four phases, and what comes out of each.

Durations are indicative and assume reasonable data availability. Where data is poor we say so in the first fortnight rather than modelling on sand.
01

2 weeks

Measure what is actually happening

We reconstruct the current state from visit records, GPS traces where they exist, and order data, travel time, service time, coverage achieved and workload distribution. This nearly always contradicts the internal account, and the gap is usually the argument that makes the redesign possible.

Outputs

  • Current territory and route geometry with workload per unit
  • Travel versus service time split from observed data
  • Coverage and frequency compliance against the stated plan
02

2 weeks

Build the travel model

Everything downstream depends on realistic travel times, so these come from a routed road network calibrated against your own GPS traces rather than from a generic speed assumption. Urban congestion, time-of-day variation and the difference between a mapped road and a usable one all matter, and a model built on straight-line distance will produce plans the field cannot execute.

Outputs

  • Routed network with travel times calibrated to observed traces
  • Time-of-day and seasonal travel profiles where they matter
  • Service time model by customer type
03

3–4 weeks

Design territories and routes together

Territories are formed to balance workload subject to contiguity and the constraints the field genuinely operates under, and routes are built within them. We produce several designs at different points on the balance-versus-travel trade-off rather than one answer, because that trade-off is a management decision and should be made explicitly with the numbers in view.

Outputs

  • Alternative designs across the balance and travel trade-off
  • Route plans within each territory with the resulting day structure
  • Quantified impact on coverage, travel and capacity released
04

2–3 weeks

Sequence a transition the field will accept

A redesign implemented wholesale is a redesign that gets reversed. Relationships, incentive plans and local knowledge all attach to the existing structure, so we sequence the change, identify the moves that cause the most disruption for the least gain and drop them, and build the case each affected person will be shown.

Outputs

  • Phased transition plan with disruption assessed per move
  • Incentive and target implications quantified
  • Communication pack for the field organisation

What good looks like

The ranges we design toward.

These are the improvement ranges these levers are known to produce where the underlying practice has not been examined recently. They are targets to test against your baseline, not promises.

10–25%

Travel time

Typical reduction from a properly optimised territory and route structure over an inherited one.

2–3×

Workload spread

Common ratio between the heaviest and lightest territory before redesign.

8–15%

Coverage gain

Additional visits achievable from released travel time, at constant headcount.

Deliverables

What you are left holding.

All of it handed over, documented, and with a session for whoever inherits it.
  1. 01Honest picture of the current state, workload imbalance included
  2. 02Travel time model calibrated against your own GPS traces
  3. 03Several designs across the balance-versus-travel trade-off, not a single answer
  4. 04Phased transition plan with disruption weighed against gain per move
  5. 05The working model, so territories can be redrawn again without another engagement

What an engagement looks like

A representative shape.

Illustrative. This is the shape of work in gis & spatial analysis, not an account of a specific client. We do not publish named results, and we would be wary of a firm that publishes them without the client in the room.

10 weeks

  1. 01Situation

    A distribution business was assessing eight candidate locations using ten-kilometre radius catchments, and had recently opened two sites after which nearby existing sites declined without anyone having forecast it.

  2. 02What we did

    Geocoded three years of transaction data to customer origin, built drive-time catchments calibrated against where customers demonstrably came from, and fitted a gravity model to allocate demand between competing sites.

  3. 03Where it landed

    Modelled catchments were substantially smaller and differently shaped than the radii implied. Two candidates that had ranked highly on gross population fell sharply once cannibalisation was subtracted, and the ranking changed at the top.

Where this connects

Rarely a self-contained problem.

These are the adjacencies that come up most often on this kind of work. Naming them is usually cheaper than discovering them halfway through.

Questions

The ones we get asked.

Our field team will resist this. How do you handle that?

By assuming it from the start and designing for it. Resistance is usually rational, someone is losing accounts they built, or a territory they can finish by four. We model the disruption of each individual move, drop the ones that cost a lot of goodwill for little gain, and give management the numbers for the ones worth doing anyway. A mathematically optimal design implemented against the field's will underperforms a slightly worse one they accept.

Do we need GPS tracking on our vehicles first?

It helps considerably and is not a prerequisite. GPS traces let travel times be calibrated to reality rather than to a routing engine's assumptions, which is worth a lot. Without them we calibrate from visit timestamps and order records, which is coarser but workable, and we state the resulting uncertainty rather than hiding it.

Can this handle daily dynamic routing rather than fixed beats?

Yes, though it is a different problem with different economics. Fixed beats give customers predictability and reps relationship continuity; dynamic routing gives efficiency. Most businesses want a hybrid (fixed frequency and territory, dynamic sequence within the day) and we would want to understand why you need full dynamic routing before recommending the operational complexity it carries.

How is this different from what our routing software does?

Routing software solves the daily sequencing problem well and takes the territory structure as given. Almost all the value here is in the structure (how territories are drawn, how frequencies are set, how the workload is balanced) which sits upstream of what the software optimises. Fixing the structure typically returns more than any amount of daily re-sequencing within a bad one.

Start a conversation

Talk to us about route & territory design.

Most useful first conversations are thirty minutes and involve no proposal. Describe the problem you are looking at and we will tell you honestly whether it is one we can help with.

Or write directly to hello@shyenova.com