Dock appointment, detention and dwell records: why AI teams value them

What a dock and dwell record captures#

A dock and dwell record captures the life of one truck visit at a facility, from the booked appointment to the moment the truck leaves the gate. Each step has a timestamp, and the gaps between them measure where the time went.

Shippers, receivers, 3PL warehouses and carriers each hold part of the same visit. The facility sees the dock side; the carrier sees the wait from the cab and bills for it.

• 1Appointment: requested window, confirmed window, reschedules and who asked for them.
• 2Arrival: when the truck reached the gate or geofence, and whether it was early, on time or late.
• 3Check-in: when the driver was processed and the paperwork accepted.
• 4Door assignment: when a door opened up, or how long the trailer sat in the yard.
• 5Unload or load: start and finish, with piece counts and any exceptions.
• 6Departure: gate-out time and the signed delivery receipt or bill of lading.
• 7Cause note: the reason for any delay, from short staffing to a missing PO or a late carrier.

Why AI teams value the gaps between timestamps#

AI teams value the gaps between timestamps because each gap is a labeled outcome tied directly to an operating decision. A long wait between check-in and door assignment points to dock capacity; a long unload points to freight condition, labor or paperwork.

Those labeled gaps support appointment scheduling assistants, dwell and detention prediction, labor planning and tools that draft or review detention charges. Developers also use them to evaluate scheduling agents, checking whether a proposed slot would have reduced waiting against what actually happened.

Cause notes are the difference between a timing log and a teaching record. A gap with no explanation tells a model that something happened; a gap with a note saying receiving was waiting on a missing ASN tells it why, and what cleared it.

Field by field: what each timestamp tells a model#

Each timestamp in a dock record answers a different operational question, and a missing one breaks the chain at that point. The table shows what each field tells a model and which kind of tool depends on it, so you can see which gaps matter for the use a buyer has in mind.

Where detention and dwell records come from#

Detention and dwell records come from several systems that rarely share a clock. Dock scheduling tools hold appointments, yard management systems hold gate and door events, the WMS holds receipt times, the TMS holds check calls and EDI status events, and telematics platforms may record geofence arrivals for an asset fleet.

Detention billing adds a separate trail: accessorial invoices, the carrier's detention claim, the shipper's or receiver's response and the final settlement. Detention usually starts after the free time allowed in the rate confirmation, contract or tariff, so each dispute turns on which arrival and departure times both sides accept. Those records show how each side used the timestamps in an argument, which is useful for tools that review or contest charges.

Before scoping, compare the same visits across systems. Time zones, daylight saving shifts and manual entries create disagreements, so write down which source wins for each event and apply that rule across the whole archive.

What reduces the value of dock records#

Dock records lose value when the chain is incomplete, when timestamps were entered after the fact or when the cause is never recorded. Most facilities have some of each, so the scoping job is to find the periods and sites where the chain is reliable.

A simple test helps. Pick a recent month at each site, pull every visit and check how many carry every element of the chain, from appointment to cause note. Sites and periods where most visits pass form the core package; the rest can wait for a later phase.

Driver details, carrier names and customer names are tokenized or removed, and detention amounts usually come out after counsel's review. Facility identities are often generalized to a facility type and region.

• 1Backfilled times: unload start and finish entered together at the end of a shift.
• 2Overwritten appointments: reschedules that erase the original window and who changed it.
• 3Generic causes: one catch-all code used for most delays.
• 4Uneven rollout: sites that adopted the scheduling tool at different times.
• 5Identity leakage: driver names, phone numbers and plates in gate logs and notes.
• 6Commercial detail: detention rates and settlement amounts in billing records.

Illustrative: a food distributor's receiving docks#

Illustrative: a fictional foodservice distributor runs several distribution centers with a dock scheduling tool, a WMS and a yard system installed only at its two newest sites. Inbound carriers often bill detention, and the receiving manager disputes many charges by email.

The COO scopes the package to the sites with a yard system, where the timestamp chain is complete, and adds detention disputes linked by appointment number. Cause notes are mapped to a short cause list, with the original text kept alongside after redaction.

Carrier, driver and supplier names are tokenized, plates are removed from gate logs and detention amounts are dropped. The distributor approves the package for a buyer building scheduling and dispute review tools, and leaves the older sites for a later phase.

How SourceX approaches dock and yard records#

SourceX approaches dock and yard records by checking linkage and clock consistency first, because those decide whether the history can be used at all. The fit check in the Supply step asks which systems record each event and how many years and sites are covered, without collecting files.

Under the SourceX Enterprise Data Value Framework, a complete chain with cause notes rates higher on human-generated signal and data cleanliness than a gate log alone, while the privacy burden of driver details and the preparation cost of reconciling clocks reduce net value.

If the supplier proceeds, the SourceX Evidence Packet documents the source rule for each timestamp, the privacy treatments applied and the permitted use the supplier approved.