What We See at AEBP

We’ve managed Berkeley rentals since 2005, and we treat every Berkeley tenancy — brand-new or decades old — the same way from a compliance standpoint: covered from the day the lease starts, with no internal “grace period” built into how we draft or review termination notices. That’s a company-wide practice, not a workaround for a specific case — Berkeley’s ordinance doesn’t give a new tenancy a pass, so neither do we.

Berkeley’s just-cause clock starts at move-in — there’s no waiting period to plan around.

What to Confirm Before You End a Berkeley Tenancy

1. Treat every Berkeley tenancy as just-cause-protected starting on day one. Never assume a new tenancy gives you extra room to act without cause.
2. Confirm which ground applies under BMC 13.76.130 before drafting anything. Tenancy length isn’t a substitute for cause.
3. If it’s a no-fault termination (Owner Move-In or Ellis Act), budget for Berkeley’s 2026 relocation payment. $19,413 standard, plus $6,471 for qualifying households.
4. Don’t confuse Berkeley’s local ordinance with AB 1482’s separate 12-month statewide rule. That backstop only applies to a Berkeley unit the local ordinance doesn’t cover at all — a narrow exception, not the general rule.

💡 This Week’s Takeaway

Berkeley’s just-cause protection isn’t something that phases in. It’s baseline from the day a tenancy starts — treating a new tenant as unprotected for their first year is one of the fastest ways to turn a routine notice into a legal problem.

📘 Learn More

This is one piece of the full Berkeley breakdown in this week’s cornerstone guide:

→ Berkeley Rent Control Compliance Guide 2026: AGA, Registration & Just Cause — the full guide this tip is drawn from
→ Property Management in Berkeley — how we handle Berkeley compliance day to day

Berkeley’s 1.0% AGA — and Why the Calendar Matters More Than the Rate

Berkeley’s Annual General Adjustment for 2026 is 1.0%, set by the Rent Stabilization Board using 65% of the CPI change for the San Francisco-Oakland-San Jose region over a July 2024–June 2025 lookback window. Berkeley’s rent ceilings adjust by this amount each January 1 — a calendar-year cycle that doesn’t match Oakland’s or AB 1482’s August 1–July 31 cycle, and the mismatch creates an easy scheduling trap for owners managing units in more than one East Bay jurisdiction. Owners shouldn’t treat August 1 as Berkeley’s reset date: the AGA itself resets January 1, though an eligible landlord may still implement an allowable increase later in the year with proper notice.

The 1.0% figure isn’t the whole rule, either. In November 2024, Berkeley voters passed Measure BB, which lowered the AGA’s maximum from 7% to 5%, tightened several just-cause and nonpayment-eviction rules, and expanded registration requirements to more government-subsidized units. Measure BB didn’t set the 1.0% rate itself — the Rent Stabilization Board calculates that separately, every year — but it changed the ceiling the rate operates under.

That 5% ceiling has one exception worth knowing: banking. Banked (deferred) AGAs from prior years can still push an owner’s actual increase above 5% in a given year, up to the unit’s lawful rent ceiling — so a banked-increase calculation isn’t automatically capped at 5% the way a single year’s fresh AGA is.

The New-Tenancy Delay Nobody Warns You About

A brand-new Berkeley tenancy doesn’t just wait out the standard notice period before its first AGA increase — it’s locked out of the AGA entirely for the rest of the calendar year it started, plus one full additional calendar year. A tenancy that begins March 1, 2026 gets no AGA increase for the remainder of 2026 or in 2027; the earliest AGA increase available is in 2028. That’s close to two full years of AGA-ineligibility from a single move-in date, and it’s the longest new-tenancy delay of any city AEBP manages a property in — longer than Oakland’s 12-month delay or Richmond’s next-September-1 rule.

The delay runs from the tenancy’s actual start date, not the lease type and not any later conversion date. A tenancy that begins on a fixed-term lease and later converts to month-to-month under Civil Code §1945 still has its AGA clock keyed to the original move-in date — the conversion doesn’t reset it. Owners coming from a market with no such rule (or from Oakland’s shorter 12-month version) are the ones most likely to try an increase too early.

Registration Isn’t One Deadline — It’s Three

Berkeley Rent Board registration gets described as “ongoing” often enough that owners assume there’s no real deadline attached to it. There is — several, in fact, depending on what triggered the filing:

• Annual registration fee. This one has a fixed, penalized due date. FY 2026–27 fees were due July 2, 2026, and Berkeley’s ordinance imposes a full 100% penalty on any payment not received or postmarked by that date. Check the current year’s Rent Board notice for whether a penalty-waiver window is open that year — it isn’t standing policy every cycle.
• New-tenancy registration. Owners must update tenancy information with the Rent Board within 15 days of a new tenancy starting. This is a rolling, per-tenancy requirement, separate from the annual fee above. For tenancies beginning on or after December 20, 2024, landlords must also give the tenant written notice within that same 15-day window — not a second copy of the city paperwork, but a disclosure telling the tenant where they stand: that the Rent Ordinance exists and applies, whether the unit is exempt (fully covered, partially covered, or exempt) and any partial exemptions, and the tenant’s right to petition against certain rent increases if applicable. The Rent Board publishes a template (“Notice of Tenant Rights”) landlords can use rather than drafting their own language.
• Exemption status-change registration. If a unit’s coverage status changes — for example, from exempt to non-exempt — it must be registered within 60 days of the change.

Treating “registration” as a single, open-ended task is exactly how the annual fee deadline gets missed — the update-anytime provision that applies to keeping contact and manager information current is real, but it isn’t the same thing as the fee deadline, and confusing the two is the mistake that actually costs money.

Just Cause Applies From Day One — Not After 12 Months

A version of Berkeley’s just-cause rule keeps circulating that’s simply wrong: that eviction protection kicks in only after 12 months of continuous occupancy, “under Measure MM.” We checked the actual ordinance text — BMC 13.76.130 — directly. It has no blanket occupancy minimum before just-cause protection applies.

A handful of specific enhanced protections inside that same section do carry their own residency thresholds — additional relocation assistance where a household member has lived there a year or more, and stronger protections for families with minor children (12 months) or seniors, disabled tenants, and tenants in larger portfolios (5 years). Those are add-on safeguards layered on top of baseline just cause, though, not a condition on whether just cause applies at all.

The 12-month figure that keeps getting attached to Berkeley is most likely a mix-up with AB 1482’s own statewide 12-month just-cause backstop, which would only be relevant for a Berkeley unit not covered by the local ordinance at all — a narrow edge case, not the general rule. It’s also a mix-up of two different Berkeley ballot measures with similar names: Measure MM (passed November 2020) is about registration requirements for partially-covered units and reclassifying pandemic-era back rent as consumer debt — it has nothing to do with eviction timing. Measure BB (passed November 2024, discussed above) is the one that actually touched just-cause rules, and even it didn’t add a waiting period.

Bottom line: Berkeley’s local just-cause ordinance applies from day one of a covered tenancy, the same as Oakland’s and Richmond’s local ordinances. If a specific unit’s coverage category is in question — fully covered, partially covered, or exempt — that’s a coverage question, not a timing question, and it’s where Berkeley’s real nuance actually lives.

No-Fault Terminations: Relocation Isn’t AB 1482’s Flat Rate

Where no local ordinance applies, AB 1482 requires relocation assistance equal to one month’s rent (or an equivalent rent waiver) for a no-fault termination. Berkeley doesn’t default to that figure — it sets its own, substantially larger amount under its own eviction-relocation ordinance, which applies to Owner Move-In and Ellis Act evictions. Effective January 1, 2026: a standard payment of $19,413, plus an additional $6,471 for qualifying households — low-income, disabled, or elderly tenants, households with minor children, or a tenancy that began before January 1, 1999 (confirm current criteria against the Rent Board’s own notice before applying it to a specific tenant). This is Berkeley’s eviction-relocation figure specifically; it’s separate from Berkeley’s temporary-displacement relocation program for code-required repairs, which is a different requirement entirely and shouldn’t be cited from the same figure.

