Beyond "Great Highway Access": The Route Documentation That Survives a First-Cut Screen

A site selector reading an industrial RFI gets one of two highway answers.

One reads: the site is 15 minutes from I-70.

The other names the interchange, traces the route turn by turn to the loading dock, gives the functional classification and truck-route status of every road segment, lists every bridge with its posting status and vertical clearance, includes swept-path drawings at the critical turns for a WB-67 tractor-semitrailer, and dates the state DOT GIS extraction.

The first may be perfectly accurate. It also can't be graded, and the selector has seven other sites in the file that answered the question.

The Site Selectors Guild's 2024 site-readiness guidance lists two separate logistics criteria: access to the public highway system, and site ingress/egress to the public road system. The first asks whether the regional network connects the site to markets. The second asks whether a loaded truck can physically and legally get from the interchange ramp to the dock. Tier-3 cities routinely answer the first and skip the second.

Mark Williams of Strategic Development Group, in a 2025 Business Facilities interview, identified four questions in his transportation screen: proximity to an Interstate or high-quality four-lane highway, near-site road conditions, whether traffic lights or congestion impede the route, and drive time to customers and suppliers. Site Selection Group's 2026 heavy-industry guidance adds weight-bearing capacity, large-vehicle turning radius, and connections to major freight corridors. A drive-time claim answers none of them.

The five evidence chains below apply to every industrial prospect. What shifts by sector is which chain gets weighted first, and that is where tier-3 cities most often misjudge what to document.

Five evidence chains, five authorities

A highway connection resolves into at least five separate evidence chains. Each is controlled by a different authority and documented in a different system.

1. Functional classification and truck-route status. FHWA's 2023 functional classification guidance assigns every public road a class: Interstate, Other Freeways/Expressways, Other Principal Arterial, Minor Arterial, Major Collector, Minor Collector, or Local. Classification describes the road's intended service function in the network hierarchy. It does not describe legal truck status. A road classified as an Other Principal Arterial may or may not be a designated truck route. FHWA's Highway Performance Monitoring System maintains functional class and National Truck Network status as separate data fields.

Under the federal reasonable-access rule, states must allow STAA-dimension vehicles (the standard 48-foot and 53-foot semitrailers authorized by the Surface Transportation Assistance Act) to travel between the National Network and terminals by the most reasonable and safe route. The general presumption is one road mile. A 12-mile route from an Interstate interchange to an industrial site sits well outside that presumption and needs its own documented truck-route designation or access determination.

The state DOT maintains the official classification. MPOs are typically the local contact inside urbanized areas. Outside MPO boundaries, the state DOT district or county planning organization may participate. The data lives in the state's GIS layers. A route answer should preserve the classification, owner, and truck-route status of every segment, because all three can change at a segment boundary.

2. Bridge and structure clearances. Every bridge, culvert, and overhead structure on the route has a posting status, load rating, and vertical clearance maintained by its owner. The National Bridge Inventory compiles these nationally, but FHWA warns that NBI data should not be used for route-clearance purposes: inspections run on a 24-month cycle, and displayed clearances may not be current. The transition to the SNBI specifications introduces more granular fields, including legal-load configuration, posting value by vehicle type, routine-permit-load status, and clearance by lane and direction. The state or local bridge owner remains the authoritative source.

Wisconsin's weight-restricted bridges map shows how far a database can sit from field conditions. It draws from the state's Highway Structures Information System every two weeks, and it warns that a posted sign supersedes the map. Small bridges or culverts under 20 feet may be omitted entirely.

3. Seasonal restrictions. Northern states add a layer that year-round operations cannot ignore. Wisconsin maintains three separate seasonal programs: frozen-road declarations, Class II restrictions, and seasonal posted roads. The state highway system is covered. County and township authorities decide independently when their local roads are frozen or thawing and whether local limits apply. A route file that omits seasonal restrictions is incomplete for any operation that ships 12 months a year.

4. Turning geometry. The standard industrial design vehicle is the WB-67: a tractor-semitrailer with a 53-foot trailer, 73.5 feet overall length, and a minimum design-turn radius of 44.8 feet. The swept path is the area the vehicle needs to complete a turn. It has to be evaluated at every interchange ramp, signalized intersection, industrial-park entrance, gate, and dock approach on the route.

A Minnesota freight-connector study demonstrated the method: high-resolution aerial imagery overlaid with an AutoTURN WB-67 template at each intersection, grading whether the vehicle could complete the turn without overtracking curbs or encroaching into opposing lanes. Desktop swept-path analysis followed by field verification is the documented public-agency approach.

"Trucks get in and out fine" is an assurance. It carries no more evidentiary weight than a utility telling a prospect that power is available.

