The AI agent for transport & logistics: keep the delivery promise, without overloading operations

Four files taken in hand this morning, with no request from you — each one still inside its useful window.
· 47 delivered shipments are waiting for their proof of delivery to be scanned, 12 of them for more than 30 days. That proof is what wins a claim: next turn I tell you which ones can be recovered, and in what order.
· A haulier has been working for 9 days on a goods insurance certificate that lapsed on 29/07, across 14 consignments. The request for an up-to-date certificate is already written: he is covered again the moment he sends it back.
· Eight lines on a haulage invoice exceed the agreed rate by 12%, all with the same subcontractor — caught before payment, so still negotiable.
· Your operating licence comes up for renewal in 47 days, and the financial standing evidence takes your accountant three weeks: 26 days of margin, and the request goes out today on one word from you. morning-watch_4-flags.pdf4 flags · shipments and consignments concerned
⛓ Source · proofs of delivery, subcontractor certificates, haulage invoices, regulatory deadlines

35 of 47, and I will tell you which come first — because the clock is not the same for all of them.
What I found:
· 35 exist on paper with three of your drivers, according to their run sheets. They are to be scanned, not reconstructed.
· 12 exist nowhere: no scan, no paper reported.
The order that matters: of the 12 that cannot be found, three relate to shipments the customer has already disputed. Those are the ones that cost today, not in thirty days.
For the 12 that cannot be found, I have prepared the only route left: a request to the customer for a delivery confirmation, drafted for each of the 12, with the date, the consignment and the recipient's name. It works, and it has a price: it means asking the party disputing to acknowledge receipt. So it is a commercial decision, and it gets signed — I have ranked the 12 by amount at stake and by age of the relationship, the three already-disputed shipments first. You point at one, two or none; the messages go out within the minute.
The list is sorted by claim deadline, with the three urgent ones first. proofs-of-delivery_47-missing.pdf35 recoverable · 12 not found, 3 urgent
⛓ Source · shipments, run sheets, open claims

I watch, continuously, what you have opened to me: delivered shipments against their scanned proofs, your subcontractors' certificates and their validity, haulage invoices against agreed rates, and your regulatory deadlines. A proof missing, a certificate expiring, a rate drifting, a licence approaching — I say so, I do not wait to be asked.
Routing follows your organisation: the missing proofs to operations, with the three drivers named in the message addressed to them and nowhere else; the uninsured haulier to the haulage manager and the director, because it is a company risk; the invoice to purchasing; the licence to the director, copied to the accountant.
With a chase: 12 h on the uninsured haulier — every run adds consignments; 48 h on the proofs; 7 days on the rest. Then a weekly summary: by subject, never by driver.

What this arrangement gives you, in figures. This morning's four flags arrived with their file already built: the 47 proofs sorted by claim deadline, the uninsured haulier with his 14 consignments and the certificate request already written, the 8 invoice lines with the gap to the agreed rate line by line, and the licence renewal with the list of supporting documents to request from your accountant. Stopping a haulage job, settling an invoice, closing a claim: those three are signed, because they commit the company towards a third party. I build each one in full and hand it to you ready — you decide on a complete file, in minutes, instead of rebuilding it over two days. An arrangement made by word of mouth on the dock enters the file as soon as I am told: one line is enough, and from then on it counts as a document, dated and attributed, like everything else.
✎ Proposal · watch and chases to be configured — you set the thresholds

486 quote requests over the quarter, qualified on arrival against four points: origin, destination, volume, deadline.
Without those four, a quote gets redone twice. 312 requests carried all four; for the other 174, the missing question went back within the minute, in one sentence, and 149 answered within 24 hours.
· 361 fall inside your rate card — groupage, pallet, part load on your regular lanes. The quote goes out priced, with the transit time and the applicable conditions. Average response time: 4 minutes, against 1 day and 3 hours before.
· 125 fall outside it — out of gauge, regulated goods, destinations off your lanes, or volumes that warrant a negotiation. Those become a prepared sales meeting: the file reaches the salesperson with the four points, the customer's history where there is one, and the estimated cost of the lane.
Collections are planned straight away, not by hand: 212 collections booked over the quarter, each with its slot, the dock or loading address, the equipment needed — tail lift, pallet truck, straps — and the driver whose round already passes nearby. 34 were merged into an existing round, saving 610 km over the quarter.
What went wrong, and how I closed it: 19 collections were booked on a vehicle with no tail lift when the customer has no dock — 19 wasted journeys in three weeks. I was reading the round and not the vehicle record. Loading equipment is now a condition of the booking: a collection with no compatible equipment is not booked, it goes back to operations with the two vehicles that could take it. No wasted journey across the following 96 collections.
⛓ Sourced · rate card, route plan, vehicle and dock records