FlowsBook a callSign inCreate free accountSign up
Population and demographics

Demographic data for site selection: what to pull for each candidate

Which resident figures to gather for every candidate site, how far around each one to look, which countries have the data, and how to line sites up fairly.

Part of the guide Location intelligence automation

By the xMap team · · 4 min read

Good demographic data for site selection comes down to four numbers for every candidate: how many people live within reach of it, the split between men and women, the age groups, and how tightly they are packed. Gather the same four for each site, measured over the same distance or drive, and the shortlist sorts itself into strong, average and weak before anyone visits.

This guide is for expansion managers, franchise developers and the analysts who prepare the site paper. It covers what to measure, how far to look, the countries where resident counts exist, a worked comparison of three sites and the mistakes that make one site look better than it is. For the wider picture of choosing locations, see the site selection guide.

The figures worth having for every site

The Demographics block reads xMap's population grid, small hexagons of about 0.1 km² each, and adds up the ones inside the area you give it. For each candidate it returns:

  • Residents in total, the headline figure.
  • Men and women, with the share of men in per cent. A gym aimed at women or a barbershop reads this first.
  • Nine age groups, from 0 to 9 up to 80 and over, plus three broad groups: children 0 to 19, adults 20 to 59 and seniors 60 and over, each with its share.
  • Area and density: the size of the area in km² and the people per km².

These are people who live there. Shoppers, office workers and visitors who come in by day are a separate question, answered by footfall; a site paper usually wants both, but never mixed in one column.

Radius or drive time

A radius is the quickest to set up: 500 m, 1 km, 3 km, up to 8 km in one search. It suits dense centres where most customers walk. Out of the centre, a drive time is fairer. The Travel area block draws what can be reached by car, on foot or by bike within a set time or road distance (up to 15 minutes or 10 km for now), and Demographics then counts the residents inside that shape. A river with one bridge or a motorway with few crossings can halve the people a circle promises; a drive area shows that.

Where the data exists

The population grid covers about 100 countries, among them France, Canada, India, Thailand, Egypt and Australia. It does not cover the United Kingdom or the United States yet. A site in a country without data comes back with 0 and the step says there is no data there, so a shortlist that crosses borders should be read with that in mind: an empty row is missing data, not an empty district. The article on why population data is missing in some countries explains more.

A worked comparison

Made-up figures, to show the method: a bakery chain weighs three sites in Montreal, each measured over a 10-minute walk.

Made-up siteResidentsAdults 20 to 59Seniors 60+People per km²
Site 1, near a metro exit14,2009,1002,3009,500
Site 2, a quiet residential street11,8006,2003,4007,900
Site 3, beside a ring road6,9004,3001,2004,600

Invented figures to explain the reading; not data about Montreal.

Site 1 has the most residents and the most working-age adults, the morning coffee and lunch crowd. Site 2 is smaller but older, which suits a bakery selling bread and cakes to people at home through the day. Site 3 trails on every measure: the ring road cuts its walking area in half. The decision between 1 and 2 is no longer about the numbers alone; it is about which customer the format is built for. That is the point of demographic data: it narrows the argument to the question that matters.

Mistakes to avoid

  • Using residents alone. Count the competitors inside the same area too, so a site full of people and full of rivals does not win by default.
  • Mixing distances. Every candidate on one distance, or the ranking is noise.
  • Reading a zero as an empty place. Check the step for a no-data note first.
  • Expecting single-year ages. The groups are ten years wide; a format aimed at 25 to 34 year-olds has to read two of them.
  • Treating residents as customers. A business park can have few residents and many daytime workers.

Let an AI employee measure the shortlist

When candidates arrive every week from brokers or a planning sheet, measuring them by hand stops scaling. One flow does it each time a row is added:

  1. New rows: starts when a candidate address lands in the shortlist sheet or a table in My data.
  2. Travel area: a 10-minute walk or drive around it.
  3. Demographics: residents, men and women and age groups inside the area.
  4. Nearby places: the competitors in the same area, counted.
  5. xMap LLM: a short verdict written from the figures, against the brief you give it.
  6. Email to the expansion team, or Make a report for the committee.

What lands in the inbox is each new candidate with its residents, age profile, density, rival count and a two-line verdict, plus a CSV of every field. Over a quarter that becomes a consistent record of every site considered, which is what a board asks for when a location underperforms. The Where to open next and Demographic profile of each city templates start close to this.

Questions

Which demographic figures matter most for choosing a site?

Residents within reach, the age groups that match your customer, and density. Add the men and women split when your offer leans to one.

Does it give household income?

No. The figures are residents by sex and age group. Income has to come from your own research or a local source.

Can I use it for sites in the United States or the United Kingdom?

Not yet. Resident counts are not available there; the block says so instead of returning a made-up number.

How many candidate sites can one run measure?

Up to 200 places a run, each with its own circle or travel area.

Templates that do this

Read next

More on population and demographics · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.