DIY vs. AEBP-Managed: Berkeley Compliance Side by Side

Requirement	Handling It Yourself	With AEBP
AGA calculation & notice timing	Track the calendar-year cycle separately from any Oakland/Richmond units you also own, and confirm each unit’s new-tenancy delay before issuing a notice	Calculated and served on the correct calendar, per unit, automatically
Rent Board registration (3 deadlines)	Track the annual fee, the 15-day new-tenancy window, and the 60-day status-change window separately, with no single reminder system	All three deadlines tracked and filed as part of standard portfolio management
Security deposit interest	Calculate the current rate, pay by January 31, and manage the check-escheatment risk yourself	Calculated, delivered as a rent-ledger credit, and reconciled — no outstanding checks
Just-cause documentation	Confirm coverage and grounds yourself before serving any notice, with no local track record to check assumptions against	Paperwork, Rent Board coordination, and legal referral when a case needs it
Relocation assistance (no-fault)	Confirm the current year’s dollar figures and qualifying-household criteria before calculating a payment	Current figures applied correctly, verified against the Rent Board’s own current-year notice

Before You Raise the Rent on a Berkeley Unit

Run through this before serving any AGA increase notice:

• Confirm the unit is fully covered by Berkeley’s Rent Ordinance, not partially covered or exempt.
• Confirm the tenancy has cleared Berkeley’s new-tenancy delay (rest of the start year, plus one full additional calendar year).
• Check the unit’s current lawful rent ceiling and whether any banked AGAs from prior years apply.
• Confirm the annual Rent Board registration fee is paid and current for the fiscal year.
• Confirm there’s no open Rent Board order, unresolved habitability violation, or unpaid security deposit interest that could block the increase.
• Check whether a fixed-term lease’s terms permit the increase before its end date.
• Serve the increase with the correct written notice period (30 days for increases of 10% or less, 90 days for larger increases).

Sources

• Berkeley 2026 AGA, 1.0% — Required by local ordinance. Berkeley Rent Board — 2026 AGA Published
• Measure BB (Nov 2024) — Required by local ordinance. Measure BB Changes to Berkeley’s Rent Ordinance
• New-tenancy AGA delay — Required by local ordinance. Berkeley Rent Board — Annual General Adjustment
• Registration fee deadline & penalty — Required by local ordinance. Berkeley Rent Board — Registration Fees, FY 2026–2027
• New-tenancy & status-change registration windows — Required by local ordinance. Berkeley Rent Board — Partially Covered Unit Registration
• Just cause, no waiting period — Required by local ordinance. Confirmed directly against BMC 13.76.130, corroborated by Berkeley Rent Board — Just Cause & Other Local Requirements
• No-fault relocation payments, effective Jan 1, 2026 — Required by local ordinance. Berkeley Rent Board — 2026 Adjustments of Relocation Assistance Payments
• Security deposit interest (Nov 1–Oct 31 interest year, December payment, Jan 31 legal deadline, 10% penalty) — Required by local ordinance. Berkeley Rent Board — Security Deposit Interest & Calculator; Berkeley Rent Board — 2026 AGA Published and 2025 Security Deposit Interest Payment Due Soon
• AEBP’s security-deposit-interest ledger-credit practice — AEBP documented experience / company policy. Confirmed by Brian; see knowledge/company/anecdote-log.md, entry dated 2026-08-26.
• AB 1482 statewide relocation baseline — Required by law. Civil Code §1946.2

What We See at AEBP

We’ve been headquartered in Emeryville since 2005, and license renewal sits on our own compliance calendar for exactly this reason — not because a rent board requires it, since Emeryville doesn’t have one, but because it’s the one document standing between a routine termination and one that legally can’t be served. We track it the same way we track registration deadlines in cities that do have a rent board: on a calendar, ahead of when it’s needed, not looked up for the first time after a notice is already drafted.

In Emeryville, a lapsed business license doesn’t just risk a fine — it removes your ability to legally end a tenancy at all.

What to Check Before You Send a Notice in Emeryville

1. Confirm your business license is current — before you draft anything. Not after you’ve already written the notice.
2. Don’t treat “no rent control” as “no local rules.” Emeryville’s ordinance still requires a qualifying just cause and a tenant rights notice, license or no license.
3. Renewal isn’t instant. Check license status well before you plan to act, not on the day you need it.
4. File a copy of the termination notice with the City Clerk within 10 days. A separate filing requirement from the license itself.
5. Confirm relocation payments if the termination is no-fault. The amount scales by how many units you own — larger owners owe more.

💡 This Week’s Takeaway

No rent cap doesn’t mean no rules. In Emeryville, your business license is the gatekeeping document for every termination you might ever need to file — confirm it’s current before you need it, not after.

📘 Learn More

This is one piece of the full jurisdiction-by-jurisdiction breakdown in this week’s cornerstone guide:

→ East Bay Rent Control 2026: Oakland vs. Berkeley vs. Richmond vs. Emeryville — Side by Side — the full guide this tip is drawn from
→ Property Management in Emeryville — how we handle compliance for owners in our own home city
→ Ending a Month-to-Month Tenancy in California — notice rules, just cause, and where Emeryville’s ordinance fits in

Why East Bay Rent Control Is a Patchwork — and Why That Matters

There is no single “East Bay rent control law.” AB 1482 (the statewide Tenant Protection Act) sets a statewide baseline for the units it covers — it is not a blanket rule for every rental in California, since it carries its own exemptions (certain single-family homes, newer construction, and more). Oakland, Berkeley, and Richmond each layer a stricter local ordinance on top of that baseline for units their ordinance covers, and each of those three ordinances was written by a different city council or ballot initiative, on a different timeline, with different mechanics. Emeryville never adopted a local rent-control ordinance at all, so AB 1482 governs the rate directly for units it covers there — but Emeryville does have its own separate landlord-tenant ordinance covering eviction and notice rules, which is a different thing from a rent cap and easy to conflate.

The result is a real patchwork, not four flavors of the same rule: different rates, different fiscal-year calendars, different registration systems, and — this is the one that catches even experienced owners — different rules for when just-cause eviction protection actually starts.

Side-by-Side: Rate, Registration & Just Cause

	AB 1482 (statewide formula)	Oakland RAP	Berkeley AGA	Richmond AGA	Emeryville
2026–27 rate	8.8%	2.3%	1.0%	1.5%	No local cap; AB 1482’s 8.8% applies to covered units
Cycle	Aug 1 – Jul 31	Aug 1 – Jul 31	Calendar year	Sept 1 – Aug 31	Aug 1 – Jul 31
Registration	None (statewide law, no local registry)	Annual, due March 1 via the city’s Rent Registry	Annual registration/fees; FY 2026–27 fees were due July 2, 2026 (100% penalty on late payment). New tenancies must be registered with the Rent Board within 15 days.	Property Enrollment once per property, plus Tenancy Registration filed for each individual tenancy — not an annual renewal	No rent registry; a valid residential landlord business license is required to terminate a tenancy
Just cause for covered units	12 months’ continuous occupancy required before protection applies	No AB-1482-style 12-month waiting period identified in Oakland’s local ordinance for covered units	Applies from day one of a covered tenancy — no waiting period under BMC 13.76, confirmed directly against the ordinance text	No AB-1482-style 12-month waiting period identified in Richmond’s local ordinance for covered units	Its own ordinance’s just-cause list applies (with unusual grounds like a landlord returning from sabbatical or military deployment)
Local quirk	Statewide baseline for covered units; a stricter applicable local rent cap generally controls the allowable increase	New tenancies also can’t take their first rent increase until 12 months after move-in — a separate rule from just cause, easy to conflate with it	AGA capped at 5% by 2024’s Measure BB, which also tightened just-cause and nonpayment-eviction rules (banked AGAs can still push an actual increase above 5%, up to the lawful rent ceiling)	Banked increases use an additive formula (current AGA + up to 5 points of deferred AGAs) — not Oakland’s multiplier	Relocation payments scale by landlord size: greater of one month’s fair market rent or one month’s rent for owners of 4 units or fewer; greater of five months’ fair market rent or four months’ rent for larger owners

