FlowsBook a callSign inCreate free accountSign up
Footfall and mobility

Foot traffic in industrial areas: reading worker presence by shift

Factory zones fill and empty with the shifts. How to read those waves, and use them to place a canteen, a food truck, a clinic or a shift bus where workers actually are.

Part of the guide Location intelligence automation

By the xMap team · · 4 min read

Foot traffic in industrial areas follows the shift pattern, not the shopping day. An estate running two or three shifts shows sharp rises around each changeover, a long working-hours plateau, and a weekend that may look nothing like the week. Reading those waves hour by hour tells a canteen operator when to open, a food truck where to park at 05:30, and a transport or health provider where the workers really are.

The guide is for caterers and food vendors, convenience store chains, occupational clinics, staff transport operators, and the industrial landlords who want services that keep tenants. It explains how to measure an estate, how to read a shift profile, a made-up example, the errors to watch, and an AI employee that keeps the picture current.

Why the hourly profile matters more than the total

Mobility Footfall gives the average day in people-hours around a point and, with Busy hours on, an hour-by-hour profile in the place's own local time, the busiest hour and the share of the day in the morning, midday, evening and late night. In a shopping street the total is a decent summary. In a factory zone it hides almost everything useful, because a worker on a twelve-hour shift adds a lot of people-hours while buying lunch once.

What you want from an industrial point is the shape: when presence climbs, how long it holds, and whether the night is busy. A late-night share near a third of the day means a night shift worth serving; a near-empty evening means the gates close at six.

Measuring an estate

  1. List the factory gates, the main internal road junction, the bus stops at the estate edge and any existing canteen or kiosk, each with a latitude and longitude, in a table on the My data page.
  2. Keep the circle at 200 m so each point reads its own block of the map. A wider circle can pull in a motorway or a housing estate across the road.
  3. Set Days to weekdays only for the working pattern, and run a second block on weekends to see whether production carries on.
  4. Use the last 30 days so a public holiday or a plant shutdown does not dominate.

A made-up example

The figures are not real. A catering company looks at an industrial park on the edge of Monterrey with six gates. Four gates peak at 06:00 and 18:00, with a steady plateau between, and their late-night share is high: a two-shift operation round the clock. Two gates peak at 08:00 and are quiet after 17:00. The places count finds one small restaurant within 500 m of the busiest round-the-clock gate. The company proposes a 24-hour canteen there to the landlord and sends a breakfast truck to the day-shift gates from 07:30.

The same reading in an estate near Chennai shows a weekend almost as busy as the week at three gates, which tells a clinic chain that Saturday opening would be used. In Johor, a staff bus operator uses the changeover hours to set departure times at each stop.

Errors to watch

  • Thinking people-hours are headcount. A plant with 500 workers on long shifts can show more people-hours than one with 800 on short ones.
  • Trusting a single week. Maintenance stops and holidays empty an estate for days. The 30-day window evens that out.
  • Forgetting the time zone. Hours are local to each point. That matters when you compare estates in several countries in one table.
  • Mixing in residents. An industrial point next to housing will show night presence from people asleep at home, not a night shift. Check the map before reading the late-night share.
  • Expecting yesterday's figures. Each day arrives about ten days later, and the data starts on 17 October 2026.

An AI employee for shift-based sites

  1. Schedule: every other Monday.
  2. My data: the estate gates and stops.
  3. Mobility Footfall: weekdays, 200 m, last 30 days, with Footfall and Busy hours.
  4. Nearby places: restaurants, cafes and convenience stores within 500 m, with a count.
  5. xMap LLM: for each gate, name the shift pattern from the hourly profile (day only, two shifts, round the clock) and suggest when a food service should open.
  6. Sort and limit: the busiest gates with the fewest places to eat first.
  7. Email to the operations team, with a map.

The email lists each gate with its shift pattern, busiest hours, how many places to eat are nearby, and a suggested opening time. To grow the list of sites, New manufacturers in the industrial zones and Factories hiring production staff find new and expanding plants; Where my workers live, for shift buses helps with transport. More on the manufacturing page and in the location intelligence automation guide.

Questions

Can footfall tell me how many people work at a plant?

No. It measures people-hours of presence around a point, so long shifts weigh more. It shows the pattern of the day, which is what a service provider needs.

How do I tell a night shift from nearby homes?

Look at the map first. If housing shares the block, night presence may be residents. Points at gates inside a fenced estate give a cleaner read.

Should I look at weekdays and weekends separately?

Yes. Run one block on weekdays only and one on weekends only. Many estates work Saturdays; some run every day.

How often should I refresh it?

Every two to four weeks is enough. Shift patterns change slowly, unless a plant opens, closes or adds a line.

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.