2017 ORS 634.720¹
Plan coordinators

(1) The governing body shall provide for the designation of one or more persons as integrated pest management plan coordinators for the governed schools. A plan coordinator must be an employee of the governed district, unit, school or entity, unless the governing body delegates pest management duties to an independent contractor. Each school shall have the services of at least one integrated pest management plan coordinator. A plan coordinator may serve more than one school. The responsibilities of the plan coordinator shall include, but need not be limited to:

(a) Giving notice and posting warnings under ORS 634.740 (Written notice requirements);

(b) Overseeing pest prevention efforts;

(c) Providing for the identification and evaluation of pest situations;

(d) Determining the means of appropriately managing pest damage that will cause the least possible hazard to people, property and the environment;

(e) Ensuring the proper and lawful performance of pesticide applications;

(f) Evaluating pest management results; and

(g) Keeping records as required by ORS 634.750 (Pesticide application records).

(2) A plan coordinator shall complete not less than six hours of training each year. The training shall include at least a general review of integrated pest management principles and the requirements of ORS 634.700 (Definitions for ORS 634.700 to 634.750) to 634.750 (Pesticide application records). [2009 c.501 §4]

Chapter 634

See also annota­tions under ORS chapter 573 in permanent edi­tion.

Atty. Gen. Opinions

County ac­tion to regulate pest­i­cides, (1980) Vol 41, p 21

1 Legislative Counsel Committee, CHAPTER 634—Pesticide Control, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors634.­html (2017) (last ac­cessed Mar. 30, 2018).
 
2 Legislative Counsel Committee, Annotations to the Oregon Revised Stat­utes, Cumulative Supplement - 2017, Chapter 634, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ano634.­html (2017) (last ac­cessed Mar. 30, 2018).
 
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.