Research 2026
Research Brief: What Evidence Makes Freight-Terminal Detention Reviewable?
An evidence-led study of the records small carriers need to distinguish terminal detention from incomplete appointment and arrival documentation.
August 21, 2026
Research question
When a truck waits at a freight terminal, what evidence lets a small carrier separate billable detention from an appointment problem, an early arrival, a missing check-in, or an ordinary queue? This question matters because a single elapsed-time number collapses several different events. A carrier that treats every long visit as detention can create an inaccurate customer claim; a carrier that records only a final departure time cannot explain a legitimate delay. This study examines a practical evidence model for trucking operations without setting a universal detention threshold or making a legal conclusion.
Why the record is harder than the clock
The Federal Motor Carrier Safety Administration describes detention as time a driver spends waiting beyond the time reasonably necessary for loading or unloading, but the operational record still needs context. The Bureau of Transportation Statistics' freight data likewise shows that movement and location measurements depend on their source and collection method. A terminal appointment, gate scan, dock assignment, loading completion, and release can all be accurate while answering different questions.
For a small carrier, the useful unit is therefore an event bundle: the agreed appointment, the arrival or check-in evidence, the first service event, the completion event, the release or departure event, and the communication trail. Each event should carry a source, timestamp, time zone, and confidence note. Facts should remain separate from the analyst's interpretation.
Method and evidence scope
This review uses documentary analysis of public transportation and safety materials, then tests those concepts against a proposed sample design for carrier records. The scope includes ordinary dry-van and refrigerated terminal visits as an operating example, but it does not claim that every facility uses the same process. No private rate confirmations, driver records, customer contracts, or live tracking feeds were reviewed. Public sources explain measurement concepts; they do not prove what happened on a particular load.
The minimum event chain
Start with the appointment evidence. Record the scheduled date, local time, facility identifier, load reference, and any stated free-time rule in the carrier's authorized source. Next record arrival and check-in separately. A driver may reach the property, queue at a gate, and receive a check-in confirmation at three different times. Treating them as one timestamp hides the precise waiting interval.
The service interval needs two boundaries as well. Dock assignment or loading start is not necessarily the same as the first action by facility staff. Record what the source actually says, then label an inferred boundary as inferred. Finally capture completion and release. A departure timestamp without release context can reflect a driver who left voluntarily, was released after loading, or moved to a staging area.
Sampling design for small fleets
A useful first sample can cover four weeks and include both short visits and disputed long visits. Select records by operating lane, facility, equipment type, and outcome rather than selecting only claims. For each record, reviewers can answer five questions: Can the appointment be verified? Can arrival be verified? Is check-in distinct from arrival? Is the service boundary documented? Is the end state supported by a source?
The review should preserve missingness as a finding. “No check-in source available” is not the same as “driver did not check in.” Add a reason code for unavailable facility data, driver app outage, conflicting clocks, customer instruction, or incomplete handoff. This avoids turning a documentation gap into an accusation about performance.
What the sources can and cannot establish
FMCSA material supports the importance of reliable operational information and the safety consequences of delay, but it cannot adjudicate a commercial claim. BTS data can provide context about freight movement and time, but a national dataset does not establish a single terminal's appointment practice. The American Transportation Research Institute's work on detention is valuable for understanding industry effects, yet an industry association report is not a substitute for the underlying contract or facility record.
Analysis begins only after those boundaries are explicit. A long gap between arrival and release may be consistent with detention, but it may also include an unrecorded break, a driver-initiated reposition, or a facility closure. The finding should therefore be phrased as “record supports review of a delay” until the responsible parties apply the governing agreement.
Operational roles and delegation
An assistant can collect timestamps, reconcile the load reference, attach source links, compare the event sequence with the appointment, and place an exception in a review queue. The accountable carrier manager should decide whether to submit a claim, accept a customer explanation, or escalate a contract question. A role boundary protects the evidence from becoming an unauthorized commercial judgment.
The queue also needs a closure rule. A record is not closed when someone sends an email. Close it when the response, decision, adjustment, or reason for no action is attached. Keep the original source and the interpretation visible together, with the interpreter and review date identified.
Measures worth testing
Useful local measures include the share of visits with all five event boundaries, median time from valid arrival to release, percentage of records with a facility-source timestamp, percentage of claims returned for missing evidence, and age of unresolved reviews. These are process measures, not promises about revenue or recovery. Segment by facility and lane before comparing. A facility with better data may appear to have more exceptions simply because its records are more complete.
Limitations
This is a proposed documentary model, not a statistically representative estimate of terminal detention. Public sources use different definitions, populations, and collection methods. Contract language, facility practice, electronic logging, and local conditions vary. Weather, congestion, security screening, and equipment problems can affect the same timeline. The model cannot determine liability, compensation, compliance, or a driver's legal status. Those decisions belong to authorized operational, legal, safety, or commercial reviewers.
Evidence-led conclusion
The evidence supports a narrow conclusion: freight-terminal detention becomes reviewable when the record preserves the appointment, arrival, check-in, service, release, and communication events as separate, sourced facts. Elapsed time is a useful prompt for review, not a conclusion by itself. A small carrier can pilot this model on a bounded set of visits, code missing evidence honestly, and keep commercial judgment with the accountable manager. That approach produces a clearer record without pretending that one clock answers every terminal question.