State DOT Permit Process for Fiber Deployment: A 2026 Source and Variance Map

A fiber route may touch a state highway without placing every segment under one office or one permit instrument, so the useful first question is not which package starts the process. It is which published source identifies the authority for that exact corridor. State terminology, district assignments and local agreements can change the answer before technical work begins.

This guide compares source authority rather than recreating the broad lifecycle covered in our DOT permit coordination guide because we separate federal context from state and local control. Then we compare administering offices, policy exception routes and closeout language across verified examples. Our final one-page brief sends package preparation, review handling and field execution to the existing Draftech process articles that own those decisions.

Separate Federal Context from State and Local Authority

No nationwide state dot permit process for fiber deployment exists. Identify each route's state or local authority and administering office. Use its policy and instructions before checking issued terms and closeout direction. The 6 Draftech controls below are project guidance, not a government process. Authorities may combine, reorder or omit them.

The Federal Highway Administration Utilities Program provides the national context for Federal-aid highway right of way because it explains that states decide whether utilities may occupy highway right of way, to what extent and under what conditions. That statement does not create a common application sequence. It points readers to the legal authority and accommodation policy that govern the specific highway. That distinction is legally important.

The legal attribution needs two separate readings, and under 23 CFR Part 645 Subpart B §645.215(a), a state submits an authority statement addressing its legal authority or regulatory power. The statement also identifies its policies and any Federal-aid highway areas where the state transportation department lacks legal authority. It is an authority disclosure, not an approval of an individual fiber permit.

A different provision controls qualifying policy approval. Under 23 CFR Part 645 Subpart B §645.215(b), FHWA approves state transportation department policies for use on Federal-aid highway projects when they satisfy the listed federal provisions and the regulation. Policy approval does not erase the limits disclosed in the authority statement. It also does not transfer every application decision to FHWA.

Local authority remains possible. 23 CFR Part 645 Subpart B §645.209(g) addresses Federal-aid projects where the state transportation department lacks legal authority to regulate highway use by utilities. In that situation, the state transportation department must make formal agreements with the responsible local officials who hold that authority. Our source hierarchy therefore leaves room for a state policy, a local agreement and corridor-specific instructions.

For Draftech work, we read the hierarchy from authority to application detail by beginning with the regulation and the state's approved accommodation policy before we identify the controlling highway record and any formal local arrangement. Only then do we use the administering office's current instructions or issued document. Our permitting service applies that hierarchy without treating federal context as a nationwide permit checklist. The hierarchy starts there.

Compare State Terms and Administering Offices

State sources do not use one shared label for the permission: California publishes Encroachment Permit Application Package material, Arizona discusses encroachment permits, and Minnesota describes permits for utilities on trunk highway right of way. Virginia uses a land use permit application for utility installations. North Carolina publishes encroachment agreement information. We preserve each source's term because the term leads to the correct office and governing document. Office names still vary.

Office assignment varies too because the Arizona Department of Transportation Encroachment Permits page says permits are issued by the respective ADOT district office where the encroachment will be located. MnDOT's Permit Information and Forms page says a utility owner needs an approved permit before work on trunk highway right of way. These verified statements have different scopes, so neither should be translated into a rule for every state highway.

This is a cross-state variance and source map, not a six-step government procedure because each row identifies what the cited publication can establish and what it cannot export. California's screening language does not appoint a Permit Engineer in Virginia. ADOT's district assignment does not define a MnDOT trunk highway. NCDOT's bond release text does not create a national closeout requirement.

Read each row vertically before comparing it across states because the source identity tells our team what can be reproduced and the administering difference tells us who may speak for that publication. The final question exposes what still needs corridor-specific confirmation. This reading order prevents a familiar state name from outranking the actual authority source. It also keeps office custom separate from published policy when the two appear to conflict.

The map also keeps state and local roads from blending together, so if the route leaves state-controlled right of way, our team rechecks the authority source instead of carrying the state instrument forward by assumption. The county road permit guide owns county-specific package preparation. Here, we only decide which authority branch and office should govern each segment.

Compare Caltrans and MnDOT Exception Sources

Caltrans provides a reproducible California source set on its Applications & Forms page and identifies Caltrans TR-0413 Rev 03/23, EP Application Check List - Utilities and Broadband. It also states that every Encroachment Permit Application Package submittal is screened by a Permit Engineer before acceptance. Those details describe California intake and source selection. They do not prove how another state screens a utility request. Templates are not interchangeable.

The same Caltrans page lists the Encroachment or Utility Policy Exception Request template dated 12/24 and separate preparation guidance, and that identity matters because a generic reference to a California exception form is hard to reproduce after files change. In our adaptation brief, we write the exact title and date. We also note the district contact that confirmed the document applies to the planned work.

Minnesota publishes a different route because MnDOT's Utility Accommodation on Highway Right of Way policy says an exception is requested by an authorized person representing the utility owner. The MnDOT District Engineer or authorized representative recommends approval. The MnDOT Utilities Engineer acts for the Commissioner when approving. The policy also identifies when FHWA concurrence is involved. These are Minnesota roles, not a reusable national chain.