A note on the Berkeley just-cause cell above: an earlier version of this page (and of our Berkeley property management page) attributed a 12-month waiting period to “Measure MM.” We checked the actual ordinance text (BMC 13.76.130) directly — it has no blanket occupancy minimum before just-cause protection applies. A few specific enhanced protections within it (extra relocation assistance, protections for families with minor children or for seniors/disabled tenants) do carry their own 1–5 year residency thresholds, but those are add-on safeguards, not a condition on baseline just-cause eligibility. Measure MM (2020) is about registration for partially-covered units and reclassifying pandemic-era back rent, not eviction timing. Both pages have been corrected accordingly.

Oakland: The Established Model — But Not the Template for the Others

Oakland’s Rent Adjustment Program (RAP) is the East Bay’s longest-running local system, and it’s what most owners picture when they hear “East Bay rent control.” The 2.3% AGA applies August 1, 2026 through July 31, 2027, and registration renews annually by March 1. We found no AB-1482-style 12-month waiting period for just-cause protection itself in Oakland’s own ordinance materials — but the first rent increase on a new tenancy can’t take effect until 12 months after the tenant’s actual move-in date, a separate rule that’s easy to confuse with the just-cause timing question, and worth confirming directly with the Rent Adjustment Program for a specific unit. For the full ground list and notice mechanics, see our Oakland Rent Control guide and Oakland Just Cause Eviction guide.

Berkeley: The Most Layered System, After Measure BB

Berkeley runs on a calendar-year AGA cycle (not Oakland’s August–July window), which is the single most common scheduling mistake we see from owners who manage in both cities. The 1.0% rate has been in effect since January 1, 2026, but Berkeley’s own framework changed underneath that rate in November 2024, when voters passed Measure BB. Measure BB didn’t set the 1.0% figure — the Rent Stabilization Board did that separately — but it capped the AGA at 5% going forward (there was previously no statutory ceiling; banked AGAs can still push an actual increase above 5%, up to the lawful rent ceiling), tightened several just-cause and nonpayment-eviction rules, and expanded registration requirements to more government-subsidized units. Registration itself runs on a firm annual calendar, not an open-ended cycle: FY 2026–27 registration fees were due July 2, 2026, with a 100% penalty for late payment, and any new tenancy must be registered with the Rent Board within 15 days of move-in. A brand-new Berkeley tenancy also can’t see its first AGA increase until the rest of the year it started, plus one full additional calendar year — the longest new-tenancy delay of any city in AEBP’s territory. Full detail is coming in next week’s Berkeley deep dive; in the meantime, our Berkeley property management page covers the current compliance calendar.

Richmond: Easy to Underestimate, Increasingly Not

Richmond’s 1.5% AGA (down from 1.62% the prior cycle) takes effect September 1, 2026 — the day after this post publishes, which makes it the one rate on this page that’s about to change rather than one that already has. Richmond is also the city where registration mechanics differ most from what an Oakland- or Berkeley-trained owner expects: instead of an annual renewal, Richmond requires a one-time Property Enrollment per property plus a Tenancy Registration filed for each individual tenancy, and a rent increase issued while either is out of date is void. Richmond’s banked-increase formula is additive (current AGA plus up to 5 percentage points of deferred AGAs) rather than Oakland’s multiplier-based approach — the two land in a similar range some years by coincidence, not because the underlying math matches. See our Richmond property management page for the fuller compliance calendar, including the March 1 Business License Tax deadline.

Emeryville: No Rent Cap Doesn’t Mean No Local Rules

Emeryville is the one city on this list with no local rent-control ordinance — for units it covers, AB 1482’s 8.8% rate governs directly, with no city-specific AGA to track. But “no rent control” isn’t the same as “no local rules.” Emeryville has its own Residential Landlord and Tenant Relations Ordinance: to terminate a covered tenancy, a landlord must hold a valid residential business license, give tenants the required rights notice, use a qualifying cause, and file a copy of the termination notice with the City Clerk within 10 days. Its just-cause list includes a few unusual grounds not found in Oakland, Berkeley, or Richmond’s ordinances, like a landlord returning from sabbatical or military deployment. No-fault terminations also carry relocation payments that scale by landlord size — the greater of one month’s fair market rent or one month’s rent for owners of 4 units or fewer, and the greater of five months’ fair market rent or four months’ rent for larger owners. See our Emeryville property management page for the fuller compliance picture — we’ll cover this ordinance in full in next month’s Emeryville deep dive.

Bottom Line

If you own in one East Bay city, learn that city’s system once and you’re set for the year. If you own across more than one, the rate is the thing you’re least likely to get wrong — everyone knows to look it up. The registration deadline, the just-cause waiting period, and which calendar governs your renewal notice are the details that don’t transfer from one city to the next, and they’re the ones that turn a technically-correct rent increase into a void one.

Before You Send a Rent Increase or Termination Notice

1. Confirm which ordinance covers the specific unit, not merely the city — coverage rules, not the address, decide which rate and rules apply.
2. Verify the unit’s registration, enrollment, or business-license status is current before serving any notice.
3. Check when the tenancy began, and against which jurisdiction’s new-tenancy rules (Oakland’s 12-month first-increase delay, Berkeley’s 15-day registration window, etc.).
4. Confirm the jurisdiction’s current allowable increase and effective window — not last year’s figure from memory.
5. Check whether prior AGAs have been banked, and recalculate the banked-increase cap if so.
6. Confirm the required notice period and any city filing requirements (e.g., Emeryville’s 10-day City Clerk filing).
7. When eviction or termination is involved, verify the applicable just-cause ground and any city-specific relocation-payment requirement before serving anything.

Sources

• AB 1482 8.8% (SF-Oakland-Hayward region) — Required by law. Civil Code §1947.12; BLS CPI release, San Francisco Area, April 2026
• Oakland RAP 2.3%, March 1 registration — Required by local ordinance. City of Oakland — Allowable Rent Increases
• Oakland just-cause coverage — Required by local ordinance (O.M.C. 8.22.300). City of Oakland — Just Cause for Eviction Ordinance
• Berkeley AGA 1.0%, Measure BB — Required by local ordinance. Berkeley Rent Board — 2026 AGA Published; Measure BB Changes to Berkeley’s Rent Ordinance
• Berkeley just cause, no waiting period — Required by local ordinance. Confirmed directly against BMC 13.76.130 (“Just cause required for eviction”), corroborated by Berkeley Rent Board — Just Cause & Other Local Requirements
• Berkeley registration deadlines (FY 2026–27 fees, 15-day new-tenancy registration) — Required by local ordinance. Berkeley Rent Board — Registration Fees, FY 2026-2027; Berkeley Rent Board — Partially Covered Unit Registration
• Richmond AGA 1.5%, enrollment/registration structure — Required by local ordinance (Regulation 615; RMC 11.100). City of Richmond — Rent Increase / Annual General Adjustment
• Emeryville ordinance summary (business license, City Clerk filing, relocation payments) — Required by local ordinance. City of Emeryville — Tenant Protection Resources; City of Emeryville — Eviction Ordinance overview
• AEBP portfolio anecdotes (Berkeley registration, Richmond business license) — AEBP documented experience. Examples anonymized to protect client privacy.

What We See at AEBP

Confirming just-cause coverage — not just checking whether the lease term has run out — is one of the first things we check before advising on any termination. It’s the distinction that trips up landlords most often on properties that were self-managed, or managed elsewhere, before just-cause protections applied.

