For fleets, dispatchers and the office
Add the rate con once, choose who is taking it, and see the paperwork come back without asking twice. One load, seen from the office and from the cab, with company data and an owner-operator's private books kept apart.
Sample records. Each part below says whether it is being built now or planned.
Step through a sample load the way the office and the driver would see it. Switch sides on a phone, try the missing-page example, and see what a changed assignment looks like.
Review pickup, delivery and dates in one place. The rate stays on the office side.
No trip assigned yet.
The office starts from the actual booking document instead of typing the same load into three places. Review is explicit: adding the page does not settle every field on its own.
The trip appears in Trips with the details the work needs. A company driver does not see the rate or the office’s copy of the booking.
The driver gets the operational details. The office keeps the booking and the rate. An independent operator may receive the rate con when it is deliberately shared for their work.
The office sees the driver’s updates on the same load. No live map, no guessed arrival.
The driver finds the work without hunting through a text thread. No automatic arrival, no tracking and no changed broker appointment: this is a sample, not a truck observation.
“POD received” is what the office sees. Delivery itself stays a separate fact.
If the upload fails, the trip stays selected and the app explains how to retry. It never shows “Received” before the save succeeds.
The office knows the page arrived and does not ask for it again. POD received is recorded as its own fact; it is not a delivery time and it is not payment.
Your part is done. The office prepares the packet and the payment paperwork.
A load update and a complete paperwork set are different things. A corrected POD becomes “Updated paperwork” with the earlier version kept; private fuel receipts stay out of the shared packet.
Your part is done. The office prepares the packet and the payment paperwork.
A complete packet means fewer pages to hunt for before invoicing or factoring preparation. Factoring paperwork with less re-entry is a planned integration: OTR Solutions is our first integration target, subject to access and approval, and no connection is live yet. CarrierAgent has not sent an invoice or collected money in this example.
Reassignments, missing pages and corrections are Tuesday. The app is built to keep one load and one history through all of them.
The load shows “Assignment changed” with the current truck and person. The old driver stops receiving new work on it, the new driver sees it, and the trip keeps its history. If the change cannot be confirmed yet, the app shows “Checking the assignment” with a retry, never a second Assign that could duplicate the load.
The packet says “POD missing” and stays that way until the page arrives. The load is not started over and nobody is asked for the same page twice.
The driver adds the corrected page. The office sees “Updated paperwork” with the earlier version kept, not a second delivery and not a duplicate completion.
Leave an email and tell us whether you run the office, the trucks or both. The pilot is how the office side gets built with real loads behind it.
