OAR 813 § 813-115-0035
Required Notice by Owner to Tenants and Prospective Tenants of Properties with OHCS Restrictions
Operative Text
(1) In addition to the notices required under ORS 456.781 and ORS 456.814, and OAR 813-115-0030, owners of publicly supported housing properties subject to OHCS restrictions are required to notify tenants and prospective tenants of withdrawal of a participating property. (2) The notice described in subsection (1) above must be on a form as prescribed and provided by OHCS. The most current version of the tenant notice form will be made available on the department's website. (3) If a dwelling unit is subject to an affordability restriction, as defined in ORS 456.766, the landlord must provide written notice to any applicant or prospective tenant prior to charging a screening fee or entering into a rental agreement. (4) The written notice described in subsection (3) must: (a) Be in the form prescribed by OHCS; (b) Clearly state the earliest possible date the affordability restrictions could be terminated; (c) Be provided before a screening charge is assessed or a rental agreement is executed. (d) The most current version of the prospective tenant notice form will be made available on the department’s website. (5) The owner must deliver the notices described in ORS 456.788 and this rule to tenants and prospective tenants and post onsite in a common area as prescribed in ORS 456.788.
OAR 813 § 813-115-0035 requires owners of publicly supported housing properties with Oregon Housing and Community Services (OHCS) restrictions to give written notice to both current tenants and prospective tenants when a property is being withdrawn from a program. For prospective tenants, this notice must be delivered before any screening fee is charged or a rental agreement is signed, and it must clearly state the earliest date that affordability restrictions could end. All required notices must follow forms prescribed by OHCS, which publishes the most current versions on its website, and must also be posted in a common area on the property.
Plain English — not legal advice.
Under OAR 813 § 813-115-0035, compliant operators of OHCS-restricted properties use the official OHCS-prescribed notice forms — available on the OHCS website — for all required disclosures to current and prospective tenants. When a property is being withdrawn from a program, owners deliver timely written notice to existing tenants and post the required notice in an onsite common area. For prospective tenants, operators provide the written affordability-restriction notice before collecting any screening fee or executing a rental agreement, ensuring the notice clearly identifies the earliest possible date restrictions could be terminated.
General guidance for property managers — not legal advice for your specific situation. Consult an attorney for advice on your case.
OAR 813 § 813-115-0035 gives prospective tenants the right to receive a written notice — on an OHCS-prescribed form — disclosing affordability restrictions and the earliest date those restrictions could end, and this notice must be provided before a landlord charges a screening fee or asks you to sign a rental agreement. Current tenants in OHCS-restricted properties are also entitled to written notice if the owner intends to withdraw the property from the program. Tenants who believe these notice requirements were not followed may contact Oregon Housing and Community Services directly, consult a local tenant-rights organization, or explore whether the omission can be raised as a defense in a relevant legal proceeding.
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