Lanepost assigns tomorrow's loads to the right driver, checks every truck against its booked slot, and messages the customer the minute a drop slips.
A sick call, a closed A-road, a missed slot. Here is what Lanepost did with each before your planner had finished the first coffee.
Lanepost reads your TMS, telematics and tachograph data, proposes the move, and waits for a yes on anything outside your rules.
Lanepost weighs drivers' hours, trailer type, start postcode and the customer's booking window, then lays out the plan. Your planner reads it once and approves.
Telematics, live traffic and tacho breaks feed one ETA per drop. When a delivery drifts past its window, the planner sees it before the driver rings in.
When T14 runs late, Lanepost checks what it was due to collect next, finds the nearest driver with hours left, and offers the swap.
One late drop, from the closure on the M62 to the goods-in manager's reply. Four minutes, no phone calls.
M62 J27 closed eastbound.
LP-2207 now 07:52, 22 min late. Bay 4 still OK?
Drivers' hours, trailer fit and the customer's booking window are checked on every suggestion. Breaking one needs a named person.
4 h 28 m drivenBreak due 11:40Tacho data in, so no load is offered to a driver who can't legally finish it.
26 palletsCurtainsiderPallet count, tail-lift and reefer needs matched per load.
Goods-in 06:30Retail DC windows read from the customer's portal.
Sample figures from 40-, 84- and 150-truck fleets, shown here to illustrate the kind of change to expect.
Planning speedloads assigned per planner hour, up from 11
On timeof drops inside the customer's booked slot
Calls avoided"where's my delivery" calls avoided a month
Start with one depot. Lanepost earns each new right only after your planners have watched it get the last one right.
Reads your TMS and telematics, plans alongside your team, changes nothing.
Planners accept or reject each proposed load; every no teaches it your rules.
Routine loads go out on their own; edge cases still wait for a person.
Late-drop emails and texts go to goods-in contacts you have approved.
A sample quote from a pilot fleet, shown for illustration; names and firms on this page are fictional.
We used to hear a drop was late when the DC rang us. Now goods-in has the email before my planner has finished his first brew.
Every planner, depot and customer contact is included. The first four weeks are a free pilot on one depot.
Over 150 trucks or running cold chain? Volume and reefer-temperature tracking are priced with you.
Systems, what it does without asking, and what your drivers and customers see.
Our team ran traffic offices before building this. Calls answered from Stoke, 06:00 to 18:00.
Email the teamNo. Lanepost reads loads from your TMS and writes assignments back to it, so invoicing, PODs and your reports stay where they are.
The common fleet telematics and tachograph download services connect in the first week. If yours isn't on the list, we build the link during the pilot.
Delay alerts work from day two. Load suggestions are useful by the end of week two, once it has seen how your planners decide.
Only what you switch on: routine assignments under your rules and late-drop messages under your time limit. Everything else waits for a planner.
It never offers a load a driver can't legally finish. Overriding that needs a named person, and the override is logged.
Replies land on the load. Anything it can't answer, such as a refused delivery, goes straight to the planner on shift.
No. Drivers keep their current handheld or app; Lanepost sends job changes through it.
In UK data centres, encrypted at rest and in transit, and never used to train models for other customers.
Yours. Messages go out from your domain with your depot's phone number.