Was the driver late, or was the dock closed? Document the pickup event
Key Takeaways
When a pickup fails, the team can only tell whether the driver was late or the dock was closed if the pickup event was documented at the time: the appointment, the dock hours, the driver's arrival, what the driver was told, and the messages exchanged. An AI logistics coordinator should collect these facts on the day of the pickup and save them with the shipment, so the question is settled with records instead of memory.
- A failed pickup is one where the truck came but the freight did not leave, or the truck never came.
- The two most common stories are "the driver was late" and "the dock was closed or not ready."
- Both can be true on different days, and sometimes on the same day.
- The facts needed are the appointment, the dock hours, the arrival time, the site's response, and the messages.
- The answer decides who pays for the second attempt, any truck ordered not used fee, and any detention.
- Patterns across many pickups show whether a carrier or a site needs to change.
- Wilson, by Cartage, is an AI logistics coordinator that confirms pickup details with the carrier, tracks each load, and records what happened at every stop.
Why does it matter whether the driver was late or the dock was closed?
It matters because the answer decides who pays for the failed pickup, who must fix the cause, and whether the customer's delivery promise was broken by the carrier or by the shipper. An AI logistics coordinator should document each failed pickup clearly, because the same question will be asked by the carrier, finance, and the customer.
What depends on the answer
| Question | If the driver was late | If the dock was closed or not ready |
|---|---|---|
| Who pays for a second attempt? | Usually the carrier | Usually the shipper |
| Is a TONU fee owed? | Usually not | Often yes |
| Is detention owed? | Usually not | Possibly, if the truck waited |
| Who fixes the cause? | Carrier dispatch | Warehouse or scheduling |
| Who explains to the customer? | Shipper, with carrier facts | Shipper, with site facts |
TONU means truck ordered not used, a fee some carriers bill when a truck is sent but the load cannot be picked up. Detention is a fee a carrier bills when its truck waits too long at a dock.
Both stories are common
Drivers run late because of traffic, earlier stops, or hours-of-service limits. Docks close early, run out of doors, or are not ready because the freight is not staged. Neither side is always right. The team needs facts, not assumptions.
Hours-of-service rules affect the driver
Federal hours-of-service rules limit how long a driver can work. For example, a property-carrying driver cannot drive after the 14th hour on duty following 10 consecutive hours off duty, and cannot drive more than 11 hours in that period. A driver who waits too long at one stop may run out of hours and miss the next. A late arrival can be the result of a long wait at an earlier stop, not carelessness.
Windows versus appointments
A pickup window, such as 1:00–5:00 p.m., gives the carrier a range. An appointment, such as 2:00 p.m., is a fixed time. A driver who arrives at 4:50 p.m. is inside a window but may be too late to load if loading takes an hour and the dock closes at 5:00 p.m. The booking should make clear whether the window is for arrival or for completed loading. That detail settles many disputes.
The customer sees only the result
The customer sees a late delivery. It does not matter to the customer whose fault it was, but the shipper needs to know, so it can fix the cause and charge the right party. A clear record also helps the shipper explain the delay honestly.
Hypothetical example: two accounts of one afternoon
This example is hypothetical and does not describe a real customer. A carrier bills a TONU fee, saying the driver arrived at 3:45 p.m. for a 3:00–5:00 p.m. pickup window and found the dock closed. The warehouse says the driver arrived at 5:20 p.m., after closing. Without records, the team has two stories. With a gate log or location data, it has an answer.
What should be documented about a pickup event?
A pickup event should be documented with the appointment or window, the dock's posted hours that day, the driver's arrival time with its source, what the site told the driver, any messages exchanged, and the outcome. An AI logistics coordinator should fill in each item from the booking, the tracking data, and the site's records.
The pickup event record
| Item | Example | Source |
|---|---|---|
| Appointment or window | 3:00–5:00 p.m. | Booking and rate confirmation |
| Dock hours that day | Shipping closes at 5:00 p.m. | Site schedule |
| Special conditions | Early closing for inventory count | Site notice |
| Driver arrival time | 3:45 p.m. | Location data, gate log, or driver claim |
| Site response | "Dock closed early today" or "Freight not ready" | Site staff or driver report |
| Messages | Carrier called at 3:50 p.m.; warehouse replied 4:05 p.m. | Phone and email records |
| Outcome | No pickup; rescheduled to next day 8:00 a.m. | Booking update |
| Charges claimed | TONU $250 | Carrier invoice |
A rate confirmation is the document that states the agreed price and terms for one load.
Dock hours are often the missing fact
Many disputes turn on whether the dock was open. The posted hours may differ from the actual hours on a given day because of holidays, staff shortages, inventory counts, or early closing. If the site changed its hours and did not tell the carrier, the failed pickup is usually the shipper's responsibility. The record should show the hours in effect that day.
What the driver was told matters
The driver's report of what the site said is useful, but it should be checked with the site. "The dock was closed" can mean the doors were locked, or that the staff said they could not load until tomorrow, or that the freight was not ready. Each has a different meaning for responsibility.
Photos and notes from the driver
A driver may send a photo of a locked gate or a closed dock door, with a sign showing the hours. Photos can be strong support when they show the site and the time clearly. They should be saved with the record, along with any note the driver left with security or the site.
Messages show who knew what, when
If the carrier called at 2:00 p.m. to say the driver would be late, and the warehouse said it would wait, the late arrival is not a failed pickup by the carrier. If the warehouse emailed at noon that the dock would close early, and the carrier did not pass it to the driver, the failed pickup is the carrier's. The messages should be saved with the load.
Freight readiness is part of the record
A dock can be open while the freight is not ready. The driver then waits or leaves. The record should note whether the freight was staged and the paperwork, such as the bill of lading, was ready when the driver arrived. A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it. If the freight was not ready, the failure is usually the shipper's, even though the dock was technically open.
Weather and outside events
Sometimes neither side is at fault: a storm closes roads, a plant loses power, or an accident blocks the highway. The record should still show the facts. Many terms treat these events differently, and the reviewer needs to know what happened before deciding whether any charge applies.
Hypothetical example: an early closing
This example is hypothetical and does not describe a real customer. A distributor's warehouse closes at 3:00 p.m. instead of 5:00 p.m. for a quarterly inventory count. The warehouse told the logistics team, but nobody told the carrier. The driver arrives at 3:45 p.m. and finds the dock closed. The record shows the early closing and no message to the carrier. The AI logistics coordinator flags the TONU charge as likely valid and the reviewer approves it.
How should the pickup event be documented on the day?
The pickup event should be documented on the day it happens, starting when the pickup window opens: confirm the truck is coming, record its arrival, confirm loading or the reason it did not happen, and save every message. An AI logistics coordinator can run these steps on every pickup so the record is complete before anyone asks.
The day-of workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Confirm | Morning of pickup | Confirms the carrier is on schedule and the dock hours are unchanged | When the site changed its hours |
| 2. Watch | Window opens | Tracks the truck using the best available source | Never |
| 3. Record arrival | Truck arrives or is reported | Saves the arrival with its source | Never |
| 4. Confirm outcome | Expected loading time passes | Asks the site whether loading happened | When the site reports a problem |
| 5. Record failure | Pickup did not happen | Saves the reason from both sides and all messages | Load owner decides next steps |
| 6. Reschedule | Failure recorded | Books a new pickup with the carrier | When cost or delivery changes |
Confirm dock hours in the morning
A short check on the morning of the pickup, asking whether the dock hours are normal that day, prevents many failed pickups. If the site closes early, the carrier can be told in time to move the pickup earlier or to the next day.
Track the truck during the window
Tracking shows whether the truck is on its way and when it will arrive. The source may be the carrier's API, GPS or ELD data where shared, the carrier's website by PRO number, or a call to dispatch. An API is a connection that lets two systems exchange data directly. 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.
Ask the warehouse to report problems right away
The warehouse should report a failed or delayed pickup as soon as it happens, not at the end of the shift. A short message, such as "Load 3310: driver left at 4:15, freight not loaded, reason: dock closed early," lets the AI logistics coordinator start rescheduling and record the facts while they are fresh.
Close the loop the same day
When a pickup fails, both the carrier and the site should give their account the same day. The AI logistics coordinator should ask each side what happened and save the answers. Accounts collected the same day are more accurate than accounts collected when the invoice arrives.
Record the source of every time
The arrival time in a failed pickup record should show where it came from: a gate log, location data, the driver, or dispatch. In a dispute, a time from a device or the site carries more weight than a time reported later by phone. The record should make this clear without anyone having to ask.
Hypothetical example: a late truck caught early
This example is hypothetical and does not describe a real customer. A truck is due between 1:00 and 3:00 p.m. At 1:30 p.m., tracking shows the truck still 120 miles away. The AI logistics coordinator calls the carrier, which says the driver had a long wait at an earlier stop and will arrive at 4:30 p.m. The warehouse closes at 4:00 p.m. The coordinator asks the warehouse whether it can stay open. It cannot, so the coordinator reschedules the pickup for 7:00 a.m. the next day and records the reason as carrier delay.
How should responsibility be decided after a failed pickup?
Responsibility should be decided by comparing the arrival time with the window and the dock hours in effect, then checking the messages to see who knew about any change. An AI logistics coordinator should present the facts and a suggested answer, and the reviewer should decide and record the reason.
Decision guide
| Facts | Usual responsibility |
|---|---|
| Truck arrived after the window; dock hours normal | Carrier |
| Truck arrived in the window; dock closed early without notice to carrier | Shipper |
| Truck arrived in the window; freight not ready | Shipper |
| Truck arrived late; carrier warned in advance and site agreed to wait, then did not | Shipper |
| Site told logistics about early closing; logistics told carrier; driver still came late | Carrier |
| Site told logistics; logistics did not tell carrier | Shipper |
| Truck never came; no message from carrier | Carrier |
Detention before a failed pickup
Sometimes the truck waits for hours and then leaves without the freight. The carrier may bill both detention and a TONU fee. The reviewer should check each one separately: was the wait within free time, and was the failure the shipper's or the carrier's? The terms may allow one charge but not both.
Charges follow responsibility
If the carrier was responsible, the shipper should not pay a TONU fee or detention, and the carrier should cover any extra cost of the second attempt where the terms say so. If the shipper was responsible, the shipper should pay valid charges promptly. The rate confirmation's terms decide the amounts.
The second attempt
When the pickup is rescheduled, the second attempt should be confirmed as carefully as the first: date, window, dock hours, and freight readiness. A failed second attempt is twice as costly and twice as hard to explain to the customer. The record for the second attempt should link back to the first.
Missed pickups and backup carriers
If the carrier never came, the team may need to rebook with another approved carrier. That decision is part of the missed-pickup routine, and the failed pickup record supports it. Teams that want the full response can read about who is responsible for detention after a missed pickup.
When the facts are incomplete
Sometimes the site has no gate log, the carrier shares no location data, and the messages do not settle it. The reviewer then has to make a judgment. In that case, the record should say the facts were incomplete and what the judgment was based on. Over time, incomplete cases point to sites or carriers where better records are needed.
Save the decision and share it
The decision, its reason, and the facts should be saved with the load. The carrier should get the facts if a charge is denied. The warehouse should get the facts if the site was responsible. Sharing facts without blame helps both sides fix the cause.
Hypothetical example: freight not ready
This example is hypothetical and does not describe a real customer. A driver arrives at 10:05 a.m. for a 10:00 a.m. appointment. The freight is still being packed, and the warehouse asks the driver to wait. After two hours, the driver leaves for another load. The carrier bills a TONU fee. The record shows the arrival on time and the freight not ready. The reviewer approves the fee and asks the warehouse to start packing earlier for that customer's orders.
How can teams reduce failed pickups?
Teams can reduce failed pickups by confirming dock hours and freight readiness before the window opens, sending complete site instructions to carriers, tracking trucks during the window, and reviewing failed pickups by cause each month. An AI logistics coordinator can handle the routine checks and report the patterns.
Prevention checklist
| Step | When | Who |
|---|---|---|
| Confirm freight will be ready | Day before pickup | Warehouse, prompted by the AI logistics coordinator |
| Confirm dock hours | Morning of pickup | Site, prompted by the AI logistics coordinator |
| Send site instructions with the tender | At booking | Logistics |
| Track truck in the window | Pickup day | AI logistics coordinator |
| Review failed pickups by cause | Monthly | Logistics manager |
Readiness before the truck
Many failed pickups start the day before, when the freight is not staged or the paperwork is not ready. Teams building a pre-pickup routine can see why missed pickups are an execution problem and how confirmation, follow-up, and escalation work together.
Keep site instructions current
Site instructions, such as dock hours, gate locations, and check-in rules, change over time. Old instructions sent with a tender can cause a driver to arrive after closing or at the wrong gate. The team should review site instructions every few months and update the booking templates.
Share site changes with carriers right away
When a site changes its hours, every carrier with a pickup that day should be told. A single list of today's pickups by site makes this quick. The AI logistics coordinator can send the notices and save each carrier's confirmation.
Plan around driver hours
Afternoon pickups are more likely to fail when drivers have long mornings. Knowing which carriers run long routes, and booking them earlier in the day, reduces late arrivals. The pickup records show which carriers and lanes have this problem.
Look for patterns
After a few months of documented pickups, the patterns are clear. One carrier may run late every Friday. One site may close early often. One customer's orders may never be ready on time. Each pattern has a different fix, and the records show which fix is needed.
Hypothetical example: a carrier pattern
This example is hypothetical and does not describe a real customer. A manufacturer reviews three months of failed pickups and finds that one carrier missed 7 of 30 afternoon windows, each time because the driver ran out of hours after a long morning stop. The team moves that carrier to morning pickups only. Its failed pickups drop to one in the next quarter.
Where does Wilson fit in documenting pickup events?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers, confirms pickup details, tracks each load, and records what happened at every stop. 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.
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.
Confirming the pickup ahead of time
Wilson confirms the pickup details with the carrier before the window, including the date, window, location, and equipment, and checks that the site's hours are unchanged where configured. Most failed pickups start with a detail that nobody confirmed.
How Wilson handles a failed pickup
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 saves the arrival record, the site's account, and every message with the load. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured, and it notifies internal teams through Slack, Microsoft Teams, email, or SMS.
At invoice time
Wilson audits and reconciles each carrier invoice against what was booked, including any TONU or detention line against the pickup record and the terms. 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 decide alone
Wilson does not decide who was responsible for a failed pickup when the facts are unclear. It presents the record and a suggested answer, and the reviewer decides. Wilson does not approve TONU or detention charges above the customer's approval limits.
What Cartage asks in discovery
Cartage asks how dock hours are shared with carriers, which sites keep gate logs, how failed pickups are handled today, and who decides on TONU charges. These answers shape the pickup records an AI logistics coordinator keeps.
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 pickup event is saved in the shipment record with change history.
This article is part of our complete guide to driver arrival and detention records.
FAQs
How can a team tell if the driver was late or the dock was closed?
By comparing the arrival time with the window and the dock hours in effect that day, and checking the messages. An AI logistics coordinator collects these facts on the day.
What should a pickup event record include?
The appointment, dock hours, arrival time with its source, the site's response, messages, outcome, and charges claimed. An AI logistics coordinator fills these in automatically.
Who pays the TONU fee after a failed pickup?
Usually the party responsible for the failure, under the rate confirmation's terms. An AI logistics coordinator presents the facts so the reviewer can decide.
How can failed pickups be reduced?
Confirm freight readiness and dock hours in advance, send full site instructions, and review causes monthly. An AI logistics coordinator handles the routine checks.
Can both the driver and the dock be at fault?
Yes. A driver may arrive late and the dock may also be short-staffed. An AI logistics coordinator records both facts so the reviewer can decide fairly.
Sources
- Electronic Code of Federal Regulations, 49 CFR 395.3, "Maximum driving time for property-carrying vehicles": https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/section-395.3
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator documents every pickup event so the team knows whether the driver was late or the dock was closed: talk to the Cartage team.