Lease expiration, by itself, is never a valid just cause.

What to Check Before You Assume the Lease Ending Means Move-Out

1. Confirm just-cause coverage first. Check the statewide AB 1482 threshold (12 continuous months, or the added-tenant either/or test) and whether the property sits in Oakland, Berkeley, or Emeryville, where coverage starts day one regardless of how long the tenant has lived there.
2. If it applies, find the real ground. The lease’s own end date isn’t one — you need a qualifying at-fault reason (like nonpayment) or no-fault reason (like an owner move-in).
3. If it’s no-fault, confirm relocation assistance first. AB 1482’s baseline is one month’s rent within 15 calendar days of service; Oakland, Berkeley, and Emeryville each set their own amount and deadline. Missing it can invalidate the notice.
4. If just cause doesn’t yet apply, use the right §1946.1 notice. 30 days under a year of tenancy, 60 days at a year or more — but don’t assume that route stays open once coverage kicks in.

💡 This Week’s Takeaway

A lease simply reaching its end date is never, by itself, a valid reason to end a just-cause-protected tenancy — you still need a real at-fault or no-fault ground, and the right notice to go with it.

📘 Learn More

For the complete decision path — no-cause vs. just-cause, the 12-month statewide threshold, and Oakland’s, Berkeley’s, and Emeryville’s day-one rules — see the full guide:

→ Ending a Month-to-Month Tenancy in California: Notice, Just Cause & What Landlords Get Wrong (2026) — the complete breakdown, including relocation assistance and the added-tenant occupancy wrinkle.
→ California Lease Renewals 2026 — how a fixed-term lease actually converts to month-to-month in the first place.

Last updated August 2026 — reflects AB 1482’s 12-month just-cause rule (plus its added-tenant occupancy test) and Oakland’s, Berkeley’s, and Emeryville’s day-one just-cause coverage under their current ordinances.

In Short

Ending a month-to-month tenancy in California runs on one of two entirely different tracks, and using the wrong one is the single most common mistake landlords make. If the tenancy isn’t just-cause protected, Civil Code §1946.1 lets a landlord end it with no reason given — 30 days’ notice if the tenant has lived there less than a year, 60 days’ if a year or longer. But once just cause applies, a no-cause notice isn’t a lawful option at all: the landlord needs a qualifying at-fault or no-fault reason under Civil Code §1946.2 (AB 1482), which kicks in after 12 continuous months of tenancy statewide in the usual case — adding another adult tenant triggers a special either/or occupancy test instead (see below) — or, in Oakland, Berkeley, and Emeryville, from day one under their own just-cause ordinances, regardless of how long the tenant has lived there. Lease expiration by itself is never a valid just cause in any of these jurisdictions. Relocation assistance for a no-fault termination isn’t a flat figure either — Oakland, Berkeley, and Emeryville each set their own local relocation rules and amounts under ordinance instead of simply defaulting to AB 1482’s one-month statewide baseline — often substantially higher, though not always — and offering it doesn’t obligate the tenant to accept it or move out. This is a different notice, a different statute, and a different question than raising the rent, which runs on its own separate clock under §827(b) — covered in our month-to-month rent increase guide.

Two Tracks: No-Cause Notice vs. Just Cause

“Ending a tenancy” and “evicting a tenant” get used interchangeably, but the legal question underneath is really: does this unit require a reason to end the tenancy, or not? That answer splits into two completely different tracks, and the split determines which statute, which notice period, and which paperwork actually apply.

Under Civil Code §1946.1, a landlord ending a month-to-month tenancy that isn’t just-cause protected doesn’t need to state a reason at all — a “no-cause” or “no-fault” termination, in the sense that no wrongdoing or qualifying business reason has to be shown. The required notice is 30 days if the tenant has lived there less than a year, and 60 days if a year or longer.

Once just cause applies — whether under AB 1482’s statewide threshold or Oakland’s, Berkeley’s, or Emeryville’s day-one local ordinances — that no-cause option disappears. Civil Code §1946.2 requires a qualifying at-fault or no-fault reason instead, and §1946.1’s no-cause notice is no longer a lawful basis for ending the tenancy, regardless of how much notice is given.

A tenancy that’s for-cause — ending because of unpaid rent or a lease violation — is a third category with its own notice mechanics (a 3-day notice to pay rent or quit, or to cure or quit), covered separately in our eviction notice requirements guide. This guide focuses on the no-cause/just-cause question, which is where the confusion is most common.

When Just Cause Kicks In Statewide: The 12-/24-Month Rule

For units covered by AB 1482 and not subject to a stricter local ordinance, just-cause protection attaches once all tenants under the same household have continuously and lawfully occupied the unit for 12 months. There’s one wrinkle: if an additional adult tenant is added to the lease before an existing tenant has occupied the unit for 24 months, the rule gets more nuanced — just cause applies once either all tenants have occupied the unit for 12 months or more, or at least one tenant has occupied it for 24 months or more, whichever comes first. In practice, that often means coverage attaches sooner than a simple “24-month reset” would suggest.

Before the applicable threshold is met, a no-cause termination under §1946.1 is still a lawful option for AB 1482 purposes. Once it’s met, the landlord needs one of the law’s recognized categories:

At-Fault Just Cause

• Failure to pay rent
• Material breach of the lease, after written notice to cure
• Criminal activity or nuisance
• Unauthorized subletting
• Refusal to allow lawful entry

No-Fault Just Cause

Legitimate business reasons that aren’t the tenant’s fault — owner move-in, Ellis Act withdrawal, substantial renovation requiring vacant possession, or a government order requiring vacancy. A no-fault termination requires relocation assistance equal to one month’s rent, or an equivalent rent waiver, due within 15 calendar days of the notice being served — skipping or missing that deadline can invalidate the notice. See our full AB 1482 guide for the complete grounds list and notice mechanics.

Lease expiration is not on either list. A fixed-term lease simply reaching its end date — or a tenancy that has already converted to month-to-month under Civil Code §1945 — is not, by itself, a qualifying just cause once the threshold is met. See California Lease Renewals 2026 for how that conversion works.

Oakland, Berkeley, and Emeryville: Just Cause From Day One, No Waiting Period

AB 1482’s 12-/24-month threshold doesn’t apply in Oakland, Berkeley, or Emeryville the way it does everywhere else in AEBP’s service area — all three cities’ local just-cause ordinances cover eligible units from the very start of the tenancy, which means a true no-cause termination is rarely, if ever, available on a covered unit in any of them.

Oakland’s Just Cause for Eviction Ordinance (OMC §8.22.360) applies to covered units from day one — a tenant who moved in a month ago has the same protection as one who’s lived there for years, and lease expiration is not among the ordinance’s permitted grounds. See our Oakland Just Cause Eviction guide for the complete list of permitted grounds.

Berkeley’s Rent Stabilization Ordinance (BMC Ch. 13.76) works the same way for covered units — just-cause protection attaches at the start of the tenancy, and expiration of the lease term is not, by itself, good cause to end it.

Emeryville’s Residential Landlord and Tenant Relations Ordinance (Emeryville Municipal Code §5-40.04(a)) goes further still — just cause is required from day one of the tenancy for covered units, and relocation assistance is owed on essentially every no-fault termination, which means a true no-cause termination is rarely a realistic option on an Emeryville rental at all.

The practical trap: a landlord who correctly tracks the statewide 12-month AB 1482 threshold can still get this wrong on an Oakland, Berkeley, or Emeryville property, because the local ordinance overrides the statewide waiting period entirely rather than adding to it. A brand-new tenant on a covered unit in any of these three cities may already be just-cause protected on day one, even though the same tenant in a jurisdiction without a local ordinance wouldn’t be for another 11 months.

Not the Same Question as Raising the Rent