5. Oversize/overweight permitting. Federal law sets Interstate weight limits — 80,000 pounds gross, 20,000 on a single axle, 34,000 on a tandem — but does not issue OS/OW permits. Permitting is a state function. Each state on a multistate route issues its own permit, with conditions that may specify the route, travel dates and hours, escorts, and infrastructure contacts.

Minnesota requires a physical route survey when a load exceeds 16 feet high, 20 feet wide, or 175 feet long. The survey must be conducted within 14 days of the permit start date, requires six inches of vertical clearance and one foot of lateral clearance, and remains valid for up to 60 days only under specified same-dimension, same-carrier conditions. A state permit is not valid on local roads. A separate local permit may be required.

A city cannot obtain final OS/OW movement authority without the live load's dimensions, weight, axle arrangement, carrier, and dates. It can pre-document the candidate corridor: every bridge and overhead structure, tight turns, rail crossings, utility crossings, issuing jurisdictions, permit categories, survey triggers, and escort requirements. Pre-documentation converts a question that takes weeks into one that takes days.

What each sector screens first

How these chains rank against each other shifts by sector, and the shift changes what a passing answer looks like.

JIT automotive and time-sensitive production. A 2025 Area Development account of automotive site selection identifies supply-chain proximity, logistical readiness, and truck-ready docks among current expectations. The controlling variable is transit-time reliability. FHWA defines Truck Travel Time Reliability as the ratio of the 95th-percentile truck travel time to the 50th-percentile time, calculated on Interstate segments using NPMRDS data. A route file for an automotive prospect should report normal and 95th-percentile truck times by shift period, recurring bottlenecks, construction exposure, weather vulnerability, and alternate-route performance.

The selector is answering whether a specific delivery pattern survives the corridor's worst recurring conditions. That means the route file gets built around the customer plant's receiving windows rather than around generic peak and off-peak periods. If the customer runs three shifts with a 45-minute dock window at each changeover, the file should report travel-time variability for those departure times. It should also state the number of daily inbound and outbound truck movements the prospect assumes, because a route that works for 12 daily trips may fail at 40 once signal timing, intersection queuing, and construction-season detours compound. Include the alternate route and its time penalty. The selector will ask what happens when the primary corridor is blocked.

Bulk and heavy-haul operations. The controlling variable is whether the load can legally and physically reach the site. Federal regulations require bridge analysis for every permit load crossing. For heavy equipment manufacturing, transformer delivery, modular construction, or wind-energy components, the OS/OW corridor is a binary gate.

A pre-documented corridor for these sectors looks different from a general industrial route file. The design vehicle is the actual transport configuration: a 13-axle transformer hauler, a blade transporter at 200-plus feet, a modular building section at 20 feet wide. The corridor package should include bridge-by-bridge load analysis for that axle configuration, swept-path drawings using the actual vehicle template at every constrained turn, overhead utility clearances with the contact and estimated cost for each required lift, escort staging points, and the jurisdictional permit sequence from state through township with an estimated administrative timeline. A city targeting these sectors without a pre-documented OS/OW corridor is asking the prospect to do the city's infrastructure homework during the evaluation window.

Finished-goods distribution. Site Selection Group frames DC location as a network-optimization exercise: drive-time coverage and logistics access. The screen measures reach in multiple directions to the facility's demand nodes and evaluates intermodal terminal access for containerized freight. A Wisconsin regional intermodal study treated a one-way 30-mile dray as optimal for its study area, but WisDOT's 2025 update found actual 2024 drayage quotes covering one-way distances from 57 to 253 miles. There is no universal competitive drayage radius.

The relevant answer names the actual terminal, operator, serving carrier, accepted equipment, road miles and truck time from site to gate, and a current drayage quote for the tested lane. The quote needs to separate line-haul from accessorials. WisDOT's 2025 analysis found that quoted drayage prices reflected chassis rental, storage, detention, tolls, and fuel surcharges, costs that vary by terminal and operator rather than by mileage. The file should also confirm the specific rail lane and service frequency for the shipper's origin-destination pair, container or trailer equipment type, chassis source, and gate appointment process. BTS's national intermodal facility layer lists 241 TOFC/COFC facilities in 37 states. That layer confirms a facility exists at a location. It does not confirm that the facility accepts the shipper's equipment or serves the shipper's lane.

Two city profiles, two documentation gaps

Profile A: a 70,000-person city at two U.S. highways, 12 miles from the Interstate interchange. Cities at this kind of junction typically carry an industrial base built on regional distribution: food processing, agricultural equipment, building materials, light fabrication. The highway intersection gave them a logistics reason to exist. If the city is now targeting automotive supply-chain or advanced manufacturing investment, the 12-mile connecting route becomes the entire evaluation. The JIT reliability screen hits hardest here, because every minute of variability on that corridor compounds across dozens of daily deliveries.

