FireApproved

Minnesota

Minnesota

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 Minnesota. A ZIP personalizes priority; it does not decide a parcel boundary.

What is established here

Minnesota does not adopt a statewide WUI construction book. Minnesota Rules 1305.0011 adopts the 2018 IBC, chapters 2 through 35, and deletes all IBC appendices. IWUIC is not that rule. 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 Minnesota →

What is not established

A ZIP in Minnesota 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 Minnesota (not reprinted here):

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

Plants documented in Minnesota

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 260 Keep away 32 Documented conflict 3 Awaiting evidence 111

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

Plant groups in Minnesota →

Human page and machine twin

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