Ending a tenancy and raising the rent on one that continues are two separate legal actions, governed by two separate parts of the Civil Code, and mixing them up is one of the more common mistakes we see. Ending a tenancy runs through §1946.1 (no cause) or §1946.2 (just cause), covered above. Raising the rent on a tenancy that continues runs through §827(b) instead — a 30- or 90-day notice depending on the increase’s size, capped by AB 1482 or the applicable local rate. Neither notice substitutes for the other, and serving one doesn’t extend or shorten the deadline for the other. See our full month-to-month rent increase guide for that side of the ledger.

Relocation Assistance Isn’t One-Size-Fits-All

AB 1482’s one-month baseline is a floor, not the number that actually applies on most of the no-fault terminations we handle. Oakland, Berkeley, and Emeryville each have their own local relocation rules and amounts under ordinance instead of simply defaulting to AB 1482’s figure — often substantially higher, though not always (Emeryville’s small-landlord formula, for example, can land close to that same one-month baseline). Here’s what we check before advising an owner on a no-fault termination in any of these three cities:

• Oakland — under the Uniform Residential Tenant Relocation Ordinance, the amount depends on unit size and the specific no-fault ground (owner/relative move-in, Ellis Act, and code-compliance displacement each have their own provisions), and the citywide schedule adjusts every August 1st. Payment is typically split — part due within 15 calendar days of serving the notice, the rest within 15 calendar days of the tenant vacating. Confirm the current amount and applicable program with Oakland’s Rent Adjustment Program before serving notice or quoting a figure.
• Berkeley — Berkeley’s own no-fault relocation program (separate from AB 1482) adjusts each January 1st; for 2026 it’s $19,413 per household, plus an additional $6,471 for a qualifying household.
• Emeryville — under the Residential Landlord and Tenant Relations Ordinance (Emeryville Municipal Code §5-40.04(a)), the amount depends on the size of the landlord’s portfolio: an owner of four units or fewer owes the greater of one month’s HUD Fair Market Rent or one month’s actual rent; a larger landlord owes the greater of five months’ HUD Fair Market Rent or four months’ actual rent. Payment is due by the last day of the tenancy for which the landlord received rent.

What We See Managing East Bay Rentals

Here’s the part that catches owners off guard: paying the relocation amount doesn’t obligate the tenant to accept it or move out. We’ve seen tenants refuse a relocation offer outright and simply stay put, which pushes the owner toward a full eviction as the only remaining option. We got a call recently from an owner who needed to sell a property in Oakland with a family member living in it — they offered $30,000, well above what Oakland’s ordinance required, and the tenant still refused both the money and the move-out date. We referred that owner to a local attorney who specializes in housing and unlawful detainer cases, because at that point the relocation offer had satisfied the notice requirement — it hadn’t, by itself, gotten the owner possession of the unit. Relocation assistance satisfies a legal payment requirement; it isn’t a buyout agreement, and it doesn’t guarantee voluntary possession.

No-Cause vs. Just-Cause Termination: Quick Comparison

	No-Cause Termination	Just-Cause Termination
Governing statute	Civil Code §1946.1	Civil Code §1946.2 (AB 1482) or local ordinance
When available	Only where just cause doesn’t yet apply	Once the applicable just-cause threshold is met
Reason required	None — no reason has to be stated	A qualifying at-fault or no-fault reason
Notice period	30 days (tenant <1 yr) or 60 days (≥1 yr)	Varies by ground; no-fault grounds also require relocation assistance
Is lease expiration alone sufficient?	N/A — no reason needed either way	No, in any AEBP jurisdiction
Relocation assistance owed?	No — though Oakland, Berkeley, and Emeryville’s day-one just-cause coverage means a true no-cause termination is rarely available there at all	Yes, for no-fault grounds — AB 1482’s one month’s rent (or equivalent waiver), due within 15 days of service, is the statewide floor; Oakland, Berkeley, and Emeryville each set their own amount and deadline under local ordinance, often higher

Common Mistakes With Ending a Month-to-Month Tenancy

• Serving a no-cause §1946.1 notice on a just-cause-protected tenant — once just cause applies, no-cause notice isn’t a lawful basis for ending the tenancy at all
• Assuming AB 1482’s 12-month wait applies in Oakland, Berkeley, or Emeryville — all three cities’ local ordinances cover eligible units from day one instead
• Treating lease expiration as its own valid just cause — it isn’t, once the applicable threshold or local ordinance is in effect
• Skipping relocation assistance on a no-fault termination — this can invalidate the notice entirely, not just create a payment obligation after the fact
• Assuming AB 1482’s flat one-month relocation figure and service-day timing applies everywhere — Oakland, Berkeley, and Emeryville each set their own amount and payment deadline under local ordinance instead
• Assuming an offered relocation payment guarantees the tenant will move — a tenant can refuse the assistance and stay, which can push the owner toward a full eviction as the only remaining option
• Confusing a rent-increase notice with a termination notice — they’re governed by different statutes with different timelines and don’t substitute for each other
• Assuming an added adult tenant simply pushes the AB 1482 threshold from 12 months to 24 — the actual rule is more nuanced (whichever comes first: all tenants at 12 months, or any one tenant at 24), and coverage can attach earlier than a flat 24-month reset would suggest

Before You Serve a Termination Notice: A Quick Checklist

• Confirm the tenancy is actually month-to-month, not still inside an active fixed-term lease
• Check just-cause coverage first: has the unit hit AB 1482’s 12- or 24-month threshold, or is it in Oakland, Berkeley, or Emeryville, where coverage may already apply from day one?
• If just cause applies, confirm the termination fits a recognized at-fault or no-fault ground — lease expiration alone doesn’t qualify
• If it’s a no-fault ground, confirm the correct relocation-assistance amount and payment deadline for the property’s location — AB 1482’s baseline is due within 15 calendar days of service, but Oakland, Berkeley, and Emeryville each set their own amount and deadline under local ordinance — and remember that paying it doesn’t obligate the tenant to accept it or move out
• If just cause doesn’t yet apply, calculate the correct §1946.1 notice period: 30 days under a year, 60 days at a year or more
• Serve written notice, keep proof of service, and check for any additional local filing requirement (e.g., Oakland’s RAP or Berkeley’s Rent Board)
• Don’t conflate this with a rent-increase notice — confirm each notice independently against its own statute and timeline

Termination and eviction rules are highly fact-specific, especially where state and local just-cause laws overlap. If possession is disputed, the termination ground is uncertain, or a local relocation rule applies, consult a California landlord-tenant attorney before serving the notice.

Frequently Asked Questions About Ending a Month-to-Month Tenancy

Sources

• Civil Code §1946.1 — 30/60-day notice to end a periodic (month-to-month) tenancy without cause
• Civil Code §1946.2 — AB 1482 statewide just-cause eviction requirements, including the 12-/24-month occupancy thresholds and relocation assistance
• Civil Code §1945 — holdover tenancy presumed renewed month-to-month on acceptance of rent
• Civil Code §827(b) — rent-increase notice requirements (separate from termination)
• City of Oakland — Just Cause for Eviction Ordinance (OMC §8.22.360)
• Berkeley Rent Board — AB 1482 / Tenant Protection Act
• Berkeley Rent Board — 2026 Adjustments of Relocation Assistance Payments
• City of Oakland — Uniform Residential Tenant Relocation Ordinance
• Emeryville Residential Landlord and Tenant Relations Ordinance (Just Cause Ordinance)

What We See at AEBP

We flag every new Berkeley tenancy’s move-in date specifically the moment it’s entered into our system, and mark that unit as increase-ineligible until the correct calendar year — not the anniversary date. It’s a small operational step, but it’s there because this is one of the questions we get most often from Berkeley owners: a call around month 11 or 12 asking about a rent increase, assuming it works the same way it does in Oakland or under the statewide cap. It doesn’t.

A tenancy that starts in March 2026 doesn’t see its first Berkeley increase until 2028.

What to Check Before You Plan a Berkeley Increase

