VDOT Land Use Permits: Commercial Entrances, Chapter 527 TIA, and Urban Maintenance

Virginia's VDOT Land Use Permit (LUP) under 24VAC30-151 governs any work or non-transportation use on VDOT-maintained highway right-of-way or VDOT-owned property — including commercial entrance construction. VDOT targets ~10 business day review when preliminary comments are addressed and the county-approved grading plan is unchanged. Chapter 527 (24VAC30-155) adds a layer for rezoning and special use permit applications: Traffic Impact Analysis review. And two counties — Arlington and Henrico — administer their own urban road maintenance rather than relying on VDOT, which affects which permit track applies. This essay walks the VDOT access framework.

Virginia state highway with commercial development and roadway access at golden hour, photorealistic, warm cinematic lighting, VDOT access management aesthetic

The statutory and regulatory framework

Primary source: virginiadot.org.

When an LUP is required

Any work on or non-transportation use of VDOT-maintained state highway ROW or VDOT-owned property. For commercial development, the most common triggers:

Single-use permits handle specific activities like permanent highway entrance construction. Districtwide permits exist for utilities and other ongoing occupancy types.

The LUP application process

  1. Preliminary engineering analysis submitted by applicant.
  2. VDOT evaluation and approval of engineering analysis — contingent on approval for commercial entrance permits.
  3. Application submission with plans or sketches.
  4. Other permissions secured by applicant from other parties with ROW interests.
  5. Performance surety — district administrator's designee sets amount based on estimated cost of work within ROW.
  6. VDOT review targeting ~10 business days when preliminary comments are addressed and county grading plan is unchanged.
  7. Permit issuance.
  8. Construction and inspection.

Chapter 527 Traffic Impact Analysis (TIA)

24VAC30-155, enacted under Va. Code § 15.2-2222.1, requires localities to submit TIAs to VDOT for review when proposed land use changes (rezoning, SUP) are expected to substantially affect transportation on state-controlled highways:

The TIA process in VA is locality-driven (localities submit for VDOT review), in contrast to the developer-driven TIS submission structure in DE, PA, NJ, and MD. The practical effect: developers work with the locality to prepare the TIA for VDOT review, rather than directly submitting to the state.

Road and Bridge Specifications — the design floor

VDOT's Road and Bridge Specifications govern:

Localities (e.g., Virginia Beach) may adopt VDOT's current specifications (e.g., 2020 Road and Bridge Specifications) with local amendments for their capital improvement projects.

The Urban Maintenance Program exception

VDOT maintains most public roads in most VA counties (interstate, primary, and secondary systems). Two counties — Arlington and Henrico — maintain their own local road systems:

Practical effect: commercial projects on local roads in Arlington or Henrico engage the county/locality for maintenance-related matters, not VDOT. Projects on state highways in those jurisdictions still engage VDOT LUP. See our Arlington County essay for the Arlington-specific context.

Coordination with local land-use process

LUP review is often concurrent with or downstream of local land-use approvals:

How VDOT compares to neighbors

Practical implications for developers

What to do with this

If your VA project fronts VDOT-maintained road: LUP required. Engineering analysis first.

If your project is in Arlington or Henrico on local roads: county/local administration, not VDOT.

If you're doing rezoning or SUP: Chapter 527 TIA through the locality.

For adjacent VA regulatory context, see our VA USBC, VA CBPA, Richmond DPDR, Norfolk, Fairfax County, Alexandria, and Arlington essays.

About The Hive

The Hive builds tools and publishes essays for working construction and MEP professionals in the Delaware Valley and Mid-Atlantic. Primary-source-grounded, practitioner-voiced, free to use.