ORS § 90 § 90.392
Termination of tenancy for cause; tenant right to cure violation.
Operative Text
(1) Except as provided in this chapter, after delivery of written notice a landlord may terminate the rental agreement for cause and take possession as provided in ORS 105.100 to 105.168, unless the tenant cures the violation as provided in this section. (2) Causes for termination under this section are: (a) Material violation by the tenant of the rental agreement. For purposes of this paragraph, material violation of the rental agreement includes, but is not limited to, the nonpayment of a late charge under ORS 90.260 or a utility or service charge under ORS 90.315. (b) Material violation by the tenant of ORS 90.325. (c) Failure by the tenant to pay rent. (3) The notice must: (a) Specify the acts and omissions constituting the violation; (b) Except as provided in subsection (5)(a) of this section, state that the rental agreement will terminate upon a designated date not less than 30 days after delivery of the notice; and (c) If the tenant can cure the violation as provided in subsection (4) of this section, state that the violation can be cured, describe at least one possible remedy to cure the violation and designate the date by which the tenant must cure the violation. (4)(a) If the violation described in the notice can be cured by the tenant by a change in conduct, repairs, payment of money or otherwise, the rental agreement does not terminate if the tenant cures the violation by the designated date. The designated date must be: (A) At least 14 days after delivery of the notice; or (B) If the violation is conduct that was a separate and distinct act or omission and is not ongoing, no earlier than the date of delivery of the notice as provided in ORS 90.155. For purposes of this paragraph, conduct is ongoing if the conduct is constant or persistent or has been sufficiently repetitive over time that a reasonable person would consider the conduct to be ongoing. (b) If the tenant does not cure the violation, the rental agreement terminates as provided in the notice. (5)(a) If the cause of a written notice delivered under subsection (1) of this section is substantially the same act or omission that constituted a prior violation for which notice was given under this section within the previous six months, the designated termination date stated in the notice must be not less than 10 days after delivery of the notice and no earlier than the designated termination date stated in the previously given notice. The tenant does not have a right to cure this subsequent violation. (b) A landlord may not terminate a rental agreement under this subsection if the only violation is a failure to pay the current month’s rent. (6) When a tenancy is a week-to-week tenancy, the notice period in: (a) Subsection (3)(b) of this section changes from 30 days to seven days; (b) Subsection (4)(a)(A) of this section changes from 14 days to four days; and (c) Subsection (5)(a) of this section changes from 10 days to four days. (7) The termination of a tenancy for a manufactured dwelling or floating home space in a facility under ORS 90.505 to 90.850 is governed by ORS 90.630 and not by this section.
Oregon Revised Statutes § 90.392 establishes the process by which a landlord may end a tenancy for cause — such as a material violation of the rental agreement, a violation of ORS 90.325, or failure to pay rent. Before termination can occur, the landlord must deliver a written notice that identifies the specific violation and, in most cases, gives the tenant at least 30 days' notice and an opportunity to cure the problem within at least 14 days. If the tenant successfully corrects the violation by the designated cure date, the rental agreement remains in effect; if the same or substantially similar violation recurs within six months of a prior notice, the tenant loses the right to cure and the landlord may set a shorter termination window of as few as 10 days.
Plain English — not legal advice.
Under ORS § 90.392, compliant operators ensure that any termination-for-cause notice is in writing and precisely identifies the acts or omissions that constitute the violation, rather than using vague or general language. The notice must state a termination date of at least 30 days out (or seven days for week-to-week tenancies) and, where the violation is curable, must describe at least one possible remedy and set a cure deadline of no fewer than 14 days from delivery (or four days for week-to-week tenancies). Operators who have already issued a notice for a substantially similar violation within the prior six months may use a shorter 10-day termination window and are not required to offer a cure period, though they should be aware that this accelerated path cannot be used when the sole violation is nonpayment of the current month's rent.
General guidance for property managers — not legal advice for your specific situation. Consult an attorney for advice on your case.
ORS § 90.392 gives tenants important protections before a landlord can terminate a tenancy for cause: the landlord must deliver a written notice that spells out exactly what the alleged violation is, and in most situations tenants have at least 14 days to cure the problem — meaning that correcting the issue in time generally stops the termination from taking effect. If a tenant believes a notice does not meet the specific requirements of § 90.392 — such as failing to describe a possible remedy or setting an unlawfully short cure period — that deficiency may be raised as a defense in any eviction proceeding. Tenants facing a termination notice may wish to contact a local tenant-rights organization or Oregon's legal aid services to understand the options available under this provision.
General guidance for tenants — not legal advice for your specific situation. Consult a tenant-rights organization or attorney for advice on your case.
Generated October 7, 2026 — auto-generated, not yet human-reviewed. See /transparency for methodology.
Effective Timeline
References Out
Rules and statutes cited by this regulation
References In
No inbound references recorded yet for this provision.
Related Rules
Source Information
Use this in your app
Access this data programmatically via our API