At any given address, radius, drive time, and walk time represent different measures. If a shortlist combines them, it compares the methods rather than the sites. For each store format, select one definition, record its settings, and use both consistently across every site.
Most teams understand that a circle is only a rough tool. The issue in this article is separate and remains even after that is corrected. Everyone agrees to use drive times, yet the definition continues shifting between sites without anyone noticing. By the time the shortlist reaches the committee, the comparison is no longer fair.
What each method actually measures
These methods answer different questions. A radius shows who is nearby in a straight line. Drive time shows who can reach the site on actual roads within a set number of minutes, while walk time applies the same test to the sidewalk network. The result is three distinct populations, not three estimates of one population.
Our trade area analysis guide reviews all five delineation methods in common use, including gravity models and customer-derived boundaries. This piece begins once you've selected one.
What the three methods return at one real address
In GrowthFactor, we ran all three for one downtown Pittsburgh address in September 2026, with the platform's default demographic preset. The issue isn't that the walk-time zone is smaller. It represents an entirely different place.
| Measure | 3-mile ring | 10-minute drive | 10-minute walk |
|---|---|---|---|
| Population | 161,724 | 132,259 | 5,170 |
| Median household income | $64,777 | $66,047 | $109,641 |
| Graduate or professional degree | 22.7% | 22.7% | 43.6% |
| Median home value | $241,321 | $245,857 | $521,516 |
| Average household size | 1.93 | 1.92 | 1.41 |
On every demographic line, the ring and drive time figures are close, with the ring counting about 22% more people. Reviewing only those columns would suggest that the choice of method barely matters here.
The walk-time column represents a fundamentally different market. Median household income is 69% higher than the ring, the share of residents with a graduate degree is about twice as high, and average household size is lower by half a person. This is the residential core of downtown, and its profile differs entirely from the surrounding metro. Underwrite the concept to the ring but open it to the walk-up trade, and you're targeting the wrong customer. Precision within the wrong boundary won't correct that.
A single address is an example, not a study. It demonstrates the mechanism: the boundary defines the population you're describing, and changing that boundary can change the customer.
The gap is widest exactly where it matters most
The differences between methods are most pronounced at smaller geographic levels. The City of Hanford, California publishes a demographic comparison for its own commercial sites, placing both methods side by side across several geographic sizes.
At the narrower end, a 3-mile radius counts 55,555 people, while a 5-minute drive time counts 21,343, roughly 2.6 times as many. At the broader end, the same document lists a 10-mile radius at 104,619 and a 15-minute drive time at 103,158, a difference below 1.5% (City of Hanford, municipal economic development document, June 2023).
The pattern merits attention. Convenience, quick-service, and urban-infill deals, where a few blocks decide the outcome, are precisely where the methods diverge most. Regional big-box deals are where teams tend to spend the most time on methodology, yet the methods there already nearly agree. Method discipline pays off in inverse proportion to the attention it usually receives.
Circles overstate reach, and the research says by how much
The academic research on this issue is mostly from public health, not retail, because walkability researchers faced the same measurement problem and had reason to quantify it.
A 2022 study drew on Multi-Ethnic Study of Atherosclerosis data from six US sites to compare circular and network buffers of the same nominal size. At a quarter-kilometre radius, the circular boundary included a median 2.8 times more walkable destinations than the route-based boundary. The ratio was 1.8 at one kilometre and 1.5 at five kilometres. This measurement choice also understated the relationship between the built environment and actual walking behaviour by roughly 20% to 80% across the sites (Li et al., International Journal of Health Geographics, September 2022).
A prior study in that journal showed that geometry affects composition, not merely size. For the same Vancouver-area respondents, residential land accounted for 51.25% of the circular buffer versus 64.94% of the network buffer, while park and recreational land decreased from 11.81% to 4.47%. One land-use association that was statistically insignificant with the circular boundary became significant with the network boundary (Oliver, Schuurman and Hall, International Journal of Health Geographics, September 2007).
Both findings lead to the same conclusion. A circle drawn at a walkable scale isn't a conservative proxy for a walkshed. It consistently covers a larger area and a different mix, with the overstatement worsening as the boundary gets smaller.
Your isochrone tool has a traffic default you probably have not checked
Most teams don't review this part at all. Drive time isn't a single configuration. Whether traffic is modeled, and which traffic is included, depends on the per-vendor default, and the major providers disagree.
- Esri's Generate Drive Time Trade Areas tool presents Time of Day as an optional input: the time and date used to calculate distance. It doesn't explain what happens when that field is left blank, so the documentation alone can't establish whether traffic reached your polygon (Esri ArcGIS Pro documentation).
- Google's Isochrones API, which became available for public preview in July 2026, uses a default routing preference that ignores traffic and produces, Google says, "a deterministic shape that does not fluctuate based on the time of day" (Google Maps Platform documentation).
- Mapbox's Isochrone API conceals the choice in the profile string. Ask for
mapbox/drivingto receive average conditions, ormapbox/driving-trafficto receive current and historic traffic. The requests differ by one word (Mapbox documentation). - HERE's Isoline Routing API works in reverse: omit a departure time, and it uses the current time, which draws traffic in. Turning it off requires passing
departureTime=any(HERE developer documentation). - TravelTime allows the traffic model parameter set to be pessimistic, balanced, or optimistic, so you choose the congestion assumption rather than inherit it (TravelTime documentation).
Using two platforms, analysts who leave the default settings unchanged can produce different polygons for the same address under the same stated method. Neither analyst made an error, and the output gives neither any indication that this occurred.
We couldn't find a credible published estimate for how much a drive-time polygon contracts during rush hour that could be tied to actual measurement. The figure repeated in the trade press comes from a vendor page, which says a peak contour "can shrink by close to a third," as an illustration with no dataset behind it; a later article recast it as an exact measured percentage. We no longer cite that exact figure. We'd rather use the vendor defaults above to demonstrate the mechanism than repeat a statistic that doesn't hold up when its source is checked.
A trade area number is four decisions, not one
Method is the decision teams debate, but it accounts for only one of four; the other three move unnoticed.
The threshold determines the size, while the traffic assumption determines the shape. Data vintage tells you which year's population is counted. If any of these settings differs between two sites, the comparison is no longer truly a comparison, even when both rows on the shortlist still read "drive time" and appear to show the same measurement.
The same failure causes cannibalization estimates to vary from one analysis to the next. Since overlap between two trade areas is entirely determined by how each one was drawn, a cannibalization number carries all four decisions twice, once for each area.
When walk time is the right instrument
Walk time belongs at sites where customers arrive on foot, and nowhere else. That covers downtown cores, transit-adjacent sites, dense mixed-use districts, and small-format urban stores. Suburban and highway retail don't fit that approach, and applying a walkshed there gives you a catchment too small to underwrite.
Before applying one, there are two points to keep in mind. Because the pedestrian network is sparser than the road network, a walkshed covers a much smaller share of its nominal circle than a drive-time polygon does of its own, which is exactly what the buffer research above measures. Thresholds aren't standardized either: the widely used five-minute quarter-mile and ten-minute half-mile conventions come from neighbourhood planning rather than retail, while Walk Score's methodology gives full credit inside a quarter mile and decays to zero around a thirty-minute walk.
Choose a threshold suited to the format and keep it fixed. Changing walk time between an urban site and its comparison set causes the same damage as changing methods altogether.
How to lock a definition your portfolio can live with
No industry standard addresses this directly. We searched published guidance from the major retail real estate bodies for a requirement that trade area methodology be disclosed or kept constant in comparative analysis, but found none. Appraisal and feasibility work come closest: a lender or reviewer can always ask you to support the method used to reach a conclusion. Still, none of the published standards we found specifically identifies trade area delineation. That discipline is yours to impose.
Four rules cover most of it.
- Set the definition by store format, not by site. Define urban small-format, suburban inline, and highway separately. Since sites in each format compete with one another, evaluate all sites within that format using the same measure.
- Record all four settings with every number. The population figure won't remain reusable next quarter unless its method, threshold, traffic assumption, and data vintage stay with it.
- Calibrate against real customers where you have them. For a current store, where customers actually come from shows the threshold that matches its true trade area. That calibration gives you a defensible basis for defining trade areas at sites where you don't have customers yet. In custom modelling work we've done, using actual customer data instead of arbitrary ring studies changed which variables mattered, and several conventional assumptions turned out to run in the opposite direction.
- Re-run the incumbent, do not trust the old number. Before comparing a new site with one approved two years earlier, measure the older site again using today's definition. The cost is low, yet this is the step skipped most often.
None of this establishes a correct boundary. It makes a group of boundaries comparable, which is the only thing a shortlist actually needs. An honestly and consistently drawn trade area is better than a cleverer one applied unevenly, just as foot traffic comparisons only mean something inside a consistent category.
Across a growing pipeline, keeping four settings with each site is primarily a record-keeping task, not an analytical one. GrowthFactor's market planning workflow stores the trade area definition on the site record with the score and deal status. That keeps the settings behind each number visible when someone asks, six months later, where it came from.
Frequently Asked Questions about Trade Area Definitions
What is the difference between a radius and a drive-time trade area?
A radius measures straight-line distance from the site and produces a circle. A drive-time trade area measures travel along the road network and produces an irregular polygon that stops at rivers, freeways without exits, and rail lines. The circle is faster to produce and easier for outside parties to accept. The polygon is closer to how customers actually reach the store, which is why the two can return very different populations at the same address.
Can I compare two sites if they use different trade area methods?
No, not directly. Population, income, and competitor counts all inherit the boundary they were measured inside, so a site measured on a 3-mile ring and a site measured on a 10-minute drive time are answering different questions. If the two numbers sit in the same column of a shortlist, the ranking partly reflects the method rather than the sites. Re-run both under one definition before comparing them.
When should I use a walk-time trade area instead of a drive time?
Use walk time when most customers arrive on foot: downtown cores, transit-adjacent sites, dense mixed-use districts, and small-format urban stores. Walk time is the wrong instrument for suburban and highway retail, where it will return a catchment far too small to underwrite. The test is how your customers actually get there, not how dense the surrounding area looks on a map.
Does the time of day change a drive-time trade area?
It can, and the tool you use decides whether it does at all. Some isochrone services default to traffic-free routing, which returns the same polygon regardless of when you run it. Others use live or historical traffic by default, so the same request returns different shapes at different hours. Two analysts on two platforms, both leaving the defaults alone, can produce different boundaries for the same address.
How does GrowthFactor compare to Kalibrate for trade area analysis?
Kalibrate has deep roots in fuel and convenience retail, with catchment modeling and demand forecasting built around that sector and delivered largely as consulting-led engagements. GrowthFactor is a platform your own team runs, where trade area definition sits inside the same workflow as site scoring, demographics, and deal tracking, so the boundary settings behind a number stay attached to the site record. Teams can re-run a site under a different definition in seconds rather than commissioning new work.
The version that matters
With a trade area, boundary accuracy isn't the point; every boundary is wrong in some places. What matters is whether the boundary for site A is the same instrument used for site B. The entire shortlist depends on that assumption, yet almost no one documents it.
For each format, establish the definition once and record it. When an incumbent becomes the benchmark, measure it again. That keeps comparisons honest and shifts committee debate to the sites, where it belongs. If you're setting a standard from scratch, our companion guide to trade area mapping methods explains the definitional groundwork.
