Route Planning and Optimisation
The use of location data with the clearest return and the least intrusion, because it works on rounds rather than on people.
Of everything in this field, routing is the use that produces measurable savings without needing to identify anybody.
What it uses
Historical journeys in aggregate: how long legs actually take, at what times of day.
Real travel times rather than map estimates, which for urban work differ substantially.
Service durations by job type, so rounds are sized from reality.
Depot and site locations.
None of this requires knowing which driver made which journey, and stripping the identifier before analysis costs nothing.
What it produces
Rounds that can actually be completed, which is the largest single source of overtime, rushed work and missed appointments.
Better appointment windows, which customers notice more than anything else in the operation.
Fuel and mileage reduction, which is the number that funds it.
Fewer callbacks, where jobs stop being rushed to make the round.
The honest caution about savings
Vendor figures assume the round was badly planned before, which is sometimes true.
Measure your own baseline first: distance per job, jobs completed per day, overtime hours.
Compare like periods, because seasonality dominates in most field operations.
And attribute carefully. A round that improves after optimisation may have improved because it was resized, which is a planning decision rather than a software one.
Where optimisation goes wrong
Rounds optimised to the theoretical maximum, with no slack, so a single delay cascades through the day.
Service durations taken from averages when the distribution is wide, which guarantees half the jobs overrun.
Breaks not modelled, which produces rounds that are only achievable by skipping them — a legal problem as well as a practical one.
Traffic modelled as an average, which is wrong twice a day in both directions.
Build in slack deliberately. A round planned at ninety percent of capacity completes; one planned at a hundred does not.
Doing it without identifying people
Aggregate before analysis.
Report at round level, not driver level.
Which also removes the temptation to compare drivers on rounds that are not comparable.
And it means the routing use can continue even where individual tracking is turned down or off, because it never needed the identifier.
The conversation worth having first
Ask the drivers which parts of the round do not work.
They know: the customer who is never in before ten, the street with no parking, the site that takes an hour to get into.
A fortnight of that produces improvements that no amount of data will find, because none of it is in the data.
Strip the identifier
A step that costs nothing and removes a temptation.
Route patterns are a property of the round, not of the driver.
Aggregate before analysis so the optimisation works on journeys rather than on people.
Which means this use survives even where individual tracking is turned down or switched off.
And it removes the possibility of the routing project quietly becoming a driver comparison, which is the drift to watch for.
Turn the principle into a test
For an example that can make this requirement testable, consult project time tracking application. Treat the page as a starting point rather than proof: reproduce the workflow with real roles, failures and permissions.
Independent reference
For an external point of reference, see OpenStreetMap. This widely used mapping project offers a useful comparison point for map data and route-related assumptions.