Or. Admin. Code § 660-012-0012 - Effective Dates and Transition
(1) The rules in this division adopted on
July 21, 2022, and amendments to rules in this division adopted on that date,
are effective August 17, 2022, except as provided in this rule.
(2) A city or county subject to the
requirements as provided in OAR
660-012-0100 may make interim
updates to the local transportation system plan using requirements as provided
in OAR 660-012-0015 if the city or
county:
(a) Has submitted notice of the
proposed change to the comprehensive plan to the department as provided in OAR
660-018-0020 no later than
December 31, 2022; or
(b) The
interim update is not a major transportation system plan update as provided in
OAR 660-012-0105, and the city or
county has submitted notice of the proposed change to the comprehensive plan to
the department as provided in OAR
660-018-0020 no later than June
30, 2027. Interim updates must comply with applicable requirements in this
division within the scope of the transportation system plan amendment but need
not bring the entire transportation system plan in compliance with all
applicable regulations.
(3) Cities, counties, or Metro may choose to
propose alternative dates in lieu of the effective dates or deadlines in
section (4) of this rule.
(a) A submitted
proposal for alternative dates shall include:
(A) A description of any work already
underway to begin complying with the new or amended requirements of this
division;
(B) Proposed dates for
accomplishing requirements in lieu of effective dates or deadlines provided in
this rule; and
(C) A schedule for
updating local transportation system plans to comply with new or amended
requirements of this division.
(b) Proposed alternative dates must
demonstrate consistent progress toward meeting the updated requirements of this
division. Proposed alternative dates must include completion of all elements
included in the alternative dates, except for a major update to the
transportation system plan, by December 31, 2029.
(c) Proposed alternative dates should be
designed to sequence work in a logical progression, considering acknowledged
plans, other work, and the work of other jurisdictions within the metropolitan
area. Cities and counties in a metropolitan area may submit joint proposed
alternative dates for a metropolitan area.
(d) Local governments in regions required to
submit a work program as provided in OAR
660-044-0015 may submit a single
combined work program that proposes alternative dates as provided in this rule
and meets the requirements as provided in OAR
660-044-0100.
(e) The director shall review the proposed
alternative dates to determine whether the proposed alternative dates meet the
following criteria:
(A) Ensures urgent
action;
(B) Coordinates actions
across jurisdictions within the metropolitan area;
(C) Coordinates with work required as
provided in OAR 660-044-0100;
(D) Sequences elements into a logical
progression; and
(E) Considers
availability of funding and other resources to complete the work.
(f) Upon the director finding the
proposed alternative dates meet the criteria in (f), the alternative dates
shall be used.
(g) The director may
modify alternative dates at any time as necessary to achieve the purposes of
this division.
(4) The
dates in this section apply unless alternative dates are approved by the
director as provided in section (3).
(a)
Cities outside the Portland Metropolitan Area with a population over 5,000 in
the urban area, and counties outside the Portland Metropolitan Area with an
unincorporated population over 5,000 in the urban area, must adopt a major
transportation system plan update as provided in OAR
660-012-0105 by December 31,
2029.
(b) The provisions of OAR
660-012-0215 requiring the
adoption of multiple transportation performance standards take effect upon the
adoption of a major update to the local transportation system plan.
(c) A city or county that is subject to the
requirements of OAR 660-012-0310 shall adopt land
use requirements for climate-friendly areas and a climate-friendly
comprehensive plan element as provided in OAR
660-012-0315 by December 31,
2024.
(d) Metro shall amend its
Urban Growth Management Functional Plan in conjunction with its next growth
management analysis under ORS
197.296 and no later than
December 31, 2024, to require each city and county within Metro to:
(A) By December 31, 2025, adopt boundaries
for all regional and town centers identified on Metro's 2040 Growth Concept map
for which the city or county has adopted urban land use designations in their
comprehensive plan, except for any portions of centers that have boundaries
adopted by another city or county;
(B) Adopt boundaries for any other regional
and town center identified on Metro's 2040 Growth Concept map when the city or
county adopts urban land use designations for the area of that center in their
comprehensive plan, unless portions of the center have boundaries already
adopted by another city or county; and
(C) Identify boundaries for regional and town
centers that are adopted pursuant to this subsection to be located in the
general area of the center as identified in the Metro 2040 Growth Concept
map.
(e) Cities and
counties shall adopt land use regulations to meet the requirements of OAR
660-012-0330 no later than the
date of adoption of a major transportation system plan update as provided in
OAR 660-012-0105.
(f) Cities and counties shall adopt
comprehensive plan amendments and land use regulations meeting requirements
provided in OAR 660-012-0400, OAR
660-012-0405, and OAR
660-012-0415 through OAR
660-012-0450 no later than June
30, 2023, except as provided below. If a city or county has not done so, it may
not enforce parking mandates after that date.
(A) Cities and counties that pass population
thresholds in OAR 660-012-0400, OAR
660-012-0415, or OAR
660-012-0450 must adopt
comprehensive plan amendments and land use regulations meeting requirements
within 12 months of passing those population thresholds.
(B) If cities and counties adopt an approach
in OAR 660-012-0445, policies must take
effect no later than June 30, 2023.
(C) Cities and counties adopting an approach
in OAR 660-012-0435 shall do so
concurrently with adoption of any climate-friendly area under OAR
660-012-0315.
(g) Cities choosing to report on
the share of on-street parking spaces that are priced as provided in OAR
660-012-0450(1)(b)
must:
(A) Demonstrate at least five percent of
on-street parking spaces are priced by September 30, 2023; and
(B) Demonstrate at least 10 percent of
on-street parking spaces are priced by September 30, 2025.
(5) The following dates and
provisions may not be adjusted through proposed alternative dates as provided
in section (3):
(a) The provisions of OAR
660-012-0210 take effect
December 31, 2027.
(b) A city or
county subject to the requirements of OAR
660-012-0310 shall submit a
study of climate-friendly areas as provided in OAR
660-012-0315(4) and
(5) by December 31, 2023.
(c) The provisions of OAR
660-012-0310(4)(a) and
(b) take effect June 30, 2023.
(d) Cities shall implement the requirements
for electric vehicle charging as provided in OAR
660-012-0410 no later than March
31, 2023.
(e) Cities and counties
shall implement the requirements of OAR
660-012-0430 and
660-012-0440 when reviewing
development applications submitted after December 31, 2022.
(f) The provisions of OAR
660-012-0350(1)(a)
take effect December 31, 2029.
(g)
The provisions of OAR
660-012-0830(2)(b)
take effect upon the adoption of a major
update to the local transportation system plan.
(6) Cities and counties with voter-approved
bond-funded projects where the election occurred before January 1, 2022 may use
approved bond funding as a factor when prioritizing projects in an
unconstrained project list as provided in OAR
660-012-0170(4).
(7) The first reporting year for the
reporting requirements provided in OAR
660-012-0900 is 2023, with
reports due no later than May 31, 2024.
Notes
Statutory/Other Authority: ORS 197.040
Statutes/Other Implemented: ORS 197.712, ORS 197.296 & ORS 455.417
State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.
No prior version found.