Why manual route planning eats your morning
Most small fleets plan routes from the dispatcher's memory. Yesterday's traffic, this week's regular customers, which van had a flat tyre on Tuesday, which driver knows the back roads of Edenvale. That works at five drivers. It quietly fails at fifteen.
The hidden cost is not the planning hour itself. The cost is rework: backtracking, missed delivery windows, drivers waiting on the side of Witkoppen Road for new instructions. Every one of those compounds with fleet size.
What route optimisation actually buys you
A route optimiser takes a list of stops, the fleet's constraints, and the day's traffic shape, and produces an order. That is the entire feature. It does not solve dirty address data, missing parcel weights, or a customer who changes the drop-off location at 09:14.
The useful framing: optimisation is a multiplier on clean inputs, never a substitute for them. A great optimiser running on bad data is worse than a manual dispatcher with a notebook, because it produces a confidently wrong plan in less time.
Five things to fix before you write a cheque
- Address quality. Two-line “next to the Engen” addresses cannot be optimised. Capture latitude and longitude, or at least a clean street, suburb, and postal code on every intake.
- Promised time windows. A driver who arrives at the right address at the wrong time still books a failed delivery. Push the customer's window into the delivery record at intake, not into the dispatcher's head.
- Realistic service durations. A drop at a quiet residential gate is two minutes. A drop at a Pretoria security estate with biometric access is fifteen. Optimisation is off by thirty percent if every stop is hard-coded to “5 min”.
- Driver and vehicle constraints. Vehicle size, parcel volume, suburb familiarity, cash-on-delivery permissions. These belong in the data, where the system can actually act on them.
- Feedback loops. A plan optimised at 06:00 is stale by 09:00. The loop where drivers can flag exceptions, and the plan adapts during the day, matters more than the cleverness of the morning solver.
How CouriB approaches route work today
CouriB keeps route-related delivery work visible to dispatchers and drivers so the team can coordinate the plan before the day gets noisy. Address context, parcel context, driver assignments, and the delivery calendar all live on one record. There is no whiteboard side-channel where the real routing decisions hide.
Our public road map for routing is intentionally conservative. The route planning page describes workflow visibility today rather than promising automated optimisation outcomes we have not signed off on. We would rather ship route automation honestly, in steps, than market a flash demo and walk it back later.
Where to start tomorrow
Score yourself on the five points above before booking a vendor demo. Below three out of five, no tool will make routing materially better — fix the inputs first. At four or five out of five, evaluate options on operational fit, not on feature-list length.
Running a small South African courier fleet? The small-fleet use-case page is the closest match for what CouriB tries to solve, and the dispatch features page is the right next read after this one.