HaulAuditTexas Permit Execution

Texas DMV, on its own page for annual crane permits

“You are responsible for routing and obtaining current restrictions prior to movement.”

Your permit was right the day it printed.

Read it cover to cover and you know the rules as they stood at issuance. You will not find the width limit that appeared last summer, the four sections that closed to permits in June, or the railroad crossing that now wants eighteen inches of clearance. Those live in a separate stack of state documents your permit never contained. We check them against your route the day you roll.

See the live route reviewOpened with an access key — ask and we’ll walk you through it.

What reading it yourself will not tell you

Verified
One permit we tested — a finding from our own research, not a product screen

A 107-mile run across West Texas. Load: 12 ft 6 in wide, 13 ft 6 in high, 70 ft long. The permit is correct, complete, and was accurate the day the state issued it.

We took the roads that permit travels and the counties it crosses, and searched the state’s current district lists. Nine restrictions came back on those roads in those counties — six printed after that permit was issued. Four are outright no-permit sections. One is this:

“10’ max width between W.LP193 and IH27. This restriction also affects US82 where it is double signed with US62.”

A ten-foot limit on a twelve-and-a-half-foot load. No amount of reading that permit would have found it — it did not exist when the permit printed.

Rules that changed after issuance

We hold 2,541 current TxDMV district restrictions across 26 districts — width, height, weight, closures — each with its restriction number, its printed date, and the checksum of the state document we read it from. Your permit is a snapshot; this list is not. Binding each rule to your specific segments is the next thing we ship, and until it is proven we will not tell you a rule applies to you.

The conditions block, decoded

Yes — we do read your permit, and we lift the special-conditions block word for word. But that is table stakes. The value is that we read it against everything the state has published since.

Your route on the state’s own map

The issued route drawn on TxDOT’s published centerline — the same geometry the state uses — colour-coded by how well we can stand behind each stretch. Not a line between dots. The actual road. Today that covers 79.6% of permitted miles; the rest is marked, not hidden.

Turn-by-turn a driver can follow

Your permit says 2.90 FM400 sw Turn left onto US70 e [5TH]. We say it the way you would say it out loud, with the permit’s exact wording beside it so nothing is lost in translation.

Next — a heads-up before you need it

Three turns inside a mile. A road you will be on five separate times. A stretch where you double back the other way and think you are lost. We have measured all of it in the permit data — seven such turns on one route, one road visited five times. Surfacing it to the driver is built next, and it is not in the product today.

Next — a record you never have to file

Tap a leg when you start it, get a live arrival time for every jurisdiction ahead, and let those same taps become the record of what you drove. Designed, not built. We will not describe it as shipped, and we will not sell it as a shield against a damage claim — Texas ties that liability to axle weight, which no positional record speaks to.

TxPROS issues the permit and it does that well. Everything above happens after it prints — and today it happens on a clipboard, or it does not happen.

How a heavy move works in Texas

Verified
  1. 1

    The load breaks the normal rules

    A crane, a transformer, a wind-turbine blade — too wide, too tall, too long or too heavy for what any truck may legally haul. The industry calls these oversize/overweight loads, abbreviated OS/OW. They cannot move at all without written permission from the state.

  2. 2

    The state issues a permit and a route

    The Texas Department of Motor Vehicles (TxDMV) runs a system called TxPROS that authorizes the move and computes a specific legal route — not the fastest way there, the way you are permitted to go. It draws that route on road geometry published by a second agency, the Texas Department of Transportation (TxDOT), which owns the state’s roadway data.

  3. 3

    One person has to actually drive it

    That exact route, at ten miles an hour through intersections a hundred feet of trailer cannot turn in one motion, past bridges with inches to spare. Leave the permitted route and the permission may no longer apply. The wrong road can mean a struck bridge, a cracked county road, or a crane stopped on a shoulder waiting for a decision.

  4. 4

    Afterward, nobody can prove much

    The permit says where you were allowed to go. Very little says where you actually went. When a county sends a damage claim months later, the record is usually a folded permit and someone’s memory of a Tuesday.

Steps 1 and 2 are solved, and solved well. Everything HaulAudit does lives in steps 3 and 4.

