How tour operators plan around the busiest days at attractions

Tour operators plan around busy days by measuring how busy the area around each attraction is, day by day and hour by hour, and then putting groups where the crowd is not. Footfall data gives each attraction its busiest day of the week, its busiest hour and how the day splits between morning, midday, evening and late night. A walking tour moved from the busiest hour to a quieter one is a better tour, and a slot that is always busy can carry a higher price or a smaller group.

This article is for tour operators, destination management companies, school-trip and coach planners, and the hotel concierge teams who book them. It covers what footfall around an attraction measures, how to read it without mistaking it for ticket sales, a worked example, the mistakes to avoid, and an AI employee that refreshes the picture every week.

What footfall around an attraction measures

The Mobility Footfall block adds up how busy the area within a chosen distance of each place is, from xMap's own mobility data. It gives footfall per day, the busiest hour, the busiest and quietest day of the week, the share of the day in each part, and the trend against the week before. A setting limits it to weekdays or weekends, and the weekend follows the country.

It measures the area around the attraction, not the queue at the gate. A museum on a busy shopping street will show the street's crowd as well as its own. That is still what a tour group walks through, which is the point for a planner.

How to read it for a tour programme

• Busiest day and quietest day. The plainest signal. If an attraction's busiest day is Saturday and its quietest is Tuesday, a midweek programme sells calm as part of the product.
• Busiest hour. Shows when to avoid the area, and when the cafes and shops nearby will be full for a group break.
• The day in parts. An attraction whose area is busiest late in the evening suits a morning tour; one that peaks at midday suits an early start or a late afternoon slot.
• The trend. A rise against the week before often means a school holiday, a festival or a cruise ship in port. Read it with your own calendar, not on its own.
• Compare attractions with each other. Footfall is best for ranking the stops on one itinerary against each other, not for promising a number of people.

A worked example in Rome

Here is a made-up example. A small operator in Rome runs a half-day walking tour with five stops: a fountain, a square, a church, a market and a viewpoint. Guests complain that two of the stops are too crowded to hear the guide. The operator puts the five stops in a table and measures footfall within 200 m of each over the most recent weeks there are.

A made-up example to show how the figures are read. Not measured data.

Read together, the table says the weekend tour fights the crowd at almost every stop, and that the market is busiest exactly when the tour reaches it. The operator moves the weekend start to 8:30 so the fountain and square come before the midday peak, swaps the market for the viewpoint on Saturdays, and adds a Tuesday departure sold as the quiet tour. None of this needs a number of people; it needs the order of the days and hours.

Mistakes to avoid

• Reading people-hours as people. A plaza where tourists linger scores high even if fewer people pass. For a guide, lingering crowds are what make a stop hard.
• Using too wide a radius. A 500 m circle around a central attraction takes in half the old town. Keep it to the stop itself, 100 to 200 m.
• Planning next month from last week alone. With only a few weeks of data, check that a pattern repeats before rebuilding a programme around it.
• Expecting figures everywhere. Where an area has no data yet, the place says so. In Australia, plan with your own booking history for now.

Doing it with an AI employee

A weekly AI employee keeps the itinerary's picture fresh. The blocks in order: Schedule (every Monday), My data (the stops of each tour, with their positions), Mobility Footfall (busy hours, busiest and quietest days, the trend), Weather forecast for the week ahead, an xMap LLM block that reads each tour's stops and suggests a start time and stop order for the coming week, then Email to the operations team. What lands in the inbox each Monday is one line per tour, the crowded stops flagged, and the suggested changes with the reason.

To find new stops and partners near each attraction, add Nearby places. Ready-made starting points are Tour and attraction partners near my hotels, Destination report: the attractions visitors rate best and Rainy day ideas for my guests.