Driver arrival is not pickup completion. Which status should the team trust?
Key Takeaways
The team should trust "picked up" only when there is evidence that the freight was loaded and the driver left with it, such as a signed bill of lading, a warehouse loading record, or departure data, not just a report that the driver arrived. An AI logistics coordinator should keep arrival and pickup as separate statuses and move a load to "picked up" only when the evidence supports it.
- Driver arrival means the truck reached the pickup site. Pickup completion means the freight was loaded and left.
- Between arrival and completion, the truck may wait, be refused, take only part of the load, or leave empty.
- Many tracking tools jump from "arrived" to "in transit" without confirming loading.
- The strongest evidence of pickup is the signed bill of lading and the warehouse's loading record.
- Customer updates, delivery estimates, and invoices should all use the confirmed pickup, not the arrival.
- A load that stays at "arrived" too long needs a follow-up, because something may have gone wrong.
- Wilson, by Cartage, is an AI logistics coordinator that tracks each load from booking to delivery and records the evidence for each status change.
Why is driver arrival not the same as pickup completion?
Driver arrival is not pickup completion because the truck reaching the dock says nothing about whether the freight was loaded, whether the right freight was loaded, or whether the truck left with it. An AI logistics coordinator should treat arrival as one step and completion as a later step that needs its own evidence.
What happens between arrival and completion
| Event | What it means | What can go wrong |
|---|---|---|
| Arrival | Truck at the site | Wrong site, wrong gate, too early, too late |
| Check-in | Driver logged by the site | Missing pickup number, wrong load |
| Door assigned | Truck moved to a dock door | Long wait for a door |
| Loading | Freight placed on the truck | Freight not ready, wrong freight, partial load |
| BOL signed | Driver signs for what was loaded | Count differs; exceptions noted |
| Departure | Truck leaves the site | Truck leaves empty or partly loaded |
A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
The status gap in many systems
Many tracking tools show a few statuses: booked, arrived, in transit, delivered. When the truck leaves the pickup site, the status jumps from "arrived" to "in transit." The tool assumes that leaving means the freight was loaded. Sometimes it was not. A truck can leave empty after a long wait, or with only part of the order.
Why tools skip the middle
Tools skip the middle statuses because they are harder to get. Arrival and departure can come from location data. Loading and the signed BOL usually come from the warehouse, which may not be connected to the tracking tool. Skipping the middle makes the screen simpler, but it hides the part of the stop where most problems happen.
Why this matters downstream
The pickup time drives the delivery estimate. If the team believes the freight left at 9 a.m. but it actually left at 2 p.m., the customer gets a delivery estimate five hours too early. If the freight never left, the customer expects a delivery that will not come. Invoices can be wrong too: a carrier may bill for a load it did not carry, or bill detention for a wait the shipper caused.
Detention lives in this gap
The time between arrival and departure is where detention happens. Detention is a fee a carrier bills when its truck waits too long at a dock. In a September 2024 study, the American Transportation Research Institute (ATRI) found that detention affected 39.3% of truck stops in 2023. Recording arrival and completion separately is the only way to know how long the truck actually waited.
LTL pickups are short but still separate
On less-than-truckload pickups, the driver may be at the dock for only 15 minutes. Less-than-truckload, or LTL, is freight that shares a trailer with other shippers' freight. Arrival and pickup may happen almost together. But the driver may still refuse a pallet that is poorly wrapped, or leave without freight that was not ready. The statuses should stay separate even when the gap is short.
Drop trailers
On a drop trailer pickup, the carrier leaves an empty trailer and later collects it loaded. The "arrival" may be the carrier coming to hook the loaded trailer, and pickup completes when that trailer leaves. The signed BOL may be left in the trailer or at the office. The same rule applies: pickup is complete only when the loaded trailer leaves with paperwork that matches.
Hypothetical example: arrived, left empty
This example is hypothetical and does not describe a real customer. A carrier's tracking shows "arrived" at 8:00 a.m. and "in transit" at 11:30 a.m. The shipper's team tells the customer the order is on its way. In fact, the freight was not ready, and the driver left empty for another load. The customer learns the truth the next day when nothing arrives. Separate statuses for arrival and loading would have shown the problem at 11:30 a.m.
Which statuses should the team trust, and what evidence does each need?
The team should trust each status only to the level of its evidence: arrival needs a site or device record, loading needs the warehouse's record, and pickup completion needs a signed BOL or a departure record with loading confirmed. An AI logistics coordinator should attach the evidence to each status change.
Status and evidence
| Status | Minimum evidence | Stronger evidence |
|---|---|---|
| Arrived | Carrier or driver report | Gate log, check-in record, or location data |
| Loading | Warehouse report | Door assignment and loading start time |
| Loaded | Warehouse confirms loading finished | Count matches the BOL |
| Picked up | Signed BOL or warehouse confirmation of departure with freight | Signed BOL plus departure time from site or location data |
| In transit | Truck moving away from the site after pickup | Location data or carrier tracking after confirmed pickup |
The signed BOL is the key document
The signed BOL shows that the driver accepted the freight listed on it. It is the carrier's receipt. If the warehouse scans the signed BOL right after loading, the team has strong proof of pickup. If the BOL shows exceptions, such as a short count, the team knows about them right away.
Warehouse records support the BOL
Many warehouses record when loading started and finished, and which door was used. These records confirm the BOL and show how long loading took. If the warehouse system records shipments as "shipped" only after loading, that event is a strong pickup signal.
When the warehouse is a third party
When freight ships from a third-party warehouse, the shipper may not see the warehouse's loading records directly. The warehouse may send a shipped notice or a BOL scan by email. The AI logistics coordinator should know how each third-party warehouse confirms shipments and use that confirmation as the pickup evidence.
Carrier "picked up" statuses need care
When a carrier's system says "picked up," the team should know how that status was created. Some carriers set it when the driver scans the BOL. Others set it when the truck leaves a geofence around the site, even if nothing was loaded. A geofence is a virtual boundary around a location that triggers an event when a vehicle enters or leaves it. The first is good evidence. The second is not.
Weigh the sources
Not every source is equal. A signed BOL scan from the warehouse is strong. A gate log is strong. A carrier status set by a scan is good. A carrier status set by a geofence or typed by dispatch later is weaker. The AI logistics coordinator should record which source each status came from, so a reviewer can see why the load was marked picked up.
Time stamps should be local
Pickup times should be stored in the pickup site's local time, with the time zone. Carrier systems may report times in another zone. A pickup that looks like it happened at 1:35 p.m. may really have happened at 12:35 p.m. local time. Getting this right keeps delivery estimates and detention reviews accurate.
Hypothetical example: matching three records
This example is hypothetical and does not describe a real customer. For one load, the carrier reports "picked up" at 10:40 a.m., the warehouse scans the signed BOL at 10:35 a.m., and the gate log shows the truck leaving at 10:48 a.m. The AI logistics coordinator sees three records that agree and marks the load picked up at 10:35 a.m., with the BOL attached.
How should the team move a load from arrived to picked up?
The team should move a load from arrived to picked up through a set sequence: confirm check-in, confirm loading, collect the signed BOL, and confirm departure. An AI logistics coordinator can run this sequence on every pickup and flag any load that stalls between steps.
The status workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Arrival | Carrier or site reports arrival | Records it with its source | Never |
| 2. Check-in | Expected check-in time passes | Asks the site or reads the yard system | When the driver cannot check in |
| 3. Loading | Truck at a door | Records loading start where available | Never |
| 4. Signed BOL | Loading finishes | Asks the warehouse for the signed BOL scan | When the count differs or exceptions are noted |
| 5. Departure | Truck leaves | Records departure time | Never |
| 6. Picked up | BOL and departure on file | Marks the load picked up and updates the delivery estimate | Never |
Ask for the BOL scan at the dock
The easiest way to get pickup evidence is to make the BOL scan part of the dock routine: the driver signs, the dock lead scans or photographs the signed copy, and it goes to the shipment record before the truck leaves the yard. This takes a minute and settles most questions about pickup.
Set time limits between steps
Each step should have a time limit. If the truck has been "arrived" for two hours with no check-in, something is wrong. If loading started three hours ago and no BOL has been scanned, something is wrong. The AI logistics coordinator should alert the load owner when a load stays in one status too long.
Time limits by site
Time limits should reflect each site. A small plant with two doors may load a truck in 45 minutes. A large distribution center may take three hours at peak times. Using one limit for every site will create false alarms at busy sites and miss problems at fast ones.
Partial pickups
Sometimes the truck leaves with only part of the order, because the rest was not ready or did not fit. The signed BOL should show the actual count. The status should be "picked up, partial," and the team should plan the rest of the order. The customer should be told what is coming and what is not.
Exceptions on the signed BOL
The driver may note an exception on the BOL, such as "1 pallet damaged" or "shipper load and count." Shipper load and count means the driver did not watch the loading or count the pieces, so the shipper's count is used. These notes affect any later claim. The status should show that pickup completed with exceptions, and the notes should be visible to anyone who looks at the load.
Empty departures
If the truck leaves empty, the status should not move to "picked up" or "in transit." It should move to "failed pickup," with the reason. The team then needs to reschedule and decide whether any charges apply, such as a truck ordered not used fee. A truck ordered not used fee, or TONU, is a charge some carriers bill when a truck is sent but the load is not picked up.
Who confirms when the warehouse is busy
A busy warehouse may not answer a message during a rush. The AI logistics coordinator can check the warehouse system directly where connected, or ask the carrier whether the driver has the signed BOL. Two sources are better than waiting for one. The goal is to know, within a reasonable time, whether the pickup happened.
Hypothetical example: a stalled load
This example is hypothetical and does not describe a real customer. A load shows "arrived" at 1:00 p.m. At 3:00 p.m., there is still no check-in. The AI logistics coordinator asks the warehouse, which says the driver is at the wrong building. The coordinator sends the driver the correct dock instructions through the carrier. The truck checks in at 3:20 p.m., is loaded by 4:10 p.m., and the signed BOL is scanned at 4:15 p.m.
Which status should drive customer updates, delivery estimates, and invoices?
Customer updates, delivery estimates, and invoice reviews should all use the confirmed pickup, supported by the signed BOL and departure time, not the arrival time. An AI logistics coordinator should send "shipped" messages and calculate delivery times only after pickup is confirmed.
Which status drives what
| Use | Status to use | Why |
|---|---|---|
| "Shipped" message to the customer | Picked up (confirmed) | The freight is actually on its way |
| Delivery estimate | Picked up time plus transit time | Arrival time can be hours earlier |
| Detention review at pickup | Arrival and departure times | Shows the full wait |
| Carrier invoice for linehaul | Picked up with signed BOL | Proves the carrier carried the load |
| Customer invoice | Picked up, or delivered, per company rules | Matches what shipped |
Linehaul is the base charge for moving the freight.
Update the plan when pickup is late
When pickup completes much later than planned, other plans may need to change: the delivery appointment, the receiver's labor, or a connecting shipment. The AI logistics coordinator should compare the confirmed pickup time with the delivery promise and alert the load owner if the promise is at risk.
Shipped messages
A customer should hear "your order has shipped" only after the freight is on the truck and the truck has left. The message should include the carrier, the tracking number, and the count from the signed BOL. If the pickup was partial, the message should say so.
Delivery estimates
Transit time starts when the truck leaves with the freight. Using the arrival time instead can make the estimate several hours too early. If the customer plans labor around that estimate, the error costs them time and trust.
Customer invoices
Many companies invoice their customers when the order ships. If the invoice is triggered by the arrival status, a customer may be billed for an order that left empty. The customer invoice should wait for confirmed pickup, with the shipped count from the signed BOL.
Invoices
The carrier should be paid for loads it carried. The signed BOL proves the carrier received the freight. For detention at pickup, the reviewer needs both the arrival time and the departure time. Teams that want the full method can read how to audit detention charges against pickup timestamps.
Internal teams need the same discipline
Sales, customer service, and finance often look at the same tracking screen. If they see "in transit" after an empty departure, they may promise a delivery that will not happen. Clear statuses with evidence protect every team, not just logistics.
Hypothetical example: a corrected estimate
This example is hypothetical and does not describe a real customer. A truck arrives at 7:00 a.m. but is loaded and leaves at 12:30 p.m. after a long wait. The delivery estimate based on arrival would have said 4:00 p.m. that day. Based on confirmed pickup, it says 9:30 p.m., after the receiver closes, so delivery moves to the next morning. The AI logistics coordinator tells the customer the next-morning time before the customer schedules staff for 4:00 p.m.
How should teams test whether software separates arrival from pickup?
Teams should test software with loads that arrive and load normally, arrive and wait for hours, arrive and leave empty, leave with a partial load, and get a carrier "picked up" status before loading. An AI logistics coordinator should keep arrival and pickup separate, require evidence for pickup, and act on loads that stall.
The test
| Test case | Pass | Fail |
|---|---|---|
| Normal pickup | Arrived, loaded, picked up with BOL | Jumps to in transit with no BOL |
| Long wait before loading | Alert after the time limit | No action until the invoice |
| Truck leaves empty | Marked failed pickup | Marked in transit |
| Partial pickup | Marked partial with count | Marked complete |
| Carrier "picked up" before BOL scan | Held until evidence | Accepted as fact |
| Delivery estimate | Based on confirmed pickup | Based on arrival |
Use the team's own past problems
The test is strongest when it uses pickups the team remembers: the day the driver left empty, the partial load nobody noticed, the "in transit" load that never left. If the software would have caught those, it will catch the next ones.
Questions to ask in a demo
- What statuses does the software use between arrival and in transit?
- What evidence does it need to mark a load picked up?
- How does it know whether a carrier's "picked up" status came from a scan or a geofence?
- What happens if a load stays "arrived" for hours?
- When does it tell the customer the order shipped?
Check the customer's view
For each test case, look at what the customer would have been told and when. The best internal statuses mean little if the customer still gets a "shipped" message on arrival.
Warning signs
- Only one status between booked and in transit.
- "Picked up" is set when the truck leaves the area.
- Partial pickups look the same as full pickups.
- Customer "shipped" messages go out on arrival.
Teams checking carrier pickup claims can also read where the proof is when a carrier says picked up.
Where does Wilson fit in separating arrival from pickup?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers, prepares the bill of lading, tracks each load, and records the evidence for each status change. Wilson tracks each load using the best source available: carrier API, GPS or ELD data where it exists, the carrier's website by PRO number, and email or phone where configured. An ELD, or electronic logging device, records a truck's driving time and can share location. A PRO number is a tracking number a carrier gives to a shipment.
Wilson replaces the TMS for freight execution and connects to the company's ERP. A TMS, or transportation management system, is software used to plan, book, and track freight. An ERP, or enterprise resource planning system, is the company's main business system for orders, inventory, and accounting.
How Wilson confirms pickup
Wilson records arrival, asks for the signed BOL and departure time, and marks the load picked up when the evidence is in. If a load stalls, Wilson contacts the carrier and alerts the internal team. Wilson keeps the customer's team informed through Slack or Microsoft Teams on booked, picked up, running late, delivered, and POD filed, and updates the shipper by email at each step. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured.
Exceptions and payment
When Wilson detects a missed pickup, a cancellation, or a delay, it contacts the carrier, notifies the internal team, notifies the customer where configured, and initiates rebooking from the approved carrier list within the customer's rules or with approval. Wilson audits and reconciles each carrier invoice against what was booked. Customers use the Wilson Wallet to pay their carriers. Payments above approval limits or outside the rules wait for a person. Wilson has no subscription or platform fee; its pricing is a percentage of the freight payments coordinated through the Wallet. Pricing scales down as volume grows, and Enterprise pricing is custom.
What Wilson does not assume
Wilson does not treat a truck leaving the area as proof that the freight was loaded. It does not send a "shipped" message on arrival. When the evidence for pickup is missing, Wilson asks for it and keeps the load in its current status until it arrives.
What Cartage asks in discovery
Cartage asks how the warehouse records loading, how signed BOLs are scanned, which carriers send pickup statuses and how, and what the customer is told when an order ships. These answers shape the pickup rules an AI logistics coordinator applies.
Where teams start
Wilson starts with assisted execution. Approval limits are set by the customer, and routine actions can run automatically within those rules as reliability is proven. Timing depends on scope: most teams start on a few lanes and expand from there. Every status change and its evidence is saved in the shipment record with change history.
This article is part of our complete guide to driver arrival and detention records.
FAQs
Is driver arrival the same as pickup?
No. Arrival means the truck reached the site; pickup means the freight was loaded and left. An AI logistics coordinator keeps them as separate statuses.
What proves a pickup is complete?
A signed bill of lading, a warehouse loading record, and a departure time. An AI logistics coordinator marks the load picked up only with this evidence.
Which status should drive the customer's shipped message?
The confirmed pickup, not the arrival. An AI logistics coordinator sends the message with the count from the signed BOL.
What if a load stays at arrived for hours?
Something may be wrong, such as a long wait or a wrong dock. An AI logistics coordinator alerts the load owner after a set time.
What if the truck leaves with only part of the order?
The load should be marked as a partial pickup with the actual count. An AI logistics coordinator tells the customer what shipped and what is still to come.
Sources
- American Transportation Research Institute, "New Research Documents Substantial Financial and Safety Impacts from Truck Driver Detention," September 2024: https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator separates driver arrival from confirmed pickup and keeps every status backed by evidence: talk to the Cartage team.