Bend

Local adoption Bend adopted ORSC R327. This is the rule.

Sourced code adoption city in Deschutes County, Oregon · last verified 2026-08-27

Bend is a sourced city record in Deschutes County, Oregon. The construction answer is the application of Bend ORSC R327 application, adopted 2026-04-15. A ZIP is a postal lead, not a parcel.

What is established here

Current Bend Code establishes all Bend city limits as the WUI Hazard Zone and applies ORSC R327 throughout that area. Ordinance NS-2552 was adopted on 15 April 2026 and codified in May; the exact effective date is not established by the opened sources. Use the local Build evidence, then confirm the parcel and project with City Building Safety.

Bend · active application documented

Bend ORSC R327 application

Current Bend Code 9.10.010 establishes the entire area within Bend city limits as the WUI Hazard Zone and applies ORSC R327 throughout that area. Ordinance NS-2552 was adopted on 15 April 2026 and codified in May 2026, but the opened sources do not establish its exact effective date or decide the boundary and project trigger for a parcel. Confirm with Building Safety.

Scope: incorporated boundary · adopted 2026-04-15

Still verify with the authority

Confirm the parcel is inside the cited authority or boundary.
Confirm that the project type and permit scope trigger the provision.
Confirm the ordinance's effective date for this project.
Confirm the result with the authority having jurisdiction.

9 joined requirements · Bend Code 9.10.010, Specialty Codes · source accessed 2026-08-27

Open the Build rules for Bend →

What is not established — the contrast

Oregon has 11 sourced local nodes; 5 have a sourced construction application. Adoption is not statewide by implication: Lincoln County, Marion County, Medford, Portland, Redmond, Yamhill County have none sourced here. A ZIP is a postal lead; confirm official boundaries and project conditions.

What meets the rule here

2 vents products match the governing requirement → Adopted
11 roofing products match the governing requirement → Adopted
25 windows products match the governing requirement → Adopted
No sourced doors product matches the governing requirement yet → Adopted
11 siding products match the governing requirement → Adopted
No sourced decking product matches the governing requirement yet → Adopted
1 eaves product matches the governing requirement → Adopted
No sourced gutters product matches the governing requirement yet → Adopted
25 fencing products match the governing requirement → Voluntary program
1 landscaping product matches the governing requirement → Voluntary program

What differs here

Object records that name Bend (not reprinted here):

9 more on the JSON twin.

Inherited and sibling claims stay on their object pages and on Bend JSON. 17 place-focused guides → Learn.

What we do not have

These checks stay open because the sourced instrument leaves them to the official record, not because this page skipped them:

Whether the instrument is in force for this project's date.
The official boundary that would put a parcel inside the application.
Confirmation from the building official for this project.
Whether this project type is in scope of the instrument.

3 requirement rows have no matched product in the directory

doors: orsc-r327-multilayered-glazing
decking: orsc-r327-noncombustible-walking-surface
gutters: orsc-r327-noncombustible-gutters

Plant context for Bend

Grow for this city is the state plant pool cut to USDA half-zones observed on ZIPs that resolve here (6a, 6b). Zone is not a fire rating. 622 records document distribution in Oregon; 0 explicitly document native range; 147 carry an invasive or noxious flag that applies in the state.

Plant groups in Bend →

What to verify before acting

Confirm the official boundary or hazard map, the adopted instrument and effective date, the project type, and the exact product model or plant conditions. Methodology · Bend JSON