Bindinglaw

OR · rules

ORAP 16.45

ELECTRONIC SERVICE

activein force · 2026-09-03 – presentact-effective-date

(1) Registration as an eFiler with the eFiling system constitutes consent to receive

service via the electronic service function of the eFiling system.

(2) (a) Except as provided in subsection (3), a party eFiling a document may use

the eFiling system's eService function to accomplish service of that document on any other

party's attorney or on a self-represented party, if that party's attorney or the self-represented party

is a registered eFiler.[fn 1] The eFiling system will generate an email to the attorney or self-represented party being eServed that includes a link to the document that was eFiled. To access

the eFiled document, the attorney or self-represented party who has been eServed must log in to

the eFiling system.

(b) eService is effective under this rule when the eFiler has received a

confirmation email stating that the eFiled document has been received by the eFiling

system.

(3) A party eFiling a document must accomplish service via paper service or other

form of service permitted by ORCP 9, if:

(a) The document to be served:

(i) initiates a case in the Court of Appeals;

(ii) initiates a case in the Supreme Court under that court's original

jurisdiction;

(iii) is a first motion for extension of time to file a petition for review in

the Supreme Court; or

(iv) if no motion for extension of time has been filed, is a petition for

review in the Supreme Court;

(b) The party to be served is self-represented and is not a registered eFiler; or

(c) The attorney to be served is not a licensee of the Oregon State Bar and is

not a registered eFiler, or is a licensee of the Oregon State Bar but has obtained a waiver

to the mandatory eFiling requirement under ORAP 16.60.

(4) All eFiled documents must be accompanied by a proof of service under ORAP

1.35(2)(e). The proof of service must certify service on all parties regardless of the means by

which service was accomplished, including eService. The proof of service must state that

service was accomplished at the person's email address as recorded on the date of service in the

eFiling system and need not include that person's email address or mailing address.

(5) If an eFiled document is not eServed by the eFiling system because of an error in

the transmission of the document or other technical problem experienced by the eFiler, the court

may, upon satisfactory proof, permit the service date of the document to relate back to the date

that the eFiler first attempted to eServe the document. A party must show satisfactory proof by

filing and serving an accompanying letter explaining the circumstances, together with any

supporting documentation.

Provenance

Source
courts.oregon.gov
Retrieved
2026-09-25
Edition
2026-09-25
Content hash
a30b9519adb631b36ecad4bcdf60999d98dfc34a60e31caa8dbcca02d9d887d0
View the official source →

The link goes to the issuing authority’s own document — the one we read to produce this record. Where a source publishes whole titles rather than sections, your browser may need a moment to jump to the provision.

Unofficial copy of government-published law, reproduced from official sources with full provenance. Not an official publication; verify against official sources before relying on it in a filing. Records in the 'guidance' corpus, and only that corpus, are sub-regulatory (interpretive guidelines, survey procedures) and are not binding law. Validity bounds follow each jurisdiction's declared temporalBasis.

Coverage · API docs

Bindinglaw

Point-in-time US law with the receipt attached. Source URL, retrieval time, content hash, and validity dates on every answer.

curl api.binding.law/v1/law/coverage

© 2026 binding.law · a Jubal, Inc. productAttorneys and firms never pay. Ever.