FireApproved

Maryland

Maryland

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

What is established here

Maryland does not adopt a statewide WUI construction book. The Maryland Building Performance Standards are the IBC, IRC, and IECC with state modifications. IWUIC is not those standards. 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 Maryland →

What is not established

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

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

Plants documented in Maryland

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 460 Keep away 141 Documented conflict 44 Awaiting evidence 207

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

Plant groups in Maryland →

Human page and machine twin

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