Skip to content
Building now

Run the load.

A rate confirmation comes in. Somebody decides which truck takes it, tells the driver, and later needs to know what actually happened and where the pages are. That is one record, and for most people today it is three.

One load. Everyone knows what comes next.

Step through one example load the way the office and the driver would see it. Switch sides, try the missing-page example, and see what a changed assignment looks like.

1. Start with the rate con: Add the page. Review the load details in one place.

Office · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH
Rate conOriginal page kept with the load

Review pickup, delivery and dates in one place. The rate stays on the office side.

Driver

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.

2. Choose the truck and driver: Keep the right details with their trip.

Office · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH
Rate conStays with the office
Truck 12 · Driver AChosen for this load
Driver · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH

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.

3. Work the stops: Keep the stops and their paperwork with the load.

Office · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH
Work updatedPickup recorded by the driver

The office sees the driver’s updates on the same load. No live map, no guessed arrival.

Driver · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH
PickupDone · paperwork can be added here
DeliveryNext stop

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.

4. Add the POD: Add it here. The office can see the page with the load.

Office · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH
  • Rate conAdded
  • Proof of deliveryAdded

“POD received” is what the office sees. Delivery itself stays a separate fact.

Driver · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH
Proof of deliveryPOD received · 2:14 pm

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.

5. Get the packet ready: See what is included. Fix what is missing.

Office · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH
  • Rate conAdded
  • Proof of deliveryUpdated · earlier version kept
  • Fuel receiptPrivate · not in the packet
Trip packetReady when every required page is in
Driver · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH

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.

6. Prepare the payment paperwork: Have the trip paperwork ready for the next step.

Office · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH
Trip packetRate con + POD, all pages present
Payment paperworkInvoiceStage: preparation
Driver · Load 1042
PickupIndianapolis, INDeliveryColumbus, OH

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.

1 / 6Planned trip flow · Sample load
Planned

Factoring paperwork, with less re-entry.

We plan to connect load details and the right paperwork to your factoring workflow, so the ready packet is not retyped and re-uploaded. OTR Solutions is our first integration target, subject to access and approval. No connection is live yet. You stay free to use your own factor, and packet ready, submitted, accepted and funded remain separate stages.

  1. The load arrives as paper.

    Photograph the rate confirmation or pull the PDF. The app proposes the pickup, the drop, the dates and the rate, and flags anything it is unsure about. Nothing becomes a record until you confirm it.

  2. You put it on a truck and a person.

    Pick the truck and whoever is driving it. That creates one assigned trip with one identity — not a screenshot in a group chat that nobody can find in March.

  3. It shows up where they already look.

    The driver sees the trip in their own Trips list on their own phone. A company driver sees what the work requires; the rate and the office's copy of the booking are not part of that.

  4. The paperwork comes back with the load.

    The POD is added from the dock and the office sees “POD received” on the same load. Delivery, POD receipt and a finished packet are three different facts, and the app keeps them that way.

  5. A change of plan updates the work.

    If the assignment changes, the load is not copied: the new driver sees it, the old driver stops receiving new work on it, and the trip keeps one history. If a change cannot be confirmed yet, the app says “Checking the assignment” and offers a retry rather than a second Assign.

  6. Work for someone else stays separate from your own.

    One account can own a company, drive a truck, and take work from another carrier without those becoming the same pile. Your private books stay private even when you are hauling for somebody else.

What is in it, and where each part stands.

  • Trips and loads

    Building now

    One trip record carrying the load, the truck, the dates and the documents attached to it.

  • Truck and driver records

    Building now

    Which trucks you run and who is entitled to drive them, kept as a real relationship rather than a label.

  • Company dispatch

    Planned

    Assigning a load to an eligible truck and person so it lands in their Trips, including a changed assignment that updates the work instead of copying the load.

  • Independent and employee work kinds

    Planned

    An independent operator and a company driver are different arrangements, and the paperwork each one receives differs accordingly.

  • POD receipt and paperwork readiness

    Planned

    Recording the proof of delivery when it arrives, kept distinct from the delivery itself, and knowing when the required packet is complete.

  • Payment paperwork preparation

    Planned

    Using the ready trip documents for the next invoicing or factoring preparation step. Not sending invoices, not collecting money.

  • Factoring paperwork, with less re-entry

    Planned

    Reusing load details and the allowed paperwork in your factoring workflow. OTR Solutions is our first integration target, subject to access and approval; no connection is live yet.

Bring your real trip workflow to the pilot.

The pilot is how this gets built with real trucks behind it. Leave an email and we will write when there is something to try.

Optional — what should we tell you about?

Your email is used to send you CarrierAgent pilot and launch updates. See the privacy policy for what the pilot list stores.