Route planning used to belong to specialist software, or to a dispatcher with a whiteboard and a lot of patience. That’s changing fast.
These days a courier can do it in a chat window. Spoke’s free route planner tool handles up to 20 stops in a browser, with no account and nothing to download. It also works inside ChatGPT and Claude: you add it as an app or connector, ask for a route, and paste your addresses. A small form pops up in the chat. You confirm the address matches, set a start and end point, enter the time at each stop, and hit optimize.
That last field is where things quietly go wrong. Whatever number you type there is all the optimizer knows about that stop. The sequencing math is now nearly free. Knowing how long a stop really takes is as hard as it ever was.
Fifty stops is where guessing stops working
With six stops and a quiet Tuesday, almost any order works. Push it to 50, and the nearest-next-address habit falls apart.
Customers have delivery windows. Vans have weight limits. Drivers run out of legal hours, some roads ban trucks, and a pickup has to happen before its matching drop-off. Shift one stop and three others move with it. Once the stop count climbs, software beats even a sharp human planner, and this is the part where it does.
Four hours on screen, five and a half on the road
Here’s a made-up but very ordinary morning. A courier pastes 18 addresses into a chat, leaves the default stop time alone, and gets back a neat four-hour route.
Stop six is a hospital. The courier has to circle for parking, sign in at security, wait for the lift and chase a signature. Call it 25 minutes. The plan allowed a couple.
The day runs to five and a half hours, and three afternoon windows slip past. Nothing in the algorithm broke. It optimized beautifully around a number nobody checked.
That’s the risk with easy optimization. A route timed to the minute looks authoritative, so the assumptions underneath rarely get a second look.
So what does the AI part actually do?
Mostly, it predicts time. Mileage is a weak guide to how long a stop takes, since five miles across a downtown core can outlast 15 on an open highway. Machine learning models study past trips to estimate how travel time shifts by road, weekday, and hour.
They can learn stop durations too. A suburban doorstep might take two minutes and a high-rise office twenty, and a model with enough completed stops can tell the difference.
“Enough completed stops” carries a lot of weight in that sentence. The model needs clean geocodes, real-time on-site records, logged reasons for failed deliveries, accurate vehicle specs, and planned-versus-actual finish times. Plenty of fleets have half of that, recorded inconsistently. Fix those records before you shop for a cleverer algorithm.
Washington’s read on freight data
Federal planners have landed in a similar spot. The U.S. Department of Transportation released the 2026 National Freight Strategic Plan in May 2026, describing a network that moves more than 54 million tons of goods, worth over $68 billion, every single day.
One of the plan’s innovation objectives is promoting interoperable digital standards for freight data and operations. Data-driven planning runs through its other strategies too.
DOT’s February 2026 guidance for state freight plans spells out the AI piece directly. It observes that private companies increasingly use AI and machine learning to optimize routes, predict demand, and automate decisions, with gains in efficiency, fuel use, and delivery times.
So the models are already out there. Shared, usable data is the piece that’s still under construction.
Not every traffic jam deserves a new route
The plan you built at 7 a.m. can look silly by lunchtime. A crash closes a road, a customer cancels, an urgent pickup lands, a van won’t start. Dynamic routing tools weigh those events and decide whether to reshuffle stops or hand them to another driver.
Restraint matters here. Rebuild the route every time traffic slows and drivers stop trusting it, and frankly so would you. Better systems only replan when the expected gain is big enough to justify the disruption.
Some of the smartest routing happens before the day starts. If order history shows one zone spiking every Monday and another filling up toward Saturday, you can stage vans and drivers ahead of time.
The van knows things the model doesn’t
Ask any veteran driver about their route and you’ll hear things no database holds. That loading dock shuts from noon to one. The back street looks shorter on the map but scrapes the mirrors off the big van. The flower shop owner always needs an extra hand unloading.
A good routing setup gives that knowledge somewhere to go. Dispatchers should be able to override a suggestion and note the reason, and those notes become tomorrow’s training data. Farming has run into the same wall: with agentic AI on farms, building the plan turns out to be easy, and getting operators to trust it is the real work.
Dispatch jobs shift as a result. Software takes over the repetitive sequencing, and people keep the judgment calls. It’s one of the more concrete examples in the wider AI jobs debate.
At the door
No route survives a driver who can’t find the parcel. Load the van in stop order, keep devices charged, and make it quick to log a completion, an exception, or a proof-of-delivery photo. Each of those taps feeds the service-time data the optimizer leans on.
There’s a people side too. When several crews show up for one company at offices, clinics and managed buildings, front desks need to spot them fast. Branded uniforms, ID badges and custom patches on jackets help with that. They won’t change a single line of routing code. They might save a few minutes at exactly the stops where plans tend to slip.
Track the gap
Fewer miles can still mean a worse day. Save five miles, miss three delivery windows, and you’ve lost. These numbers are worth watching together:
| Metric | What it tends to reveal |
| Planned vs. actual route duration | Shaky service-time or traffic assumptions |
| On-time delivery rate | Windows the optimizer couldn’t keep |
| First-attempt success rate | Address, access or “nobody home” problems |
| Average service time by stop type | Stop types the model keeps lowballing |
| Cost per stop and driver overtime | Savings that never reached payroll |
When a route predicted at six hours keeps finishing at eight, dig in. Was it parking? Traffic? A missing constraint? Whatever you find should flow back into the planning data. Routing gets better through that slow feedback loop, more than through any single model upgrade.
The direction of travel is toward planning that keeps adjusting all day. DOT’s July 2026 AI initiative targets network optimization and less gridlock and supply chain friction, which suggests more connected data is on its way.
Even then, somebody still has to type the right number into that small field for stop six.
Related: How Can You Improve Brand Visibility in AI Search Engines in 2026?
