The carrier says it picked up the load. Where is the proof?

Key Takeaways

A carrier's "picked up" message is a claim, not proof. Proof is a signed BOL, the warehouse's confirmation that the freight left, or a tracking event from the truck or the carrier's system.
Use two independent sources for every pickup: one from your dock and one from the carrier's side. When they agree, tell the customer.
When the sources disagree, treat it as a possible missed pickup and check it within the hour, before anyone promises a delivery date.
Wilson, by Cartage, is an AI logistics agent that reconfirms the pickup window, tracks each load with the best source available and calls the carrier when the status is unclear.
If the pickup didn't happen, Wilson runs the missed pickup response: carrier, team, customer if configured, then rebooking from approved carriers.

Why isn't "picked up" enough?

"Picked up" isn't enough because a status message can be sent before the freight leaves, or without it leaving at all. A dispatcher may update the status from the plan, a driver may check in at the wrong door, or the truck may still be waiting at a previous stop. Proof means a record that the freight is off your dock and on that carrier's truck.

This matters to any manufacturer or distributor whose customer updates, production plans or delivery appointments depend on pickup happening on time. Dock delays are common: ATRI found truck drivers were detained at 39.3% of stops in 2023. When drivers run late, status messages often run ahead of the trucks.

Some terms. A tender is the offer of a load to a carrier; once the carrier accepts, the load is booked. The BOL (bill of lading) is the document the driver signs at pickup. A missed pickup is a pickup that didn't happen in the confirmed window. Carrier follow-up is the work of contacting the carrier until you have a confirmed answer.

Here is one load, with times given for example:

Wednesday, 1:00–3:00 p.m. An FTL load is booked for pickup at a plant in Indiana.
Wednesday, 2:40 p.m. The carrier dispatcher emails: "Picked up." The driver had told dispatch he was on his way.
Wednesday, 2:45 p.m. The coordinator tells customer service, who promises the customer a Thursday morning delivery.
Wednesday, 4:30 p.m. The shipping lead walks the dock. The pallets are still at door 6, with an unsigned BOL.
Wednesday, 5:10 p.m. The coordinator calls the carrier. The driver was held at his previous stop and won't make it today.
Thursday, 7:00 a.m. The customer calls about the delivery that isn't coming.

What proves a pickup happened?

Four sources can confirm a pickup, and they’re not equally strong. The strongest proof combines one source from your dock with one from the carrier’s side.

Source	What it shows	Limit
Signed BOL	The driver signed for the freight	It sits at the dock until someone sends it
Warehouse confirmation	The freight left the dock on a named carrier’s truck	Depends on someone checking
Tracking event	Carrier API, GPS or ELD data showing the truck at and leaving the site, or a PRO scan	Not every carrier has every source
Carrier dispatch	The carrier says the pickup happened	It’s a claim until another source backs it

The ELD (electronic logging device) records the truck’s hours and location, and the PRO number is the carrier’s tracking number for an LTL shipment. A truck leaving your site after arriving is strong evidence; a PRO scan at the carrier’s terminal is stronger still for LTL.

The right pair depends on the carrier. With an API or ELD data, the tracking event plus the warehouse is usually enough. With a small carrier that has neither, the signed BOL plus a call to the driver is often the only combination available.

What should the team do when the proof doesn't match?

Check within the hour, and don’t update the customer until two sources agree. A false “picked up” costs the most when it reaches the customer, because the next message is a broken promise.

Ask the warehouse whether the freight left and on whose truck.
Check the tracking source: is the truck at the site, past it, or somewhere else?
Call the carrier dispatcher, then the driver if needed, for the real status and a new pickup time.
If the freight is still on the dock, treat it as a missed pickup. Decide whether the carrier can still recover in a time that works, or whether to rebook with another approved carrier.
Then tell the customer, with the confirmed new plan.

The condition that changes the response is whether the driver is on site. A driver at the gate but stuck at another door is a dock problem; a driver still two hours away is a carrier problem. For what to do first, see the first hour after a missed pickup.

Common mistakes

Passing the carrier’s message straight to the customer. One unverified status becomes a promise the team can’t keep.
Waiting for the end of the day to check the dock. By then, rebooking options for the same day are usually gone.
Accepting “picked up” without a PRO number or a signed BOL. There’s nothing to track and nothing to show later.
Calling only the dispatcher. The driver often knows more, and faster.

