Tracking Documents & billing
The POD, collected the moment the truck unloads.
Autopilot asks for the paperwork at the dock, reads what comes back, checks it against the load, and files it into your TMS so the load can be billed the same day.
The chase
Once the truck leaves the dock, you're chasing.
The load delivers Thursday. Nobody has the POD. Friday someone emails the carrier. Wednesday the driver sends page two only. The following Monday you invoice. Seven days on the clock, and none of them moved freight.
Timed to the delivery
At the appointment it confirms arrival. Thirty minutes on site, it asks whether they're unloaded. Then it asks for the POD, all pages, and collects the out-time.
Read, not just received
Every photo and attachment gets classified, checked against the load and filed: POD, BOL, lumper receipt, seal and securement photos.
Filed where you bill from
Into your TMS in the document categories your team already uses, then on to billing or audit, or into a review queue first if you prefer.
Photo intelligence
What it reads off a photo.
A pin on a map can't tell you any of this. A photo can, if something actually reads it.
| It sees | What that catches |
|---|---|
| The reference on the paperwork | A POD from the wrong load, sent back with a request for the right one by lane |
| Seal number on the seal photo | Matched to the BOL and written to the TMS before anyone disputes it |
| Reefer temperature on the gauge | A unit running off its setpoint, on the record at pickup |
| Pallet and piece counts | Shortages caught at the shipper, not discovered at delivery |
| Straps, tarps and load bars | A flatbed leaving untarped, before the weather finds it |
| MC and DOT on the door | A truck that isn't the carrier you booked |
| Signature on the POD | An unsigned copy, re-requested before it becomes an invoice problem |
Restraint
The 5:00 AM lumper, handled without a dollar decision.
Autopilot keeps the truck moving and gets the receipt. It doesn't approve the lumper, issue a comcheck or touch the amount. Money decisions go to your rep.
- It doesn't do collections or replace your invoice audit. It hands the file off clean.
- It asks once. A driver who already sent the POD doesn't get asked again.
- It's honest about limits. It sees that a signature is present, but can't tell a pickup signature from a delivery one unless the form labels them.
Proof
The paperwork side, on the record
Does the driver need our app to send a POD?
No. A phone photo over text works, so does the driver app, and so does an email from the dispatcher.
Can different customers require different paperwork?
Yes. Required documents, and what counts as ready to bill, are set per customer.
Will it flip the load to ready to bill?
Once the document set that customer requires is complete, yes. "Complete" is your definition, set during implementation.
Does this replace our audit or factoring platform?
No. Chain collects, reads and validates the documents and hands them off. Audit, factoring and collections stay where they are.