SLR 20-5.061: Ex Parte Matters
Edition: 2026Effective: UnknownLast verified: 2026-09-07
(1) The court will schedule an ex parte hearing date and time when the filing party notifies it that they are requesting an ex parte appearance. Unless there is an emergency, the party must contact the Case Management Department at least 24 hours before filing to schedule a hearing. The court will hold an ex parte hearing only if: (a) The party is requesting a Temporary Restraining Order (TRO) under ORCP 79 and notice is being provided to the opposing party, or (b) The party claims that giving notice would defeat the purpose of the motion and believes a personal appearance is necessary. If neither of these apply, the court will decide the matter based on the documents submitted. The Motion for TRO and any related documents must be filed using File and Serve before the hearing. (2) Petitions for relief under ORS 107.700 to 107.735, ORS 124.005 to 124.040, ORS 166.525 to 166.543, and ORS 163.760 to 163.777 shall be heard at 1:00 P.M., Monday through Friday, in a courtroom designated by the Presiding Judge. (3) Any motion which is to be presented ex parte shall have attached to it a certificate of service which shall include the date, time, and manner of service upon the opposing party, the party’s attorney, or that no service was made, if appropriate. When service is required, it must be completed at least 24 hours prior to the ex parte appearance unless it is an emergency or service is not possible. The following shall be added to the Certificate of Service: "I certify that I did / did not (circle one) serve a copy or give notice of said documents to him / her (circle one) on [date] at [time] AM / PM (circle one) by [method of service/notice] ." If no service, explain why. Page 8 of 46 Washington County, 20th Judicial District February 1, 2026 CHAPTER 6 – TRIALS
This rule cites
- ORCP 79 — resolved
- ORS 107.700 — resolved
- 107.735 — resolved
- ORS 124.005 — resolved
- 124.040 — resolved
- ORS 166.525 — resolved
- 166.543 — resolved
- ORS 163.760 — resolved
- 163.777 — resolved
Cited by
Official source: URL pending reconciliation; preserved manual snapshot is identified below.