Drive time analysis across a whole store network
Drive time analysis on every branch at once shows where areas overlap, where nobody is covered, and what each area holds. How to run it, read it and keep it current.
Part of the guide AI employee for site selection
A drive time analysis draws, for each of your sites, the area a car can reach along the roads within a set number of minutes, then counts what falls inside: residents, rivals, customers, incidents. Run on one site it answers "who can reach this store". Run on the whole network at once it answers the questions that matter more to an operations or expansion team: which stores share the same customers, which neighbourhoods no store reaches in time, and whether each branch's area holds what its targets assume.
This is for retail, service and delivery businesses with several branches or depots. It explains what a network-wide analysis shows, the limits of the drive times you can draw today, a made-up network of seven stores in Toronto, the traps in reading the maps, and an AI employee that keeps the analysis current each month.
What a network-wide view shows
- Overlap. Where two stores' areas cover the same streets, they draw on the same households. A little overlap is normal in a dense city; a lot means one store mostly feeds on the other.
- Gaps. Neighbourhoods inside your market that no store reaches within the time you promise. Those are candidate locations, or places to stop promising same-day service.
- Area by area. Residents, competitors and anchors inside each store's own area, so a manager's targets match what they can really serve.
- Change. Competitors that opened inside an area this month, or road closures inside a depot's delivery area today.
The limits of the drive times you can draw
In xMap Flows the Travel area block draws areas by car, on foot or by bike, as a travel time or as a distance along the roads. For now it goes up to 15 minutes and 10 km by road, which suits store catchments, delivery promises and service visits in a city, but not regional reach of an hour or more. It takes up to 25 places a run, so a large network is split across runs or flows.
When the routing service cannot draw an area (it is not set up, the day's share is used, or a call failed), the block falls back to an estimate: a circle at a typical straight-line speed for the mode of travel. The step and every email say plainly which areas are estimates, so a report never passes off a circle as a real drive time.
A made-up network in Toronto
This example is made up. A home goods retailer has seven stores in Toronto and draws a 12-minute drive area around each. Three things stand out on the map.
- Two downtown stores overlap heavily. More than half of one store's area sits inside the other's. Sales data confirms the smaller one has been flat since the larger one opened. It becomes a candidate for a smaller format or a move.
- A gap in the north east. A belt of suburbs with about 140,000 residents sits outside every store's 12-minute area. It goes on the expansion list for a site visit.
- One suburban store's area holds far fewer residents than the others, because a ravine and a motorway cut it off on two sides. Its target is revised down instead of its manager being blamed.
Population figures come from xMap's population grid, which covers Canada; they would not be available for a network in the United States or the United Kingdom, where the same analysis would count places and competitors only.
Traps in reading drive time maps
- One time of day. Drive times change with traffic. A free-flowing area at noon may shrink at 17:30. Draw areas for the time customers come, and check live road speeds at those hours with Traffic Flow.
- Mixing modes. Comparing a walking area for a city-centre store with a driving area for a suburban one is fine, as long as you know that is what you did and why.
- Counting overlap as lost sales. Overlap means shared reach, not proven cannibalisation. Check your own sales before closing anything.
- Forgetting estimates. An area drawn as an estimate is a circle. Do not draw conclusions about a river or a motorway from it.
- Analysing once. New rivals and new roads change what an area holds. Re-run it.
Keeping the analysis current with an AI employee
An AI employee in xMap Flows can redraw and recount every area on a timetable and tell each manager what changed in theirs. It is one of the jobs in the site selection guide.
- Schedule: the first Monday of each month.
- My data: your stores or depots, with their addresses.
- Travel area: 12 minutes by car (or the walk or ride you choose) around each.
- Nearby places: competitors inside each area; each one found carries the name of the store area it falls in.
- Demographics: residents inside each area, where the country has population data.
- Only new, then Email to each area manager and Show on a map for the whole network.
Managers get the new competitors in their own area with a map; the expansion team gets the network map with every area drawn. The template rivals within 10 minutes' drive of each store is this flow ready to use, who my warehouse reaches in 15 minutes, for same-day delivery applies it to delivery, and where to put micro-fulfilment hubs looks for gaps.
Questions
What is the difference between drive time and distance by road?
A drive time is everything a car reaches in a set number of minutes; a distance by road is everything within so many kilometres along the roads, whatever the speed. Use time for customers and service promises, distance for delivery costs.
How long a drive time can I draw?
Up to 15 minutes, or 10 km by road, for now. That covers most city catchments and delivery areas, but not regional reach of an hour or more.
Does a drive time account for traffic?
It follows the road network. Live traffic changes it through the day, so check road speeds at the hours that matter with Traffic Flow.
Can I analyse walking or cycling areas too?
Yes. Travel area draws walking and cycling areas the same way, which suits city-centre shops and bike couriers.
Templates that do this
Read next
More on site selection and expansion · Every article · Templates