What leaves the building
Most delivery problems look like routing problems and are staffing problems wearing a route sheet.
Delivery volume in a seasonal rental business is not spread evenly. Changeover days carry the drops and the collections, and midweek carries the swaps and the repairs.
A roster built as equal shifts across seven days puts the same number of drivers on the heaviest day and the lightest one. The heavy day runs late and the light day pays people to wait.
Look at stops per day across four weeks of last season before writing this season's roster. The shape is usually sharper than anybody remembers, and it repeats.
A run sequenced by zone and time window beats a run built in booking order every time, and that gain is available to anybody with an hour and a map.
What sequencing cannot do is add a van. If Saturday needs eight trucks and you have six, the best sequence in the category moves the failure to a different stop rather than removing it.
The question to answer first is how many driver hours the heaviest day needs, then whether you have them, and only then how to order the stops.
The addresses come off the reservations. The run is built as one loop that turns right out of the depot and right back into it, so no road is driven twice and no stop is passed before its window opens.
A run that changes at eleven at night, after the driver has seen it, is worse than a slightly suboptimal run that everybody knows about.
Set a time after which tomorrow's runs are fixed and late bookings go to a second slot or the following day. That single rule converts a class of chaos into a known, priced constraint.
The platform side of this is that a run re-adapts when orders change: an order taken at half past ten lands in the right place on a loop already running rather than becoming a second trip at the end of the day. Route planning covers the mechanics and its limits, which include no traffic re-routing.
Most of the friction in a delivery week is the office not knowing where a run has got to, and answering guests by guessing.
Live position on the same screen as the stops turns that guess into a fact, and closed stops leaving the screen turns the map into a live audit of what was skipped. Delivery vehicle tracking covers what that reports and what it does not.
That is an operations tool rather than a monitoring one. It is no substitute for a driver scorecard, a payroll timeclock or an hours-of-service system, and it should not be sold to a team as one.
Open stops 6
Alerts
Van 1 leaves the depot with six stops in the order the run was built. Everything on the map is open work.
A second driver in an existing van raises stops per hour on routes with long stop times, because two people unload faster. It does nothing for a round whose cost is windscreen time.
A second van adds coverage on a day where the constraint is geography rather than hands. Working out which constraint binds is a matter of looking at the split between driving minutes and stop minutes across a real day.
Most operators guess at that split, and most guesses are wrong in the direction of blaming the route.
Around the shape of the week rather than as equal shifts. Changeover days carry the drops and collections while midweek carries swaps and repairs, so an even roster overloads the heavy day and pays people to wait on the light one. Look at stops per day across several weeks of last season before setting this season.
Sequencing the morning by zone and time window is the easy gain and it cannot add a van. Work out the driver hours the heaviest day needs first, set a cut-off after which runs are fixed, and give the office the same live view of the run that the driver has.
Depends which constraint binds. A second person in the same van speeds up rounds with long stop times; a second van helps when the cost is driving between stops. Compare driving minutes against stop minutes on a real day.
Yes. An order taken mid-morning is sequenced into a run already under way so it lands in the right place on the loop, rather than becoming a second trip at the end of the day.
No. It reports position and raises idle, braking and speeding events against the vehicle, driver and run. It is not a scorecard, a payroll timeclock or an hours-of-service compliance system.
A demo takes six fields and someone who understands rental operations calls you back. Where Bodhisys is the wrong fit you will hear it on that call rather than after three meetings.