- • cover and signature sheet requirements
- • circulation
- • filing deadline
(1) Before circulating a petition to initiate or refer a county measure, the petitioner shall file with the county clerk a prospective petition. The county clerk immediately shall date and time stamp the prospective petition, and specify the form on which the petition shall be printed for circulation. The clerk shall retain the prospective petition.
(2) The cover of an initiative or referendum petition shall designate the name and residence address of not more than three persons as chief petitioners and shall contain instructions for persons obtaining signatures of electors on the petition. The instructions shall be adopted by the Secretary of State by rule. The cover of a referendum petition shall contain the title described in ORS 250.175 (Preparation of ballot titles for certain county measures) (1). If the circuit court has not reviewed the ballot title under ORS 250.195 (Procedure for elector dissatisfied with ballot title of county measure), the cover of an initiative petition shall contain the ballot title described in ORS 250.175 (Preparation of ballot titles for certain county measures) (3). If the circuit court has reviewed the ballot title, the cover of the initiative petition shall contain the title certified by the court.
(3) The chief petitioners shall include with the prospective petition a statement declaring whether one or more persons will be paid money or other valuable consideration for obtaining signatures of electors on the initiative or referendum petition. After the prospective petition is filed, the chief petitioners shall notify the filing officer not later than the 10th day after any of the chief petitioners first has knowledge or should have had knowledge that:
(a) Any person is being paid for obtaining signatures, when the statement included with the prospective petition declared that no such person would be paid.
(b) No person is being paid for obtaining signatures, when the statement included with the prospective petition declared that one or more such persons would be paid.
(4)(a) Each sheet of signatures on an initiative petition shall contain the caption of the ballot title. Each sheet of signatures on a referendum petition shall contain the number of the ordinance or resolution to be referred, if any, and the date it was adopted by the county governing body.
(b) Each sheet of signatures on an initiative or referendum petition shall, if one or more persons will be paid for obtaining signatures of electors on the petition, contain a notice stating: “Some Circulators For This Petition Are Being Paid.”
(5) The reverse side of the cover of an initiative or referendum petition shall be used for obtaining signatures on an initiative or referendum petition.
(6) Not more than 20 signatures on the signature sheet of the initiative or referendum petition shall be counted. The circulator shall certify on each signature sheet that the circulator:
(a) Witnessed the signing of the signature sheet by each individual whose signature appears on the signature sheet; and
(b) Believes each individual is an elector registered in the county.
(7) Unless otherwise provided by a county ordinance, the gathering of signatures on a petition to initiate a county measure may not exceed a period of two years from the time the petition is approved for circulation.
(8) A county clerk may not accept for filing any petition which has not met the provisions of subsection (7) of this section.
(9) A petition to initiate a county measure must be filed not less than 90 days before the election at which the proposed law is to be voted on.
(10) The person obtaining signatures on the petition shall carry at least one full and correct copy of the measure to be initiated or referred and shall allow any person to review a copy upon request of the person. [1979 c.190 §154; 1981 c.909 §3; 1983 c.756 §10; 1991 c.106 §1; 1992 c.1 §2; 1995 c.607 §28; 1997 c.846 §2; 1999 c.318 §28; 2001 c.965 §5; 2005 c.797 §39; 2007 c.848 §16; 2009 c.571 §1]
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.