Virginia's USBC: The Most Uniform Statewide Building Code in the Mid-Atlantic

USBC statutory framework

• Statutory authority: Va. Code §§ 36-97 et seq. (Uniform Statewide Building Code).
• Regulation: 13VAC5-63 (the USBC itself).
• Adoption body: Virginia Board of Housing and Community Development (BHCD), which adopts and amends the USBC based on nationally accepted model codes.
• Agency administration: Virginia Department of Housing and Community Development (DHCD).
• Local enforcement: County and city building officials enforce the USBC locally.
• Appeals: State Building Code Technical Review Board (SBCTRB) hears appeals after local boards and issues binding interpretations.

Primary source: dhcd.virginia.gov.

The three-part structure

The USBC is organized into three parts, each handling a different life-cycle phase of the built environment:

Part I — Virginia Construction Code (VCC)

Regulates new construction. Current edition based on the 2021 International Codes, effective January 18, 2024, with Virginia-specific amendments. Contractors and designers building new work reference Part I.

Part II — Virginia Existing Building Code (VEBC)

Regulates rehabilitation of existing buildings — repairs, alterations, additions, and changes of occupancy. Parallel to MD's MBRC structure; gives design teams on existing-building work a more workable standard than force-fitting new-construction rules.

Part III — Virginia Maintenance Code (VMC)

Regulates ongoing maintenance of existing structures. Enforcement is optional for local governments — a locality can adopt Part III for routine property-maintenance enforcement, or leave it unenforced. This is the one part where jurisdictional variation is expected.

Most commercial construction is in Part I or Part II territory; Part III shows up for owners/landlords dealing with chronic property maintenance situations.

How "uniform" actually shows up

Statewide uniformity isn't a slogan — it's structural:

• USBC supersedes local building regulation. A locality cannot adopt a building code ordinance that conflicts with USBC.
• Few state-specific amendments. BHCD's practice is to base the USBC on nationally accepted model codes with as few amendments as possible. This makes Virginia more model-code-aligned than MD (which amends actively on energy) or NJ (which amends for statewide uniformity of its own).
• Limited local amendment authority. Local officials can enforce the code and delegate duties, but cannot alter USBC provisions or create new building regulations. Exceptions permitted: local zoning, historic preservation, and floodplain management — the adjacent-but-distinct regulatory areas.
• Modification approvals at the building-official level. On a project-specific basis, a building official may approve written modifications to USBC provisions where the code's spirit and intent are preserved and public safety is assured. This is project-level discretion, not local code-base amendment.

The net: a designer's VCC compliance analysis produced for a Richmond project translates to a Tidewater project or a rural Southwest VA project with minimal code-base adjustment. Local process differs; local code base substantially does not.

DHCD's role

DHCD supports BHCD in code adoption, administers the code development process, and serves as the state agency interfacing between the model-code world (ICC) and Virginia's adopted provisions. DHCD also:

• Regulates manufactured housing and industrialized buildings under related safety regulations.
• Facilitates stakeholder input in code development.
• Provides resources to local code enforcement personnel (including ICC Digital Codes Premium subscriptions).
• Coordinates the Virginia Statewide Fire Prevention Code (SFPC) in parallel with USBC.

SBCTRB — the appeals and interpretations body

The State Building Code Technical Review Board is governor-appointed and operates within DHCD. Its responsibilities:

• Hearing appeals from enforcement actions taken under the USBC, SFPC, and related regulations. Aggrieved parties first appeal to a local appeals board; unsuccessful appeals escalate to SBCTRB.
• Providing binding interpretations of USBC and SFPC provisions.
• Making recommendations to BHCD on future modifications, amendments, or repeals.

SBCTRB's interpretations matter. A designer or contractor dealing with a code question on which local building officials differ can seek an interpretation that applies statewide, not just in one locality. This is a real uniformity lever that neighboring states' structures don't offer in the same way.

What uniformity doesn't mean

USBC uniformity is about the code base itself. It does not homogenize:

• Permit process. Richmond's DPDR (see our Richmond DPDR essay), Fairfax's building department, Norfolk's process, and rural county building offices each run their own procedures, portals, review cadences, and fee schedules.
• Historic preservation overlays. Richmond's CAR, Old Town Alexandria's BAR, Colonial Williamsburg-adjacent review — each has its own authority under an exception to USBC uniformity.
• Zoning. Fully local and substantially variable.
• Floodplain management. Local ordinances under the NFIP can add substantive requirements beyond USBC.
• Environmental and stormwater. Separate regulatory frameworks (CBPA, VSMP, Wetlands Act) interact with USBC at the project level but aren't part of it. See our VA VSMP essay.
• Contractor licensing. DPOR Class A/B/C framework (see our VA Class A/B/C essay) is parallel to USBC and operates independently.

So a contractor moving from Fairfax work to Richmond work or Tidewater work isn't learning a new code base — they're learning new local procedures, new historic overlays, and new project stakeholders.

How VA compares to the other Mid-Atlantic states

• Virginia — USBC uniformity. Strong statewide base, narrow local amendment, SBCTRB for binding interpretations.
• New Jersey — UCC uniformity without opt-out. N.J.A.C. 5:23 uniform; Construction Officials administer at city level. No local code-base amendment authority. See our Camden UCC essay.
• Maryland — MBPS with active local amendment. Localities genuinely differ (Montgomery County ≠ Washington County). See our MBPS essay.
• Pennsylvania — UCC with municipal opt-out. Most municipalities opt in; opt-out municipalities route commercial to PA L&I and residential to third-party agencies. See our PA UCC essay.
• Delaware — no statewide base. Adoption varies city/county by city/county.

A ranking on statewide-code-uniformity from most to least: VA ≥ NJ > MD > PA > DE.

Operational implications for VA projects

• Design to USBC, not to locality-specific code. A single set of code-compliant details works across VA.
• Check USBC edition vs project permit application date. Adoption cycles matter; 2021 I-Codes became VCC effective January 18, 2024.
• Use VEBC for existing building work. Don't force-fit new-construction requirements onto existing structures when VEBC pathways are available.
• When local officials interpret differently, SBCTRB is the route. Binding statewide interpretations resolve persistent inconsistencies.
• Local permit process still varies. Uniform code, local process.

What to do with this

If you're crossing into VA from a more-varied-code state (MD, PA): the VA code base is more predictable than your home market. Lean into that.

If you're working multi-locality in VA: one compliance analysis travels across projects. Differentiate investment on local process, not on code-base relearning.

If you're on an existing building: use VEBC. It's designed for rehabilitation work and usually produces more feasible paths than VCC new-construction requirements.

If you're stuck on a code interpretation at the local level: local appeals board first, then SBCTRB if needed.

For the full VA regulatory stack, see our Virginia Contractor Licensing Navigator and Virginia Prevailing Wage Navigator.

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.