Virginia

Virginia

Program and model No adopted WUI code we can source here. IBHS Wildfire Prepared asks for the inspection measures, and the 2024 IWUIC model says the same floor.

No statewide construction book — sourced Last verified 2026-08-26

One local briefing, built from separate evidence layers: what the state has published, where an instrument is documented to apply, what still depends on a map or project fact, and which plant records are documented in Virginia. A ZIP personalizes priority; it does not decide a parcel boundary.

What is established here

Virginia does not adopt a statewide WUI construction book. 13VAC5-63 adopts IBC 2021 chapters 2–35 as the Uniform Statewide Building Code. Referenced standards apply only to the prescribed extent of each IBC reference. IWUIC is not adopted as a statewide construction book. Confirm with the building official.

No exact code-application record is normalized for this state. A source node alone does not activate requirements.

Open the Build rules for Virginia →

What is not established

A ZIP in Virginia is a postal match, not a parcel, map, or permit. No city or county briefing is open here yet.

What differs here

Object records that name Virginia (not reprinted here):

Child-place and sibling claims stay on those place pages, their object URLs, and the JSON twin.

Plants documented in Virginia

State distribution, native range, invasive status, hardiness, and fire evidence answer different questions. None is a planting approval. The list itself is on Grow — this page carries the aggregates.

675 plant records documented in the state. 8 explicitly document Virginia as native range. 169 carry an invasive or noxious flag applying here. 1 fire-evidence sources name Virginia in publication scope.

Plant groups in Virginia →

Human page and machine twin

This briefing is the place answer. The claim graph lives on object pages and the JSON twin. Methodology · Virginia JSON · place node JSON