A landlord serving the same dollar amount of rent increase by mail on the morning of May 1, 2026 will see that increase become enforceable on different effective dates in every one of the ten RentCeiling jurisdictions. The earliest enforceable date is roughly June 1 in a Saint Paul month-to-month tenancy under Minnesota's payment-interval notice rule. The latest enforceable date is roughly October 1 — a full five months later — for a New York rent-stabilized tenant who used the full 60 days of acceptance time on a 90-day RTP-8 renewal-lease offer mailed at the outer edge of the 150-day offer window. Same notice, same rent increase, same calendar day. Different statute, different calendar.
This post is the deep-dive we promised back in the four-California-rent-caps head-to-head and on the blog index: the notice-period rule, statute-by-statute, for every one of the ten jurisdictions RentCeiling models. We will cover the four California jurisdictions that all share Cal. Civ. Code §827(b)'s 30-day-versus-90-day split (with one ordinance-specific layer per city); Oregon's universal 90-day rule under ORS §90.323(3); NYC's 90-to-150-day RTP-8 renewal-offer window under 9 NYCRR Part 2523; DC's post-2024 60-day rule under D.C. Code §42-3505.51 and the older RAD Form 8 mechanics; Saint Paul's payment-interval rule from Minnesota Statutes §504B.135; Montgomery County's 90-day rent-stabilized rule under Bill 15-23 (codified at Mont. Co. Code Ch. 29 Art. VII); and Washington State's 90-day Department of Commerce-form rule under RCW §59.18.140 and §59.20.090. We will close with the four mailing-add presumptions you have to layer on top of all of this — Cal. Code Civ. Proc. §1013's five-day add, ORS §90.155's three-day add, Maryland Real Property §8-208's three-day add, and the RCW §59.12.040 substituted-service add — because the bare statute number is almost never the actual calendar count you serve to.
Each section answers the same three questions in the same order, so you can skim straight to the jurisdiction that controls your unit: (1) which statute governs? (2) how many calendar days does it require? (3) what does the actual on-the-ground calendar look like once you layer the mailing-add presumption and the once-per-12-month rule?
1. The Cal. Civ. Code §827(b) floor — controls all four California jurisdictions
California Civil Code §827(b) is the statewide month-to-month rent-increase notice statute. It is older than AB 1482 by roughly two decades, it controls every covered tenancy in California regardless of whether AB 1482 or any local rent-control ordinance applies, and it sets the floor that the four covered California jurisdictions in our catalogue — the AB 1482 statewide regime, the LA RSO, San Francisco's Chapter 37 ordinance, and Berkeley's BMC 13.76 ordinance — all build on top of.
The structure is a single split, anchored on the percentage size of the increase relative to the lowest rent charged at any time during the prior 12 months:
- Increase under 10%. Cal. Civ. Code §827(b)(2)(A) requires 30 calendar days written notice.
- Increase of 10% or more. Cal. Civ. Code §827(b)(3) requires 90 calendar days written notice.
The two traps in §827(b)(3) that catch California landlords most often are the cumulative-trigger trap and the anchor-period trap. The cumulative-trigger says that the 10% threshold is measured against the lowest rent the tenant paid at any time during the prior 12 months, not the rent currently in force. So a landlord who already raised rent from $2,000 to $2,100 in March (5%) and then issues a second notice raising rent from $2,100 to $2,250 in November (about 7%) is delivering a cumulative increase of 12.5% on the $2,000 baseline — both notices needed 90 days, even though no single notice broke 10% on its own face. The anchor-period trap is the same point in reverse: a landlord who reduced rent from $2,200 to $2,000 in February as a retention concession and then tries to restore it to $2,200 in October is on a 10% increase from the prior-12-months low, and the notice needs 90 days, not 30. We walked the cumulative-trigger trap in detail at our deep-dive on the AB 1482 90-day rule; this post is the cross-jurisdictional companion piece, so we will cite the trap once here and move on.
California statewide (AB 1482) — the 30/90 split, layered onto the 8.8% cap
The AB 1482 statewide cap for 2026 is 8.8% — computed at Cal. Civ. Code §1947.12 as the lower of 10% or 5% plus the regional CPI-U change of 3.8%. Because 8.8% is below the §827(b)(3) 10% trigger, an AB 1482 increase served at the cap takes 30 days, not 90. A landlord who serves below the AB 1482 cap (which is most of them) is in 30-day land. The only realistic ways to land in 90-day territory under AB 1482 are (a) a unit that was previously discounted below market and is now being restored, where the cumulative rent change against the prior-12-months low crosses 10%, or (b) a unit that is exempt from AB 1482 (single-family corporately owned, building under 15 years old, deed-restricted, dorm, or owner-occupied SFR) and is therefore uncapped — in which case there is no 8.8% ceiling and the §827(b)(3) 10% trigger is the only thing that decides between 30 and 90 days. The free California draft-notice flow picks the right window automatically.
Los Angeles RSO — the 30/90 split, plus LAHD registration disclosure
The LA RSO 2026 cap is 3.0% through June 30, 2026, dropping to roughly 2.8% from July 1, 2026 onward under Ordinance No. 188558 (which switches the formula from a fixed 3-to-8% statutory band to a CPI-driven number capped at 4%). Both numbers are well below 10%, so an LA RSO covered increase served at the cap is squarely in §827(b)(2)(A) 30-day territory. The LAMC §151.06.01 ordinance layer adds a registration-status disclosure requirement (the unit must be registered with the LA Housing Department for the current registration year before any §151.06 increase is enforceable) and a LAHD-registration certificate attachment to the notice itself, but it does not extend the 30-day window. A landlord serving an LA RSO increase by mail on May 1, 2026 is looking at a notice received under the §1013 5-day mailing-add presumption around May 6 and an effective date around June 6 — assuming the unit is registered. If it is not, the registration cure has to land before the rent change becomes enforceable, regardless of what the calendar says.
San Francisco — the 30/90 split, plus the §4.12 banking ceiling
San Francisco's 2026 allowable annual increase under S.F. Admin. Code §37.3(a)(1) is 1.6% for Rent Year 2026-27 (the rate for the prior cycle, RY 2025-26, was 1.4%). Because 1.6% is the lowest allowable in our entire catalogue except Berkeley, the §827(b) floor virtually always lands a covered SF increase in 30-day territory. The one path to 90 days under SF's regime is via the SF Rent Board Rules §4.12 banking provision: a landlord who has accumulated unused increase capacity from prior Rent Years may stack the banked balance onto the current year's allowable, subject to a 7%-per-year and a 10%-per-notice ceiling. Stacking up to the 10%-per-notice ceiling is the only way to reach the §827(b)(3) 10% trigger from an SF cap base — and the moment that notice prints at exactly 10.0%, it has to be a 90-day notice, not a 30-day one. Most SF landlords will never see the 90-day window in practice, but the small minority who have banked aggressively across multiple low-AGA cycles can land there.
Berkeley — the 30/90 split, plus the rent-ceiling-accumulation banking model
Berkeley's 2026 Annual General Adjustment under BMC §13.76.110 and Rent Board Regulation 1271 is 1.0%, the lowest cap in the entire RentCeiling catalogue. Same statewide-floor rule applies: 1.0% is well under 10%, so a Berkeley AGA notice served at the cap is a 30-day notice. The path to a 90-day Berkeley notice is the same in shape as San Francisco's but mechanically different: Berkeley uses a rent-ceiling-accumulation model under §13.76.110(C) where unused capacity does not have a per-year or per-notice ceiling but is gated by the once-per-12-months rule and (for catch-up of more than the current AGA) by a Rent Board petition. A landlord who accumulates a multi-year unused-ceiling shortfall and serves the catch-up via the petition path can land at or above 10% and trip the §827(b)(3) 90-day window. We covered the AGA-denial gate and the rent-ceiling-accumulation mechanics in detail in the Berkeley 1.0% deep-dive; the notice-period takeaway is that §827(b) controls and the 30/90 split is decided by the size of the catch-up.
2. Oregon — ORS §90.323(3) requires 90 days for any increase, no exceptions
Oregon does not split its notice period by increase size. ORS §90.323(3), as amended by SB 611 in 2023 and currently codified at the same section, requires 90 calendar days written notice for any rent increase on a covered tenancy, regardless of whether the increase is 1% or 9.5% or anywhere in between. There is no California-style 30-day window. There is also no first-12-months exception — ORS §90.323(1) bars any rent increase whatsoever during the first 12 months of any tenancy, so the 90-day clock cannot start running until the tenancy crosses the one-year mark.
Layered on top of the bare 90-day count is ORS §90.155(1)(c), which presumes service by first-class mail to be effective three calendar days after deposit (not five, as in California). So an Oregon rent-increase notice mailed on the morning of May 1, 2026 is presumed served on May 4, and the earliest lawful effective date for the increase is roughly August 2 (May 4 + 90 days). The 2026 cap of 9.5% is the lower of 7% plus the West-Region CPI-U change (2.5%) or 10%; the cap question is decided at ORS §90.323(2), the notice question is decided at ORS §90.323(3). Two separate rules; both have to clear. The free Oregon draft-notice flow picks the right effective date automatically once you fill in the service method.
The penalty for a defective Oregon notice is severe: ORS §90.323(7) makes the landlord liable for three months' rent plus actual damages, plus reasonable attorney fees and costs — and the tenant can either sue affirmatively or raise it as a counterclaim in any subsequent eviction proceeding under ORS §90.392. Oregon also makes the just-cause linkage explicit: a defective notice breaks the just-cause posture for the duration of the dispute, which can unwind a later eviction filed for a wholly unrelated reason. We modeled this in the Oregon 2026 calculator deep-dive.
3. NYC rent-stabilized — the RTP-8 renewal-lease offer window: 90 to 150 days
NYC's rent-stabilized regime does not use a notice-period statute in the same shape as the California or Oregon model. Rent increases on stabilized units happen at lease renewal, not by notice on a month-to-month tenancy, so the controlling rule is the renewal-lease offer window codified at 9 NYCRR §2523.5(a) — the regulation that implements the New York State Rent Stabilization Code under the broader NYC Administrative Code §26-501 et seq. The offer window is:
- Earliest: 150 calendar days before the current lease expires.
- Latest: 90 calendar days before the current lease expires.
- Tenant acceptance window: 60 calendar days after the offer is served, during which the tenant chooses 1-year or 2-year renewal at the corresponding RGB rate.
The form is mandatory and statutorily prescribed: NY DHCR Form RTP-8, the Rent Stabilized Renewal Lease Form, with the current Rent Guidelines Board order number printed on the face. The 2026 form will cite RGB Order #57 (covering leases commencing October 1, 2025 through September 30, 2026 at 2.75% on a 1-year renewal and 5.25% on a 2-year renewal), with Order #58 expected to refresh the form in June or July 2026 and govern the next cycle. We modeled the full RTP-8 mechanics in the NYC rent-stabilization renewal 2026 deep-dive.
The practical calendar matters because of the 60-day tenant-acceptance window: a landlord who serves the RTP-8 at the outer edge of the offer window (150 days before lease expiration) and a tenant who uses the full 60 days of acceptance is looking at a 90-day gap between acceptance and the new lease commencement — functionally identical in time-on-the-clock to a California 90-day notice. A landlord who serves at the inner edge of the offer window (90 days before lease expiration) and a tenant who returns the form the next day is functionally identical in time-on-the-clock to a 90-day notice with same-day acceptance. The 60-day acceptance window is the tenant's option to lock in the lower 1-year rate without committing to two years up front; it is also the source of most NYC landlord-tenant disputes about whether a renewal was timely refused or constructively accepted.
Failure to serve the RTP-8 in the window itself does not waive the right to a renewal — the tenant retains the right to a renewal lease at the prevailing RGB rate even if the landlord misses the window — but it does shift the economic posture: a tenant in a unit where the RTP-8 was never served can hold the prior rent indefinitely until a proper offer arrives, and DHCR's administrative remedy at NYC Admin. Code §26-516 (rent overcharge) reaches back six years under the 2019 HSTPA amendment as interpreted by Regina Metropolitan Co. v. NYS Division of Housing and Community Renewal, 35 N.Y.3d 332 (2020).
4. Washington DC — D.C. Code §42-3505.51's post-2024 60-day rule and Form 8 content
DC operates two parallel notice systems, one statutory and one regulatory. The Rental Housing Act of 1985 sets the rent-adjustment ceiling at D.C. Official Code §42-3502.08 (the source of the 2026 RY caps of 4.1% standard / 2.1% elderly-or-disabled that took effect on May 1, 2026, today's effective date for any RY 2026 first increase). The notice-of-rent-adjustment requirement, since the 2024 Rental Housing Adjustment Reform Amendment Act, lives at D.C. Code §42-3505.51, which requires 60 calendar days written notice for any rent adjustment served on or after January 1, 2024.
Underlying the bare 60-day count is the regulatory RAD Form 8 (Notice to Tenant of Adjustment in Rent Charged), the DC Office of the Tenant Advocate's prescribed form. Form 8 controls notice content, not the calendar count: it requires the tenant's name, the unit address, the current rent, the proposed new rent, the effective date, the controlling rent-control year cap percentage, the RAD-registration number for the housing accommodation, the elderly/disability tier election (if applicable), and signature lines with date of service. A 60-day notice that lacks any of these content elements is defective on its face and the rent change is not enforceable until a corrected notice has been served and another 60 days have run from re-service.
DC also imposes the once-per-12-months rule at D.C. Official Code §42-3502.08(g)(1) — no unit may be increased more than once in any rolling 12-month period, regardless of tenant turnover. This is functionally identical to California's, San Francisco's, Oregon's, LA RSO's, Berkeley's, Montgomery County's, Saint Paul's, and Washington State's once-per-12-months rules; the only jurisdiction in our catalogue without a clean once-per-12-months bar is NYC, where the rule is expressed instead as a one-renewal-per-lease-cycle constraint. The penalty cascade for a DC defective notice is the steepest in our catalogue: D.C. Code §42-3509.01 authorizes treble damages on willful overcharges, building-wide audit risk for systemic errors, and Office of Administrative Hearings adjudication of tenant petitions. We modeled the full DC mechanics in the DC rent control increase 2026 deep-dive — particularly relevant today because RY 2026 begins on May 1, 2026, the same day this post is published.
5. Saint Paul — Minnesota Statutes §504B.135's payment-interval rule
Saint Paul's local rent-stabilization ordinance at Saint Paul Legislative Code Chapter 193A (as amended in May 2025) sets the cap — 3.0% standard, up to 8.0% with capital-improvement banking, and up to 15.0% on a qualifying just-cause vacancy reset — but Chapter 193A does not contain its own notice-period statute. The notice-period rule comes from the Minnesota statewide landlord-tenant code at Minnesota Statutes §504B.135, which governs notice to terminate and notice of change of terms (including rent) in periodic tenancies.
The §504B.135 rule is intentionally simple: the notice period equals one rent-payment interval. For a typical month-to-month tenancy, that is one full calendar month — service on April 1 makes the rent change effective on June 1 (one full payment interval after the next-occurring rent due date). For a fixed-term lease, the rent change cannot take effect until the lease term ends and a renewal commences; the notice has to be served before the lease's renewal-notice deadline, which the lease itself usually sets at 30 to 60 days before expiration. The Saint Paul-specific overlay is the once-per-12-months rule at Saint Paul Legislative Code §193A.04(a) — same shape as the bars in DC, California, Oregon, LA RSO, and SF.
One Saint Paul-specific quirk worth noting: the May 2025 ordinance amendment introduced partial vacancy decontrol at §193A.04(c), which lets a landlord reset the rent for the next tenant by up to 8% plus the published 12-month CPI-U change for the Minneapolis-St. Paul MSA — but only on a just-cause vacancy. A no-fault vacancy (retaliatory eviction, harassment, constructive eviction) does not qualify, and the cap remains 3% even on the new tenancy. The notice-period rule does not change with the vacancy-reset path, because the new tenancy is a new lease, not a notice on the existing tenancy — the lease itself sets the new rent at execution.
6. Montgomery County MD — Bill 15-23's 90-day stabilized rule preempts the Maryland Real Property baseline
Montgomery County's HOME Act (Bill 15-23, codified at Montgomery County Code Ch. 29 Art. VII) requires 90 calendar days written notice for any rent increase on a rent-stabilized unit, regardless of the size of the increase. The county-specific 90-day rule preempts the Maryland statewide baseline at Maryland Real Property Article §8-208 (which would otherwise require only 60 days for a month-to-month rent increase). A landlord serving an FY 2026 5.8% increase — the current VRGA cap under §29-53 — on a covered Montgomery County unit needs the full 90-day calendar, not 60. The Maryland Real Property §8-208 service rules still apply to the manner of service: hand delivery, certified mail with return receipt, or first-class mail with the §8-208 three-day mailing-add presumption.
Two Montgomery County exceptions to keep in mind: (1) rent-stabilized status under Bill 15-23 carves out four categories — buildings whose first certificate of occupancy was issued less than 23 years ago (rolling), subsidized housing covered by federal or state rent-setting rules, owner-occupied accessory dwelling units, and rentals of less than 30 days' duration. A unit in any of these categories falls back to the Maryland Real Property §8-208 60-day baseline (or shorter, depending on the lease terms). And (2) the once-per-12-months rule at Mont. Co. Code §29-53(c) closes the cumulative loophole — a landlord who might otherwise serve two 60-day notices six months apart is bound to a single 90-day notice per 12-month period. The penalty cascade is at §29-58 (unenforceability) and §29-59 (civil penalties up to $1,000 per violation). We modeled the full mechanics in the Montgomery County 2026 deep-dive.
7. Washington State — RCW §59.18.140 + §59.20.090's 90-day Department of Commerce-form rule
Washington State's HB 1217 (2025), codified at RCW §§59.18.700-770 (residential) and RCW §59.20.120 (manufactured/mobile-home parks), set the statewide caps at 9.683% for residential tenancies and 5.0% for manufactured-housing tenancies for 2026. The notice-period rule is at RCW §59.18.140 for residential and RCW §59.20.090 for manufactured-housing — both require 90 calendar days written notice on the prescribed Department of Commerce form, regardless of increase size.
The Department of Commerce form is the analog of DC's RAD Form 8 and NYC's RTP-8 — it is mandatory, prescribed by the agency, and a notice that omits any required content is defective on its face. The form requires landlord and tenant names, the unit address, the current rent, the proposed new rent, the effective date, the controlling RCW citation, and a signature with date of service. Service is per RCW §59.12.040, which permits personal service, substituted service, or posting and mailing — and posting-and-mailing adds a service-completion presumption that effectively shifts the receipt date forward, lengthening the calendar.
Two Washington State quirks worth noting. First, the first-12-months protection at RCW §59.18.700(1) bars any rent increase whatsoever during the first 12 months of any new tenancy — identical in shape to Oregon's ORS §90.323(1) first-year rule. Second, the new-construction exemption is a 12-year rolling window (a building loses its exemption 12 years after its first certificate of occupancy), shorter than California's and Oregon's 15-year windows and Montgomery County's 23-year window. The penalty cascade for a defective Washington notice is at RCW §59.18.700(8) — the tenant may recover the overcharge, three months' rent in damages, plus reasonable attorney fees and costs.
8. The four mailing-add presumptions you have to layer on top
The bare statutory notice-period count almost never matches the actual on-the-ground calendar, because every state in our catalogue has a service-by-mail presumption that adds a few days to the receipt date. These are the four:
- California — Cal. Code Civ. Proc. §1013: service by first-class mail is complete on deposit, but the notice period is extended by 5 calendar days. So a 30-day notice mailed becomes a 35-day notice for effective-date math; a 90-day notice mailed becomes a 95-day notice. Hand delivery or substituted service per Cal. Civ. Code §1162 does not get the 5-day extension. This rule controls all four California jurisdictions: AB 1482 statewide, LA RSO, San Francisco, Berkeley.
- Oregon — ORS §90.155(1)(c): service by first-class mail to the premises is presumed effective on the third day after deposit. So a 90-day notice mailed becomes a 93-day notice for effective-date math (the receipt date moves forward, the 90-day count starts on the presumed receipt date).
- Maryland — Maryland Real Property §8-208 (and the Maryland Rules of civil procedure): service by first-class mail carries a three-day mailing-add presumption, mirroring Oregon's structure. This rule controls Montgomery County in any case where the 90-day Bill 15-23 rule does not preempt it (i.e., on units carved out of rent stabilization, where the §8-208 60-day baseline applies and gets the three-day mail add).
- Washington State — RCW §59.12.040: service by posting and mailing (the most common method for absentee landlords) is effective when the posting-and-mailing is complete; the practical effect is a small forward shift of the receipt date. Personal service has no add. The 90-day count starts on the presumed receipt date.
DC and Saint Paul do not impose a mailing-add presumption on the rent-adjustment notice itself; in DC the Form 8 is filed and served per RAD's regulations and the 60-day count runs from the date of service rather than the date of receipt, and in Saint Paul the one-payment-interval rule under Minn. Stat. §504B.135 measures from the next rent due date after service. NYC similarly does not impose a mailing-add on the RTP-8 because the renewal-offer window is anchored to the lease-expiration date, not the service date.
9. The practical sequence: how to figure out the right notice-period for your unit in 90 seconds
Across the ten jurisdictions, the right way to read the notice-period question is (a) which jurisdiction's statute governs?, then (b) does that statute have a single uniform window or a split?, then (c) if it's a split, which side am I on?, then (d) what mailing-add adds calendar days on top? A practical sequence for any landlord:
- Identify the unit's controlling jurisdiction. Use the all-ten compare page or the homepage calculator; enter the unit's state, city, and building-age, and the calculator returns the controlling rent-control regime.
- Look up the notice-period rule. Each jurisdiction's per-jurisdiction page lists the controlling notice-period statute and the calendar count: California, LA RSO, San Francisco, Berkeley, Oregon, New York, DC, Saint Paul, Montgomery County, Washington State.
- If the rule is a split, compare the new rent to the prior-12-months baseline. Only the four California jurisdictions have a split (30/90 under §827(b)). Take the lowest rent the tenant paid at any time in the prior 12 months and divide the proposed increase by it. Above 10%, you need 90 days. At or under 10%, you need 30 days. If you are in cumulative-trigger territory because of a recent prior increase, recompute against the original baseline and treat the cumulative number as the trigger.
- Layer the mailing-add. If service is by mail, add the state-specific mailing-add: 5 days in California, 3 days in Oregon and Maryland, the posting-and-mailing presumption in Washington State. Hand-delivery and substituted service typically do not get the mailing add (check the specific service rules for your jurisdiction).
- Confirm the once-per-12-months rule has cleared. Every jurisdiction in our catalogue except NYC bars more than one rent increase in any rolling 12-month period. If the unit had a prior increase within the past 12 months, the new notice is not enforceable until 12 months after the prior effective date.
- Generate the right notice form. The form is mandatory in NYC (RTP-8), DC (RAD Form 8), and Washington State (Department of Commerce form); it is content-mandatory but format-flexible everywhere else. Use the per-jurisdiction draft-notice flow to generate the correct form: California, LA RSO, San Francisco, Berkeley, Oregon, New York, DC, Saint Paul, Montgomery County, Washington State.
10. Why getting this wrong is expensive: the four overcharge regimes
The cost of a defective notice is jurisdiction-specific, and the spread is wide. We covered each penalty regime in its respective per-jurisdiction page; the cross-cutting summary is:
- California (all four jurisdictions): Cal. Civ. Code §1947.12(h)(2) makes an over-cap notice void as to the increase — the tenant continues to pay the prior rent and any overpayment must be refunded; §1947.12(h)(3) authorizes treble damages plus attorney fees on willful overcharges; the unit may also lose its just-cause protection under Cal. Civ. Code §1946.2 for the dispute period.
- Oregon: ORS §90.323(7) makes the landlord liable for three months' rent plus actual damages plus reasonable attorney fees and costs — and the just-cause linkage at ORS §90.392 makes the defective notice a defense to any subsequent eviction action, regardless of the eviction's stated grounds.
- NYC: NYC Admin. Code §26-516 authorizes overcharge claims with treble damages and a six-year HSTPA-2019 lookback as interpreted by Regina Metropolitan; the tenant can file with DHCR or in Supreme Court (Civil Court for individual unit claims).
- DC: D.C. Code §42-3509.01 authorizes treble damages on willful overcharges plus building-wide audit risk; the Office of the Tenant Advocate routinely files multi-tenant audits when one defective notice surfaces in a building.
- Saint Paul: Saint Paul Legislative Code Chapter 193A authorizes refund of the overcharge plus a civil penalty; DSI's enforcement office adjudicates tenant petitions.
- Montgomery County: Mont. Co. Code §29-58 makes the over-cap rent unenforceable; §29-59 authorizes civil penalties up to $1,000 per violation; the Office of Landlord-Tenant Affairs (OLTA) handles enforcement and has subpoena power.
- Washington State: RCW §59.18.700(8) authorizes recovery of the overcharge, three months' rent in damages, plus reasonable attorney fees and costs — modeled on Oregon's ORS §90.323(7) penalty.
Notice-period defects fall under the same penalty regimes as overcharge defects in every jurisdiction in our catalogue: a notice served with insufficient days is treated as no notice at all, and the rent change does not become enforceable until a corrected notice has been served and the full statutory window has run again. The economic cost is not the small extra calendar days — it is the re-service-and-re-run-the-clock cost compounded across the unit's full annual increase cycle, plus (in California, Oregon, NYC, DC, and Washington State) the potential for treble damages and attorney fees.
Footnote on scope and cite-staleness
This post discusses the notice-period rule for the ten jurisdictions RentCeiling currently models. We do not cover Oakland, Santa Monica, West Hollywood, or any New Jersey, Massachusetts, or other state and local rent-stabilization regimes here — those are on the per-jurisdiction roadmap and will receive their own deep-dives as they roll into the catalogue. Statute citations are accurate as of the post's published date (April 30, 2026); the Maryland Real Property Article, the Minnesota Statutes, the Washington Revised Code, the Oregon Revised Statutes, and the New York Codes, Rules, and Regulations all see periodic legislative refresh, and the California Code of Civil Procedure §1013 and Civil Code §827(b) are unusually stable in shape but their interpretation continues to evolve through case law. Always check the controlling rent board or housing-services agency's most recent guidance before serving a notice in any single dispute, and call a landlord-tenant attorney in the relevant jurisdiction for any edge case the calculator does not cleanly resolve.
This post is the third long-form entry in the RentCeiling blog. The next planned post in the queue covers the rolling first-certificate-of-occupancy exemption that exists in four of the ten jurisdictions we model (California's 15-year, Oregon's 15-year, Montgomery County's 23-year, Washington State's 12-year) and the practical mechanics for landlords whose buildings are about to lose their exemption. After that we expect to publish a head-to-head comparison of Oakland's CPI-of-CPI formula at OMC §8.22 and Santa Monica's charter-based regime at SM Charter Article XVIII — the two most-frequently-asked-about California jurisdictions outside our current ten.