Our compiler does not draw a route from a description of one. It takes each instruction on your issued permit and binds it to TxDOT’s own published roadway centerline — the state’s coordinate geometry for that exact road. Where an instruction cannot be tied to real geometry, that segment is marked unresolved and left undrawn. This page is held to the same standard as the routes.

  • VerifiedTraceable to a named source — a state document we cite by page, a vendor’s own published text, or TxDOT centerline coordinates for a specific road. Not our summary of it.
  • InferredOur reasoning from those sources. Argument, not evidence — weigh it accordingly.
  • UnprovenNothing we can show you settles this. Only fleets paying for live moves will.

What already exists

Verified

Every system below is good at its actual job. We are not competing with the state, and any pitch that needs TxPROS to be bad should be disbelieved — including ours. The real question is narrower: what happens to an issued permit between the office and the shoulder of the road.

TxPROS

The State of Texas permitting and routing system

Does well

Issues the permit and computes a restriction-aware route with turn-by-turn directions and a map. Maintains roughly 9,000 restrictions. Eligible customers self-issue around the clock.

776,696
OS/OW permits issued, FY 2025
82%
issued as single-trip routed permits
~25 min
average single-trip issuance
>99%
reported uptime since launch
Stops at

Public materials do not describe an offline package for the cab, a driver-and-office exception workflow, or a record of what was issued against what was actually driven.

TxDMV system narrative; FY 2025 Chairman’s Annual Report, p. 19

ProMiles Permit Route Guidance

Free in-cab guidance for permits from supported jurisdictions

Does well

Follows the state-created breadcrumb trail and maneuvers with visual and voice guidance. Shipping on both major app stores.

Stops at

The vendor’s own published FAQ states it does not route independently, carries no OS/OW restriction data, does not alert the driver to a permit-route change, does not store the route, and leaves route-following mode when the vehicle deviates.

Public ratings sat at 2.0/5 on Apple (58 ratings) and 2.1/5 on Google Play (71 reviews) when observed on 31 July 2026. Store ratings are self-selected and they move. They point to a driver-layer experience problem — they establish nothing about the accuracy of Texas routes.

ProMiles published FAQ and app-store listings, accessed 31 July 2026

ProMiles PermitManager

Multi-jurisdiction permit planning and management

Does well

The most serious competitor here, and it should be treated that way. Route restrictions, quoting, custom fleet restrictions, digital route surveys, permit management, audible directions.

Stops at

Public materials reviewed do not establish deterministic ingestion of an already-issued TxPROS permit, instruction-to-geometry provenance for Texas, or a complete as-issued versus as-driven record.

Vendor product pages, accessed 31 July 2026

Truck navigation, generally

Truck-legal routing, offline maps, low-bridge avoidance

Does well

Mature, well understood, and genuinely good at keeping an ordinary truck on roads it is allowed to use.

Stops at

A route optimized for a truck is not the route authorized by a permit. Automatic rerouting is a feature everywhere else and a hazard here — it can quietly substitute a road the permit does not cover.

Vendor product documentation, accessed 31 July 2026

What we will claim

Nothing we reviewed takes an issued Texas permit, binds each instruction to authoritative roadway geometry with provenance, packages it for a cab with no signal, handles deviations and exceptions, and produces a record of issued against driven.

What we will not claim

That there is no competition. That TxPROS is unreliable. That ProMiles could not build this. All three are false, and anyone in this market will know it inside a day.

What HaulAudit holds

Inferred

Five outcomes the permit does not deliver on its own. These are the product’s requirements — not a description of a finished system.

Exactness

Every maneuver binds to the issued permit and to Texas roadway geometry. The legal route is never silently replaced with a better one.

Continuity

Permit, geometry, maneuvers, contacts and conditions are readable before departure — and stay readable where there is no signal.

Change control

Conditions are re-checked before the wheels turn, and what changed is shown as a change, not refreshed underneath you.

Coordination

Driver, office, escorts, curfews and jurisdiction contacts live in one move, so a question does not become five phone calls.

Proof

The issued route, its version, the track actually driven, and how each exception was handled are retained as an ordinary record of the move.

A gap is better than a guess

Verified

When the compiler cannot tie a permit instruction to real roadway geometry, it leaves that segment unresolved and says so. It does not draw a plausible line across the gap.

This costs us coverage on every permit we publish, and we publish the coverage number anyway. It is also the only reason the rest of the route is worth anything — a system that never admits uncertainty gives you no way to tell its confident answers from its invented ones. An unresolved segment is the product working, not the product failing.

