OptiRoute: See where every route-day's time really goes

Metric	Expected	Actual	Difference
Stops	24	24	0
Drive time	3h 05m	3h 21m	+16m
Service time	4h 40m	4h 28m	−12m
Total	8h 55m	8h 59m	+4m

Long days nobody can explain.

“The route sheet says one thing, the truck did another, and I find out a week later, if at all.”

“I can't tell whether a long day was traffic, a slow stop, or a bad stop order.”

“Our expected stop times are guesses someone typed in years ago.”

“When five accounts share a building, half our reports either double-count them or lose them.”

Know what your routes really cost. Then fix them.

Four things OptiRoute does for every route, every day.

Drive & service time, in full view.

Truck GPS shows what happened. Routing the stop order your dispatch system gave the driver, with typical traffic, shows what should have. OptiRoute puts them side by side and splits the difference into drive time and service time.

Expected, actual and difference for stops, miles, drive, service and total time.
The whole day: clock-in, setup, departure, stops, arrival, wrap-up, clock-out.
A realistic service time learned for every account from real GPS dwell. Dispatchers can correct it, and every change is logged.
Each stop gets a verdict with a plain reason, or none when the data can't support one.

Route 12 · Tuesday · Day timelineSample data

Expected

Actual

Setup / wrap-upDriveService

Many accounts, one site.

About one in five accounts shares a site with another: a hospital's departments, a plant's cost centers. OptiRoute matches each GPS stop to the accounts scheduled on that route, gives each its own row, and splits the shared time instead of copying it.

Shared site3 accounts

Account A8m

Account B6m

Account C4m

One visit, 18m on site. Split, scored once, marked shared.

Closing the loop, in stages.

Most routing tools stop at "here is a better route." OptiRoute carries it to your dispatch system one stage at a time, and checks each one.

MeasureRebuild what the driver did from GPS.
ProposeRe-sequence the stops to cut drive distance.
PublishSend the confirmed order to dispatch.
VerifyConfirm it was applied exactly as sent.

In the first pilot publication, all 36 stop positions were applied exactly as sent.

Route 7 · Stop orderSample data

ScheduledProposed

Sent to dispatchApplied exactly as sent

Schedules that follow reality.

Holidays, redates and customers that can't be served shuffle the week. OptiRoute keeps every delivery accounted for.

Deliveries moved to another day show on both days, so nothing silently disappears.
Stops that could not be served are flagged, not lost.
Coming soon: holiday & service-day planning.

Route 4 · Holiday weekSample data

Wednesday

Account A
Account B
Account DMoved to Thu
Account FNot served
Account G

Thursday

Account H
Account DFrom Wed
Account J
Account K
Account L

Reports & trends.

Roll any view up from a day to a week, month or year, and watch how expected service time moves per route and per account.

Drive, service and total time as expected, actual and difference, plus miles.
A weekly trend of expected service time per route and per account.
Shareable links, and Excel and CSV exports.

All routes

Metric	Expected	Actual	Difference
Drive time	74h 10m	78h 32m	+4h 22m
Service time	112h 05m	109h 40m	−2h 25m
Total	214h 30m	216h 12m	+1h 42m
Miles	2,016	2,140	+124

Expected service time per stop, weekly · sample data

Measured on live routes.

36 / 36

stop positions applied exactly as sent in the first pilot publication.

8.37 h

median workday measured by OptiRoute, against 8.35 h on official time cards.

3,500+

customer accounts and 30+ trucks, every day.

Internal measurements on live operating data.

Built inside a real laundry operation.

OptiRoute was built inside a regional uniform & linen provider's route operation and is used there every day.

Real trucks, real routes, real payroll. Not a demo dataset.

300+

improvements shipped to the live system since June 2026.

Works with your systems.

No need to replace dispatch. We connect to your telematics and route system during the pilot.

Today

Your GPS / telematics provider
Your route-accounting / dispatch system

Discussed per pilot

Other telematics providers
Other route-accounting and ERP systems

Questions

Do we need to replace our dispatch system?

No. OptiRoute works alongside it, reading your schedules and writing back confirmed stop orders.

What telematics do you support?

We connect to your GPS / telematics provider during the pilot.

Does it build routes from scratch?

Not today. It optimizes the stop order within your existing routes.

What does a pilot look like?

A small set of your routes, connected to your data, reviewed together.

Is our data safe?

Per-customer deployment, role-based access, and an audit log of every change.

Run a pilot on your own routes.

A small set of routes, connected to your telematics and route system, reviewed together. Early access for operators running 10–80 routes.

pilots@opti-route.ai