Delivery route optimisation for rental dispatch

Ask most rental operators what a delivery costs and they will quote you fuel and a driver's hour. The real number is bigger and lives in the parts nobody measures: the truck that drives across town twice in one morning, the collection that gets scheduled as if the vehicle teleports back to base, the failed drop that becomes a second trip tomorrow, and the empty return leg that carries nothing but air.

Route optimisation is not a luxury for large fleets. For a rental business it is one of the few levers that improves margin without raising prices or cutting service. Every mile you do not drive is pure saving, and every stop you sequence properly is time your driver spends delivering instead of navigating.

The goal is not a fancy algorithm. It is a dispatch discipline: group the right stops together, put them in an order that respects geography and time windows, prove each one happened, and feed the whole thing off live equipment availability so you never send a truck for kit that is not actually free. Get those four things right and the gaps between stops stop leaking money.

The most expensive habit in rental logistics is treating deliveries and collections as separate operations. A truck goes out full and comes back empty in the morning, then goes out empty and comes back full in the afternoon. That is two runs doing the work of one, and it doubles the mileage on routes you were driving anyway.

The fix is to batch by geography and time, not by transaction type. If you are delivering to a customer near where another customer's hire is ending, that outbound truck should come home with the returning kit on board. Every collection folded into an existing delivery route is a trip you did not have to make. Over a week, on a busy fleet, that consolidation is the difference between five trucks and four.

Batching only works if your dispatch view shows deliveries and collections on the same map for the same day. When they live in separate lists or separate people's heads, the overlaps are invisible and the savings never happen. Renttix surfaces upcoming deliveries and returns together, so the person building the day's runs can see which collection sits neatly on the way back from which drop — and load the truck once for both directions.

Batching decides which stops go on a run. Sequencing decides the order — and a bad order can waste as much fuel as a missing batch. The instinct is to sequence by booking time or by whoever called first. Geography does not care about your booking system. A route that zigzags across a city because stop three was booked before stop two burns fuel and hours for no reason.

Sequence by proximity first, then bend the order to respect hard constraints: a site that only accepts deliveries before 10am, a customer who needs kit for a job starting at a fixed hour, an access window on a controlled site. The art is fitting the fixed points into an otherwise geographically efficient loop, rather than letting one time window scatter the whole route.

There is a load-order payoff too. When stops are sequenced properly, the truck is packed in reverse order of delivery — first drop at the tail, last drop at the nose — so the driver is never shifting equipment around at the roadside to reach the item they need. That is minutes saved at every stop, which across a full route is another delivery you could have fitted in.

The moment equipment leaves your yard, you lose visibility unless the driver carries a tool that keeps you connected. A driver app is that tool. It gives the driver the day's sequenced stops, turn-by-turn navigation, and a way to record what actually happened at each one — arrival time, who received the kit, condition on handover, and a signature or photo as proof.

Proof of delivery is where the app pays for itself. The classic dispute — "it never arrived," "it was already damaged," "nobody signed for it" — evaporates when you can produce a timestamped photo and a signature captured at the point of handover. That record protects your late fees, your damage charges, and your invoice, and it does it without a phone call.

There is an operational dividend beyond disputes. When a driver marks a stop complete in the app, the office sees it in real time. Dispatch knows the run is on schedule or slipping, the next customer can be given an accurate window, and the equipment's status updates the instant it changes hands. Renttix connects driver activity back to the order and the item, so proof of delivery is not a photo lost on someone's phone — it is attached to the hire, where every downstream charge and record can rely on it.

A failed delivery is the most expensive event in your day. You have paid the fuel, the driver's time, and the vehicle wear to arrive at a locked gate or an absent customer — and you have to pay all of it again tomorrow to try once more. Worse, the failed drop displaces a stop you could have made, so it costs you twice over.

Most failed drops are preventable with information the customer already has. Confirm the delivery window the day before, get a site contact and access details onto the run, and give the customer a realistic arrival time so someone is there to receive the kit. A driver app that lets the customer track the approaching truck removes the single biggest cause of failure: nobody home. Industry cost benchmarks put a truck's fully loaded running cost well into the tens per hour before you count the equipment sitting idle on board, so one avoided re-run pays for a lot of prevention.

Empty return legs are the quieter leak. A truck driving back to base with nothing on it is capacity you paid for and did not use. This is where batching and sequencing meet: the disciplined operator plans the return leg as carefully as the outbound one, filling it with collections so that no mile is driven empty when kit is waiting to come home along the route.

The most damaging routing error is not a wrong turn — it is dispatching a truck for equipment that is not actually available. It happens when the delivery schedule and the equipment availability live in different systems, or in the same system but out of sync. The truck arrives, the kit is still out on another hire, still in the workshop, or already promised to someone else, and the run collapses.

Dispatch has to be built on live availability. Before a delivery is ever scheduled, the system should confirm that the specific item — not just the product type — is free for that date, at that quantity, and not committed elsewhere. When availability and dispatch are one connected view, you cannot route a truck for kit that does not exist to send.

This is the payoff of running routing inside your rental platform rather than a standalone mapping tool. Renttix ties dispatch to real-time availability, so a delivery can only be scheduled against equipment the system knows is free, and every completed run — outbound or collection — updates availability the moment it happens. The route you optimise is a route you can actually drive, because the equipment behind every stop is genuinely there. That connection between the map and the stock is what turns route planning from a wish into a schedule.