Most route planning tools can put stops on a map and draw a line between them. Far fewer let a route planner make the small tweaks that take a route from being theoretical to practicel. Tweaks like pulling a job off one run and onto another, seeing exactly how long a driver will sit waiting at a dock, adjusting a single stop, or reporting how many pallets and kilograms each vehicle is carrying.
These capabilities are so small and mundane that planners forget about them when they're evaluating software, and only after they've bought a solution and are using it day-to-day they notice it's missing. This guide covers the features that separate a genuine route optimization platform from a basic mapping tool, and why each one matters to the people building routes every day.
What features does route planning software need?
At a minimum, route planning software for a commercial fleet must:
- Edit routes directly on the map itself, including moving stops between routes and changing the stop sequence
- Report driver working time, job counts and load by weight, volume, cartons or pallets for every route
- Show the actual driven path between stops, not a straight line
- Break down waiting time, service time and driving time at every stop
- Flag constraint violations such as missed time windows or overloaded vehicles
- Model "what if" scenarios before you commit to a change
If a tool can't do these things, planners end up working around it. That costs time, and the workarounds usually replicate the inefficiencies the software was bought to fix. For a broader checklist, see our guide on how to pick the best route optimization software.
Why do route planners need to edit routes directly on the map?
A perfectly optimized route is almost never actually practical. It looks great in theory and doesn't translate to the real world. It might be that a customer calls to change a delivery window, a driver knows a loading dock is blocked every morning, drivers have personal preferences for which intersection to turn at, or two stops on opposite sides of a highway ended up on the same run. A planner needs to fix these individual pieces of a route without starting from scratch each time.
Map-based route editing should let planners:
- Drag and drop stops to change the order a driver visits them
- Move stops between routes without re-entering data
- Select and transfer groups of stops at once using a lasso or multi-select tool
- Reverse a route when the run makes more sense backwards
- Re-optimize or recalculate ETAs after manual changes, while keeping the stop order they've locked in
- Optimize parking so drivers aren't looping the same block for a new parking spot for two close-by stops
In Adiona, planners can make all of these changes on the map, then resequence, re-optimize or recalculate ETAs for the edited route. The plan stays practical without losing the benefit of optimization. We've written more about why this balance matters in Adiona's top route optimization tools.
Tools that lock the output, or force planners to export, edit and re-import, are a sign that routing was bolted on rather than built in. The planner ends up trusting the optimizer less, and drivers end up ignoring "perfect" routes that don't match the road.

What route summary reports should a route planning tool provide?
A route plan is only as useful as the numbers behind it. Planners, operations managers and finance teams all need answers to the same questions, that is, how long will each driver work, how many jobs are on each run, and how full is each vehicle?
Strong route planning software produces a summary for every route that includes:
- Driver working time, split into driving, service and waiting time
- Job and stop counts per route
- Load by any dimension your operation uses, such as kilograms, pallets, cartons, or volume
- Asset utilization, so you can see which vehicles are under-used
- Distance, cost including tolls, and emissions for each run
Adiona's route stats include arrival, departure, service, waiting, driving time and toll cost for every stop and route, including depots. Capacity is configurable across multiple dimensions, so a pallet freight operation and a parcel courier can each report in the units they actually plan around. Individual route plans can also be printed as PDFs for drivers or depot teams.
Without this level of reporting, it's hard to track the KPIs that matter for delivery fleets, and even harder to explain to a customer what a service will actually cost.
Why should route planning software show the actual route between stops?
A straight line between two pins (or even worse, a spreadsheet without a map interface) tells a planner almost nothing. It hides one-way streets, river crossings, toll roads, and the traffic a driver will hit during peak hour. When a tool can't show the real route, planners can't sense-check the plan, and the ETAs it produces are guesswork.
Look for software that:
- Draws the turn-by-turn route between each stop
- Uses traffic-aware travel times rather than straight-line or free-flow estimates
- Accounts for vehicle type, because truck routing isn't just car routing with a bigger vehicle
- Can calculate toll costs along the route
Adiona's route polylines show the exact path a driver will take, and routes can be optimized with stop-by-stop toll costs. Travel times are built on commercial mapping and traffic data, so the plan reflects real roads rather than distances on a grid. This is also why accurate real-time delivery ETAs are possible once the route is on the road.
How do you measure driver waiting time in route planning?
Waiting time is one of the most expensive hidden costs in delivery. A driver who arrives 40 minutes before a receiving window opens is being paid to sit in a car park. Multiply that across a fleet and a month or a year and it can be the difference between needing 20 drivers and needing 15.
Good software shows:
- Planned arrival and departure times at every stop
- Waiting time caused by early arrival against a time window
- Service time on site, modelled on the job rather than a flat default
- Suggested route start times that cut unnecessary waiting
Adiona reports waiting time for every stop and every route, and can suggest start times so drivers don't leave the depot earlier than they need to. Planners can then make an informed call: shift the start time, resequence the run, or renegotiate a delivery window with the customer.
How does route optimization software handle constraint violations?
Real operations break rules sometimes. A must-have delivery doesn't fit the time window, or a vehicle runs slightly over capacity on a peak day. The worst outcome is software that hides this, or refuses to produce a plan at all.
Adiona flags time window, capacity and other constraint violations directly on the plan, and still lets planners make an operational override when the business needs one. The planner stays in control, and nothing is left to surprise the driver.
Why is scenario modelling important for route planners?

Many of the biggest routing decisions aren't about today's runs at all. They're about the new customer you're quoting, the depot you're thinking of moving, or the vans you're considering replacing with EVs. Planners need to test those decisions on real data before committing to them.
Scenario modelling in Adiona lets planners:
- Clone jobs and run them against different fleet and vehicle combinations
- Model new business to price tenders on realistic service levels, as covered in winning new business using route optimization
- Test depot locations, fleet mixes, and EV transitions with the FlexOps Fleet Simulator
- Organize scenarios into divisions and share them with teammates using owner, admin, and user permissions
For freight and courier businesses, this is how routing turns into revenue. Our new business simulation page explains how teams use simulated routes, costs and impact on existing runs to submit more accurate proposals.
What data do you need to start using route optimization software?
Getting started shouldn't require a data science team. Adiona accepts data through CSV templates or the API, covering:
- Vehicles: capacity, depot, shift times, and vehicle type
- Customers and jobs: location, service windows, service duration, and load
Latitude and longitude are ideal, but Adiona can geocode addresses when coordinates aren't available. Planners can review and correct raw data, fix addresses, and clean up records before optimizing. Data hygiene matters more than most teams expect, which we've covered in cleaning logistics data with machine learning.
Is a telematics platform with a routing add-on good enough?
For route planners who need to edit runs, report on loads, and driver time, and model new business, usually not. A monitoring platform is built to report what already happened. A route optimization engine is built to decide what should happen next. We break down the difference in route optimization vs telematics.
Adiona is hardware-agnostic and works alongside existing tracking systems. Its engine is built to handle 10,000+ stops in minutes, and across our customer base, optimization has helped avoid more than 58 million miles of unnecessary driving.
Try route planning software built for route planners
If your current tool leaves you exporting to spreadsheets to answer basic questions, it's time to see what a purpose-built platform can do. Register for free access to Adiona's full route optimization suite and test the whole platform with your real data and requirements.
