2007 ORS 455.080¹
Inspector may require proof of compliance

Notwithstanding ORS 455.630 (Enforcement) (2), any inspector, including a specialty code inspector licensed under ORS 455.457 (Licensing specialty code inspectors and plan reviewers), authorized by ORS 455.150 (Selective municipal building inspection programs) or 455.153 (Municipal authority to administer specialty code or building requirements) to determine compliance with the requirements of the state building code or any specialty code under this chapter may, in accordance with a compliance program as described in ORS 455.153 (Municipal authority to administer specialty code or building requirements) (2), require any person who is engaged in any activity regulated by the state building code to demonstrate proof of compliance with the applicable licensing, registration or certification requirements of ORS chapters 446, 447, 455, 460, 479, 480, 693 and 701. [Formerly 456.802; 1999 c.1045 §14; 2001 c.411 §16]

Note: 455.080 (Inspector may require proof of compliance) was enacted into law by the Legislative Assembly but was not added to or made a part of ORS chapter 455 or any series therein by legislative action. See Preface to Oregon Revised Statutes for further explanation.

Notes of Decisions

Although state structural specialty code sets standard requiring only single wall construc­tion, home rule city was entitled to enact ordinance requiring new homes to use double wall construc­tion. State ex rel Haley v. Troutdale, 281 Or 203, 576 P2d 1238 (1978)

Atty. Gen. Opinions

Authority of State Fire Marshal to adopt regula­tions, (1974) Vol 36, p 1102

1 Legislative Counsel Committee, CHAPTER 455—Building Code, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­455.­html (2007) (last ac­cessed Feb. 12, 2009).
 
2 Legislative Counsel Committee, Annotations to the Oregon Revised Stat­utes, Cumulative Supplement - 2007, Chapter 455, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­455ano.­htm (2007) (last ac­cessed Feb. 12, 2009).
 
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.