How today's traffic changes the best route through the day's visits
A visit order planned on usual traffic can be wrong by nine o'clock. How to check it against live road speeds and closures each morning, and when to change the order.
Part of the guide Location intelligence automation
A route that is best on an ordinary day stops being best when one part of the city jams or a road closes. The fix is not to plan from scratch every hour: plan the order of visits on usual travel times, then, early in the morning, check the live speed and any closures around each stop, and move the stops in the worst-affected areas later in the day or to another rep. Most mornings nothing changes. On the mornings that matter, the check saves an hour of sitting still.
This is for field service managers, sales managers with reps on the road, and dispatchers who send technicians, merchandisers or inspectors out each day. It explains what a route planner can and cannot know about today, what live traffic data adds, a made-up morning in Sao Paulo, and an AI employee that does the check before the first van leaves.
What the planned route already knows
Route planner puts the day's stops in the best order from a start you pick, on the roads, by car, on foot or by bike, as one route or one per rep. Its times are travel times for usual traffic. That is the right basis for planning: usual traffic is what most days look like, and an order built on it holds up well on an average Tuesday.
What it does not know is this morning: the lorry that overturned on the ring road at six, the water main repair that closed a bridge, the rain that slowed the whole east side. Those are the things that turn a sensible order into a bad one.
What live traffic adds
- Traffic Flow measures, at the moment the flow runs, how traffic is moving on the roads around each stop: the current speed, the free-flow speed, the jam factor from 0 (free) to 10 (standstill), the congestion as a percentage, how many roads are closed and the busiest road. It does not count cars and has no forecast; it describes now.
- Traffic incidents lists closures, roadworks and other incidents across the area, with where they are.
- Weather forecast gives the rain hour by hour, which explains many slow mornings before they happen.
Put together, they answer the only question a dispatcher has at 6:30: which of today's stops sit in a part of the city that is moving badly right now?
When to change the order, and when not to
Not every slow road justifies a change. A rule of thumb that works for many teams: leave the order alone unless a stop's area is heavy or at a standstill, or a road next to it is closed. Then ask three questions.
- Can the stop move later in the day? Many visits have no fixed time; moving a stop from first to last often clears the problem.
- Can another rep take it? With routes per rep, a stop on the edge of two territories can switch to the rep coming from the side that is moving.
- Does the customer need to know? A technician who will be late should send word before the window opens, not after.
A morning in Sao Paulo (made up)
Say an equipment maintenance firm has three technicians covering twelve client sites across the south of Sao Paulo. Everything below is invented to show the logic.
- At 6:15 the flow reads the day's twelve visits from a sheet in Google Sheets the planners filled in the afternoon before.
- Route planner orders them into three routes, one per technician, from their usual starts.
- Traffic Flow measures the roads within 500 metres of each stop: two stops near a riverside avenue come back Heavy, with a jam factor above 7 and one road closed.
- Traffic incidents confirms a closure on that avenue from roadworks.
- xMap LLM reads the routes and the traffic and writes one line per technician: move the two riverside visits from second and third to the end of the day, and warn one client of a later arrival.
- At 6:25 each technician gets the message on WhatsApp; the dispatcher gets a summary by email.
On the eleven other mornings of that fortnight, the same message says the routes stand as planned, which is useful too: nobody second-guesses the plan.
Mistakes that make live checks useless
- Checking too late. A check at 8:30 after vans left at 7 changes nothing. Schedule it before departure.
- Reacting to every amber road. Moderate congestion at rush hour is normal and already in the usual times. Act on heavy, standstill and closed.
- Reordering by hand. If the change is a rule, write the rule once in the flow instead of asking a dispatcher to judge it each morning.
- Forgetting the return. If routes end back at the depot, check the roads around the depot too.
Setting it up as an AI employee
In xMap Flows, several templates hold the parts. Merchandiser visit plan for the week orders visits with Route planner. Road closures in my city watches incidents every morning. Road closures and storms at today's install sites combines closures and weather for a field team. Start from one, add Traffic Flow after the route, and tell the AI step your rule in a sentence: move flexible stops in heavy traffic to the end, keep fixed ones, and say who to warn.
The Learn page on route planning covers the planning side; the help article on the Route planner lists every field each stop gets, and the logistics industry page has more flows for teams on the road.
Questions
Does the Route planner use live traffic?
No. It orders stops on travel times for usual traffic. Live conditions come from Traffic Flow and Traffic incidents, which a flow can check around each stop just before departure.
Can live traffic data tell me how many cars are on a road?
Traffic Flow gives speeds and the jam factor, not car counts. Hourly car counts exist only for roads in the United Arab Emirates, through Regional data.
How often should the check run?
Once, shortly before vans leave, suits most teams. For long days, a second check at midday covers the afternoon's stops.
Can the flow tell the customer about a delay?
It can write the message and send it by email or an app such as WhatsApp. Many teams have it go to the technician or dispatcher first, who forwards it.