Oversize and Overweight Permit Software Problems: The 5 That Strand Loads at State Lines

Why does the scope of a permit build get set too small so often?

The brief that arrives is a tracker: the permit desk works from state portals, a whiteboard and a folder of past routings, so build somewhere to record permits and their dates. What gets built is a list of permits with statuses and expiry alerts, and the permit manager keeps working exactly as before, because the coordination problem was never in the list.

The reason is that a heavy haul move is a project rather than a load. It is a system of interdependent constraints held together by one person, and changing any element invalidates several others. A dry van dispatcher who reroutes a load changes an arrival time. A heavy haul permit manager who reroutes changes permits, escorts, curfews, bridge clearances, utility appointments and possibly the legality of the move. A permit list models none of that.

The other half of the scoping failure is the vehicle. Ask a candidate developer to model your equipment before they model a permit. Your trailer catalogue is engineering data: axle counts, groups, spacings and rated capacities, with spreads that change per move.

The fix is to make the move the object and the configuration the foundation. Permits, routes, restrictions and appointments hang off the move as segments. The permit application is generated from the configuration rather than typed from a drawing, which removes the transcription errors that cause permits to be issued for the wrong dimensions, and it lets a planner ask which configuration can make this move legally with the fewest permits.

What goes wrong when jurisdiction rules get captured as data?

This is the migration problem in heavy haul, and the source data is a person rather than a database. Curfew windows around metropolitan areas, holiday restrictions, weather condition rules in some states, escort thresholds that differ by dimension and by jurisdiction, where certified escorts are required and where police are, night movement permitted here and prohibited there. Every experienced permit manager knows most of this, which is exactly the problem: the business cannot scale past the people holding it, and hiring a second coordinator is a twelve month training exercise with predictable errors along the way.

Two things go wrong when a project tries to capture it. The first is underestimating the effort. Rule capture is not an interview, it is a series of structured sessions working through real past moves, and it is the usual cause of schedule slip here. Budget it explicitly rather than assuming it happens alongside design.

The second is rule rot. Rules change, and a rule captured once and left alone decays quietly until a coordinator gets caught out, at which point people revert to memory and you now have a system to feed as well. That is worse than where you started.

The fix is to give every rule a source and a review date, so the data is maintainable by design rather than by diligence. Treat the rule catalogue as a living deliverable with a named owner, and report on rules past review as you would anything else that ages. A new coordinator becoming productive in weeks rather than a year is usually the real reason an owner funds this project, and it only holds if the rules stay current.

Why do state portal integrations break after launch?

Because they are the least stable part of the entire build and they are frequently the most attractive item in the proposal. State portals differ enormously in what they expose. Several have no interface at all. The automated ones change without notice, and a submission path that worked last quarter starts failing in a way that looks like a rejection rather than a fault.

The deeper issue is that automating submission optimises the wrong step. Submission is a few minutes of work. The weeks of effort go into coordination, chasing, and reworking everything when a state returns an amended route. A build that automates submission and leaves coordination on a whiteboard has automated the cheap part.

The fix is sequencing. Treat portal automation as phase two at the earliest, and automate only where a state offers a stable documented interface and your volume justifies it. Keep a human confirmation step and monitor on submission volume rather than only on error, because a silently failing submission here means a crew waiting. Everything else belongs in the coordination layer, which is durable and specific to how your company runs projects.

What happens when route continuity and the move file are not covered?

Each state issues its own permit with its own route. That is the regime and it will not change. What breaks operations is that states get worked sequentially, so the third state's route can invalidate the first state's assumptions, and no artefact represents the complete movement. A permit comes back avoiding a bridge and adding sixty miles, the new route crosses a 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.

The second uncovered gap is resource bookings. Certified escorts, sometimes police, a utility crew for a line lift, a crane at destination, specialised trailers and qualified drivers are all committed in advance against a date that depends on permits not yet issued. When a bridge review adds two weeks, everything downstream needs rebooking, done by phone by the same person chasing the permit.

The third is the file of record. If a structure is struck or a citation is issued at a scale, the questions are immediate: what dimensions were permitted, what route was authorised, were escorts present as required, was the move within its window, was the configuration as declared. Those answers currently sit across four portals, an email thread and a driver's phone.

The fixes follow from making the move the object. Check connection points against neighbouring permits whenever a state amends a route, and flag the break the day it appears rather than at a state line at two in the morning. Model escorts, cranes and crews as bookings tied to the move so a date change surfaces every affected commitment with the contacts needed to change them. And keep the complete move file as one immutable record with every permit, every amendment, the routes as issued and crew acknowledgements.

Should you build custom or configure what you already own?

If you run a handful of routine oversize moves a month across two states with repeatable dimensions, do not build. A permit service takes the administrative load and you will never recover a build. The same applies 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.

Be accurate about the tools. ProMiles offers strong routing, mileage and permit ordering. Bestpass handles permits alongside tolling as a service. TransCore is deeply embedded in state permitting systems. All three are useful and many carriers should keep one. Their common limitation for a carrier with engineered equipment is that they work from a general vehicle profile and a permit request rather than your actual trailer build.

The middle path is worth naming because it is what most carriers should actually do. Keep a permit service for 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.

The build case starts when two or more hold: you move across five or more jurisdictions regularly, you run engineered configurations whose spread varies by move, your permit knowledge sits with one or two people, you carry superloads needing bridge review, or you coordinate escorts, cranes and utility crews around dates that permits keep moving.

How do hidden costs get into the quote?

A focused first release covering 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 over 6 to 12 months.

Jurisdiction count is the largest driver, because each state's rules, forms and portal behaviour are separate work and some have no interface at all. Routing data is second and is a recurring cost: commercial road network data with structure attributes is licensed, and it belongs in your budget from the start. Bridge analysis is third and is often misunderstood in estimates, because for superloads it is a state engineering process the system tracks as a workflow rather than a calculation. Canadian provinces are fourth if you run cross border, and transportation management system integration is fifth.

The sixth is the rule capture described above, which is labour rather than licensing and is regularly left out entirely. Hold the first release to your top five jurisdictions by move count, one equipment class and manual permit submission, and the estimate stays honest.

What separates a build that works from one that fails here?

Whether the equipment model is real. Everything else is downstream of it. If configurations carry actual axle groups, spacings and rated capacities, permit applications generate correctly, routing questions can be asked against a specific build, and a planner can compare configurations for a move. If the model is a category, the system produces confident answers that are wrong in ways nobody catches until a scale.

Second, licence road network data rather than building it. The correct answer from a developer is to licence a commercial network with structure attributes and build your configuration logic on top. Anyone proposing to assemble their own network data does not understand the maintenance obligation they are creating for you, and that obligation has no competitive value.

Third, keep the coordination layer ahead of the automation layer in every phase. Carriers who fund portal automation first because it demonstrates well end up with a fragile integration and the same whiteboard.

Finally, settle ownership before kickoff: repository, infrastructure accounts and the right to bring in anyone else. Treat the move file archive explicitly in that conversation, since it is your evidence if a structure is ever struck or a citation is issued, and it needs to hold permits, amendments, routes as issued and crew acknowledgements. At Digital Heroes the client owns the code from the first commit.