Multi-Stop Dispatch Optimization: Driver Layover, Per Diem & Out-of-Route Settlement Control

The Operational Friction of Multi-Stop Freight

Truckload carriers that regularly accept 3-stop, 4-stop, or even 5-stop loads face persistent margin erosion. Without tight system controls, these loads generate excessive out-of-route (OOR) mileage, unauthorized driver layovers, disputed stop-off pay, and unbilled accessorial revenue. The complexity compounds when drivers are compensated using a combination of hourly layover pay, tiered stop pay, fuel surcharges, and IRS-compliant per diem.

In legacy TMS environments such as McLeod LoadMaster, Truckmate, or TMW Systems, dispatchers often rely on manual routing decisions. This leads to practical route deviations that exceed the 6% OOR threshold commonly allowed by carriers. The result is inflated fuel costs, driver pay disputes during settlement, and customer invoices that fail to recover the full accessorial value of each stop and layover event.

Automated Sequence Routing and Mileage Auditing in the TMS

Modern dispatch optimization begins with proper configuration of the TMS routing engine. Both McLeod LoadMaster and Truckmate support integration with PC*Miler and Trimble MAPS. The key is to establish a "Practical" routing profile rather than "Shortest" or "Fastest" and to enforce it at the time of load tender acceptance (EDI 204).

Once the load is dispatched, the system must continuously compare actual miles reported via EDI 214 status messages or driver mobile applications against the authorized practical route. Variances greater than 6% are automatically flagged for review. SQL-based exception reports can be written directly against the load and route tables to surface OOR events before final settlement.

This automated audit prevents drivers from taking unauthorized routes that inflate fuel spend while protecting the carrier from paying phantom miles during weekly driver settlement.

Automated Driver Stop-Off, Layover, and Per Diem Compensation

Driver settlement complexity increases dramatically with multi-stop loads. Strong Tower recommends configuring the TMS settlement module with the following tiered logic:

• First stop-off: $50 flat pay
• Each additional stop: $75 flat pay
• Layover pay: guaranteed $25 - $32 per hour after free time expires (configurable by customer)
• Per diem: automatic split between taxable wages and IRS-compliant tax-exempt per diem based on overnight stops and current IRS rates

When these rules are maintained in the TMS payroll engine, stop and layover events captured through EDI 214 or mobile time-entry automatically flow into the driver pay calculation. This eliminates the majority of manual settlement adjustments and reduces payroll disputes.

Shipper Accessorial Billing Synchronization

Every driver stop-off and approved layover event should generate a matching accessorial line on the customer freight invoice. In a well-configured TMS, the same EDI 214 stop events that trigger driver pay also populate the 210 invoice with appropriate accessorial codes for stop-off charges, detention, and layover. This closed-loop synchronization virtually eliminates unbilled accessorial leakage on multi-stop freight.

Carriers using TMW or McLeod can further automate this process by leveraging the rating engine’s accessorial tables and workflow rules that fire upon load closeout.

Independent Advisory Perspective

Strong Tower Consulting, LLC maintains complete independence from TMS vendors, mapping providers, and payroll platforms. Our consultants have deep experience with Truckmate, McLeod LoadMaster, TMW, and their underlying SQL schemas. We focus exclusively on helping motor carriers and freight brokers extract maximum asset yield from complex multi-stop dispatch while protecting driver pay accuracy and customer billing integrity.

Whether you run 50 trucks or 500, the principles remain the same: practical routing enforcement, automated variance detection, tiered settlement rules, and synchronized accessorial billing are non-negotiable for profitable multi-stop operations.

Frequently Asked Questions

How do you configure a TMS like McLeod LoadMaster or Truckmate to automatically calculate out-of-route mileage on multi-stop loads?

By integrating PC*Miler or Trimble MAPS practical routing profiles into the dispatch engine and setting variance thresholds (typically 6%) that trigger automated alerts and settlement adjustments. The system compares the dispatched practical route against actual GPS or driver-entered miles to isolate true out-of-route variances.

What is the correct way to automate driver stop-off pay, layover pay, and IRS-compliant per diem in the settlement system?

Configure settlement rules within the TMS payroll module to apply tiered stop pay (commonly $50 for the first stop and $75 for each additional stop), guaranteed hourly layover rates when detention exceeds free time, and split compensation between taxable wages and tax-exempt per diem according to current IRS guidelines. These rules should trigger automatically from EDI 214 status updates and driver mobile entries.

Why do most carriers lose money on multi-stop freight and how can this be corrected?

High out-of-route mileage, unauthorized layovers, unbilled accessorials, and inaccurate driver settlements frequently erode margin. The solution is algorithmic dispatch optimization combined with automated accessorial generation on the customer invoice (EDI 210) that exactly matches the driver settlement events.

How does fuel surcharge calculation interact with multi-stop per diem and layover pay?

Fuel surcharge must be calculated on the authorized practical route miles only. When OOR mileage is identified and approved, the fuel surcharge portion is typically excluded from driver settlement or adjusted per company policy. Layover and per diem remain separate line items and are not affected by the fuel surcharge calculation.