Explore

Trucking glossary for carrier teams

Ten trucking terms with practical load-workflow examples, from rate confirmations and BOLs to PODs, accessorials and driver-pay handoffs.

A practical trucking glossary for carrier owners, dispatchers and finance teams. These definitions explain common operating language. Charges and responsibilities follow the applicable agreement; the examples below are hypothetical.

Rate confirmation (rate con)

A rate confirmation records the agreed details of a booked load, such as parties, stops, appointment windows, equipment, rate and references. Dispatch and billing use it as a source for the load record.

Operating example: A revised confirmation changes a pickup window. Keep the earlier version and record who approved the new instruction.

Explore the related workflow.

Bill of lading (BOL)

A bill of lading accompanies freight and records shipment information, such as the parties, goods and movement. Carrier teams use it alongside booking and delivery records; it is distinct from the rate confirmation.

Operating example: A load reference on the BOL differs from the booking reference. Keep both identifiers linked to the same load rather than replacing one.

Explore the related workflow.

Proof of delivery (POD)

Proof of delivery is the delivery evidence a carrier uses to document receipt of a shipment. It can include a signed delivery document and any noted exceptions. A delivered status alone is not a complete billing packet.

Operating example: A signed document includes a shortage note. Route that exception to a reviewer before treating the load as invoice-ready.

Explore the related workflow.

Detention

Detention describes waiting beyond the agreed loading or unloading allowance. Whether a charge or driver payment applies depends on the relevant agreement and supporting records.

Operating example: Record arrival, release and the agreed allowance before calculating an amount. Do not use a universal hourly rate.

Explore the related workflow.

Layover

Layover describes an extended delay that interrupts the planned load schedule, often across a day. Keep it distinct from shorter waiting time and use the applicable agreement to decide any charge.

Operating example: A facility moves unloading to the next day. Record the changed appointment and the impact on the driver and next load.

Explore the related workflow.

Truck ordered not used (TONU)

TONU describes a booked truck that is no longer used for the planned load. Cancellation terms and approvals determine whether a charge is payable.

Operating example: A customer cancels after capacity has been committed. Preserve the cancellation time, original booking and approval of any charge.

Explore the related workflow.

Lumper

A lumper is a third-party loading or unloading service. A lumper charge should be connected to the relevant load, receipt and approval before reimbursement or invoicing.

Operating example: A driver sends an unloading receipt. Match the receipt to the stop and confirm how it is treated in the customer invoice and driver settlement.

Explore the related workflow.

Deadhead

Deadhead is truck travel without a revenue load. Dispatchers consider empty travel alongside equipment, availability and service commitments when reviewing an assignment.

Operating example: An illustrative trip has 60 empty miles and 240 loaded miles. Empty miles are 60 divided by 300 total miles, or 20%; this is an example, not a fleet benchmark.

Explore the related workflow.

Accessorials

Accessorials are additional charges beyond the base transportation rate for agreed services or events. Keep the reason, amount and authorization with the load.

Operating example: An approved extra stop changes the invoice. Keep its approval separate from an unapproved waiting-time request.

Explore the related workflow.

Backhaul

A backhaul is a return or follow-on movement that uses capacity after an outbound load. It can reduce empty travel, but still needs to fit equipment, availability and commitments.

Operating example: A return load is close to the delivery point but has an incompatible pickup window. Proximity alone does not make it a suitable assignment.

Explore the related workflow.

Use the trucking TMS guide to connect these terms across a load, or explore RunaboutX features.