The driver says they arrived. What proves it?
Key Takeaways
A driver's statement that they arrived is a claim, not proof. Proof comes from records made at the time by someone other than the driver, or by a device: a gate check-in, a dock appointment log, ELD or GPS location data, or a timestamped message from the site. An AI logistics coordinator should collect these records for every stop and compare them before the arrival time is accepted.
- Arrival time decides who is responsible for a delay and whether detention applies.
- A driver's text, call, or carrier status update is a useful first signal, but it is not independent proof.
- The strongest proof is a record from the site, such as a gate log or check-in, made when the truck arrived.
- Location data from an ELD or GPS device can confirm the truck was at or near the site.
- Two records that agree are stronger than one. Records that disagree need a person to review.
- The time to collect proof is during the load, not weeks later when the invoice arrives.
- Wilson, by Cartage, is an AI logistics coordinator that tracks each load using the best source available and keeps arrival records with the shipment for later review.
Why does it matter when the driver arrived?
Arrival time matters because it decides who is responsible for a delay, whether the carrier was on time for its appointment, and whether detention charges are owed. An AI logistics coordinator should treat the arrival time as a fact to be proven, because money and blame both depend on it.
What arrival time decides
| Question | Why arrival time answers it |
|---|---|
| Was the carrier late? | Compares arrival with the appointment or window |
| Did detention start? | Free time usually starts at arrival or appointment time |
| Did the dock cause the wait? | Compares arrival with when loading began |
| Was a missed pickup the carrier's fault? | Shows whether the truck came at all |
| Was the customer told the truth? | Supports the delivery updates sent |
Detention is a fee a carrier bills when its truck waits too long at a dock. Free time is the time a carrier allows before detention starts.
Detention is common and costly
In a September 2024 study, the American Transportation Research Institute (ATRI) found that detention affected 39.3% of truck stops in 2023. The same study found that 94.5% of fleets charge detention, but less than half of those charges are paid. That gap often comes from arguments about when the truck arrived and when it left.
Federal regulators see the same problem
In a February 2024 Federal Register notice, the Federal Motor Carrier Safety Administration (FMCSA) noted that there is no standard industry definition of detention, and it used dwell time over two hours as a working measure. Dwell time is the total time a truck spends at a facility. Without a clear arrival record, there is no clear start to that time.
Arrival is not the same as check-in
A truck can arrive at the gate and wait in line before checking in. It can check in and wait for a door. It can be at a door and wait for loading to start. Each of these times is different. When a carrier says "arrived," the team needs to know which one it means.
Arrival matters at delivery too
The same questions apply at the receiver. A carrier may bill detention at delivery, or the customer may say the truck missed its appointment. The receiver's records are often harder for the shipper to get, because the receiver is a different company. That makes it even more important to ask for the receiver's check-in time on the day of delivery, while people remember.
Hypothetical example: two stories about one stop
This example is hypothetical and does not describe a real customer. A carrier bills three hours of detention at a pickup. The driver says they arrived at 7:00 a.m. for an 8:00 a.m. appointment. The warehouse says the truck checked in at 8:40 a.m. Both may be right: the driver may have parked nearby at 7:00 a.m. and come to the gate at 8:40 a.m. Without proof, the team cannot decide. With a gate log and location data, it can.
Which records prove a driver's arrival?
Records that prove arrival are those made at the time by the site or by a device, such as a gate log, a check-in record, an appointment system entry, or ELD or GPS location data. An AI logistics coordinator should rank records by how independent and precise they are, and look for at least two that agree.
Types of arrival records
| Record | Who creates it | Strength | Limits |
|---|---|---|---|
| Gate log or guard shack entry | Site security | Strong | Not every site has one |
| Dock check-in or yard system | Warehouse | Strong | May record check-in, not arrival |
| Appointment system entry | Site or scheduling software | Strong for check-in time | Depends on staff entering it on time |
| ELD location data | Truck's logging device | Strong for location and time | Shows position, not gate entry |
| GPS from a carrier app or telematics | Carrier or device | Good | Accuracy and sharing vary |
| Carrier status update via API or EDI | Carrier system | Moderate | Often entered by dispatch, not automatic |
| Driver text, call, or email | Driver | Weak alone | Not independent |
| Carrier invoice note | Carrier billing | Weak | Created after the fact |
An ELD, or electronic logging device, records a truck's driving time and status. GPS is a satellite positioning system that shows a vehicle's location. An API is a connection that lets two software systems exchange data directly. EDI, or electronic data interchange, is a standard format for exchanging business messages between systems.
What an ELD records
Federal rules require ELDs to record the date, time, location, engine hours, and vehicle miles, along with driver and vehicle identification, when the driver's duty status changes. They also require intermediate records at least once an hour while the vehicle is in motion. This makes ELD data useful for showing when a truck stopped near a site. It does not show when the truck passed through the gate.
What a carrier status update really means
When a carrier's system shows "arrived," it may come from a device, from the driver tapping a button in an app, or from a dispatcher typing it in later. Each has a different level of trust. The team should know which method each carrier uses. A status entered by dispatch an hour after the fact is a claim, not a timestamp.
Photos with time stamps
Some drivers send a photo of the gate or the check-in desk. A photo can help, especially if it shows a clock or a check-in slip. But photo times can be wrong if the phone's clock is off, and photos can be taken at other times. Photos are useful support, not the main proof.
Site records are the strongest
Records made by the shipper's or receiver's own site are usually the most trusted, because the site has no reason to favor the carrier. A gate log with a time stamp is hard to dispute. The challenge is that many sites still use paper logs or no log at all.
Two records are better than one
When a gate log and ELD data agree within a few minutes, the arrival time is settled. When the driver's text and the carrier's status update agree, they may both come from the same person. Independence matters. A good arrival proof combines one site record and one device record.
Hypothetical example: matching the records
This example is hypothetical and does not describe a real customer. A carrier claims arrival at 6:50 a.m. The ELD data shows the truck stopped 0.2 miles from the site at 6:47 a.m. and moved again at 8:35 a.m. The gate log shows entry at 8:38 a.m. The AI logistics coordinator concludes that the truck was near the site at 6:50 a.m. but did not enter until 8:38 a.m. Whether detention starts at 6:50 or 8:38 depends on the terms and on why the truck waited outside.
How should arrival proof be collected during the load?
Arrival proof should be collected at every stop while the load moves: the carrier's arrival signal first, then the site's check-in record, then location data where available, all saved with the shipment. An AI logistics coordinator can request and match these records automatically, so the proof exists before anyone needs it.
The collection workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Expect | Appointment or window set | Records the expected arrival time | Never |
| 2. Signal | Carrier or driver reports arrival | Saves the claim with its source and time | Never |
| 3. Site record | Arrival signal received | Asks the site for its check-in time or reads it from the system | When the site has no record |
| 4. Location data | Where the carrier shares it | Pulls location data for the stop | Never |
| 5. Compare | Records collected | Checks whether the times agree | When they differ by more than the set tolerance |
| 6. Save | Comparison done | Stores the accepted arrival time and the evidence | Never |
Ask the site the same day
A warehouse can usually answer "what time did the truck check in?" the same day. A week later, the paper log may be filed away and the staff may not remember. Asking on the day of the stop makes proof easy. Waiting until the invoice makes it hard.
Use the best source for each carrier
Carriers share data in different ways. Some have APIs. Some share ELD or GPS data. Some update a website by PRO number. Some answer only by phone or email. A PRO number is a tracking number a carrier gives to a shipment. The AI logistics coordinator should use the best source each carrier offers and record which one it used.
Not every carrier shares location data
Many smaller carriers do not share ELD or GPS data with shippers. For these carriers, the proof will rely more on the site's records and on calls or emails at the time of the stop. That is fine, as long as the site record exists. The team should know in advance which carriers share location data, so it knows how much to rely on the site.
Record departure too
Arrival is only half the story. Detention depends on how long the truck stayed. The same records that prove arrival should prove departure: gate-out time, signed BOL time, or location data showing the truck leaving. A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
Make the site's job easy
Warehouses are busy. A request for check-in times should be short and specific, such as "Load 8812, Carrier ABC: what time did the truck check in and leave today?" If the site can answer from a yard system or a log in one minute, it will. A daily summary request for all trucks at a site can be even easier.
Keep proof with the stop, not in an inbox
The arrival records should be saved with the shipment and the specific stop, not left in an email thread. When someone reviews detention six weeks later, they should find the gate time, the ELD data, and the site's reply in one place.
Hypothetical example: proof collected same day
This example is hypothetical and does not describe a real customer. At 9:15 a.m., a carrier's API reports "arrived at shipper" for a 9:00 a.m. appointment. The AI logistics coordinator asks the warehouse for the check-in time. The warehouse replies, "Checked in 9:12, door 4." The coordinator saves both records. Two weeks later, the invoice arrives with no detention, and the arrival question never comes up. If it had, the proof was already on file.
What should happen when the arrival records disagree?
When arrival records disagree, the team should find out why before accepting either time, because the reason decides who is responsible. An AI logistics coordinator should flag the gap, collect any missing records, and send the question to the person who owns the decision.
Common reasons records disagree
| Reason | What the records show | Usual meaning |
|---|---|---|
| Truck waited outside the gate | ELD shows truck nearby early; gate log shows later entry | Queue or early arrival; check site rules |
| Driver arrived early for the appointment | Arrival well before appointment time | Free time usually starts at the appointment |
| Check-in entered late by staff | Check-in later than gate entry | Use the gate time |
| Carrier status entered by dispatch | Status time differs from device data | Use device and site records |
| Wrong site or gate | Location data shows another address | Driver not at the right place |
| Time zone error | Records an exact number of hours apart | Correct the time zone |
Set a tolerance
Records rarely agree to the minute. A gate log may say 8:12 a.m. and the ELD 8:07 a.m. A small gap is normal. The team should set a tolerance, such as 15 minutes, within which records count as matching. Only larger gaps need a person to review. This keeps reviewers focused on real disputes.
Early arrival is not on-time arrival
A driver who arrives two hours before an appointment has not started detention in most cases. Free time usually starts at the appointment time, unless the terms say otherwise. The rate confirmation should state the rule. A rate confirmation is the document that states the agreed price and terms for one load.
Queues at the gate
Some sites have long lines at the gate. If the truck arrived on time and waited in line, the delay may be the site's responsibility. If the truck arrived late and waited, it is not. Location data plus the appointment time usually settles this.
Wrong gate, right site
Large campuses have several gates. A driver may arrive at the main gate when the shipping gate is around the corner. Location data may show the truck at the site while the shipping dock has no record. The fix is better site instructions on the booking, not a dispute after the fact.
When there is no site record
If the site has no gate log or check-in time, the team must rely on device data and the carrier's records. In that case, the team should note that the proof is weaker and decide whether to accept the carrier's time. Over time, the team should push sites to keep a check-in record.
Correct the time zone first
A surprising number of disagreements are time zone mistakes. A carrier's system may report times in its own home time zone, while the site uses local time. When two records are exactly one, two, or three hours apart, the first check should be the time zone. Every time saved with the stop should note its zone.
Who decides
The load owner, or the person who reviews detention charges, should decide when records disagree. The AI logistics coordinator should present the records side by side, the terms on the rate confirmation, and the likely explanation. The decision and its reason should be saved with the load.
How should arrival proof be used later?
Arrival proof should be used at three moments: when telling the customer about a delay, when reviewing the carrier's invoice for detention, and when reviewing carrier performance. An AI logistics coordinator should keep the proof attached to the stop, so each of these reviews takes minutes instead of days.
Uses of arrival proof
| Moment | How the proof is used |
|---|---|
| Delay update | Shows whether the delay is at pickup or in transit |
| Detention review | Sets the start time for free time and detention |
| Missed pickup | Shows whether the truck came at all |
| Carrier performance | Shows on-time arrival rate by carrier and lane |
| Site improvement | Shows which docks keep trucks waiting |
Invoice review
When a detention line appears on an invoice, the reviewer should compare it with the accepted arrival and departure times and the terms. If the proof supports the charge, it should be approved quickly. If it does not, the reviewer should send the carrier the records. Teams that want the full method can read how to audit detention charges against pickup timestamps.
Proof for missed pickups
When a carrier says the truck came but the freight was not ready, and the warehouse says the truck never came, arrival proof settles it. Location data showing the truck at the site, or a gate log entry, supports the carrier. No record at all, and location data elsewhere, supports the warehouse. Either way, the team can decide quickly and fairly.
Fair to both sides
Arrival proof protects carriers too. When a dock really kept a truck waiting, the proof supports a fair detention payment. Carriers that get paid fairly and quickly are easier to work with. The goal is accurate records, not fewer payments.
Patterns over time
When arrival proof is kept for every stop, patterns appear. One carrier may arrive late on Monday mornings. One dock may keep trucks waiting every Friday afternoon. Wilson can produce carrier-performance reports on request from the loads it executes. It does not keep a standing scorecard by default.
Use proof in carrier conversations
When the team talks with a carrier about service, arrival proof turns a complaint into a fact. "Your trucks were late to 6 of 20 appointments last month, by an average of 50 minutes" is easier to act on than "your trucks are often late." The same proof can show a carrier that its detention charges at one site are justified.
Hypothetical example: a site pattern
This example is hypothetical and does not describe a real customer. A distributor reviews a quarter of arrival records and finds that trucks at one warehouse wait an average of 2.5 hours after checking in, while trucks at its other sites wait under an hour. The team adds a dock door at that warehouse during the morning peak. Detention charges at that site drop the next quarter.
Where does Wilson fit in proving driver arrival?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers, tracks each load, and keeps the records of every stop with the shipment. 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.
What Wilson does not claim
Wilson does not create gate logs or install devices at the customer's site. It uses the records that the carrier, the site, and the customer's systems already have, and it says which source each time came from. When no independent record exists, Wilson marks the arrival time as unconfirmed.
How Wilson collects arrival records
Wilson saves each arrival claim with its source and time, asks the site for its check-in time where configured, and compares the records. When they disagree, Wilson flags the stop for the person who reviews it. 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 detention lines against the recorded arrival and departure times and the agreed 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 Cartage asks in discovery
Cartage asks which sites keep gate or check-in records, which carriers share location data, how detention is reviewed today, and who decides when the carrier and the site disagree. These answers shape the arrival records an AI logistics coordinator collects for each stop.
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 record is saved in the shipment record with change history.
Teams checking tracking claims can read why every tracking claim needs a timestamp.
This article is part of our complete guide to driver arrival and detention records.
FAQs
What proves a driver arrived?
A record made at the time by the site or a device, such as a gate log, check-in record, or ELD location data. An AI logistics coordinator looks for two records that agree.
Is a driver's text enough to prove arrival?
It is a useful signal but not independent proof. An AI logistics coordinator saves it and asks the site for its own record.
What if the arrival records disagree?
Find out why before accepting either time. An AI logistics coordinator flags the gap and sends the records to the person who decides.
When should arrival proof be collected?
On the day of the stop, while the site still has the records. An AI logistics coordinator requests and saves them during the load.
Does an early arrival start detention?
Usually not. Free time often starts at the appointment time unless the terms say otherwise. An AI logistics coordinator checks the rate confirmation before accepting a detention start time.
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/
- Federal Register, FMCSA, "Agency Information Collection Activities; Approval of a New Information Collection Request: Impact of Driver Detention Time on Safety and Operations," February 16, 2024: https://www.federalregister.gov/documents/2024/02/16/2024-03256/agency-information-collection-activities-approval-of-a-new-information-collection-request-impact-of
- Electronic Code of Federal Regulations, 49 CFR 395.26, "ELD data automatically recorded": https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/subpart-B/section-395.26
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator collects arrival proof at every stop and uses it when the detention invoice arrives: talk to the Cartage team.