Freight Appointment Data Quality in Small Fleets: A 2026 Research Test

Research question: Can a small fleet explain a missed or delayed appointment from its own dispatch records, or does the record preserve only a promised time?

The research problem

An appointment is not one timestamp. A load may have a requested window, a confirmed slot, a check-in event, a loading start, a release event, and a departure. If a dispatch system stores only the original appointment, a later review cannot tell whether the problem was a changed schedule, late arrival, facility dwell, or incomplete documentation. That ambiguity matters to a carrier deciding what to escalate and to an administrative team preparing a clean exception packet.

The Federal Highway Administration's freight resources describe freight movement and the role of bottlenecks in the transportation system. FMCSA's hours-of-service material explains why a delay can affect a driver's available duty time and recordkeeping obligations. BTS's Freight Analysis Framework provides modeled freight-flow context. None of these sources provides a universal appointment accuracy rate for a small carrier. They help define why the fields matter, not what a particular operation's result will be.

Method: test the event chain

This study proposes reviewing every appointment change and exception opened during a fixed 30-day period. For each load, retain the appointment source, the time it was received, the time it was confirmed, the actual arrival evidence, the release evidence, and the person who entered each update. Mark whether a value is scheduled, observed, reported by a third party, or calculated. Do not merge a text message and a facility timestamp into one “actual” field without recording their provenance.

The primary measure is event-chain completeness: the number of reviewed loads with all required event types divided by the number of reviewed loads. Secondary measures are update lag, unresolved age, and the share of changes with a reason code. These are proposed local calculations. The method does not infer causation from a missing timestamp and does not treat one facility's pattern as a national benchmark.

The useful distinction between schedule and observation

The appointment confirms what was expected. A gate log, telematics event, signed document, or contemporaneous driver message may show what was observed. They can disagree without either record being fraudulent; clocks, time zones, rounding, and data-entry timing can differ. A reliable queue keeps both values and records the reconciliation decision. The report should say “scheduled 09:00, reported arrival 09:18, source retained” rather than silently replacing one with the other.

For a small fleet, this can be a narrow administrative workflow. A support specialist can collect the source, normalize time-zone notation, and ask for a missing event. The dispatcher or owner decides how to handle a live service problem. Safety, contractual, claims, and legal decisions remain outside a clerical completeness score.

Reading external evidence correctly

FHWA freight material is useful for system-level context: facility delay sits within a larger movement network. FMCSA guidance is relevant to duty-time implications, but it does not define a customer's detention or service-failure rule. The Freight Analysis Framework can support corridor and commodity context, but modeled flows are not a record of one truck's appointment. Combining these sources into one percentage would mix unlike denominators. The defensible finding is that an operation needs its own event-level evidence before it explains a local delay.

A practical review design

Separate three failure modes. “Missing planned field” means the confirmation was never captured. “Missing observed field” means the load moved but the arrival or release evidence was not retained. “Conflicting field” means two sources disagree and need review. Count each category separately. Then inspect the oldest unresolved cases and the facilities or appointment types where the same failure repeats. A small sample can identify a broken handoff; it cannot prove a facility-wide cause.

Limitations

The proposed sample favors loads that generated an exception and may not represent ordinary freight. Telematics may be unavailable, facility records may be inaccessible, and driver messages may be retrospective. Time-zone normalization can create apparent precision that the original source did not have. The method therefore recommends displaying source type and confidence beside any calculated measure. It does not recommend publishing a carrier's internal rate or comparing customers publicly.

Evidence-led conclusion

The answer is conditional: a small fleet can explain appointment performance only when it preserves both the expected schedule and the observed event chain. Federal freight and safety sources provide context and boundaries, while the carrier's dated records establish what happened at a stop. Measuring completeness, update lag, and conflict count gives dispatch and back-office teams a useful local test without pretending that a spreadsheet can settle a contractual or safety decision.

A time-zone and source reconciliation test

Before calculating an interval, write down the time zone used by the appointment and the time zone used by the observation. If a facility message says 14:10 without a zone, preserve the original value and mark the normalized value as an interpretation. Do not manufacture minute-level accuracy from a source that was entered after the event. A reviewer should be able to move from the normalized timestamp back to the original message, gate record, or telematics event.

This approach also makes operational coaching more precise. If confirmations are present but release events are missing, the next experiment may concern driver or facility-document capture. If observed times exist but change reasons are absent, the problem may be dispatcher update discipline. If the same appointment changes repeatedly before pickup, the team may need a single source of truth for customer instructions. Each hypothesis should be tested against a new cohort rather than treated as a conclusion from the first month.

Sources

1. Freight Management and Operations, Federal Highway Administration, accessed August 23, 2026.
2. Hours of Service, Federal Motor Carrier Safety Administration, accessed August 23, 2026.
3. Freight Analysis Framework, Bureau of Transportation Statistics and Federal Highway Administration, accessed August 23, 2026.