Sending or receipt of documents in electronic form
- • rules
- • fees
(1) Notwithstanding any provision of ORS chapters 536 to 540, 543 or 543A that requires the mailing of a document, the submission of a document in written form or the provision of a certified copy of a document, the Water Resources Department may adopt rules:
(a) Allowing the submission of one or more types of document to the department by electronic means in lieu of submission by mailing or submission in written form;
(b) Allowing the department, with the consent of the recipient, to send one or more types of document in electronic form in lieu of mailing or other sending of the document in written form; or
(c) Identifying acceptable means for verifying the authenticity of a document sent by electronic means in lieu of the provision of a certified copy of the document.
(2) The department may not adopt rules to require the submission of documents to the department by electronic means. The department may not require a recipient to consent to the receipt of documents from the department by electronic means. The department may not use electronic means in lieu of service under ORCP 7 or notice under ORS 183.413 (Notice to parties before hearing of rights and procedure) or 183.415 (Notice of right to hearing).
(3) For purposes of determining timeliness or calculating deadlines, a document sent by electronic means in accordance with department rules is considered to be delivered when sent.
(4) Notwithstanding any provision of ORS chapters 536 to 540, 543 or 543A that specifies a fee amount, the department may reduce or waive the fee for a document that the department sends or receives by electronic means. [2011 c.51 §1]
Note: 536.045 (Sending or receipt of documents in electronic form) was enacted into law by the Legislative Assembly but was not added to or made a part of ORS chapter 536 or any series therein by legislative action. See Preface to Oregon Revised Statutes for further explanation.
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.