1. Confirm the tenancy’s actual move-in date. Not the lease signing date, not today’s date — the calendar year the tenancy actually started is what starts the clock.
2. Rule out the rest of the start year. No AGA increase is allowed for any month remaining in the calendar year the tenancy began, no matter how many months that leaves.
3. Add the entire next calendar year on top. Berkeley’s delay isn’t 12 months from move-in — it’s the rest of the start year plus one full additional calendar year.
4. Check the AGA rate in effect when the unit finally becomes eligible, not this year’s. By the time a new Berkeley tenancy clears the delay, the applicable rate is often a different cycle’s number than the one in effect at move-in.
5. Don’t assume Oakland’s or Richmond’s timeline applies. Oakland uses a flat 12 months from move-in, and Richmond uses a full calendar year before the next September 1 AGA date. Berkeley is the strictest of the three, and treating them interchangeably is the mistake we see most.

💡 This Week’s Takeaway

A new Berkeley tenant’s first rent increase isn’t a 12-month rule — it’s the rest of the start year plus a full additional calendar year. Check the actual move-in date against Berkeley’s Rent Board formula before assuming a unit is increase-eligible just because a year has passed.

📘 Learn More

This is one piece of the full jurisdiction-by-jurisdiction breakdown in this week’s cornerstone guide:

→ Month-to-Month Rent Increases in California: How Much, How Often & How Much Notice (2026) — the full guide this tip is drawn from
→ How Much Can a Landlord Raise Rent in California in 2026? AB 1482 Explained — the statewide formula and how it interacts with local caps
→ California Lease Renewals 2026 — notice requirements and renewal mechanics

Last updated August 2026 — reflects the AB 1482 statewide cap at 8.8% and Oakland’s local cap at 2.3%, both effective August 1, 2026.

In Short

Once a California tenancy is month-to-month, a rent increase is governed by Civil Code §827(b) — a completely different statute from the one that ends a tenancy (§1946.1). For 2026–2027, the maximum is 8.8% statewide under AB 1482, but far lower where local rent control applies: 2.3% in Oakland, 1.0% in Berkeley, 1.5% in Richmond. How often you can use it varies by jurisdiction — up to two increases within a rolling 12 months under AB 1482, but only one per 12 months under Oakland’s stricter local rule — and the required notice is 30 days for an increase of 10% or less, 90 days for anything above that. Section 827’s month-to-month notice procedure generally doesn’t apply while a tenant is still inside an active fixed-term lease — a mid-term increase usually needs to be authorized by the lease itself, and any applicable state or local rent cap still limits the amount if it is. That’s a separate question, covered below.

Why Civil Code §827 — Not §1946.1 — Governs a Month-to-Month Rent Increase

The two statutes landlords reach for at renewal time do different jobs, and mixing them up is one of the more common mistakes we see. Civil Code §1946.1 governs ending a month-to-month tenancy — 30 or 60 days’ notice, depending on how long the tenant has lived there. Civil Code §827 governs changing the terms of a periodic tenancy while it continues — and a rent increase is a change of terms. They’re separate statutes, triggered by separate actions. A landlord who wants to raise rent (not end the tenancy) uses §827 for the notice and change-of-terms procedure, while §1947.12 (AB 1482) or the applicable local ordinance determines how much the rent may actually go up.

Both statutes share the same scope limitation: they apply to periodic tenancies — “week to week, month to month, or other period less than a month,” in the statute’s own language — not to a lease with a stated fixed term that hasn’t yet ended. That’s the piece that trips landlords up when a rent increase gets tangled up with a “renewal”: there’s no renewal-specific rent-increase rule. There’s just §827, and it only switches on once the tenancy is actually periodic.

How Much: The Cap by Jurisdiction

For units covered by AB 1482 (Civil Code §1947.12) and not subject to a stricter local ordinance, the maximum is 5% plus the regional CPI, capped at 10%. For the period beginning August 1, 2026, that’s 8.8% (3.8% CPI + 5%). Oakland, Berkeley, and Richmond all have local rent boards that set a lower number for covered units in those cities — and where a local ordinance applies, it overrides the statewide figure entirely, not just as a lower ceiling on top of it.

Jurisdiction	Max increase, 2026–2027 cycle	Cycle
Statewide (AB 1482)	8.8%	Aug 1, 2026 – Jul 31, 2027
Oakland (RAP)	2.3% once eligible*	Aug 1, 2026 – Jul 31, 2027
Berkeley (AGA)	1.0% once eligible*	Calendar year 2026
Richmond (AGA)	1.5% once eligible*	Sept 1, 2026 – Aug 31, 2027

*Oakland, Berkeley, and Richmond each delay a brand-new tenancy’s very first increase — the details differ by city. See below.

These are flat annual limits, not hard ceilings on what can ever be charged. Oakland, Berkeley, and Richmond each allow a landlord who skipped or partially took a prior year’s increase to “bank” it and apply more than the flat annual percentage in a single notice, under three different city-specific formulas — that’s its own topic with its own math, not something to approximate here. See our Oakland Rent Control guide for Oakland’s banking rule specifically. AB 1482’s statewide cap does not have an equivalent statewide banking provision in the source material we’ve verified — treat 8.8% as the actual ceiling for statewide-only units.

For the full CPI+5% formula, why the 10% hard cap rarely gets triggered, and a worked example on an actual dollar figure, see the complete breakdown in our AB 1482 rent cap guide.

New-Tenancy Delays: Oakland, Berkeley & Richmond Each Have One (AB 1482 Doesn’t)

All three of AEBP’s local rent-control jurisdictions delay a brand-new tenancy’s very first rent increase — they just run the clock differently, and the wait is longer than most landlords expect. (AB 1482 doesn’t have an equivalent: the statewide cap only limits increases on a tenant already in occupancy — the very first rent charged to a new tenant isn’t regulated at all, so there’s no comparable “delay” to describe.)

Oakland — the first increase can’t take effect any earlier than 12 months after the tenant’s move-in date. Confirmed directly on the City of Oakland’s own Allowable Rent Increases page: “An owner can increase the rent on a covered unit only once in a 12-month period,” and “the first increase cannot be effective any earlier than 12 months after the tenant moved into the unit.”

Berkeley — the most restrictive of the three. A brand-new tenancy is ineligible for any AGA increase for the rest of the calendar year it starts in, plus the entire following calendar year. Per the Berkeley Rent Board’s own guidance: “Landlords cannot raise the rent for the rest of the year in which the tenancy started, and for one additional calendar year.” Their own example matches the math exactly: a tenancy starting March 1, 2026 can’t see its first AGA increase until 2028.

Richmond — a tenancy has to exist a full calendar year before the next September 1 AGA date. Per the city’s own Rights & Responsibilities materials: “The tenancy must exist for at least one full calendar year prior to the September 1 of the following year to implement that year’s AGA. For example, if a tenancy began in February 2020, the first AGA may be taken on September 1, 2021.” Practically, a tenancy that starts anytime after a given year’s September 1 typically won’t reach its first eligible AGA for close to two years.

The mechanics differ by city, but the takeaway is the same everywhere: check a new tenancy’s actual move-in date against the applicable rule before assuming a unit is increase-eligible just because the jurisdiction’s flat rate looks straightforward. The rule is keyed to when the tenancy actually started, not the lease type — a tenancy that begins on a fixed-term lease and later converts to month-to-month under Civil Code §1945 doesn’t get a fresh clock at conversion; the delay still runs from the original start date.

How Often: The 12-Month Rule Is Cumulative, Not Per-Increase

