LTL linehaul load planning sits at the intersection of physical trailer constraints, regulatory requirements, service commitments, and network economics. Planners must simultaneously optimize trailer cube utilization, observe legal axle weight limits, respect hazardous materials segregation rules, and protect departure cut times that drive next-day service performance.
Modern Transportation Management Systems (TMS) that support LTL operations - whether TruckMate, McLeod, TMW, or a custom platform - require a specific data model and decision framework to make these trade-offs visible in real time. This article presents the core architecture and operational rules used by successful LTL carriers.
The Core Data Model for Linehaul Load Planning
Effective planning begins with dimensioned freight data. Each shipment or handling unit must carry:
- Length, width, and height in inches
- Actual weight in pounds
- NMFC class and any hazmat UN number or placard requirements
- Destination terminal or sort code
- Service commitment (next-day, two-day, etc.)
- Special handling flags (stackable, fragile, floor-loaded only)
This data is typically stored in normalized SQL tables that link to the order header, the bill of lading (EDI 204 inbound or internal order creation), and the linehaul manifest. Many carriers maintain a separate planning cache table that is refreshed every few minutes from the operational TMS tables.
| Field | Source | Use in Planning Algorithm |
|---|---|---|
| freight_length_in | EDI 204 or capture at pickup | Cube calculation and loading pattern |
| freight_weight_lb | Scale or declared weight | Weight distribution and axle limits |
| hazmat_flag | Shipper declaration | Segregation rules (49 CFR) |
| dest_terminal | Rating engine or zip lookup | Sort sequence and head-load priority |
| cut_time | Network schedule | Departure urgency scoring |
Head-Load vs Fill-Load Decision Framework
The fundamental planning choice is whether a trailer is designated as a head-load or a fill-load. A head-load is built for a specific outbound departure that has a hard cut time - typically 10:00 PM or 11:00 PM at origin terminals. These trailers must be loaded, sealed, and ready for the linehaul driver by the published cut time.
A fill-load accumulates freight for the next available trailer once head-loads are satisfied. The TMS must surface both options with projected utilization metrics so the planner can decide whether to protect cube for later high-density freight or to load additional lower-priority shipments.
For example, a 53-foot trailer with 3,800 cubic feet of usable space might be targeted for 85-92 percent cube utilization on a typical head-load, depending on freight mix. Weight is usually capped at 42,000 - 44,000 pounds to maintain legal axle weights after fuel and driver weight are considered. These are operational planning targets, not universal benchmarks.
Weight and Axle Considerations in the TMS
Weight distribution is rarely uniform. The TMS must model approximate load position - nose, middle, or tail - to estimate axle weights. Many carriers maintain a simple linear model that assigns percentages based on cumulative cube or a more sophisticated stacking algorithm that respects freight dimensions.
Integration with the driver settlement and fuel surcharge modules is also important. Accurate trailer weight at departure feeds both the fuel surcharge calculation (if scale tickets are captured) and the linehaul driver pay if any weight-based incentives exist.
Cut-Time Logic and Network Scheduling
Departure cut times are non-negotiable for service performance. The TMS must rank open freight by a composite score that includes:
- Time until cut time (hours remaining)
- Destination urgency (next-day vs standard)
- Cube and weight efficiency of the current trailer
- Hazmat or special handling constraints
Planners use this ranking to decide when to close a trailer and start the next one. In high-volume terminals, this decision is often supported by a custom SQL view or a dedicated planning dashboard that pulls real-time data from the TMS order and dispatch tables.
EDI Integration Points
EDI 214 status messages must be generated when a trailer is closed and again when it departs. EDI 210 invoices later reference the same trailer number for rating and billing. The load planning module therefore serves as the system of record for trailer-to-shipment relationships that flow through the entire transaction lifecycle.
Comparison of Planning Approaches
| Scenario | Head-Load Priority | Target Cube | Target Weight | Decision Rule |
|---|---|---|---|---|
| Next-day freight to key hub | High | 75-85% | 38,000 lb | Protect space even if it means running lighter |
| Standard linehaul freight | Medium | 88-94% | 42,000 lb | Maximize utilization while meeting cut time |
| Fill-load after cut time | Low | 92%+ | 44,000 lb | Fill remaining trailers without service pressure |
Implementation Considerations for Legacy TMS Platforms
TruckMate, McLeod, and TMW can all support these concepts, but most installations require additional configuration or a supplemental planning layer. Strong Tower Consulting frequently builds targeted SQL data-mining views and lightweight planning screens that sit alongside the native dispatch modules. These extensions give planners the dimension-aware visibility they need without forcing a full TMS replacement.
Frequently Asked Questions
What data elements does an LTL TMS need for effective linehaul load planning?
Dimensioned freight records including length, width, height, weight, NMFC class, hazmat flags, and destination terminal. These feed cube and weight algorithms that also respect axle weight limits and departure cut times.
How does a load planner decide between a head-load and a fill-load?
A head-load is built to a specific outbound trailer that must depart by cut time. A fill-load accumulates freight for the next available trailer. The TMS must surface both options with projected cube and weight utilization so planners can meet service commitments without sacrificing trailer productivity.
Why is trailer cube utilization more complex in LTL than in truckload operations?
LTL trailers are loaded and unloaded multiple times per linehaul leg. Planners must consider not only current cube and weight but also the order of freight for intermediate terminal handling, segregation rules, and the need to protect high-priority freight that cannot be buried.
Can legacy TMS platforms such as TruckMate, McLeod, or TMW support modern LTL load planning rules?
Most legacy platforms require significant configuration or custom SQL-based decision support layers. Strong Tower Consulting designs these extensions so carriers gain precise cube, weight, and cut-time visibility without replacing their core TMS.
Strong Tower Consulting, LLC was founded in Minnesota in 2008 by Scott Elliott. In business for more than 18 years, the firm provides independent systems architecture and technology advisory services to motor carriers, freight brokers, and private fleets.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Carriers never have to buy our software. Our only product is better decisions.