trucking back office operations
Measuring detention follow-up time without overclaiming
A research brief on measuring detention follow-up time, separating the office's response from the length of a shipper wait.
Trucking VA Research Team · · 11 min read · 5 sources

Table of contents15 sections
Key takeaways
- Measure the office's follow-up, not the shipper's fault.
- Define the start, the end, and the exclusions before the first review.
- Keep the arrival evidence and the request timestamp separate.
- Report a range with a count instead of a single average.
A driver arrives at a shipper at 07:40 and checks in at 08:05. The dock assigns a door at 09:20, loading finishes at 12:10, and the driver leaves at 12:35. The detention follow-up starts somewhere in that sequence, and the choice of start point changes the number by more than an hour. The measure is only as honest as the definition behind it.
Detention follow-up time is the interval between the moment a carrier can document a delay and the moment the follow-up is complete. It is an internal measure, not a legal finding. It can show whether the office noticed a long wait and whether the request went out on time. It cannot show that a detention charge is owed or that a broker acted in bad faith.
What this brief covers
This brief defines a follow-up clock, the records that support it, and the claims it can carry. It is written for a small carrier that tracks detention informally and wants a more consistent record. It covers arrival evidence, request timing, response timing, and the cases that should be excluded. It does not offer a rule for what a shipper must pay.
The brief treats the wait and the follow-up as two separate facts. A long wait with a fast request is a different problem from a short wait with a request that sat for a week. Keeping the two apart is the main discipline the model asks for. Without that separation, the number becomes a complaint rather than a measurement the office can act on.
Define the start of the clock
The start should be the earliest time the carrier can prove the driver was available. That is usually the gate-in time, the check-in time, or the appointment time, whichever is documented and late enough to be credible. Using the appointment time when the driver arrived two hours early inflates the wait. Using the gate time when the driver sat in a parking lot outside the property deflates it. Pick one rule, write it down, and apply it to every load.
Many carriers use the appointment time because it is easy to find. That is defensible only when the driver actually arrived by then. If the driver was late, the appointment time is not the start of a shipper-caused delay. Record the arrival separately and compare the two. The gap between them explains why the same shipper can look generous on one load and strict on another.
Define the end of the clock
The follow-up ends when the request is sent with the supporting documents, not when the driver leaves the dock. Those are different events and they answer different questions. The departure time measures the wait, while the send time measures the office's response. A carrier that measures only the wait will miss the week when requests sat in a draft folder. Measure both and keep them separate.
The response time is a third interval. It starts when the request is sent and ends when the broker or shipper replies with a decision or a request for more information. Record the reply and the person who handled it. Do not treat an automated acknowledgement as a decision. A response clock that stops at an auto-reply will make every broker look fast.
What the measure can show
The measure can show whether the office followed its own rule. If the rule says a request goes out within one business day of departure, the log can show which requests did and which did not. It can show the median and the longest lag by shipper and by desk. Those are process facts, and they are actionable without a legal conclusion.
It can also show where the supporting documents are missing. A request that waits for a signed bill of lading is a different problem from one that waits for a dispatcher to write an email. Recording the reason for the delay separates a documentation gap from an attention gap. That distinction decides whether the fix is a checklist or a staffing change.
A third use is consistency across desks. Two dispatchers may handle the same shipper very differently, and the log can make that visible without naming a villain. The review can compare the rule, the exceptions, and the send times. If one desk is fast because it skips the documents, the log should show that too. Speed without the supporting file is not a better process.
What it cannot show
The measure cannot show that detention compensation is owed. Detention terms live in the contract, the rate confirmation, or the broker's accessorial schedule, and the log does not interpret them. A long wait may fall outside the free time, or it may be excluded by an appointment clause. The log can support a conversation about the terms, but it cannot settle it.
It cannot show who caused the wait. A late dock assignment, a paperwork error, a product hold, and a trailer shortage can all produce the same interval. The log records the time, not the reason. A review that assigns blame from the clock alone will be wrong often enough to lose the room. Read the notes and the gate record before drawing a conclusion.
It cannot compare shippers fairly without a common rule. One shipper may report gate times in minutes, another in quarter hours, and a third may have no gate log at all. A ranking built on those inputs measures the recordkeeping, not the operation. Report the source and the completeness beside every comparison, and resist the urge to publish a league table.
Methodology
This brief reviews public guidance on records, internal control, time measurement, and driver hours, and maps it to a private detention workflow. The sources support documentation discipline and consistent clocks. They do not create a detention obligation or define reasonable free time. The proposed measure is an internal operating tool that a carrier can test and revise against its own records.
We tested the model against four cases: a short wait with a same-day request, a long wait with a same-day request, a long wait with a late request, and a wait that should have been excluded because the driver arrived late. The cases separate the size of the wait from the speed of the follow-up. That separation is the point of the measure. It also keeps a single bad afternoon from being read as a policy failure.
Record the arrival evidence
Keep the first document that shows the driver was on the property. A gate ticket, a check-in slip, an appointment screen photo, or a text from the driver can all work if the time is visible. Record the type of evidence beside the time, because a gate ticket and a driver's memory are not equal. If there is no evidence, record the arrival as estimated and exclude it from the strict measure.
Ask the driver for the arrival time at the dock, not at the end of the day. A message sent while the wait is fresh is more reliable than a recap a week later. A short prompt in the driver app can collect the time and the door number together. The office should not have to reconstruct the morning from memory. A small habit at arrival prevents a large argument later.
Separate the request from the response
The request should carry the load, the arrival time, the departure time, the free time, and the supporting documents. Record the send time from the system that sent it, not from the time someone remembers sending it. Record the recipient and the channel. A request sent to the wrong inbox is a request that did not happen, even if the timestamp looks good.
The response should be recorded with the same discipline. Note the decision, the amount if any, the person, and the time. If the answer is a request for more documents, record that as a step and keep the clock running. If the answer is silence after the stated follow-up window, record the follow-up attempt. A response log with no follow-up is a list of hopes.
Handle the cases that do not fit
Some waits should be excluded from the strict measure. A driver who arrived after the appointment, a load cancelled at the dock, and a wait caused by the carrier's own paperwork are the common examples. Record the exclusion and the reason instead of deleting the row. The excluded set is useful because it shows how often the rule does not apply. A measure with no exclusions is usually hiding them.
Multi-stop loads need their own rule. A wait at the second stop may be caused by the first, and a single clock across the load will hide which stop produced the delay. Record each stop separately and report the follow-up by stop. A load-level average is fine for a summary, but it is not enough for a conversation with a shipper.
Report a range, not a promise
Report the count, the median, and the longest lag rather than a single average. An average hides the handful of requests that took a week. Report the share sent within the rule and the share with no recorded response. A range with a count is more honest than a percentage with no denominator. The reader should be able to see how much of the batch is complete.
Do not turn the measure into a promise to drivers. A fast follow-up does not guarantee a payment, and a slow one does not prove neglect. Tell drivers what the office will do and when, and record whether it happened. The measure is a check on the office, not a contract with the driver. Keeping that boundary clear protects trust on both sides.
Review the follow-up queue
Open the queue once a week and list every request without a response. Age the list by send date and assign an owner to each row. A request that has waited two weeks needs a decision, not another reminder. Close the row with the outcome, even when the outcome is no payment. An open queue with no owner is the most common failure in the whole process.
The queue should also show the requests that were never created. A long wait with no request is the clearest signal that the office missed the load. Compare the arrival records with the request records for the same week. The difference is the silent gap, and it is often larger than the response lag everyone talks about in the weekly review.
Bounded pilot
Run the pilot for one month on one desk. Record the arrival evidence, the request time, the response time, and every exclusion. Ask a reviewer who did not handle the loads to recompute three cases from the source documents. If the numbers differ, the definitions are not clear enough. Then change one definition, write it down, and repeat the month.
Keep the pilot small enough to finish. A month of loads from one desk is enough to find a pattern and short enough to correct. Report the number of loads, the exclusions, and the missing evidence in the same summary. A pilot that hides its gaps will produce a confident number and a bad decision that is hard to reverse.
Limitations
This brief describes an internal measurement model. It does not establish a legal entitlement, a contract term, or a standard for reasonable detention. The cited sources support records, control, timing, and hours-of-service context. Results depend on the quality of the arrival evidence and the completeness of the response log. A carrier with no gate records should treat the measure as an estimate.
The model also assumes that one desk owns the follow-up from arrival to response. In a small office, the same person may dispatch the load, send the request, and answer the broker. That concentration makes the measure easier to collect and harder to check. A second reviewer should look at a sample before the number is shared outside the office.
Sources
- Hours of Service; Federal Motor Carrier Safety Administration; checked November 18, 2026.
- The Green Book; U.S. Government Accountability Office; checked November 18, 2026.
- Records Management; U.S. National Archives and Records Administration; checked November 18, 2026.
- Time and Frequency Division; National Institute of Standards and Technology; checked November 18, 2026.
- Manage your business; U.S. Small Business Administration; checked November 18, 2026.
Conclusion
Detention follow-up time is useful when it measures the office's response rather than the shipper's fault. Define the start, the end, and the exclusions before the first review. Report a range with a count, and keep the legal question separate from the operating one. A carrier that does this can improve its follow-up without overclaiming what the clock proves. For related workflows, see the load status update log brief and the trucking VA services overview.
Sources and citations
- Federal Motor Carrier Safety Administration, Hours of Service, https://www.fmcsa.dot.gov/regulations/hours-of-service, retrieved 2026-11-18
- U.S. Government Accountability Office, Standards for Internal Control in the Federal Government, https://www.gao.gov/greenbook, retrieved 2026-11-18
- U.S. National Archives and Records Administration, Records Management, https://www.archives.gov/records-mgmt, retrieved 2026-11-18
- National Institute of Standards and Technology, Time and Frequency Division, https://www.nist.gov/time-frequency, retrieved 2026-11-18
- U.S. Small Business Administration, Manage your business, https://www.sba.gov/business-guide/manage-your-business, retrieved 2026-11-18