How Much Does Oversize and Overweight Permit Software Cost in 2026?

The bands a heavy haul permit build falls into

A focused first release runs $70,000 to $140,000 over 12 to 16 weeks. That buys the three things that stop moves falling apart: an equipment catalogue that holds your trailers as real configurations with axle groups, spacings and rated capacities rather than as a height, a weight and a length; the move as an object, with each state's permit and route hanging off it as a segment so connection points can be checked; and restriction, curfew and escort rules held as versioned data with a source and a review date on each one. Permit applications then get assembled from the configuration instead of typed from a drawing.

A full platform runs $170,000 to $400,000 phased over 6 to 12 months. It adds routing evaluated against a specific axle configuration on licensed road network data, curfew and restriction checking along the route rather than at the desk, escort, crane and utility resource scheduling tied to the move, submission into state portals where a stable documented interface exists, and the crew packet with movement capture and the immutable move file behind it.

What decides your position inside those bands is jurisdiction count and equipment variety, not fleet size. A carrier running five states with two trailer builds is a genuinely smaller project than one running fifteen states with expandables, jeeps and boosters whose spread changes per move. Every additional state is its own rule set, its own form, its own escort thresholds and its own portal behaviour, and none of that scope is shared with the last one you did.

What drives a permit software build up

• Each additional jurisdiction, $6,000 to $12,000. Rules, form fields, escort thresholds, curfew definitions and permitted routing conventions all differ. Canadian provinces cost the same again and sometimes more, because the regulatory vocabulary does not map cleanly onto the state model you have already built.
• Configuration aware routing, $45,000 to $75,000. Evaluating a route against axle groups and spacings rather than a gross weight is the hardest engineering in the project. Bridge capacity responds to how load is distributed, and two combinations at the same gross weight can produce opposite answers on the same structure.
• Licensed road network data. Commercial network data with structure attributes carries a recurring licence cost that belongs in the budget from day one. It is not a build line, it is an operating line, and pretending otherwise is how these projects surprise a finance director in month nine.
• Portal submission, $15,000 to $40,000 per state that supports it. This is the least stable part of the whole build. Automate only where a state offers a documented interface and your volume there justifies the maintenance you are signing up for.
• Resource scheduling, $25,000 to $45,000. Escorts, police, utility crews, cranes and qualified drivers modelled as bookings against a move, so a two week bridge review surfaces every affected commitment in one place.
• Transportation management system integration, $18,000 to $35,000. Worth doing if you want moves, billing and settlement joined. Worth deferring if your permit desk is the bottleneck rather than your back office.

What keeps the number down

• Start with your top five jurisdictions by move count. That is where the volume and the risk both concentrate, and the rule model built there will absorb the rest at the lower end of the per jurisdiction range.
• One equipment class in phase one. Model the configuration family you run most. The second family is a fraction of the first because the axle group abstraction already exists.
• Manual permit submission at launch. Assemble a complete and correct application, then have a permit coordinator submit it. You get most of the error reduction without buying the most fragile component in the system.
• Keep the permit service for issuance. If a service bureau is efficient in a given state, let them keep filing there and build the coordination layer above. That middle path is what most carriers should actually buy.
• Defer routing to phase two. The move file, the configuration catalogue and the rule data deliver real value without a routing engine, and they teach you what the routing engine needs to know.
• Licence rather than assemble network data. Anyone proposing to build a road graph is creating a maintenance obligation with no competitive value, and the cost lands entirely on you.

A worked example that adds up

A heavy haul carrier running regularly across twelve states, engineered configurations including a nine axle expandable with jeep and booster, a mix of routine oversize and occasional superload work, and a two person permit desk.

• Discovery and restriction rule capture with both permit managers: $12,000
• Equipment configuration catalogue with axle groups, spacings and capacities: $38,000
• Move object with permits, route segments and connection point checking: $44,000
• Restriction, curfew and escort rule model across twelve jurisdictions: $47,000
• Permit application assembly against each jurisdiction's form: $36,000
• Routing evaluated against configuration on licensed network data: $58,000
• Escort, crane and utility resource scheduling tied to the move: $31,000
• Crew packet with route, permits, windows and movement capture: $26,000
• Move file archive with immutable amendment history: $19,000

