Planning a sales day in a city split by a river
Bridges turn a short hop into a long wait. How to group visits by bank, cross once at the right time, and check the bridge approaches with live road speeds before you set off.
Part of the guide Location intelligence automation
In a city divided by a river, plan each half of the day on one bank and cross only once, at a time when the bridges are moving. Group the visits by bank first, put each group in driving order, then check how jammed the roads approaching your bridge are before you leave, and swap the order of the two halves if the morning crossing is crawling.
This is for field sales reps, merchandisers, service engineers and the managers who plan their days in cities such as Budapest, Seoul, Bangkok, Paris, Cairo or London, where a river cuts the map in two. It explains why a river breaks simple route planning, how to split and order the visits, a made-up day in Budapest, the planning mistakes that cost an hour, and an AI employee that sends each rep a plan in the morning.
Why a river breaks a simple plan
On a map, two shops on opposite banks can look a few hundred metres apart. By road they are as far apart as the nearest bridge makes them, and every rep in the city is queuing for the same few crossings at the same hours. Three things follow:
- Straight-line distance lies. Any plan that orders visits by distance as the crow flies will happily send a rep back and forth across the water.
- Bridges are bottlenecks. A crossing that takes five minutes at eleven can take thirty at half past eight. One badly timed crossing can eat the slack of a whole day.
- Each extra crossing compounds. Crossing twice means two queues, two chances of a closure, and a late finish that pushes visits into tomorrow.
Group by bank, then order each group
The planning rule is simple: decide the bank before you decide the order. For accounts you already serve, add a column to your customer table that says which bank each one is on; it takes minutes and never changes. For new places your flows find, draw each bank as its own area in the Area of interest and let Nearby places search them: each place found carries the name of the area it fell in.
Then give each bank its own route. Route planner can make one route for each value of a field, so a field holding the bank gives one route per bank, each in the best visiting order from a start you pick, with the minutes between stops. When the routing service plans on the roads, the bridges are part of the route; when it cannot and falls back to an estimate on straight lines, each stop is marked as an estimate, and in a river city that estimate ignores the water, so treat it with care.
Check the bridges before you set off
Route planner's times assume usual traffic. On the day itself, Traffic Flow reads the roads around a place right now: the current speed, the speed when the road is free, a jam factor from 0 (free) to 10 (standstill or closed), the congestion as a percentage and the busiest road. Put the approaches to the bridges you use in a small table and run Traffic Flow on them at 07:30. If the crossing you need is heavy, start on your own bank and cross late morning.
Live speeds do not tell you how many cars are on a bridge, only how fast they move, which is what matters for a rep. For closures and roadworks, Traffic incidents lists what is on the roads in an area right now, with where it is.
A made-up day in Budapest
This example is invented. A rep selling coffee machines in Budapest has nine visits on Thursday: four in Buda, west of the Danube, five in Pest, east of it. The office is in Pest.
Planned by straight-line distance, the day crosses the Danube four times. Grouped by bank, it crosses once. At 07:30 the morning check shows the approaches to the bridge nearest the first Buda visit at a jam factor of 8 and about a third of their free-flow speed, while the roads around the rep's Pest accounts are light. The flow suggests Pest first. The rep does five visits in Pest, has lunch, and crosses at 13:00 when the same approaches are free-flowing, finishing the four Buda visits before the evening rush builds on the way back.
Mistakes that cost an hour
- Trusting a map's straight lines. Order visits on the roads, or at least by bank first.
- Planning the crossing for the rush. Put the crossing in the middle of the day, when most bridges are quieter, unless the morning check says otherwise.
- Checking traffic once a month. Bridge traffic changes with events, roadworks and weather. A morning reading is worth more than an average.
- Forgetting the way back. A rep who ends on the far bank at five may spend the last hour in a queue. End on the bank where the office or home is.
- Splitting reps without the river. Fair-looking territories that straddle a river give one rep a day of crossings.
The morning plan, from an AI employee
- Schedule: every weekday at 07:15.
- My data: today's visits, each with its bank.
- Route planner: one route for each bank, starting from the office.
- A second branch reads your table of bridge approaches with Traffic Flow, the roads next to each one.
- xMap LLM on the whole list: which bank to start on and when to cross, from the jam factors only.
- Email to each rep.
What lands in the rep's inbox before they leave is the day's visits in two ordered groups, the minutes between stops, directions links, the current reading on each bridge approach and one line on which bank to start with. Templates such as Store visit route for a due diligence trip and Field sales routes to sign up new restaurants are close starting points; Road closures on cash-in-transit routes, every morning shows the closure check on its own.
Questions
Does a route planner know about bridges?
When routes are planned on the roads, yes: the bridges are part of the road network. If the routing service falls back to an estimate on straight lines, each stop says so, and that estimate does not see the river.
Can I see how many cars are on a bridge right now?
No. Live traffic data gives the speed, the free-flow speed and a jam factor, not counts of cars. Speed is what tells a rep whether to cross now.
How do I keep each rep on one side of the river?
Draw each bank as an area, or add a bank column to your accounts, and plan one route per bank. Share each bank's visits between reps only after that.
When is the best time to cross?
Usually late morning or early afternoon, but it varies by city and by day. A Traffic Flow reading of the bridge approaches at the start of the day tells you which way round to plan.