Driver arrival and detention: the complete guide to stop records

Key Takeaways

When a driver’s arrival claim conflicts with the dock record, keep both statements and check what each time means. Confirm the site, load, carrier, trailer and time zone. Arrival is not the same as pickup, and a disputed arrival time should not automatically become an approved detention charge.

• Save each time with its source.
• Distinguish gate arrival, site check-in, dock arrival and departure.
• Ask the site for its record where that workflow is configured.
• Keep “arrived” and “picked up” as separate events.
• Use agreed terms and supported times when reviewing detention.

Why can two arrival records disagree?

A driver may report arrival at the property while the warehouse records check-in at the receiving desk. Both records may describe real events at different points. Start by identifying the event before deciding which timestamp should be used.

Other differences can come from a wrong time zone, an incorrect load reference, a delayed message or a trailer recorded against the wrong appointment. Shipment tracking software should help the team investigate the difference without deleting the original statements.

Separate the event time from the time the message arrived. A carrier email received at 8:40 a.m. may state that the truck reached the gate at 8:05 a.m. Recording only 8:40 loses the claim; recording only 8:05 loses when the team learned about it.

Use the correct stop. A truck can visit more than one facility on a route. GPS close to a customer’s city does not establish check-in at the intended receiving site. The location and shipment identity need their own check.

LTL tracking may use carrier updates tied to a PRO number, a shipment reference used by the carrier. Confirm that the PRO belongs to the load being reviewed. A plausible status for a different shipment is still the wrong evidence.

Which records should the team compare?

Start with a small evidence set. Preserve the original wording and timestamps, then identify what each record can establish. Do not replace a carrier’s statement with a site’s statement before the difference is understood.

Record	What it may show	What to check
Driver call or text	The driver’s arrival claim	Site, load and meaning of arrival
Carrier API or website	Carrier milestone and event time	Correct shipment and status definition
GPS or ELD data	Vehicle position or movement	Vehicle identity and location precision
Site check-in log	The facility’s recorded event	Gate, desk or dock event
Signed BOL or departure confirmation	Evidence supporting pickup	Correct load and current document

Ask the warehouse or receiver for the event it actually records. “Truck at gate” and “truck assigned to a door” should not share one unnamed arrival field. Simple labels make the later conversation easier.

Keep the person or system that provided each item. If the facility corrects an entry, preserve the original and the correction when the workflow supports it. The final explanation should state why the team accepted the current account.

When data is unavailable, keep the arrival unresolved and name the person responsible for follow-up. Absence of a site record does not by itself prove that the driver was late or that the driver’s claimed time is correct.

How do you confirm the right truck and load?

Compare the carrier, trailer number and load number with the carrier’s confirmation. Ask the site to check the same identifiers. Start here if a driver appears checked in but the warehouse cannot find the load.

Where the site shares check-in details, Wilson compares those identifiers, flags a mismatch and corrects the records once the right load is confirmed. This depends on the site providing the details. Do not assume Wilson can read every facility’s check-in system.

If the truck is at the wrong address or the load number is wrong, ask the responsible people to confirm the next instruction. Record who agreed to it. A corrected reference should not silently become permission to change a delivery address or service commitment.

When Wilson contacts a driver directly, the carrier must have shared the driver’s contact information. Wilson also works with carrier dispatch by email, API or EDI where supported. Use the configured contact path rather than assuming a driver’s number is always available.

Close the identity issue before combining the times. A timestamp from the wrong trailer can create a false delay record, a wrong customer update and a later invoice dispute.

When should arrived become picked up?

Keep the two statuses separate. Arrival means the truck reached the defined point. Pickup means the load has moved into the confirmed pickup state. The second event needs its own evidence.

Wilson records arrival and marks a load picked up when the signed bill of lading, or BOL, or the departure is confirmed. A driver saying “I am here” is not that evidence. A scheduled appointment also does not establish pickup.

Bill of lading software should help the team keep the signed document with the correct shipment. If a BOL changes after booking, Wilson keeps each version with its source and time. Changes to address, class, carrier or price go to the load owner.

Ask what happened after check-in. Is the truck waiting, loading, loaded but not released, or departed? A short status with a next action is more useful than a single green arrival marker.

Notify the configured people when the pickup is confirmed. Keep any separate loading or document problem open until it is resolved. One completed milestone does not make every task on the shipment complete.

How should detention be reviewed when times differ?

Review the agreed detention terms before calculating a charge. The relevant starting event, appointment treatment, free time and billing increments come from the shipment agreement. Do not use a generic rule as though it applies to every carrier.

Wilson audits detention lines against the recorded times and the agreed terms. It sends unsupported charges back to the carrier with the evidence. A dispute over arrival should therefore stay visible in the invoice review.

In a fictional example, the driver claims 8:00 a.m., the site records gate check-in at 8:40 a.m. and departure is confirmed at 11:10 a.m. First determine what the contract uses as the start and whether the two arrival records refer to the same event. The difference is not solved by choosing whichever time produces the lower bill.

If the agreement uses confirmed gate check-in and provides two hours free, the period from 8:40 to 11:10 is two hours and thirty minutes before applying any other contract conditions. That example illustrates elapsed time only. It does not approve a charge or establish the applicable rate.

If a billed line does not match what was booked, Wilson sends the whole invoice to a person. Wilson does not make partial payments. Keep the arrival evidence and the commercial decision connected.

What should buyers test in a tracking demo?

Bring two conflicting arrival statements for the same stop. Ask the presenter to retain both, label their sources and show the follow-up. Then introduce a wrong trailer number and see whether the workflow identifies it before changing the shipment status.

Next, provide a signed BOL or a confirmed departure. Ask when the load becomes picked up and where the evidence is filed. If the document is revised, inspect the version history and load-owner handoff for material changes.

Finally, add a detention line using the earlier claimed arrival time. Ask how the records and accepted terms reach the invoice review. A tracking demo that stops at a map misses the operating and payment consequences.

Use the customer update guide when deciding what to tell the shipper or receiver while the facts remain open. Share the supported milestone and uncertainty. Do not communicate a disputed event as settled.

An AI logistics coordinator is useful here when it gathers the missing fact, contacts the right party and moves the case toward a supported status. Ask Cartage to demonstrate the exact site-data and carrier-contact setup for your facilities.

FAQs

Should the driver’s time or the dock time always win?

Neither should win automatically. Check the event definition, shipment identity, source, time zone and agreement. The two times may describe different events.

Can Wilson request the site’s check-in and departure times?

Yes, where configured. Wilson saves arrival claims with their sources and compares them with the site’s record.

Does arrived mean picked up?

No. Wilson records arrival separately and marks pickup when the signed BOL or departure is confirmed.

Can a disputed arrival create a detention charge?

The charge needs the recorded times and agreed terms. Wilson audits detention lines against that evidence and returns unsupported charges to the carrier.

Sources

• Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai

Show Cartage a driver arrival claim and a conflicting dock record to test the evidence and follow-up workflow.