Oversize and Overweight Permit Software: Why the Route Falls Apart at the State Line

Why a heavy haul move is a project, not a load

A transformer moves from a port in Texas to a substation in Nebraska. It is 14 feet 6 inches tall, 16 feet wide, and the combination grosses over 200,000 pounds on a nine axle configuration. The permit manager has worked the move for three weeks. Four states, four applications, four sets of dimensions, four escort rules, one bridge needing structural review before the state will issue, two counties with their own requirements, a utility line lift at a specific crossing, and a delivery date promised before any of this was known.

On Tuesday one state permit comes back with a route that avoids a bridge and adds 60 miles. That route crosses into a different county with a curfew the original did not have, and the next state's permit was issued for an entry point that no longer matches. Three of the four permits are now inconsistent, the escort company is booked for the original schedule, and the crane at destination has a window that is no longer achievable. That is what happens when a multi jurisdiction move is coordinated from a spreadsheet and a phone.

This is the defining feature of heavy haul: the move is a system of interdependent constraints held together by one person, and changing any single element invalidates several others. A dry van dispatcher who reroutes a load changes an arrival time. A heavy haul permit manager who reroutes a load changes permits, escorts, curfews, bridge clearances, utility appointments and possibly the legality of the entire move.

Problem 1: the truck in the routing tool is not your truck

Routing software has a vehicle profile. For general trucking, a profile with height, weight and length is sufficient, because bridge and road restrictions are published against those figures. For heavy haul it is not close to sufficient. What governs is the axle configuration: how many axles, in what groups, at what spacings, carrying what individual and group weights. Two combinations at the same gross weight can produce entirely different answers on the same bridge, because bridge capacity responds to how load is distributed, not just to the total.

ProMiles offers strong routing and mileage and permit ordering, Bestpass handles permits alongside tolling as a service, and TransCore is deeply embedded in state permitting systems. All three are useful and many carriers should use one. Their common limitation for a carrier with engineered equipment is that they work from a general profile and a permit request, not from your actual trailer build. If you run a nine axle expandable with a jeep and a booster and you change the spread for a particular move, that changes your permitted weights, and no service bureau tool models your trailer catalogue as engineering data.

What a custom build does: hold your equipment as configurations with real axle groups, spacings and rated capacities, so a move is planned against a specific build rather than a category. The permit application is then generated from the configuration rather than typed from a drawing, which removes the transcription errors that cause permits to be issued for dimensions you are not actually running. It also lets a planner answer a question they currently cannot: which of our configurations can make this move legally with the fewest permits.

Problem 2: the route is agreed piecewise and nobody owns the whole line

Each state issues its own permit with its own route. That is the regime and it will not change. What breaks operations is that the states are worked sequentially, so the third state's route can invalidate the first state's assumptions, and there is no artefact anywhere that represents the complete movement.

The permit tools reflect this structure because they are organised around permit issuance, which is inherently per jurisdiction. So the end to end route lives in a routing tool that does not know about the permits, or in the permit manager's head, or on a printed map with highlighter.

What a custom build does: make the move the object, with permits, routes, restrictions and appointments hanging off it as segments. When a state returns an amended route, the system checks the connection points against neighbouring permits and flags the break immediately rather than at a state line at 2am. Everything the crew needs travels as one packet: turn by turn route, permit documents, curfew windows, escort requirements per segment and restricted bridges. Drivers currently carry an envelope, and an envelope cannot tell you the permit you are relying on was superseded yesterday.

Problem 3: curfews, escorts and restrictions are known and unwritten

Movement is restricted by time of day around metropolitan areas, by day around holidays, by weather condition in some states, and by local rules that are not always in the state document. Escort requirements vary by dimension threshold and by state, some jurisdictions require certified escorts, some require police for particular dimensions, and the thresholds are not uniform. Night movement is permitted in some places and prohibited in others.

Every experienced permit manager knows most of this. That is exactly the problem, because it means the knowledge is unwritten and the business cannot scale past the people holding it. Hiring a second permit manager is a twelve month training exercise with predictable errors along the way.

What a custom build does: encode restrictions as data attached to jurisdictions and route segments, with a source and a date on each rule so it can be maintained deliberately rather than remembered. Rules change, and a rule with a review date is maintainable while a rule in someone's memory is not. The move packet then shows the crew a clear window: you may move between these hours in this segment, and here is why. A new coordinator becomes productive in weeks rather than a year, which is usually the real reason an owner funds this project.