Every segment needs its functional class, truck-route status, and owner extracted from the state DOT GIS. Every bridge needs its current posting and clearance from the owning authority. The route needs truck counts, signal locations, travel-time reliability data, and WB-67 swept paths at the highway junctions and the industrial-park entrance. If the city is targeting heavy-haul sectors, the OS/OW corridor needs a preliminary survey identifying every dimensional constraint and every issuing jurisdiction. The 12-mile distance exceeds the federal one-mile reasonable-access presumption, so the route's status for STAA vehicles has to be established through a designated truck route or a documented access determination.

Profile B: a city directly on an Interstate, with a constrained last-mile corridor through older industrial streets. These are cities with legacy industrial districts — foundries, fabricators, warehousing — built when the Interstate was new and the standard trailer was shorter. The available sites are often existing buildings or brownfield parcels in corridors designed for vehicles 15 feet narrower and 20 feet shorter than today's WB-67. Interstate frontage answers the regional question. The proof that decides the deal sits in the municipal streets between the ramp and the dock: narrow lanes, tight turns, low overhead structures, rail crossings with adverse profiles, on-street parking that narrows the effective width, signal spacing that traps long vehicles, municipal truck restrictions. Geometry is the critical gate, and heavy-haul sectors may be functionally excluded unless the constrained corridor can be mitigated.

The geometry package is the critical artifact. Where a WB-67 cannot complete a turn without opposing-lane encroachment or curb overtracking, the file should document the mitigation: removable signs, temporary parking restrictions, traffic-control procedures, each with the responsible authority, cost, lead time, and restoration conditions specified. FHWA's highway-rail crossing guidance adds that a high-profile crossing can strand a low-ground-clearance trailer, and that a nearby signal can leave a long vehicle without adequate storage beyond the tracks.

Both profiles face the structural problem I described in the rail-service piece in Issue #3: the EDO is answering for infrastructure it does not control. The road owner, bridge owner, permit authority, and intermodal terminal operator are separate parties with separate records. The EDO's job is to compile and present their documentation.

The compilation checklist

Route GIS. Extract the official state DOT functional-classification layer for every segment from the selected Interstate interchange to the parcel. Record the class, route ID, road name, owner, maintaining jurisdiction, National Network status, state or local truck-route designation, and any posted truck prohibition or time restriction. Note the extraction date.

Structures. List every bridge, culvert, tunnel, overhead sign structure, and grade-separated crossing on the route by structure number. For each: current posting status, posting value by vehicle configuration, load-rating date, minimum vertical clearance by lane and direction, maximum usable width, inspection date, owner, and a confirming contact. Photograph the current posted sign. Do not rely on the NBI or state map alone.

Seasonal and temporary restrictions. Identify spring-thaw, frozen-road, construction, work-zone, holiday, weather, and time-of-day restrictions on every segment. Record the activation source, maintaining authority, and notification mechanism.

Geometry. Produce scaled WB-67 swept-path drawings for the interchange ramp turns, every signalized or stop-controlled intersection, the industrial-park or site entrance, the gate, internal circulation, and the loading docks. Identify any assumed opposing-lane encroachment, curb overtracking, or temporary removal of signs, poles, parking, or other obstructions. If the target sector requires a larger control vehicle — wind-energy transporter, transformer hauler — produce a separate set for that vehicle.

Traffic operations. Compile available truck-classification counts, signal locations and cycle lengths, recurring congestion periods, incident and work-zone history, normal truck travel time, and 95th-percentile truck travel time or another reliability measure for the route. Identify the alternate route and its performance.

OS/OW corridor. Identify every issuing jurisdiction (state, county, city, township, toll authority) for every segment. Document available permit categories such as single-trip, annual, and superheavy; dimensional and weight triggers for route survey; survey validity period; required clearances; escort and traffic-control requirements; utility and sign-removal contacts; and the live-project inputs required before authorization can be issued.

Intermodal access (if distribution is a target sector). Name the terminal, operator, serving carrier, accepted equipment types, access road, one-way road miles and truck time from site to terminal gate, peak-period reliability, gate process, chassis availability, and a current drayage quote or operator confirmation for the tested lane. Separate line-haul from accessorial charges.

For every item, record the design vehicle or freight profile tested, the responsible authority, the effective date, the validity or reconfirmation condition, and any known constraint. A bridge posting that limits a specific vehicle type, a turn that requires temporary parking removal, a seasonal window that restricts operations for six weeks — these are the kinds of limits that belong in the file. An answer that names its own limits is an answer a selector can grade. The principle I stated in Issue #1 holds here too. A city that documents a constraint and presents a credible, time-bounded path to resolution outcompetes a city that offers assurances it cannot verify.