FlowsBook a callSign inCreate free accountSign up
Footfall and mobility

Footfall data for town centres: a monthly health read for councils

A simple monthly check on how busy a town centre is: which points to measure, what to report to councillors, and how to tell a real decline from a wet month.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

Footfall data for town centres works best as a short monthly read rather than a big annual study: the same handful of points on the high street, the market square and the station, measured every month, with the evening and weekend picture alongside the daily total. A council that keeps this up for a year knows which end of the centre is slipping, whether the evening economy is growing, and whether a regeneration scheme moved anything.

It is written for town centre managers, economic development officers, business improvement districts and the councillors they report to. You will find what to measure, what to put in front of a committee, a made-up example, the errors that make reports misleading, and the AI employee that sends the monthly sheet.

Pick fixed points and never move them

The value of a monthly read is in comparing like with like, so choose the points once and keep them. Eight to twelve is enough for most towns:

  • The busiest stretch of the main shopping street, and its quieter far end.
  • The market square, on market days and off.
  • The station or bus interchange.
  • The main car park entrance.
  • One or two side streets the council is trying to revive.
  • The cluster of restaurants and pubs that makes up the evening economy.

Measure each with Mobility Footfall at a 200 m circle, which reads the point's own block of the map. The figure is people-hours of presence: a shopper who lingers two hours counts twice as much as one who passes through in one, which is exactly what a council usually wants to know about a centre's health.

What goes in the monthly report

FigureWhy it matters
Average day at each pointThe headline: is the centre busier or quieter than last month?
Weekday against weekendA centre that only lives on Saturdays depends on one day's weather
Evening and late-night shareThe night-time economy, often the part regeneration aims at
Busiest hourShows when to schedule markets, events and cleaning
Trend on the week beforeCatches a sudden drop, such as roadworks starting
Openings and closuresFootfall next to what opened and shut tells the cause, not just the symptom

The core of a town centre health report built from footfall and places.

For the weekday and weekend split, use two Mobility Footfall blocks in the flow, one set to weekdays only and one to weekends only. The weekend follows the place: Saturday and Sunday in most countries, Friday and Saturday in most of the Gulf.

A made-up example

The figures are invented to show the reasoning. A market town in France measures ten points. In the third monthly report, the far end of the high street is down noticeably on the month before while the rest of the centre is steady. The trend field shows the fall began in one particular week. The places check finds a bakery and a bank branch at that end closed in the same fortnight, and the incidents check shows roadworks on the approach road. The officer's note to councillors says the drop is local, has two causes, and should be watched for another month before anyone talks about decline.

A district centre in Pune runs the same report for its traders' association, and an Ontario town uses it to show whether a new evening market lifted the late-night share of its square.

Errors that make reports misleading

  • Comparing December with January. Seasonal swings are larger than most real changes. Until a year of data exists, compare each month with the one before and say so; the data begins on 17 October 2026, so like-for-like year-on-year comparisons start in late 2027.
  • Reporting one number for the whole town. An average hides the street that is dying next to the one that is thriving.
  • Calling people-hours visitors. Write "how busy the centre was", not "how many people came".
  • Missing the delay. Each day arrives about ten days late, so a report sent on the 5th covers the month to roughly the 25th of the month before. State the dates, which come with every figure as footfall_from and footfall_to.
  • Ignoring the causes. A drop with a closure or a road closure beside it needs a different response from a drop with neither.

The monthly flow

  1. Schedule: the 5th of each month at 07:00.
  2. My data: the fixed points, each with a name such as "High Street east".
  3. Mobility Footfall, weekdays only, last 30 days, with Footfall, Busy hours and Trend; a second Mobility Footfall, weekends only, with Footfall.
  4. Nearby places around each point: shops, cafes and services within 200 m, with the number opened in the last year.
  5. Traffic incidents: roadworks and closures near the points at the time of the run.
  6. xMap LLM: a plain summary for councillors, told never to add a figure the data does not hold.
  7. Make a report: a PDF with the council's logo, emailed to the officers and kept in a folder.

The monthly email holds the PDF and a few lines: which points rose or fell, the evening share, and any closures or works nearby. To add a list of shop closures for the local paper or the town centre board, see Shops that closed this month, for the high street story; for new businesses registered in the area, New businesses in the municipality. The government and cities page has more, and the location intelligence automation guide puts it in context.

Questions

How many points should a town measure?

Eight to twelve fixed points cover most town centres: the main streets, the square, the station, the car park and the evening cluster. Keep them the same every month.

Can footfall replace door counters on the high street?

It answers a different question. Counters count people crossing a line; footfall measures how busy the area around a point is, in people-hours, and covers every point without installing anything.

When can we compare with the same month last year?

From late 2027. The data starts on 17 October 2026, so until then compare month on month and note seasonal effects.

Does it work for small towns?

Yes, with care: smaller places have smaller numbers and more variation, so use the 30 or 90 day window and look at the direction over several months.

Templates that do this

Read next

More on footfall and mobility · 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.