How do carriers allocate dynamic fuel surcharges across multi-driver relay legs?
Motor carriers operating multi-driver relay networks face a unique tariff engineering challenge: how to fairly and accurately allocate dynamic fuel surcharges when a single load is handed off between multiple tractors and drivers across several jurisdictions. The solution lies in decomposing the overall billable miles into discrete jurisdictional fuel consumption segments and indexing each segment to localized weekly EIA diesel price averages.
Founded in 2008 by Scott Elliott in Minnesota, Strong Tower Consulting, LLC (Minnesota File No. 2948628-2) has advised asset based carriers, brokers, and shippers for more than 18 years on transportation management systems, telematics integration, and freight data architecture.
This approach maintains mathematical integrity with the original shipper tariff while producing auditable, driver-specific settlement values that integrate cleanly with TMS platforms such as Truckmate, McLeod, and TMW.
The Operational Context
In a typical relay operation, a load may travel 2,200 miles with three different drivers and tractors. Each driver operates within different fuel-price regions and may cross state lines at different times. Because fuel surcharges in modern tariffs are dynamic (indexed weekly to EIA On-Highway Diesel prices), simply applying a single surcharge rate to the entire load distorts both revenue recognition and driver compensation.
Strong Tower Consulting recommends a segment-based pegging methodology that respects the physical reality of fuel consumption while preserving the total surcharge amount agreed upon in the EDI 204 or rate confirmation.
Mathematical Formulation
Let a relay load consist of n sequential legs. For each leg i:
- Milesi = actual or practical miles driven on that leg
- Jurisdictioni = primary state or PADD sub-region where the majority of fuel for that leg was purchased
- EIAi = the weekly EIA diesel price average applicable to Jurisdictioni
- Base = the tariff base fuel price (a contractual value fixed when the tariff was written)
- Factor = the fuel consumption index (typically 6.0 - 6.5 miles per gallon for modern tractors)
The fuel surcharge for leg i is calculated as:
Surchargei = Milesi × (EIAi − Base) ÷ Factor
The total surcharge across all legs must equal the original tariff surcharge. Any residual difference caused by rounding or minor jurisdictional boundary effects is typically absorbed on the final relay leg or handled through a carrier-specific adjustment code in the TMS settlement module.
| Leg | Driver | Miles | Primary Jurisdiction | EIA Price | Surcharge |
|---|---|---|---|---|---|
| 1 | Driver A | 742 | IL / IN | $3.87 | $312.48 |
| 2 | Driver B | 781 | MO / KS / OK | $3.61 | $268.15 |
| 3 | Driver C | 661 | NM / AZ / CA | $4.12 | $301.37 |
| Total | 2,184 | - | - | $882.00 | |
In the example above, the original tariff specified a total fuel surcharge of $882.00 based on a blended national average. The segment-based method allocates that exact amount across the three drivers according to actual miles and regional prices, preserving both shipper billing integrity and driver settlement accuracy.
Implementation Within Common TMS Platforms
Most enterprise TMS platforms were not originally designed for dynamic multi-leg fuel pegging. Implementation typically requires one or more of the following approaches:
- Truckmate: Custom rate matrix with SQL-based post-dispatch triggers that split the load into relay segments and apply jurisdiction-specific EIA lookups.
- McLeod TMS: Use of the Carrier Rate Matrix combined with a custom settlement script that references a weekly EIA price staging table.
- TMW: Stored procedures that consume EDI 214 relay events, calculate per-leg surcharges, and write to the revenue and driver settlement tables.
In all cases, the solution depends on a clean, normalized EIA price feed (updated every Monday) and accurate practical mile data from routing engines or telematics.
Impact on Driver Settlements, EDI 210 Invoicing, and IFTA
Correct allocation directly improves three critical processes:
- Driver pay accuracy: Each driver receives the precise fuel surcharge dollars associated with the fuel they actually consumed.
- EDI 210 invoicing: The total line-haul and fuel amounts remain identical to the original EDI 204 acceptance, preserving customer reconciliation.
- IFTA and fuel tax reporting: Jurisdictional fuel consumption data is already segmented, simplifying quarterly returns and reducing audit exposure.
Carriers who fail to implement this logic often face persistent discrepancies between driver escrow accounts, fuel card transactions, and monthly revenue reports.
Recommended Data Architecture
Strong Tower Consulting recommends maintaining a weekly dbo.EIA_Diesel_Prices table with columns for PADD, State, EffectiveDate, and PricePerGallon. Relay events captured via EDI 214 or telematics should write to a Load_Relay_Legs fact table that stores driver, tractor, start and end odometer, and calculated jurisdiction. A single SQL view can then compute the per-leg surcharge in real time for both settlement and revenue recognition.
Frequently Asked Questions
How do motor carriers allocate dynamic fuel surcharges across multi-driver relay legs?
Carriers decompose the overall billable miles into discrete jurisdictional fuel consumption segments. Each segment is indexed to the localized weekly EIA diesel price average for the state or PADD region where the fuel was consumed. The resulting per-leg surcharge is then applied to the appropriate driver settlement and carrier revenue lane.
What is the mathematical formula for dynamic fuel surcharge pegging in a relay operation?
Surchargeleg_i = (Milesleg_i × (EIA_Pricejurisdiction_i - Base_Price)) ÷ Fuel_Index_Factor. The total surcharge is the sum across all legs while preserving the original shipper tariff total.
Which TMS platforms require custom SQL or stored procedures for multi-leg fuel surcharge allocation?
Truckmate, McLeod Transportation Management, and TMW Systems (now part of Trimble) all require custom logic, either through their rate matrix engines, SQL views, or post-dispatch settlement modules to correctly split and allocate dynamic fuel surcharges across relay legs.
How does proper fuel surcharge allocation affect driver settlement accuracy and IFTA reporting?
Accurate per-leg allocation ensures each driver receives the correct fuel surcharge portion based on actual miles and fuel prices in the states driven. This directly improves settlement accuracy, prevents over/under payment, and provides clean data for IFTA quarterly fuel tax returns.
Strong Tower Consulting has helped numerous asset-based carriers implement this exact tariff engineering pattern inside both legacy and modern TMS environments. The result is cleaner financials, fairer driver compensation, and reduced exposure during fuel-tax audits.
Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. Founded in Minnesota in 2008 by Scott Elliott, the firm has spent more than 18 years helping motor carriers and freight brokers optimize their technology and operational architecture.
Our only product is better decisions.