How many separate increases can be served in a rolling 12 months depends on which cap applies — this isn’t the same rule everywhere. Under the statewide AB 1482 cap, a landlord can serve up to two increases within a rolling 12-month period, as long as their combined total doesn’t exceed that period’s cap (Civil Code §1947.12(a)(2)) — raise rent 4% in March and another 4% in October on a unit capped at 8.8%, and that’s allowed, because the combined total stays under the cap. Oakland’s RAP is stricter: covered units are limited to exactly one increase per 12-month period, full stop, even if a second increase would keep the combined total under 2.3%. Berkeley and Richmond apply their AGA as a single annual adjustment, though both let a landlord “bank” a skipped year’s adjustment into a later notice under their own city-specific formulas — see our Oakland Rent Control guide for how banking math works.

Whichever cap applies, a landlord can’t reset the clock by splitting a single planned increase into smaller pieces just to work around the 30-day/90-day notice threshold. The 12-month window runs from the date of the increase, not the calendar year, and it doesn’t restart just because a lease converted to month-to-month partway through.

What About a Tenant Still in a Fixed-Term Lease?

Generally, a landlord can’t raise rent during an active fixed-term lease unless the lease itself has a clause allowing it — the tenant and landlord agreed to a specific rent for a specific term, and §827 doesn’t create a mid-term increase right the lease doesn’t already provide. Where a lease does include its own escalation or step-up clause, that increase still has to fit within whatever cap otherwise applies to the unit (AB 1482 or the local ordinance) — a fixed term doesn’t exempt the unit from the rate cap itself, only from §827’s month-to-month notice procedure. That’s covered in more detail in our rent increase notice requirements guide. A rent increase on that unit becomes available once the fixed term actually ends and the tenancy either converts to month-to-month under Civil Code §1945 or a new lease is signed. See California Lease Renewals 2026 for exactly how that conversion works, how it interacts with just-cause protection, and the effective-date timing rule for combining a rent increase with the point a lease ends.

How We Time Rent Reviews Without a Renewal to Anchor Them To

As we’ve written before, we don’t send proactive renewal offers — when a fixed-term lease ends, we let it convert to month-to-month by default rather than re-papering a new fixed term as a matter of course. That means a rent increase, for most of our portfolio, isn’t something we bundle into a “renewal conversation,” because there generally isn’t one. The lease-end conversion date is still meaningful, though: it’s the point at which a unit gets flagged for a rent review, separate from any negotiation with the tenant. From there, it’s a straightforward §827(b) question — where does the current rent sit against the jurisdiction’s cap and the market, and does a notice make sense — not a lease-signing decision. It’s a smaller distinction than it sounds like, but it’s the reason our rent-increase timing and our lease-renewal timing aren’t the same conversation internally, even though landlords searching for this often assume they have to be.

Which Statute Applies? Quick Reference

Situation	Governing statute	What it requires
Tenant is inside an active fixed-term lease	Lease terms + applicable rent-control law	Generally no mid-term increase unless authorized by the lease; any applicable state or local rent cap still limits the amount if it is
Raising rent on a month-to-month tenancy	§827(b) for notice; §1947.12 or applicable local ordinance for the cap	30 days’ notice (≤10% cumulative in 12 months) or 90 days’ (>10%), amount limited per the applicable cap
Ending a month-to-month tenancy, no cause	Civil Code §1946.1	30 days’ notice (tenant <1 year) or 60 days’ (≥1 year) — only where just cause doesn’t apply
Ending a just-cause-protected tenancy	Civil Code §1946.2 (AB 1482) or local ordinance	A qualifying at-fault or no-fault reason, regardless of lease type or notice length

Common Mistakes With Month-to-Month Rent Increases

• Using §1946.1’s notice periods for a rent increase — that statute ends a tenancy; §827 raises the rent, and they run on different clocks
• Applying the statewide 8.8% cap in Oakland, Berkeley, or Richmond instead of the much lower local rate
• Assuming only Berkeley delays a new tenancy’s first increase — Oakland (12 months from move-in) and Richmond (a full calendar year before the next Sept 1 AGA date) each have their own version too
• Treating the annual cap as a per-notice allowance rather than a cumulative 12-month total
• Assuming a rent increase can be served on a tenant still inside a fixed-term lease without a lease clause permitting it
• Forgetting the 5-day mail extension when a notice is mailed rather than hand-delivered

Before You Raise Rent: A Quick Checklist

• Confirm the tenancy is actually periodic (month-to-month) — not still inside an active fixed-term lease
• Confirm which cap governs the unit: statewide AB 1482, or a stricter local ordinance (Oakland, Berkeley, or Richmond)
• If it’s a new tenancy, check the applicable new-tenancy delay before assuming it’s increase-eligible at all (Oakland: 12 months from move-in; Berkeley: rest of the start year plus one full year; Richmond: a full calendar year before the next Sept 1)
• Calculate the correct percentage for the applicable jurisdiction and cycle dates — don’t reuse last cycle’s number
• Check whether an increase has already been taken in the same 12-month window, and confirm the combined total including this one stays within the cap
• In Richmond specifically, confirm the unit’s property enrollment and tenancy registration are current with the Rent Program — an increase issued while either has lapsed is void
• Choose the correct notice period: 30 days for an increase of 10% or less, 90 days for anything above that (add 5 days if mailed)
• Serve written notice, keep proof of service, and file with the local rent board where that’s required (e.g., Richmond)

Frequently Asked Questions About Month-to-Month Rent Increases

Sources

• Civil Code §827 — notice requirements for changing the terms of a periodic tenancy, including rent increases
• Civil Code §1946.1 — 30/60-day notice to end a periodic (month-to-month) tenancy
• Civil Code §1945 — holdover tenancy presumed renewed month-to-month on acceptance of rent
• Civil Code §1947.12 — AB 1482 statewide rent cap formula
• U.S. Bureau of Labor Statistics — San Francisco-Oakland-Hayward CPI release
• City of Oakland — Allowable Rent Increases
• Berkeley Rent Board — Annual General Adjustment
• City of Richmond — Rent Increase / Rent Program
• City of Richmond — Rights and Responsibilities for Landlords and Tenants (new-tenancy AGA eligibility rule)

What We See at AEBP

We’re currently onboarding two Oakland properties where rent hadn’t been increased in years before the owner brought them to us. Rather than freezing those units at an outdated rate indefinitely or pushing a single jarring jump to market, we’re using Oakland’s banking rule to bring rent up by 6.9% — three years of the current 2.3% cap, applied in one notice, fully within RAP’s rules.

Banking turns a skipped increase into deferred income — not lost income.

Before You Assume a Skipped Increase Is Gone

1. Check whether the unit is RAP-covered. Banking only applies to Oakland units covered by the Rent Adjustment Program — confirm coverage before assuming the rule applies.
2. Confirm your Business Tax Certificate is current. A banked-increase notice requires a current Business Tax Certificate specifically — the delinquent-tax payment-plan alternative available for CPI-only increases doesn’t apply here.
3. Cap it at three times the current year’s CPI, and include the current year. A banked notice can’t exceed that multiple, and it has to include the present year’s own increase — not just prior years’.
4. Watch the 10% ceiling and the notice period. Oakland caps any single rent increase at 10% regardless of banking math, and any increase over 10% requires 90 days’ written notice instead of 30 (Civil Code §827).
5. Don’t apply one city’s math to another. Oakland caps banking at 3x the current CPI, Richmond caps it at the current AGA plus 5 points, and Berkeley caps it only at the unit’s legal rent ceiling — three different formulas, not one rule with three rates.

💡 This Week’s Takeaway

A rent increase you didn’t take last year isn’t automatically lost. In Oakland and Richmond, it can be banked and applied later, within each city’s own limits — so before assuming a unit is stuck at an old rate, check whether banking applies.

📘 Learn More

Banking is one piece of the larger renewal-math question — when a rent increase is actually worth taking versus when it costs more than it’s worth. For the full breakdown:

→ Should You Raise Rent at Renewal or Keep This Tenant? The East Bay Landlord’s Break-Even Math — the full break-even framework this tip is drawn from
→ East Bay Rent Cap Update: New 2026–2027 Increase Limits — all four jurisdictions’ current caps
→ California Lease Renewals 2026 — notice requirements and renewal mechanics

