Documentation for zone boundary change to be submitted to department
- • requirements for positive determination
(1)(a) The sponsor of an enterprise zone shall submit to the Oregon Business Development Department documentation of a boundary change under ORS 285C.115 (Change of zone boundaries).
(b) For purposes of this subsection, the documentation submitted to the department must include:
(A) A map clearly indicating the changes made to the boundary;
(B) A new description and geographic information system data for the area inside the zone; and
(C) Any other information required by the department for the purposes of making a determination under this section.
(2) As soon as practicable after receipt of the documentation required under subsection (1) of this section, the department shall notify the zone sponsor of the department’s determination.
(3)(a) The department’s determination shall be positive and final if the requirements of this section and ORS 285C.115 (Change of zone boundaries) are met.
(b) The boundary change shall take effect on the date on which the latest resolution of the sponsoring city, county or port was adopted.
(4)(a) If the department’s determination is negative, the notice required under subsection (2) of this section must state the reasons for the negative determination.
(b) The zone sponsor may resubmit documentation for a determination under this section and the sponsor and the department may discuss changes in the documentation necessary for a positive determination under this section.
(c) If the sponsor resubmits documentation and the department makes a positive determination, the boundary change shall take effect on the date on which the latest resolution of the sponsoring city, county or port was adopted, or the date on which any outstanding requirement for the boundary change is satisfied, as stipulated in the department’s determination. [2015 c.648 §18]
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.