A Layover and Breakdown Pay Documentation Log
How trucking offices document layover and breakdown pay with clean triggers, driver input, approval steps, and a monthly reconciliation that drivers trust.
Published: September 18, 2026.
Pay disputes rarely start with the amount. They start with a driver who sat for a day and a half, a dispatcher who knew why, and a payroll clerk who saw only a fraction of the story. By the time the driver asks, the reason has been retold three times and the original messages are buried in different phones. A layover and breakdown pay documentation log fixes the record at the source so payroll can apply the policy without a debate.
Treat the log as an operating record, not a complaint channel. It captures the cause, the clock, the approval, and the payout reference for each event. Done well, it also shows which facilities, customers, or lanes create the most unplanned driver time.
Start with the policy, not the form
Before anyone builds a spreadsheet, write down what the carrier actually pays. Layover and breakdown situations only create work when policy is unclear. Answer these questions in plain language:
- Which situations qualify for layover pay, and which do not?
- Is there a minimum wait before the clock starts?
- Does breakdown time count separately from facility delay?
- Who approves pay when the cause is disputed?
- How is the amount calculated, and where is the rate documented?
If two managers answer those questions differently, the log cannot fix it. Resolve the policy first, then design fields that support it. A log built on an unwritten rule will produce arguments the office cannot settle.
Four event types to keep separate
Many offices use one label for every delay and then argue about the rule. Separate the reasons so payroll can apply the right one.
| Event type | Typical cause | Clock starts |
|---|---|---|
| Facility layover | Appointment missed, dock closed, receiver not ready | When the driver reports the delay and it is confirmed |
| Customer-caused layover | Freight not ready, order changed after dispatch | When the customer's change is recorded |
| Breakdown delay | Mechanical failure that stops the assignment | When the unit is placed out of service |
| Weather or road closure | Conditions that make travel unsafe | When the driver or dispatch documents the hold |
The type drives the approval path. A facility layover may route to the account manager, while a breakdown routes to maintenance. Mixing them into one queue guarantees that the wrong person is asked to approve.
Open the record with driver and dispatch input
Create the entry when the driver reports the delay, and confirm it with the dispatch record. The driver knows the site conditions. Dispatch knows the load and the customer. Neither one alone has the full picture, so the log should require a short confirmation from each side.
Collect the driver, unit, trip or load, event type, the date and time the delay began, the expected restart, and a one-line description. Attach the messages, the work order, or the facility notice that supports the cause. If the cause is not yet known, mark it pending and assign a retrieval step instead of guessing.
PRO TIP Ask the driver for the delay report in the same message that confirms the next assignment. A driver who is already answering a dispatch message will add two facts, while a separate pay request can wait for days.
Keep the approval chain visible
Every entry needs an administrative owner and an approving manager. The owner gathers the facts and keeps the entry current. The manager decides whether the policy applies and at what amount. Do not let the same person set both roles when the cause is disputed, because the approval should be reviewable.
Record the approval date, the approver, and a short reason when an item is declined. A decline with a documented reason prevents the same item from being resubmitted three times. It also gives the driver a clear answer instead of silence.
Feed payroll from one source
Payroll should not read the log and a separate spreadsheet. Export the approved entries into the pay period, or copy the approved totals with the entry identifiers intact. Keep the log as the source of truth and reconcile the pay register back to it before release.
Reconcile twice: before each pay cutoff and at month end. The cutoff pass catches items that are still pending approval. The month-end pass catches entries that were approved after the cutoff and paid in the following cycle, which is the most common source of an apparent double payment or an apparent miss.
Track a few measures over time: entries per pay period, average days to approval, declines by reason, and the facilities or customers that appear most often. A customer that generates repeated layovers may need a schedule or appointment change, which is a better fix than paying the same delay every week.
Write the driver-facing summary
Drivers trust the log when they can see the status of each item. Send a short summary at cutoff: what was submitted, what was approved, what is pending, and what was declined with the reason. That message does more for retention than almost any other back-office routine.
Keep the language factual. "Load 44821, receiver delay 14 hours, approved" is enough. Do not include details that are private, speculative, or outside the driver's own record. Confirm any changeable pay rule against the carrier's written policy and current guidance from the Federal Motor Carrier Safety Administration where hours or records rules are involved.
Common mistakes
- Using one delay code for every situation so no rule can be applied.
- Letting the driver's report stand alone without dispatch confirmation.
- Approving pay without recording the policy reference.
- Exporting approved items without the entry identifier, which breaks the audit trail.
- Ignoring the pattern data that shows which customer keeps causing the delay.
Frequently asked questions
What is layover pay?
Layover pay is compensation for a driver who is held away from home or unable to complete the next assignment because of a delay the carrier chooses to recognize, such as a cancelled appointment or a missed connection. The policy, not the driver, defines when it applies.
Does layover pay apply when a truck is broken down?
That depends on the carrier's written policy. Many offices separate breakdown pay from layover pay because the causes and approval paths differ. The log should label the reason so payroll can apply the correct rule.
What evidence belongs in a layover pay log?
Record the driver, unit, load or trip, reason code, the date and time the delay started, the expected restart, the approving manager, and the amount or rate reference. Attach the messages or work order that show the cause.
How often should the log be reconciled?
Reconcile before every pay cutoff and again at month end. A driver should be able to see the status of each submitted item without asking a person for it.
Related articles and next step
Use this log with Driver Payroll Mileage Reconciliation and An After-Hours Breakdown Call File. If pay questions are consuming dispatch time, contact LogisticsTrucks with one pay period and the decisions that must remain with your team.
Final takeaway
A layover and breakdown pay log removes the guesswork from a recurring, emotional topic. Write the policy first, label the cause, require a driver and dispatch confirmation, and keep the approval visible. When drivers can see the status of their items, the same record that protects payroll also protects the relationship.