That totals $311,000. Add a 12 percent contingency, because at least two states will turn out to apply a rule your permit manager knows but has never written down, and the committed number is $348,320 across roughly ten months. On top of that sits the network data licence as a recurring line, which is why it is not in the build total.

How the spend phases

• Weeks 1 to 4, about $12,000. Structured rule capture sessions with your permit managers. Budget more calendar time than feels reasonable, because most carriers have never written this knowledge down and the first pass is always incomplete.
• Weeks 3 to 16, about $118,000. The first release: configuration catalogue, move object, rule model and application assembly. At the end of this a permit request is generated from your actual trailer build rather than transcribed from a drawing.
• Weeks 14 to 30, about $58,000. Configuration aware routing on licensed network data, deliberately after the configuration model exists, because routing against a badly modelled trailer is worse than no routing at all.
• Weeks 24 to 34, about $31,000. Resource scheduling, once moves carry reliable dates that the system can propagate when a bridge review slips them.
• Weeks 30 to 40, about $45,000. Crew packet, movement capture and the move file archive. The archive lands last because it needs a full history of real moves to be worth exporting.

The ongoing costs nobody quotes

• Support and maintenance, 18 to 25 percent of build. On a $348,000 platform that is roughly $63,000 to $87,000 a year, covering monitoring, defect work and the steady trickle of small requests from the permit desk.
• Restriction rule maintenance, $15,000 to $35,000 a year. Rules change. Every rule carries a source and a review date precisely so this becomes a scheduled task rather than a discovery made at a scale house. Fund the person who owns it or the data rots and your permit managers go back to trusting memory.
• Road network data licence. A recurring cost set by your provider and your coverage. Get the quote before you approve the build, because it changes the shape of the business case rather than the size of it.
• Portal changes, $10,000 to $30,000 a year. Where you have automated submission, states alter their interfaces without notice. This line is the price of the convenience and it does not go away.
• New jurisdictions, $6,000 to $12,000 each. Opening a new lane is a rule modelling task, not a settings change, and it should be planned when the commercial decision is made.
• Hosting and archive retention, $8,000 to $22,000 a year. The move file is evidence. It needs durable storage with retention rules that match your insurer's expectations, not a bucket someone set up once.
• Training, $6,000 to $15,000 a year. The whole point is that a new coordinator becomes productive in weeks. That only holds if somebody keeps the training material current.

Comparing a build against your current renewal

The temptation is to compare the build against what a permit service invoices you. That is one line of four, and it is usually the smallest.

Take the service bureau and portal fees from your invoices for a full year. Then price the permit desk: two experienced coordinators, fully loaded, most of whose week is assembling applications and chasing amendments rather than exercising judgement. Then price the failures, and this is where the real number lives. For the last twelve months, count the moves that rolled because a permit came back late or an amendment broke a neighbouring permit, and put your own figure on a rolled move: the crew day, the escort company that invoiced for a cancelled booking, the crane appointment, and the customer relationship if the date was contractual. Finally, price the key person risk. If one permit manager retiring would cost you a year of degraded output, that is a real exposure even though it never appears on a ledger.

In our delivery experience the third line dominates for carriers running five or more jurisdictions, and the fourth is the reason owners actually approve the project. If your moves are mostly annual permit territory on standing limits, all four numbers will be small and you should not build.

When buying beats building

Buy if you run a handful of routine oversize moves a month across two states with repeatable dimensions. A permit service such as Bestpass, which handles permits alongside tolling, takes the administrative load off your desk and you will never recover a build at that volume. ProMiles is a reasonable answer if what you actually need is routing, mileage and permit ordering rather than project coordination, and TransCore sits deep inside state permitting systems in a way no custom build replaces.

Buy also if your work is mostly annual permit territory, where the same trailer runs the same corridors within standing limits. The coordination complexity that justifies a build is largely absent there, and you would be paying for machinery you never load.

The middle path deserves naming because it is what most carriers should choose. Keep a permit service for actual issuance in the states where they are efficient, and build only 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.

When the shortlist is down to two and you need a tiebreaker, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You can take that specification to any other firm on your shortlist.