Start with the work pattern. Long-haul freight with predictable miles may suit a mileage model, while local work with heavy loading and waiting may make hourly or activity-based pay clearer. Percentage can align pay with revenue but requires transparent treatment of accessorials, deductions, and canceled or reworked loads.
Model both driver earnings and carrier cost using realistic weeks. Include empty miles, layovers, breakdowns, detention, orientation, paperwork, payroll taxes or benefits, and the time spent on inspections and securement. A headline rate is not a pay plan if the driver cannot predict a paycheck when freight or appointments change.
Write the rules in plain language. Define what counts as a paid mile, how routes are determined, when detention or layover begins, how advances and deductions work, and where a driver can question a calculation. Give drivers access to load and settlement detail so the plan is auditable rather than dependent on trust in a spreadsheet.
Have payroll, employment, and transportation professionals review the plan for the jurisdictions and driver relationships involved. Wage, tax, classification, reimbursement, and deduction rules vary and change. This answer is a design framework, not legal advice. A sustainable model rewards safe, reliable work without creating pressure to drive beyond lawful or safe limits.
How to apply the answer
The answer changes when the operating facts change. Before applying it, identify the carrier's fleet size, equipment, authority model, lanes, customer requirements, and the records already available. A small owner-operator may make a different decision from a multi-truck carrier with dedicated freight, an accounting team, or a shipper routing guide. State those assumptions so another person can review the reasoning instead of treating a general answer as a promise.
Use the answer as a starting point for a repeatable workflow. Write down the inputs, compare the available options, and record the evidence behind the decision. For this question, the relevant terms include settlement, deadhead, layover. Linking the question to those definitions helps a dispatcher or owner move from a short answer to the operational detail that determines what happens next.
A useful next step is to test the decision against one real load, customer, driver, or settlement record, while keeping private information out of the example. Check what changed after the decision and update the process if the result did not match the assumption. This is especially important for compliance, tax, pricing, and cash-flow topics, where requirements and commercial terms can change.
If the decision affects more than one team, write down the handoff: who prepares the information, who reviews it, and where the final record lives. That small step turns a useful answer into a repeatable operating practice and makes it easier to find the next question when the workflow changes.
Trailflow's product pages describe supported workflows separately from this answer. Review the relevant product or workflow page for current availability, and verify regulated or financial decisions with the applicable primary source or qualified advisor.
Terms in this answer: Settlement, Deadhead, Layover