Problem 4: escorts, cranes and crews are scheduled against a date that keeps moving

A heavy haul move consumes scarce resources: certified escort vehicles, sometimes police, sometimes a utility crew for a line lift, a crane at destination, specialised trailers, and drivers qualified on that equipment. All are booked in advance against a date that depends on permits that have not been issued yet. When a bridge review adds two weeks, everything downstream needs rebooking, and the rebooking is done by phone by the same person who is chasing the permit.

What a custom build does: model these as resource bookings tied to the move, so a date change surfaces every affected commitment in one place with the contacts needed to change them. That does not make the phone calls for you, but it stops the failure mode where the escort company shows up for a move that was rescheduled and invoices you for it. For carriers who own escort vehicles it also produces real utilisation data, which is usually a surprise.

Problem 5: the permit file is your defence and it is in a filing cabinet

If a bridge is struck, if a load contacts a structure, if there is a citation at a scale, the questions are immediate and specific. What dimensions were permitted. What route was authorised. Were escorts present as required. Was the move within its permitted window. Was the configuration as declared. The answers exist as PDFs across four state portals, an email thread and a driver's phone.

What a custom build does: keep the complete move file as a single immutable record with every permit, every amendment, the routes as issued, the crew acknowledgements, and the position and time record of the actual movement where you capture it. Assembling the defence becomes an export. This is also what insurers and customers increasingly want to see before awarding project work, and being able to produce it quickly is a commercial advantage as much as a risk control.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this category prices as follows. A focused first release, meaning your equipment configuration catalogue, move objects holding permits and route segments, restriction and escort rule data, and permit application assembly, runs $70,000 to $140,000 and ships in 12 to 16 weeks. A full platform adding routing evaluated against real axle configurations, curfew and restriction checking along the route, escort and resource scheduling, portal integration where states support it, and the crew packet with movement capture runs $170,000 to $400,000 phased over 6 to 12 months.

What pushes the number up here: the number of jurisdictions, since each state's rules, forms and portal behaviour are separate work and some have no interface at all. Routing data, because commercial road network data with structure attributes is licensed and adds ongoing cost. Bridge analysis, which for superloads is a state engineering process the system tracks as a workflow rather than a calculation it performs. Canadian provinces if you run cross border. And integration to a transportation management system if you want moves, billing and settlement joined.

What holds it down: your top five jurisdictions by move count, one equipment class, and manual permit submission in phase one. Automating submission against state portals is attractive and is the least stable part of the whole build.

Build versus buy, and the middle path

Buy if you run a handful of routine oversize moves a month across two states with repeatable dimensions. A permit service takes the administrative load and you will never recover a build. Buy also if your moves are mostly annual permit territory, where the same trailer runs the same corridors within standing limits, because the coordination complexity that justifies a build is largely absent.

Build when two or more of these are true. You move across five or more jurisdictions regularly. You run engineered configurations where axle spread and grouping vary by move. Your permit knowledge sits with one or two people and you cannot hire into that role without a year of training. You carry superloads that need bridge review and structural analysis. Or you coordinate escorts, cranes and utility crews around dates that permits keep moving.

The middle path is worth naming. Keep a permit service for actual issuance in jurisdictions where they are efficient, and build the coordination layer: configurations, moves, restrictions, resources and the file of record. That is where your losses and your key person risk live, and it is the part no vendor sells because it is specific to how your company runs projects rather than to how a state issues paper.

How to choose a developer for permit and heavy haul work

Ask them to model your equipment before they model a permit. If the vehicle in their design has a height, a weight and a length, they have built a general trucking system and it will not survive contact with a nine axle configuration and a booster.

Ask what happens when a state amends a route mid process. The answer must include checking connection points against neighbouring permits, because that is the specific failure that strands crews at state lines.

Ask how restriction rules are maintained. Every rule needs a source and a review date, or the data rots quietly and people go back to trusting memory, which puts you exactly where you started with an extra system to feed.

Ask about routing data honestly. The correct answer is licensing a commercial road network with structure attributes and building your configuration logic on top, not building a road graph. A developer who proposes to assemble their own network data does not understand the maintenance obligation they are creating.

Ask who owns the code and settle it before kickoff. You should hold the repository, the infrastructure accounts and the right to bring in anyone else. At Digital Heroes the client owns the code from the first commit, and here you also want clear ownership of the move file archive, since it is your evidence if a structure is ever struck.