Last updated August 2026 — reflects Oakland’s RAP allowable increase rising to 2.3% effective August 1, 2026.

In Short

A rent increase you’re legally permitted to charge isn’t automatically worth charging. Where local rent-adjustment limits are small — Oakland’s RAP allows 2.3% for RAP-covered units in 2026–2027, Berkeley’s AGA holds at 1.0% for eligible fully covered units, Richmond’s is 1.5% for covered units — the dollar value of that increase is often smaller than what a single turnover costs in lost rent. Using AEBP’s own East Bay portfolio data, the average turnover’s vacancy-rent cost alone runs roughly $2,851 on a typical Oakland unit — about 4.6 years’ worth of the Oakland increase, or a roughly 22-percentage-point rise in turnover risk on an expected-value basis. That doesn’t mean you should never raise rent at renewal. It means the decision should be run as math, tenant by tenant, not applied as a default.

Why This Math Matters Most Where the Local Limit Is Small

AB 1482’s statewide rent-increase cap for covered units this cycle is 8.8% — big enough that, on a $2,263 unit, a full year of the increase ($199/mo, ~$2,390/yr) comes close to covering an average turnover on its own. Oakland, Berkeley, and Richmond each run their own local rent-adjustment programs, and where a unit is covered by one of those programs, the applicable limit is typically well below the statewide cap: Oakland’s RAP allows 2.3% for RAP-covered units in 2026–27, Berkeley’s AGA allows 1.0% for eligible fully covered units in 2026, and Richmond’s AGA allows 1.5% for covered units beginning September 2026. If a unit isn’t covered by the local program, the next question is whether AB 1482 applies — some locally exempt units are still covered by the state cap, while others may also qualify for their own AB 1482 exemption. Coverage under one program is never automatic just because a unit is exempt from the other; the two have to be checked independently.

On a 2.3% Oakland increase, you’re gaining about $52 a month. A single turnover wipes out more than four years of that gain before you’re ahead. On Berkeley’s 1.0% AGA, it’s worse: a full year of the increase is worth about $22.63 a month, or roughly $272 a year — a turnover costs closer to ten and a half years of that increase to recoup.

This isn’t an argument against raising rent where you’re legally permitted to. It’s a reason to check the math — and confirm which limit actually applies to your unit — before deciding how much of the allowed increase to actually push on a given renewal, especially on a rent-controlled unit where the ceiling is already low.

What a Turnover Actually Costs

Landlords tend to price a rent increase against the visible number — the extra $50 or $75 a month — without pricing the alternative against what happens if the increase costs them the tenant. Thursday Tip 7928 already covered the general shape of this: self-managing landlords typically underestimate vacancy duration because they track “days the listing was up,” not the full move-out-to-move-in cycle.

We can go a step further with our own numbers, since we track the full cycle across our managed portfolio as a matter of course. Over the trailing 12 months (August 2025–July 2026), AEBP completed 79 turnovers portfolio-wide, averaging 37.8 days from move-out to move-in — cleaning, repairs, photography, listing, showings, and screening, all included. At roughly $75/day in rent value on a typical Oakland unit, that’s about $2,851 in lost rent per turnover, before counting the extra cost of turnover-specific repairs, cleaning, or a leasing fee on the replacement tenant.

That’s the number a rent increase has to outrun to be worth the risk on a tenant who might leave over it.

The Real Break-Even Question: How Much Turnover Risk Does the Increase Need to Justify?

The comparison above — 4.6 years of increases to equal one turnover — is a useful way to see the size of the stakes, but a turnover isn’t guaranteed just because you raise the rent. The sharper question is how much the increase actually raises the odds your tenant leaves.

Run it as expected value instead: $624 (one year of Oakland’s 2.3% increase) ÷ $2,851 (the cost of one turnover) ≈ 21.9%. That means the increase breaks even, on a one-year expected-value basis, if taking it raises your tenant’s probability of leaving by roughly 22 percentage points — for example, from a 5% baseline chance of turnover to somewhere around 27%.

If you think a modest, capped increase moves that probability from 5% to 10%, the expected cost is a small fraction of $2,851, and the increase clearly wins. If you think it moves the probability from 5% to 35% — a genuinely upset, price-sensitive tenant — the math flips the other way. The 4.6-year comparison shows you what’s at stake; this calculation is the actual decision threshold.

This 22-percentage-point threshold uses vacancy loss alone — it doesn’t count make-ready, repairs, or a leasing fee. Adding those in would lower the threshold further, so the real break-even point is likely an even smaller probability shift than 22 points. Vacancy loss alone is a conservative floor for this calculation, not an inflated one.

When Raising the Rent Is Still the Right Call

None of this means holding rent flat is automatically correct either. The math above assumes a turnover actually happens — and the point of running it per-tenant is to weigh how likely that is, not to assume it. A few situations where pushing the increase is still the better call:

• A turnover is already reasonably likely for reasons unrelated to the proposed increase. If the tenancy already has significant payment or compliance issues, the increase may have little effect on the underlying probability of turnover — the retention premium from holding rent flat is smaller when a turnover was already likely.
• A lawful turnover is already underway for reasons independent of the rent increase. A planned renovation that requires the unit be vacant, a tenant who has already given notice, or another legally valid tenancy-ending event already in motion — the increase decision is secondary to a decision that’s already been made, not a way to manufacture one.
• The unit is meaningfully under market and the tenant has said they’re flexible. Not every tenant will leave over a modest, legally permitted increase — some expect it and stay regardless.
• You need the increase for cash flow, not to maximize return. Rising insurance, taxes, or a mortgage reset are real reasons to raise rent that this break-even framing doesn’t capture — the math above measures return-maximizing logic, not cash-flow-necessity logic.

Push the Increase vs. Hold the Rent: A Quick Comparison

	Push the Full Allowable Increase	Hold Flat (or Increase Partially)
Immediate gain	Full permitted increase (2.3% Oakland / 1.0% Berkeley / 1.5% Richmond, for covered units)	None, or a smaller partial increase
Risk	Tenant leaves; turnover cost likely exceeds 1+ years of the increase	Tenant stays; opportunity cost is the increase not taken
Best fit	Turnover is already likely for other reasons, or a lawful turnover is already underway	Reliable tenant, low turnover risk, small local limit
What it doesn’t account for	Whether you need the cash flow now	Whether the unit is significantly under market, or whether the foregone increase can be banked

A note on banking: in jurisdictions that permit it — including Oakland and Richmond — some or all of an increase you don’t take this year may be preserved for a future year, subject to that city’s banking rules and documentation requirements. Holding below the maximum isn’t necessarily the same as forfeiting it permanently. See our AB 1482 rent cap guide for jurisdiction-specific banking rules.

How AEBP Approaches This at Renewal

We don’t skip rent increases as a default any more than we push them as a default — both are guesses without the numbers behind them. What we actually do every renewal season is check three things before recommending an amount to an owner: whether the unit is covered by a local rent-adjustment program and which limit actually applies, the tenant’s payment and compliance history, and how the increase compares to what a turnover would realistically cost on that specific unit. On a rent-controlled property with a reliable tenant, that math usually favors a modest or full increase within the applicable limit rather than risking a turnover to chase a slightly higher number later — but it’s a calculation we run per property, not a policy we apply across the board.

Frequently Asked Questions About Rent Increases at Renewal

Sources

• City of Oakland — Rent Adjustment Program (RAP), coverage rules
• City of Oakland — Allowable Rent Increases
• Berkeley Rent Board — 2026 AGA Published
• City of Richmond — Rent Increase / Rent Program
• Civil Code §1947.12 — AB 1482 rent-cap formula
• AEBP AppFolio vacancy and rent-roll data, trailing 12 months (Aug 2025–Jul 2026) — internal, AEBP documented experience