How does Wilson, by Cartage, confirm pickups?

Wilson, by Cartage, reconfirms the pickup window before the pickup, tracks the load with the best source available and calls the carrier when there’s no data or the status is unclear. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Step	Trigger	What Wilson does	When a person steps in
1. Schedule	Load is booked (LTL or FTL)	Schedules the pickup and confirms the window with the carrier	If the carrier can’t commit to a window
2. Reconfirm	Pickup is approaching	Reconfirms the window with the carrier	If the answer has changed
3. Track	Pickup window opens	Uses the carrier’s API, GPS or ELD data, or the carrier’s website by PRO number	Not required
4. Call	No data source, or status unclear	Emails or calls the carrier and driver at the frequency set in the SOP	If the carrier can’t confirm
5. Notify	Pickup is confirmed	Sends “picked up” to the team and others the company has set	Not required
6. Missed	Pickup didn’t happen	Contacts the carrier, notifies the team and the customer if configured, initiates rebooking from approved carriers	If rebooking needs approval

The frequency is the company’s choice, set in its SOP: for example, calling every hour until the load is picked up. Call transcripts are saved on the order, and every message, confirmation and change is recorded in the change history, so when a customer asks what happened, the team can see who said what and when.

Approvals follow the company’s rules. Wilson starts with assisted execution; rebooking after a missed pickup runs automatically or waits for approval, depending on what the company has set, for example a cost threshold. Wilson escalates when a carrier can’t confirm or no approved carrier accepts the load.

Wilson books and rebooks only approved carriers. It coordinates pickup times with carriers, but it doesn’t manage dock slots inside the facility, so dock assignments stay with the warehouse. For the case where status sources disagree, see the carrier email and tracking feed disagree.

How do teams make pickup proof routine?

Teams make proof routine by setting a two-source rule, reconfirming before the window and keeping the evidence on the shipment. It turns a once-a-week surprise into a check that runs on every load.

Two sources, every pickup: the warehouse and a tracking source or the carrier.
Reconfirm before the window, not after it. See what a pickup confirmation should include.
File the signed BOL on the shipment the same day.

What to ask a vendor to show in a demo

Show the pickup reconfirmation message sent to one of our carriers.
Show how status is tracked for a carrier with no API, including the call and its transcript.
Show what happens when the carrier says “picked up” but the tracking source disagrees.
Run a missed pickup on one of our lanes: who’s notified, in what order, and where approval is required.
Show the change history for that load.

FAQs

How do I verify that a carrier picked up a load? Use two independent sources: the warehouse's confirmation or the signed BOL, plus a tracking event or the carrier's confirmation. Wilson, by Cartage, tracks with the best source available and calls the carrier when status is unclear.
What if the carrier says picked up but the freight is still at the dock? Treat it as a missed pickup: contact the carrier, notify the team, then get a new time or rebook with an approved carrier.
How does Wilson track pickups? Wilson uses the carrier's API, GPS or ELD data, or the carrier's website by PRO number. When none exist, it emails or calls the carrier.
Does Wilson reconfirm pickups? Yes. For LTL and FTL, Wilson schedules the pickup, confirms the window and reconfirms it before the pickup.
Does Wilson make check calls by phone? Yes. Wilson calls carriers and drivers at the frequency set in the SOP, and call transcripts are saved on the order.
What does Wilson do if a pickup is missed? It contacts the carrier, notifies the team, notifies the customer if configured and initiates rebooking from approved carriers, automatically or with approval.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, covering the full shipment lifecycle.

Conclusion

“Picked up” is a message. Proof is the freight off your dock and a record from the carrier’s side that shows it. Checking two sources before telling the customer catches the pickups that didn’t really happen while there’s still time to recover.

Wilson, by Cartage, runs that check on every load: it reconfirms, tracks, calls and, when needed, starts the missed pickup response. It’s what an AI logistics agent does. Bring one load your team chased last week and watch Wilson run the pickup follow-up in a demo at cartage.ai.

Sources

American Transportation Research Institute (ATRI), September 2024: https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
Cartage, Wilson product FAQ, October 2026: https://cartage.ai