Planning field visits in a city where the roads jam every day
In a gridlocked city, the order of stops matters less than which district a rep works and when. A plan that keeps reps out of the worst hours and checks roads each morning.
Part of the guide Location intelligence automation
In a city where the roads jam every day, plan field visits by district and by hour first, and by route order second. Give each rep one compact part of the city per day, start the first visit before the morning peak, keep the cross-town drive out of the worst hours, and check the live roads and closures before anyone leaves. A perfectly ordered route that crosses the city at 08:00 still loses the morning.
This is for sales managers, merchandising leads and service coordinators whose people spend their day driving between shops, clinics, sites or customers in cities such as Jakarta, Lagos, Bangkok, Cairo, Mumbai, Sao Paulo or Mexico City. It covers what each kind of traffic data can and cannot do, a day plan built around the jams, a made-up example, and an AI employee that hands each rep their day before they set off.
Three kinds of road data, three different jobs
- Route order. Route planner puts the day's stops in the best order from a start point and gives the distance and time between them. Its times are travel times for usual traffic on those roads, and they do not include the time spent at each stop. It plans the sequence; it does not know about today's jam.
- Today's speeds. Traffic Flow measures, at the moment the flow runs, the current speed on the roads around each place, the speed when they are clear, the jam factor from 0 to 10 and a level in words from Free flowing to Standstill. It does not count cars and has no peak hours of its own: you learn the peaks by running it at the hours you care about.
- Closures. Traffic incidents lists road closures, roadworks and other incidents in an area right now, with where they are.
Used together they answer the three questions a coordinator asks at 06:30: which order, how bad are the roads near today's stops, and is anything closed on the way.
A day plan built around the jams
- Give each rep a district, not a list. Shops in the same part of the city, visited on the same day, cut the long drives that jams punish most. Split by territory shares the stops out by area, so each rep's are close together.
- Start inside the district. If a rep lives near their district, the first stop can be ten minutes from home; the cross-town drive to the office is the trip to avoid.
- Put the far stop first or last. The stop furthest from the rep's base belongs early, before the peak builds, or at the end of the day, when the rep is heading that way anyway.
- Leave room for each visit. Route planner's times are road times only. Add your usual minutes per stop when deciding how many stops fit.
- Check the roads before leaving. A morning reading of Traffic Flow at each stop and of closures across the city tells the rep which part of the plan to swap.
A made-up morning in Jakarta
Everything in this example is invented. A consumer goods company has four merchandisers in Jakarta, each visiting about eight shops a day. At 06:15 the AI employee splits today's 32 visits into four districts, orders each rep's stops from their home area, and reads the roads around every stop. For one rep it finds two stops in an area where the jam factor is already 8 and a closure on the main road between them. The note says: start with the three shops near home in the north of the district, move the two in the congested area to after 11:00, and avoid the closed road by going round the east side. The rep sees the plan on her phone before she starts the scooter.
The plan did not remove the jam. It moved the rep away from it, which is all a plan can do.
The AI employee that writes each rep's day
- Schedule: weekdays at 06:15 in the city's own time zone.
- My data: today's visits from a table (or new outlets found by Nearby places).
- Split by territory: between the reps you name.
- Route planner: one route for each rep, from each rep's start point, by car.
- Traffic Flow: the roads next to each stop, as they are at 06:15.
- xMap LLM: for each rep, name the stops in heavy or standstill traffic and suggest moving them later, using only the readings given.
- Email or WhatsApp: each rep's stops in order, with directions links and the note.
Add a second, smaller flow with Traffic incidents over the city at 06:00 that only writes when there is a closure near one of your stops. The Merchandiser visit plan for the week and Tower field visits around weather and closures templates are good starting points; Road closures in my city covers the closures part alone.
Mistakes that cost the morning
- Optimising stops across the whole city. The shortest route through 30 stops scattered across a jammed city is still a bad day. Fix the district first.
- Reading traffic once, the night before. Live speeds are true at the moment they are read. A reading at 21:00 says nothing about 08:00.
- Expecting a car count. Live traffic data gives speeds and congestion, not the number of vehicles. Hour-by-hour car counts exist only for roads in the United Arab Emirates.
- Fitting too many stops. In heavy traffic, fewer stops visited properly beat many visits cut short. Set the number a rep can really do, and keep it.
Once visits are under way, check-ins on the phone record what happened at each stop, so tomorrow's plan can drop a closed shop or bring back one the rep missed.
Questions
Does Route planner avoid today's traffic jams?
No. Its times are for usual traffic on those roads, and it does not add time at each stop. Read Traffic Flow and Traffic incidents in the morning to decide which stops to move.
What does a jam factor of 8 mean?
It is a scale from 0 (free flowing) to 10 (standstill) for how jammed the roads near a place are at that moment. Around 8, traffic is heavy and a short distance can take a long time.
Can I plan for motorbikes or scooters?
Route planner plans by car, walking or cycling. In cities where reps ride scooters, car times are a fair guide for main roads but slower than a scooter in heavy traffic; treat them as an upper bound.
How often should the roads be checked?
Once before the reps leave is the useful minimum. A second reading around midday helps teams that plan an afternoon block of visits.