Accessorial Evidence Queues in Trucking: Research 2026

Research question: Which records make a trucking accessorial request reviewable, and which gaps leave a carrier arguing from memory?

Detention, layover, lumper, redelivery, and other accessorial requests usually fail in the handoff between an event and an invoice. A driver remembers the delay, dispatch remembers a phone call, and billing sees a rate confirmation with no supporting time record. The result is a queue of claims that cannot move because nobody knows which fact is missing.

This research does not assume that an accessorial is owed whenever a truck waits. Entitlement depends on the governing agreement, facility facts, and approval rules. The narrower question is what evidence makes a request clear enough for the person with authority to review it.

The record should show an event, not a conclusion

Start with arrival and departure timestamps, facility identity, load or stop identifier, and the source of each time. A geofence event, gate ticket, signed receiving record, driver message, appointment confirmation, and facility email do not have identical evidentiary weight. Labeling the source lets a reviewer ask a focused question rather than treating every timestamp as equally reliable.

The Federal Motor Carrier Safety Administration's records materials show why transportation documents and electronic communications matter during an operational review. The Surface Transportation Board provides public context for transportation records and carrier practices, although it does not decide a private accessorial request. The Federal Highway Administration's freight research helps explain why facility dwell and shipment handoffs affect the wider freight system, but it does not create a payment right.

The second part of the record is the rule being applied. Store the relevant confirmation, contract excerpt, customer instruction, or approved tariff reference with the request. A coordinator can identify which document appears to govern. The accountable commercial owner must interpret it and approve or reject the request.

Four ways evidence queues become unreliable

The first failure is a timestamp without a timezone. The second is a departure time copied from a later message without preserving the original. The third is an accessorial code selected before someone verifies the event. The fourth is a customer response stored in an inbox with no connection to the request. Each failure increases the amount of reconstruction required.

The remedy is a status model that records what is known. Use states such as opened, source requested, evidence received, rule review, decision needed, submitted, disputed, and closed. Include a reason for each return. "Missing proof" is less useful than "no gate-out time from facility record" or "appointment confirmation absent from load file."

Measuring the queue without inventing an industry benchmark

A carrier can calculate median time from event to evidence request, evidence completion time, percentage of requests returned for a missing field, first-pass approval rate, and age of unresolved disputes. Segment results by customer and accessorial type. A combined average can hide one customer whose process is responsible for most rework.

The measurement window should be fixed before the audit. Keep cancelled loads and duplicate requests in a separate category. A request closed quickly because it was withdrawn is not the same as one approved on first review. This distinction matters if management uses the queue to decide whether a process changed.

Preparation and approval are separate jobs

Administrative support is well suited to opening a record, matching documents, requesting a missing gate ticket, and building a chronological event summary. It can also draft a submission that cites the source beside each claimed event. That work reduces search time while preserving the original files.

Approval belongs to the owner of the customer relationship, contract, or operating policy. Support staff should not promise payment, alter a source record, classify a disputed event as approved, or negotiate a waiver outside the assigned authority. The best queue makes this boundary visible instead of hiding it behind a generic completed status.

Method and limitations

This report synthesizes federal transportation records guidance and freight research, then tests those concepts against a proposed accessorial evidence schema. The sources provide context for records, freight movement, and operational review. They do not publish a national accessorial approval rate, and the proposed measures are internal controls rather than market statistics.

Source quality is also uneven. A facility timestamp may be precise but not explain why a truck waited. A driver message may explain the event but use an approximate time. Reviewers should preserve both instead of choosing a convenient record and deleting the conflict. Contract language can also differ by customer, so a queue cannot replace a current commercial review.

Evidence-led conclusion

An accessorial queue becomes useful when every request states the event, source, governing rule, missing fact, and decision owner. The public evidence supports careful records and clear boundaries, not an automatic approval formula. For a trucking operation, the first improvement is therefore traceability: let a reviewer move from the claim to the original time record and the rule that controls it.

Source register

1. FMCSA electronic field operations training manual, Federal Motor Carrier Safety Administration, accessed August 19, 2026.
2. Freight transportation research, Bureau of Transportation Statistics, accessed August 19, 2026.
3. Freight management and operations, Federal Highway Administration, accessed August 19, 2026.
4. Surface Transportation Board, Surface Transportation Board, accessed August 19, 2026.

FAQ

Does a timestamp prove detention?

No. It documents one part of the event. The reviewer still needs the applicable agreement, appointment facts, exclusions, and any required approval.

What is the best queue status?

Use a status that explains the next action, such as source requested or decision needed. A generic open or closed label hides the reason a request is stalled.

Who should approve an accessorial?

The person with authority under the customer relationship, contract, or operating policy should decide. Administrative staff can prepare and document the request.