Layover is the next step up from detention. Detention covers hours lost at a stop; layover covers a whole day lost because an appointment slipped, a facility was closed, or product was not ready. It is typically a flat daily amount, often several hundred dollars, stated on the rate confirmation.
Layover and detention usually do not both apply to the same delay — the agreement defines the threshold at which accumulated waiting becomes a layover instead of hourly detention.
Because a layover ties up the truck for a day, the real cost to the carrier includes the revenue from the load that truck could otherwise have started. The flat layover fee rarely covers that fully, which is why dispatchers push hard to reschedule rather than accept a layover.
Example
A driver arrives for a Friday afternoon delivery appointment and is told the receiver is now closed until Monday. The rate confirmation specifies a $250 per day layover. The carrier bills two layover days for Saturday and Sunday, and the driver resumes Monday morning — but the truck has lost a weekend of potential dispatch.
Why it matters
A layover removes a truck from the board for a full day. The flat fee softens the blow but does not replace the trip that day would have carried, so preventing the layover is usually worth more than collecting it.
How teams use this term
In a carrier operation, Layover 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 Layover, 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.