The comparison changes our next question: in California, we look for the applicable Caltrans template and preparation guidance while in Minnesota, we identify the people assigned by the MnDOT policy and confirm the highway scope. We do not convert either example into a promise that relief is available. A published route explains how to ask. Only the authorized government decision can resolve the request.

We also record the authority class of the item we cite because a regulation carries a different weight from an agency policy while a dated template serves a different purpose from preparation guidance or an email answer. Our comparison names that difference so a project team does not present a helpful example as binding law. The agency's controlling source and authorized decision remain distinct from Draftech's recommendation.

When the source is unclear or the cited document no longer matches the office's direction, our brief records the conflict in plain language and asks the administering office to identify the controlling publication. Timing diagnosis belongs in the permit delay guide. This article stops at choosing the right exception source and government decision point. The source date matters.

Compare VDOT and NCDOT Closeout Sources

Virginia's reproducible example is the Virginia Department of Transportation VDOT LUP-UT October 22 2024, Land Use Permit Application for Utility Installations and the document says the local permit office coordinates review with appropriate VDOT personnel. It also contains a Final Inspection and Completion of Permit section. Those statements support a Virginia office and closeout comparison without inventing a national inspection bundle.

North Carolina publishes a narrower example on the NCDOT Encroachment Agreements for Utilities page, and for the bond release process described there, the encroaching party submits a written request with specified agreement information. NCDOT personnel then perform a final inspection. If deficiencies are found, release waits until they are addressed. The page scopes that sequence to bond release, so our brief does the same.

The variance is practical because VDOT places final inspection and completion language inside LUP-UT while NCDOT explains a written request and inspection tied to bond release on a separate web page. We capture the exact closeout source named for the route instead of copying either state's words into a generic checklist. The administering office remains the place to resolve missing or conflicting direction. Closeout terminology also shifts.

Our state brief records what the source calls completion and whether another decision remains. It does not declare a permit closed from field completion or an internal project status. Teams that need to organize owner-facing files can use the fiber closeout report template. That article owns report structure. The state source or issued instrument still controls government closeout.

Draftech keeps engineering and permit-package coordination in-house, along with record-document work. When construction is included, Draftech delivers it full turnkey through Draftech-managed subcontract crews under Draftech QA/QC and safety oversight. The DOT or responsible local authority retains permit power. The owner-designated authority remains separate when the project requires an internal decision before construction.

Build a One-Page Draftech State Adaptation Brief

We condense the source comparison into six Draftech controls for one defined corridor and treat them as our project guidance rather than a government process while the controlling authority may combine them and may reorder or omit them. We use the brief to make the next source and decision visible before teams enter the detailed workflows maintained elsewhere. We record every mismatch.

• Authority control: cite the state authority statement and any applicable agreement with responsible local officials.
• Office control: preserve the agency's term and identify the district, region or local office for the route.
• Policy control: name the current accommodation policy and distinguish FHWA policy approval from permit authority.
• Exception control: cite the state-specific procedure or written office direction without borrowing another state's form.
• Closeout control: name the issued document or official page that defines inspection, completion or bond release for this work.
• Decision control: state the unresolved question and route execution to the article that owns the detailed work.

The brief should read like a decision note, not a database export because our heading names the route and highway limits before the body identifies the controlling authority in the agency's own words. It then gives the administering office and exact source identities for accommodation, exception and closeout questions. We finish with one unresolved decision and the person authorized to obtain it.

A useful one-page result can be read without project software. For example, it may say that ADOT controls a named highway segment through a particular district office, while a local road segment follows another authority. It may identify a Caltrans exception template as not applicable or note that NCDOT bond release language belongs only to the cited agreement. Our brief favors these bounded statements over empty labels such as standard DOT process.

Detailed execution stays in the appropriate lane because broad state DOT requirements belong in the DOT coordination guide linked above while utility conflict work belongs in our utility coordination process guide. Traffic control design and field-change handling belong in the work zone traffic control plan guide. The source brief points to those workflows but does not duplicate them. Execution stays with the cited process.

The same boundary applies to operational tools. Controlled handoffs and package checks belong in the permit workflow automation guide. Event history belongs in the permit status tracking guide. Portfolio capacity belongs in the simultaneous permit guide. Our one-page brief supplies source context to those systems rather than becoming another tracker.

We review the brief against the official source before a team relies on it. A page title without a revision identity is weak when the publisher offers a dated form. A district name without route limits is also weak. We prefer a short brief that clearly states one gap over a longer memo that hides uncertainty behind generic permit language. Shorter briefs expose uncertainty.

Author contact: Ashish Kumar Meena at Draftech.

Choose the Next Decision and Route Execution by Role

Program owners: choose one route and approve the authority branch shown in the brief. If ownership remains disputed, obtain a written state or local determination before funding detailed permit work. Route multi-permit prioritization to the portfolio guide instead of expanding this source map into another operating cadence.

Engineering leaders: recommend the exact accommodation and exception sources that govern design questions. Keep technical judgment with engineering while the agency retains exception and permit decisions. Send detailed package design, utility conflict resolution and traffic control work to their existing process guides after the authority source is confirmed.

Construction leaders: identify the issued source that governs field limits and the authority's closeout direction before mobilization. Keep owner-designated construction authorization separate from government permit power. If the brief cannot identify who decides next, pause field planning until the administering office and project authority are clear.