Utah

Construction sources: reviewed · state briefing

Utah

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.

2local authorities
432plant records
2guides
2026-08-26last verified

Utah adopts the international family statewide and, in the same statute — 15A-2-103 — names the 2006 Utah Wildland Urban Interface Code as a book any local compliance agency may adopt. Both of the state's 2 sourced local nodes have done so; local authorities lists them. What applies to your house forks on that local choice.

Between the state shelf and two city adoptions, what we can't tell you yet tracks what no official record has yet settled.

Wasatch-to-canyon planting steps down USDA half-zones 8b to 4a — 432 documented plant records, 115 of them flagged invasive or noxious — and living here climbs the same ladder.

What applies in Utah

Utah Code 15A-2-103 adopts IBC, IRC, IPC, IMC, IFGC, NEC, IECC, IEBC, and ISPSC as statewide construction codes. Subsection (2) adopts the 2006 Utah Wildland Urban Interface Code as a construction code that a local compliance agency may adopt by ordinance. That is not a statewide WUI construction mandate. 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 Utah →

What we can't tell you yet

2 sourced local authorities are open below; 2 have a sourced construction application. Local adoption is never implied from silence.

Sourced local authorities (2)

Each page is labeled by the record actually sourced. A fire-access document is not presented as a code adoption. 2 code-application records are normalized below these place nodes.

Living here

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.

432 plant records documented in the state. 115 carry an invasive or noxious flag applying here. One fire-evidence source names Utah in publication scope.

Plant groups in Utah → · Utah embed

Put this table on your own site

For Utah Firewise committees, fire districts, and HOA architectural committees. The frame stays current as the evidence does, so it does not go stale the way a copied PDF does. Free to use with the attribution line below, which the snippet already includes.

<iframe src="https://fireapproved.com/embed/plants/utah/" title="Utah wildfire plant table" width="100%" height="900" loading="lazy" style="border:1px solid #ddd"></iframe>
<p>Plant table from <a href="https://fireapproved.com/places/utah/">FireApproved.com</a>, cited to its sources. Not a planting approval.</p>

2 guides name Utah — the reading list is on Learn.

Reading that names Utah

2 more on the JSON twin.

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

This briefing is the place answer; the claim graph lives on object pages and the Utah JSON twin · place node JSON · Methodology