The whiteboard has been costing you a van.
Dispatch by memory works, in the sense that the jobs get done. It just quietly spends more fuel, more hours and more vehicles than the same day needs — and nobody can see it, because there is nothing to compare against.
One morning, planned two ways
Switch between them. Same twelve jobs, same three vans, same windows — both schedules are computed, not drawn.
12 jobs, 3 vans, one depot — the same day, planned two ways.
- Driving
- 307 km+26
- Windows missed
- 1+1
- Vans needed
- 3 of 3
- Last one back
- 14:06
What actually changed
Distances are straight-line across Riyadh with the usual 1.35 road factor, so the figures are the right order of magnitude rather than a flattering guess.
- 26 km less driving
- 9% off one morning. It is not a dramatic number on a single day, which is rather the point — it is the same 9% every day of the year, on fuel you have already budgeted.
- The missed window disappears
- The hand-dispatched day arrives at Ash Shifa at 12:47 for a window that shut at 11:00. That is the call you take at four o'clock, and the credit note that follows it.
- Everyone back 9 minutes earlier
- 13:57 rather than 14:06, with no van running past the end of its shift. Overtime is the cost nobody puts in the fleet budget because it arrives on the payroll line instead.
- The work spreads 5/4/3
- Rather than 4/4/4 by round-robin. Dealing jobs out evenly is not the same as planning them evenly — one of those accounts for where the vehicles actually are.
A plan that ignores reality is not a plan
Optimisers that only minimise distance produce schedules your drivers quietly ignore. These are constraints, not preferences.
Time windows
A customer who takes deliveries 09:00–11:00 is not offered 14:30.
Vehicle type
A three-tonne drop does not get planned onto a panel van.
Driver hours
Shift start, break and finish are inputs, not something to apologise for later.
Skills and permits
Site inductions and licence classes are matched before the job is offered.
Capacity
Volume and weight, so a van is not planned to carry what will not fit.
Site access
Height limits, gate hours and the yards that will not take an artic.
The driver never sees a plan, only the next job
A schedule that needs explaining will not survive contact with a wet Tuesday. The app shows one thing at a time, in Arabic by default.
-
Assigned
The day arrives on the phone before the shift starts. No paper run sheet.
-
Navigating
One tap to the next drop, in the app the driver already uses.
-
On site
Arrival is detected from the geofence, not typed in.
-
Proof
Signature, photo or barcode — whatever that customer requires.
-
Done
Dispatch sees it complete the moment it happens, not at end of shift.
Stop 3 of 8
Olaya district
Window 08:00 – 10:00 · 15 min
4.2 km · 11 min
Next
Shifa clinic · 10:15
Jobs come from wherever you already keep them
Nobody wants a second system to type orders into. Push jobs in from your ERP or order system, pull proof of delivery and utilisation back out — same API, documented and versioned.
Integrations{
"reference": "SO-88214",
"customer": "Olaya district",
"address": { "lat": 24.6908, "lng": 46.6853 },
"window": { "from": "08:00", "to": "10:00" },
"service_minutes": 15,
"requires": ["tail-lift"],
"proof": ["signature", "photo"]
}The rest of the platform
Live tracking
Position, speed and ignition every ten seconds.
Asset and trailer tracking
Trailers, generators, plant and containers.
AI dashcam
Road and cabin, clipped to the event.
Driver behaviour
Scored per driver and per trip.
Incident centre
Footage, telemetry and witnesses in one file.
Maintenance
By odometer, engine hours or date.