Footfall around coworking spaces: what operators and suppliers can read
What footfall around coworking spaces shows about weekday use, Friday dips and evening events, for operators running spaces and businesses that sell to them.
Part of the guide Location intelligence automation
Footfall around coworking spaces shows how busy the streets around them are through the working week: how strong the weekday middle of the day is, whether Fridays fall away, and whether anything happens after 6 pm. It cannot see inside a space or count members, but it does show whether a coworking cluster is a lively work district or a quiet street with a few desks, and it shows how that changes from month to month.
Two kinds of reader use it. Operators who run several spaces want to know which neighbourhoods are pulling people in and when to hold events. Businesses that sell to coworkers, lunch places, coffee roasters, gyms, IT support and meeting-room brokers, want to know which clusters are worth a stand, a route or a sales visit. Choosing the site of a new space is a separate question, covered in site selection for a coworking space.
The pattern a work district leaves
Around offices and coworking spaces, presence builds through the morning, holds over lunch and drops after work. In Mobility Footfall that reads as a large midday share, a busiest hour around the middle of the day or the morning arrival, and weekdays well ahead of weekends. Hybrid working adds a twist many operators know from their own bookings: Tuesday to Thursday busy, Monday softer, Friday quiet. The busiest and quietest days show whether a district follows that pattern.
A cluster that breaks it is worth a closer look. A strong evening share near a space suggests the area has restaurants and bars that keep people around, which helps evening events. A weekend that is nearly as busy as the week usually means the space sits in a mixed area with homes and shops, which suits members who live nearby.
Finding the clusters first
Before measuring, find where coworking spaces gather. Nearby places can search a city for coworking spaces, and counting them within 500 m of each one shows the clusters. Measuring footfall around every single space is rarely needed; one point per cluster tells you about the district.
Once the clusters are known, the trend is what an operator watches. When a large new space opens two streets away, or a big employer moves into the district, the weekly change around your own space shows whether the area as a whole is getting busier or whether the newcomer is drawing people from the same streets. Read it over several weeks, since a single week can move with a holiday or a conference, and set it beside your own bookings: footfall rising while your bookings fall is the signal to look at price, opening hours or what the new space offers that yours does not.
A worked example in Nairobi and Warsaw (made up)
Say an operator runs five spaces, three in Nairobi and two in Warsaw, and wants to plan the next quarter's community events and to decide where to trial longer opening hours. The figures are made up to show how to read them.
| Space | Midday share | Evening share | Busiest day | Quietest day |
|---|---|---|---|---|
| Nairobi, Westlands | 38% | 29% | Wednesday | Sunday |
| Nairobi, Kilimani | 31% | 33% | Thursday | Monday |
| Nairobi, Upper Hill | 44% | 15% | Tuesday | Saturday |
| Warsaw, centre | 40% | 24% | Thursday | Sunday |
| Warsaw, Praga | 29% | 31% | Friday | Tuesday |
Made-up figures for illustration only.
Upper Hill is a classic office district: a big midday, an empty evening. Events there belong at lunchtime. Kilimani and Praga keep their evenings, and Praga is busiest on Friday, so those two are where longer opening hours and evening talks have the best chance. A supplier reading the same table would put a lunch stand in Upper Hill and the Warsaw centre, and an evening pop-up in Praga.
Mistakes to avoid
- Reading it as occupancy. The figure covers the whole block around the space, offices, shops and homes, not the members inside. Your own booking data measures occupancy.
- Comparing a cluster with a single building. Use the same radius for every point, 200 m for one building, 500 m for a cluster.
- Missing holiday weeks. School holidays and public holidays empty work districts. A month that includes one is not a fair month for comparison.
- Waiting for last week. Footfall comes in about 10 days after the day it measures.
An AI employee for coworking clusters
For operators, one monthly flow covers every space. For suppliers, the same flow finds the clusters and ranks them. Both are typical jobs for location intelligence automation.
- A Schedule for the first Monday of the month.
- An Area of interest with the cities you work in, or My data with your own spaces.
- Nearby places set to coworking spaces, passing on each place with a count of coworking spaces within 500 m.
- Sort and limit to keep the 20 places with the most coworking around them.
- Mobility Footfall on each, 500 m, the last 30 days, with Busy hours and Busiest days.
- xMap LLM to describe each cluster in a sentence (lunch district, evening district, mixed) and suggest the best day and time for an event or a stand.
- Email or Make a report to the community or sales team.
The inbox gets a ranked list of clusters, each with its busiest day, the shape of its day and a suggested slot. Suppliers can add Apollo to find the person who runs each space.
Questions
Can footfall tell me how many members use a coworking space?
No. It measures presence in the area around the space in people-hours. Member counts come from your own booking or door system.
Which radius should I use around a coworking space?
About 200 m for one building, 500 m when you want to describe a cluster of spaces and the streets between them.
Why is my space busiest on Wednesday?
Many hybrid teams come in mid-week and stay home on Mondays and Fridays. The busiest and quietest days show whether your district follows that pattern.
Does footfall cover every city?
Footfall covers most of the world from 17 October 2026, not yet Australia. A place with no data yet says so rather than showing zero.