Research 2026
Research Brief: Which Freight Appointment Events Belong in a Dwell Measure?
A research method for separating appointment windows, arrival, gate queues, dock service, and release in trucking records.
August 21, 2026
Research question
Which events should a trucking operation count when it studies appointment dwell? Scheduled arrival, property arrival, gate acceptance, dock assignment, loading start, loading completion, and release are all plausible boundaries, but they are not interchangeable. This brief examines how to build a measurement that remains useful when a facility, driver, and dispatch record each contain only part of the timeline.
Methodology and evidence scope
The method compares public Bureau of Transportation Statistics freight data, Federal Highway Administration freight-operations material, and FMCSA hours-of-service guidance with a proposed event register. The public sources provide context about freight movement, road operations, and driver records. They do not measure a particular receiver's performance. No private appointment system, ELD file, contract, or customer message was reviewed. All recommended measures are local analytical instruments, not national standards.
A timeline with different owners
The appointment window belongs to the agreed plan. Arrival may be supported by a geofence, driver message, gate record, or facility system. Gate acceptance is a facility event. Dock assignment and service start are operational events that may be recorded separately. Completion and release show when work ended and the vehicle could move. A departure ping alone cannot establish the reason for the preceding wait.
Store the original time zone and the source timestamp. Preserve the converted display time separately if needed. Mark each event observed, reported, inferred, or unavailable. That label prevents a clean-looking timeline from implying certainty that the record does not support.
Build a comparable sample
Sample visits over a defined period and include short, typical, and disputed stops. Segment by facility, equipment, appointment type, day, and time of day. Record the number of visits with complete event chains before calculating any summary. A median made from eight fully observed visits is a different evidence object from a median made from fifty visits where dock assignment was missing.
Useful outputs include median time from arrival to release, median time from scheduled start to arrival, share with sourced gate acceptance, share with a distinct service boundary, and age of unresolved event gaps. Consider the long tail, but do not choose a percentile merely because it sounds authoritative. The measure should support a decision such as an appointment review, a data-quality repair, or a facility-specific planning adjustment.
Interpretation rules
An early arrival may explain a long property wait but not a long dock-service interval. A late arrival may change how a receiver interprets the appointment, but it does not erase the need to document what happened after arrival. A missing source does not prove a missing event. A facility explanation should be attributed to the facility, while analysis should state what the carrier's evidence can support.
Connect dwell to hours-of-service records carefully. FMCSA rules govern recordkeeping and limits, but an administrative dwell table cannot determine a violation or a safety outcome. If a pattern may affect a driver's available hours or safe planning, route it to the authorized safety role. A coordinator can reconcile times; it should not make that determination.
Evidence roles
The comparison should also preserve the appointment's purpose. A live load, drop-and-hook move, inspection stop, and delivery with paperwork hold do not expose the same process. If the purpose is unknown, keep the visit in an “unclassified” group until someone with the right context can review it. This prevents a mixed population from producing a neat but meaningless average.
For repeat facilities, document the local vocabulary. One site may call a gate scan “arrived,” while another calls it “checked in.” Definitions should be attached to the source rather than assumed to be universal. When a process changes, record the effective date and avoid combining old and new definitions without a flag. That small bit of governance often explains a sudden shift in dwell more effectively than a performance narrative.
An assistant can collect appointment confirmations, compare messages, identify gaps, and prepare a facility review. A dispatcher or manager decides how to communicate a dispute, change the plan, or accept an explanation. The driver should not be asked to create a retroactive event merely to complete a spreadsheet. The source trail should remain honest even when it is incomplete.
Limits
There is also a selection risk. Disputed visits are more likely to have message trails than ordinary visits, while routine visits may have only a gate scan. Include both groups and disclose how they were selected. If the sample changes during the pilot, record the change. A transparent sample design is more valuable than a larger count whose inclusion rules cannot be explained.
Facilities record events differently. GPS proximity does not prove gate acceptance. A message may prove communication but not physical service. Network delays, clock drift, weather, security, and equipment conditions complicate comparison. Public freight sources are broader than local operations. This study cannot establish causation, lost revenue, contract liability, or delivery probability.
Conclusion
An appointment dwell measure is credible when it names the clock it uses and keeps scheduled, arrival, gate, service, completion, and release events separate. The evidence favors a small, segmented sample with explicit source-quality labels over a universal dwell score. That design gives a trucking team a defensible basis for improving records and planning while leaving safety and commercial conclusions with the accountable decision-maker.