FireApproved

Utah

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.

Construction sources: reviewed 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 Utah. A ZIP personalizes priority; it does not decide a parcel boundary.

What is established here

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 is not established

A ZIP in Utah is a postal match, not a parcel, map, or permit. 2 sourced local authorities are open below; 2 have a sourced construction application.

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.

What differs here

Object records that name Utah (not reprinted here):

2 more on the JSON twin.

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

Guides focused on Utah

2 guides name Utah. The reading list is on Learn.

Plants documented in Utah

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.

Fire-resistant 228 Keep away 39 Documented conflict 10 Awaiting evidence 155

432 plant records documented in the state. 0 explicitly document Utah as native range. 115 carry an invasive or noxious flag applying here. 1 fire-evidence sources name Utah in publication scope.

Plant groups in Utah →

Human page and machine twin

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