trucking back office operations
What an appointment-to-arrival lag reveals about shipper dwell time
A measurement protocol for comparing scheduled appointment times with gate timestamps so a carrier can separate early arrivals, late arrivals, and actual facility dwell.
Trucking VA Research Team · · 10 min read · 9 sources

Table of contents7 sections
Key takeaways
- Appointment-to-arrival lag and gate-to-gate dwell answer different questions.
- An early arrival is not automatically a facility delay, and a late arrival is not automatically a carrier failure.
- Measure the timestamp source before comparing facilities or months.
What an appointment-to-arrival lag reveals about shipper dwell time
Published November 4, 2026.
A truck arrives at a shipper at 9:42 for a 10:00 appointment. The gate check-in takes four minutes, the dock assignment takes another twelve, and the trailer is released at 12:35. A monthly report that uses only the appointment time and the release time will call this a long dwell. A report that uses the gate-in and gate-out timestamps will call it a different number. A report that compares the 9:42 arrival to the 10:00 appointment will call it an early arrival. All three statements can be true, and none of them answers the same question.
Appointment-to-arrival lag is the gap between the scheduled time a facility gives a carrier and the time the vehicle actually reaches the facility. It is an operational measure, not a verdict. It helps a carrier see whether drivers are arriving within the window, whether appointment times are realistic, and whether a facility's gate process is adding time before the dwell clock starts. It does not, by itself, prove that a shipper caused a delay or that a carrier failed to plan.
Question and scope
The research question is: for a defined set of appointments at a defined facility, how large is the gap between the appointment time and the arrival timestamp, and how much of the total time at the facility is explained by that gap rather than by the gate-to-release interval? A second question is whether the gap is stable across shifts, days, and carriers, or whether it is concentrated in a particular window.
Scope should name the facility, the date range, the appointment types, the carriers or fleets included, and the timestamp sources. A distribution center with a strict appointment system behaves differently from a quarry with a first-come queue. A live unload behaves differently from a drop-and-hook. Mixing facility types can produce an average that describes none of them.
The scope should also define what is excluded. Appointments that were cancelled before arrival, loads that were re-routed, and arrivals with no gate record may need separate treatment. An excluded appointment is not a clean appointment. If the carrier excludes every record with a missing timestamp, the remaining sample may look better than the operation actually is.
Population and unit of analysis
Build the population from the appointment schedule or the facility's gate log, not from the carrier's detention claims. Claims are a subset of the appointments that someone decided to dispute. Starting there would bias the sample toward the worst cases and miss the ordinary arrivals that never became a claim.
The unit is one appointment tied to one vehicle visit. Record the appointment identifier, the facility, the carrier, the load, the scheduled time, the appointment window if one exists, the gate-in time, the dock-in time if available, the dock-out time, and the gate-out time. If the facility records only a gate-in and a release, the analysis should say so rather than inventing intermediate events.
Link the appointment to the load and driver only when the identifier is reliable. A carrier may swap tractors, a driver may arrive in a different unit, and a facility may record the carrier name differently from the dispatch system. The crosswalk should show its source and its confidence. A forced match can make the data look complete while attaching the wrong dwell to the wrong load.
Distinguish between a visit and a transaction. One truck may make two visits in a day, and one appointment may cover multiple trailers. The unit should be the visit that the facility measures. If the carrier and the facility count differently, the protocol should state which count it uses and why.
Definitions and measures
Define the appointment time as the time the facility told the carrier to arrive, including the start and end of any window. Define arrival as the first timestamp that shows the vehicle at the facility, usually a gate-in or a geofence entry. If the carrier uses a driver check-in call instead of a gate record, label that source clearly. A phone call is not the same event as a gate transaction.
Appointment-to-arrival lag is arrival minus appointment time. A negative value means the vehicle arrived early. A positive value means it arrived late. Report the distribution rather than only the mean, because a small number of very late arrivals can pull the average away from the typical experience. Show the median, the interquartile range, and the share arriving within the window.
Gate-to-gate dwell is gate-out minus gate-in. Dock dwell is dock-out minus dock-in. The difference between gate-to-gate dwell and dock dwell is the yard and paperwork time. That split is useful because a facility can have a short dock process and a long gate queue, or the reverse. A single dwell number hides which part of the visit is consuming the driver's day.
Also measure the appointment window, not only the appointment point. A facility that gives a two-hour window is making a different promise from one that gives a fifteen-minute slot. If the carrier compares a wide-window facility to a narrow-window facility without recording the window, the comparison is not fair. The protocol should report the window width and the share of arrivals that fall inside it.
Evidence standard
The record should preserve the original timestamp source: the gate system export, the facility portal screenshot, the appointment confirmation, the driver's message, or the ELD event. A timestamp typed into a spreadsheet from memory is a reconstruction, and it should be labeled as one. The reviewer should be able to trace every arrival value to a source without calling the driver.
Record the time zone and the daylight-saving transition if the period crosses one. A gate system in local time and a dispatch system in UTC can produce a one-hour error that looks like a facility delay. Do not change the original timestamp; add a normalized value and the rule used to convert it. The same discipline applies to appointment times that were sent in a different zone from the one the facility uses.
Keep the appointment confirmation with the load record. If the appointment changed, keep both the original and the revised time, with the time of the change and the person who made it. A revised appointment that is not recorded can make an on-time arrival look late. A confirmation that was never sent can make a late arrival look like a carrier failure when the facility never provided a usable slot.
The evidence standard should also address the negative case. If a facility does not issue gate timestamps, record that limitation rather than substituting a driver estimate without a label. If the carrier cannot obtain the appointment confirmation, say so. The absence of a source is a finding about the measurement system, not a zero.
Sampling and collection
Sample appointments across days of the week, shifts, carriers, and appointment windows. Include appointments that arrived early, appointments that arrived within the window, appointments that arrived late, and appointments with a long gate-to-gate dwell. A sample drawn only from the detention queue will overstate the problem; a sample drawn only from the facility's best-performing week will understate it.
Collect the data as close to the visit as possible. Gate logs are often overwritten or archived after a short period, and appointment portals may not retain old slots. Record the pull date and the exact filters used. If the facility changes its gate process during the study, split the period rather than averaging across the change.
Use a consistent rule for matching appointments to visits. For example, match on the appointment identifier when available, then on the load number plus the date, then on the carrier plus the time window. Report how many records required each method. A high share of time-window matches is a warning that the identifiers are weak and the dwell values may be attached to the wrong visit.
The collection should include the carrier's own arrival evidence where it exists. A geofence event or an ELD stop can confirm that the truck reached the facility before the gate logged it. That evidence does not replace the facility's timestamp, but it can explain a gap between the appointment and the gate record. Keep the two sources separate in the analysis.
Failure patterns and limits
The first failure is comparing an appointment time to a release time and calling the result dwell. That calculation mixes arrival behavior, gate processing, dock work, and paperwork. The second is treating an early arrival as free time. An early arrival may wait in a yard, occupy a door, or force the facility to reshuffle its schedule. The third is treating a late arrival as a carrier failure without checking whether the appointment was revised or the window was unrealistic.
A fourth failure is averaging across facilities with different appointment rules. A facility that accepts walk-ins and one that requires a booked slot do not produce comparable lag. A fifth failure is ignoring the gate queue. A truck can arrive on time and still wait an hour to check in, which is a facility process issue rather than a driver punctuality issue. A sixth failure is using the appointment time as the start of the driver's on-duty clock without checking the hours-of-service record.
The limits are substantial. Gate timestamps can be wrong, appointment portals can be incomplete, and a single facility's data cannot describe an industry. A carrier with a small number of visits per month will see unstable rates. The protocol measures the time between recorded events; it does not determine fault, detention liability, or whether a facility was contractually obligated to load or unload within a specific period.
Reporting and review cadence
Report the number of appointments in the population, the number matched to a visit, the number with a usable arrival timestamp, and the number excluded with a reason. Then report the median appointment-to-arrival lag, the share arriving early, within the window, and late, and the median gate-to-gate dwell with its interquartile range. Break the results out by facility, shift, and appointment window where the sample supports it.
Show the oldest unresolved data gap as well as the average. A facility with no gate timestamps is not a zero-dwell facility; it is an unmeasured one. The report should name the missing source, the person who can request it, and the date the request is due. That turns a measurement limitation into a follow-up item instead of a hidden assumption.
Review the results monthly with the dispatch lead, the billing or claims contact, and the person who maintains the appointment data. Choose one change, such as a revised arrival buffer, a facility-level appointment review, or a better gate-data request, and set a recheck date. The next sample should test whether that change affected a specific measure rather than only the headline average. The point is not to prove that a facility is slow. It is to know which part of the visit the carrier can plan around and which part it needs to escalate with evidence.
Sources and citations
- Federal Motor Carrier Safety Administration, Hours of Service, https://www.fmcsa.dot.gov/regulations/hours-service, retrieved 2026-11-04
- Electronic Code of Federal Regulations, 49 CFR 395.8: Driver's record of duty status, https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/subpart-B/section-395.8, retrieved 2026-11-04
- Electronic Code of Federal Regulations, 49 CFR 395.1: Scope of rules, https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/subpart-A/section-395.1, retrieved 2026-11-04
- U.S. Bureau of Labor Statistics, Heavy and Tractor-Trailer Truck Drivers, https://www.bls.gov/ooh/transportation-and-material-moving/heavy-and-tractor-trailer-truck-drivers.htm, retrieved 2026-11-04
- U.S. Bureau of Labor Statistics, Transportation and Warehousing, https://www.bls.gov/iag/tgs/iag48-49.htm, retrieved 2026-11-04
- Bureau of Transportation Statistics, Freight Transportation, https://www.bts.gov/topics/freight-transportation, retrieved 2026-11-04
- Federal Highway Administration, Freight Analysis Framework, https://ops.fhwa.dot.gov/freight/freight_analysis/faf/index.htm, retrieved 2026-11-04
- U.S. Department of Transportation, National Freight Strategic Plan, https://www.transportation.gov/freight/national-freight-strategic-plan, retrieved 2026-11-04
- Electronic Code of Federal Regulations, 49 CFR 379.3: Preservation of records, https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-379/subpart-A/section-379.3, retrieved 2026-11-04