Dwell time is a facility-performance measure. It starts when the equipment arrives (or when the appointment window opens) and ends when loading or unloading begins, or when the equipment leaves. High dwell at a specific shipper or receiver is a predictable, repeatable cost.
It is related to but broader than detention. Detention is the billable portion of excessive dwell — the time past a free window that the carrier can invoice for. Dwell time includes that plus the "normal" wait that no one pays for.
Operations teams track dwell by facility so they can price it in. A lane into a receiver that averages four hours of dwell is not the same load as an identical lane into a receiver that turns trucks in 45 minutes, even at the same linehaul rate.
Example
A driver arrives at a grocery distribution center for a 0600 appointment, checks in, and is not called to a door until 0910. Unloading finishes at 1045. Dwell time is about 4 hours 45 minutes. If the facility allows 2 hours free, roughly 2 hours 45 minutes of that is detention the carrier can bill, subject to the rate confirmation terms.
Why it matters
Dwell time consumes the driver’s available hours of service. Two hours lost at a dock can be the difference between the driver legally reaching the next stop and having to shut down short of it.
How teams use this term
In a carrier operation, Dwell Time belongs in the conversation about dispatch, planning, execution, and driver coordination. The useful question is not only what the term means, but which record or decision it changes. A dispatcher may see it while planning a load, a driver may create evidence for it in the field, and accounting may need the same context before a customer invoice or carrier settlement can be finalized. Keeping the term attached to the related workflow prevents a definition from becoming disconnected vocabulary.
When reviewing Dwell Time, ask who owns the next action, what evidence supports the record, and what date or threshold makes the situation change. The answer can vary by equipment, lane, authority, customer routing guide, or contract. A small carrier should document the assumption it used rather than treating a general explanation as a universal rule. The related terms on this page are intended to help a team move from the definition to the operational decision.
A practical review starts with the example above, then compares it with the carrier's own settlement, dispatch, document, or compliance records. If the term affects a regulated filing, payment obligation, or customer requirement, verify the current primary source before acting. Trailflow can provide workflow context, but the carrier remains responsible for the policies, records, and professional advice that apply to its operation.