The same discipline is why we will not describe an execution record as a shield against liability. A positional record shows where a vehicle went. It cannot speak to axle weight — which is what Texas law actually ties county road-damage liability to.

What we surface, and what we can’t

Verified

A Texas permit carries conditions that decide whether a move goes well. They are on page two, in a block most people never read, and nothing on the road reminds you of them.

We put these in front of the driver

“Self propelled cranes are exempt.”

Attached to a metro curfew. If your machine qualifies, a delay you were planning around may not apply to you at all — and the exemption is one clause below the restriction that caused the planning.

“…713-308-9050, at least 3 days in advance; the mover is responsible for all fees.”

A phone call with a three-day lead time, printed inside a paragraph. Miss it and the load stops — not because anything went wrong on the road, but because a call was never made.

“Restriction #: 17865[LBB/LBB Lubbock Truck Route: No permits unless Orig/Dest.] overridden; Reason: LUBBOCK DISTRICT BLANKET APPR DESTINATION;”

A rule that normally forbids this move, waived, with the reason recorded. The permit is carrying its own audit trail — and nobody reads it.

2,541 state district restrictions, held with page-level provenance.

Height limits, width limits, no-permit sections and weight bans across 26 TxDMV districts — each with its restriction number, printed date, and the checksum of the source document we read it from. Binding a given rule to a given stretch of your route is the next thing we ship, and we will not say a rule applies to you until it is proven.

We tell you what we do not cover

City and county rules are not in our data.

Your permit says it plainly — it does not authorize travel on county roads or city streets, and the carrier is responsible for contacting the jurisdiction. We hold the state’s district lists. We do not hold a municipal ordinance, and we will not imply that we do.

Restrictions we could not parse cleanly are held back, and counted.

In the Lubbock district, five extraction units out of a hundred and twenty-five were quarantined rather than guessed at. You see the count. A silent drop would read exactly like a district with nothing to report.

A drawn line is not a clearance, a legality, or a safety finding.

Centerline geometry says where a road is. It says nothing about what fits under a bridge, what a turn will do to a hundred feet of trailer, or what the pavement is rated to carry.

Every jurisdiction on your route gets a coverage line, including the empty ones.

“Lubbock District — 194 restrictions, snapshot 30 July 2026, source verified.” And beside it: “City of Lubbock — not in our data; your permit requires you to contact them.” The second line is the one worth paying for, and it is the one nobody else will print.

We audit ourselves

Verified

We audited our own driver narration and found eleven material errors. Three named the wrong road. The rest added operational language the permit did not support, blurred permitted miles with mapped miles, or misstated a direction or a result.

11 → 0errors before and after the audited rebuild, across 89 re-audited rows. The correction changed presentation only — no route geometry, truth tier, mileage or row authority moved.
2independent clean builds compared by automated contract audit — equivalent data, rows, drawn set and trace set. After normalising build timestamps, byte-identical.

We publish this because a vendor who has never found anything wrong with their own product has not looked. Three wrong road names is exactly the failure this industry cannot tolerate, and we would rather you hear it from us than find it yourself.

Operating boundaries

Verified

HaulAudit works from the state-issued permit, never instead of it. The carrier keeps the physical inspection and the execution responsibilities the move requires.

  • No safety certification. A mapped segment is not a finding that the move is safe.
  • No clearance certification. Centerline evidence does not establish overhead, width, weight, turning or temporary-condition clearance.
  • No legal or driveability certification. We do not approve a route, release a driver, or replace current state rules.
  • No hidden incompleteness. Unresolved legs stay labelled, and current coverage is reported in the demo itself rather than rounded up here.
  • Comparison stays in scope. Our case rests on what we demonstrably do, not on unsupported claims about anyone else’s product.

What the demo is, exactly

Unproven

The route review is generated by our compiler from historical permits against a pinned TxDOT road snapshot. It is review evidence — not navigation, and not clearance certification.

Move Pack, roadside inspection and curfew staging are roadmap mockups, not live product. Compiler-generated Move Packs carry no curfew, staging, hazard, load-profile or contact data today, so this page does not claim them.

The open question is not whether this problem exists — it does, and the evidence above is public. It is whether we execute it reliably enough that a fleet keeps paying. Live moves settle that. A landing page does not.