TMS for Oversized and Overweight Permit Load Management

Oversized and overweight loads require permits from every jurisdiction the route crosses, along with route restrictions, escort vehicle requirements, and travel time-of-day limits that ordinary freight never encounters. A TMS handling this freight class has to manage permit acquisition and route compliance as a planning prerequisite, not an afterthought handled outside the system.

A standard routing engine optimizes for distance, time, or cost across a road network assumed to be uniformly usable. Permit loads invalidate that assumption: certain bridges have weight limits, certain overpasses have height limits, certain roads prohibit wide loads entirely, and some routes require daylight-only travel or a weekday-only travel window. The TMS needs a routing mode that treats these as hard constraints per axle configuration and per load dimension, not general preferences.

Because permits are issued per state or region and often per trip, the TMS should track permit status as a gating condition before dispatch, not a parallel administrative task. Useful tracking fields include:

• Permit status per jurisdiction crossed (applied, issued, expired) with permit number and validity window
• Load dimensions and weight submitted for each permit application, since discrepancies from actual load trigger violations
• Escort vehicle requirement flags per jurisdiction (pilot car front/rear, police escort for extreme dimensions)
• Route survey confirmation for bridges, low clearances, and construction zones along the approved route

Beyond the permit itself, most jurisdictions attach conditions: minimum following distance for escort vehicles, restricted travel hours (often prohibiting movement during rush hour or after dark), and blackout dates around holidays. The TMS should encode these as scheduling constraints so a dispatcher cannot accidentally schedule a permit load to depart during a restricted window, since a violation risks both a fine and impoundment of the load mid-route.

For long-haul permit moves crossing several jurisdictions, permit validity windows, escort requirements, and travel restrictions can all differ by state or region on the same trip. The TMS needs to represent the route as a sequence of jurisdiction segments, each with its own compliance package, and should flag before dispatch if any segment's permit is not yet confirmed.

Permit loads carry accessorial costs well beyond base linehaul: permit fees per jurisdiction, escort vehicle charges, and sometimes utility company fees for temporary line-raising on the route. Freight audit for this freight class needs a cost model that expects these line items by default rather than treating them as unusual exceptions.