AB2153 repeals Section 2226 of the California Elections Code, a provision that governed how county elections officials must update, inactivate, verify, and cancel voter registrations based on change‑of‑address data and returned mail. The repealed text set out specific triggers (including NCOA and returned-mail indicators), required forwardable verification mailings, and mandated cancellation after two federal general elections of inactivity.
The bill is framed as removing an obsolete statutory provision: §2226 contained a conditional sunset tied to the Secretary of State certifying a modification to the statewide voter registration database. Repeal eliminates the redundant or outdated statutory commands and shifts reliance onto current statewide systems, guidance, and other Elections Code provisions — a change election administrators and vendor teams need to map into operational procedures and data flows.
At a Glance
What It Does
The bill removes Section 2226, which specified county duties to (1) immediately update registrations when a voter moves within California, (2) mark registrations inactive when certain mail or change‑of‑address feeds indicate a move or returned mail, (3) send forwardable verification mailings, and (4) cancel registrations after two federal general elections of inactivity. The repealed section also required that these transactions appear on voter lists and included a sunset tied to a Secretary of State certification.
Who It Affects
Primary affected parties are county elections officials (who implemented the update/inactivation/cancellation workflow), the Secretary of State (whose database functionality triggered the prior sunset), and the vendors/systems teams that process NCOA and postal change‑of‑address feeds. Organizations and campaigns that rely on inactive lists or precise voter counts for signature thresholds are also indirectly affected.
Why It Matters
Removing §2226 cleans up California’s statutory code where an older procedural rule has been superseded by statewide database capability, but it also strips an explicit legal backbone for specific county actions. That creates immediate operational questions about which statutory or administrative authorities now govern residency confirmations, inactive‑status handling, and cancellation rules.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Section 2226 laid out a tightly prescriptive workflow: when change‑of‑address information arrived (either through specific statutory channels or direct voter notice), counties had to take one of several steps depending on what the data said. If the data showed the registrant had moved to another California address, counties were to update the record immediately.
If mailings were returned undeliverable or third‑party address feeds indicated a move without a forwarding address (including NCOA or other postal data), counties were to mark the registration inactive and cease routine mailings to that record.
For voters rendered inactive because they failed to confirm their address, §2226 cross‑linked to the address‑verification mailing process in the Elections Code and set a clear cancellation horizon: a voter who did not respond and who did not vote or offer to vote during the interval up to two subsequent federal general elections was subject to cancellation. The statute also required that every update, inactivation, or cancellation be reflected on the official voter list used for administration, and it expressly tied the section’s continued existence to the Secretary of State certifying a statewide system enhancement that would notify counties when a voter confirmed their registration online.The effect of repeal is procedural rather than philosophical: AB2153 strips the explicit statutory commands that governed these specific triggers and timelines.
It does not, by its text, itself change other Elections Code duties or erase the data sources counties use; instead it removes a statutory anchor that many counties used as the legal basis for their workflows. Practically, counties will need to confirm whether the Secretary of State’s systems and existing statutes provide equivalent authority and to update written procedures, vendor contracts, and public communications to reflect the statutory change.
The Five Things You Need to Know
AB2153 removes Elections Code Section 2226 in its entirety — the subdivision added by Chapter 262 (2019) is the repealed text.
Under the repealed text, counties were required to immediately update a registration when change‑of‑address information showed a voter moved to a new California residence.
The statute put specific data sources on the clock: returned mail, NCOA, Operation Mail, and certain postal change‑of‑address feeds could trigger an inactive status when they indicated a move with no forwarding address.
§2226 mandated a forwardable address‑verification mailing for inactive voters and authorized cancellation of registrations if the voter neither responded nor voted within two federal general elections following that mailing.
The section carried a conditional repeal clause tied to certification by the Secretary of State that the statewide voter registration database had been modified to notify counties when a voter confirms a registration online — AB2153 removes that conditional framework.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Immediate in‑state address updates
This subdivision originally required county officials to apply a change when incoming data indicated a move to a new California address. Operationally, that created a legal mandate for near‑real‑time record edits and forced counties to accept and process automated feeds as authoritative for in‑state address changes. With the repeal, counties lose that explicit statutory compulsion; they must now rely on other code sections or administrative direction to justify immediate edits and to set processing SLAs.
Triggers for inactive status from postal and third‑party feeds
The clause named concrete data sources — returned mail, NCOA, Operation Mail, and nonforwardable postal change‑of‑address data — as triggers to mark a record inactive. That linkage standardized which feeds counties could treat as sufficient cause. Repeal removes this statutory list, which raises questions about acceptable data sources going forward and could produce uneven county practices unless the Secretary of State or statute supplies an alternative evidentiary standard.
Address verification mailings and two‑federal‑general‑elections cancellation rule
These provisions required counties to send a forwardable verification mailing to inactive voters and specified a two federal general election window after which nonresponsive records would be canceled. The mechanics established a predictable calendar for cancellation and tied voter behavior (voting or offering to vote) to preservation of the registration. Repeal removes the statutory timeline; counties will need to verify whether other cancellation rules remain — or whether administrative policy must recreate equivalent timelines.
Reactivation after voter contact or offer to vote
This subdivision guaranteed reactivation if the voter offered to vote, voted, or notified the elections official of continued residency within the designated window. Practically, it preserved voters’ registrations through simple affirmative acts. Eliminating that explicit right may not change outcomes where other statutes or practice provide reactivation routes, but it does eliminate a clear statutory safety net and could complicate disputes over canceled registrations.
Requirement to reflect transactions on official voter lists
The section compelled that all updates, inactivations, and cancellations appear on the official voter list per §2191, affecting who receives mailings and who counts for administrative formulas. Repeal removes this cross‑reference; counties and outside users of voter lists (campaigns, petition gatherers) will need guidance about how and when changes will be published and whether prior expectations about list contents remain valid.
Conditional sunset tied to Secretary of State certification
The final subdivision made §2226 temporary: it remained effective only until the Secretary of State certified that the statewide voter registration database had been modified to notify counties of online confirmations. That conditional structure is the central rationale for AB2153’s repeal; removing §2226 collapses the conditional mechanism and leaves current database functionality and its supporting authorities as the operative governance for confirmation notifications.
This bill is one of many.
Codify tracks hundreds of bills on Elections across all five countries.
Explore Elections in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Secretary of State — Gains statutory cleanup: removing §2226 reduces outdated cross‑statutory contingencies and aligns the code with modern statewide database capabilities, simplifying legal text the office must interpret.
- Statewide IT and vendor teams — Fewer contradictory statutory anchors: vendors supporting the statewide registration system can standardize on the system’s built‑in notification features instead of tailoring implementations to an older, county‑centric statute.
- Entities that maintain centralized voter data products — Benefit from clearer reliance on the statewide database as the canonical source rather than multiple county processes, improving data consistency for downstream consumers.
Who Bears the Cost
- County elections officials — Must reconcile local procedures and operating manuals with the statutory change, update vendor contracts and training, and may face short‑term administrative costs and legal uncertainty about acceptable data sources and timelines.
- Voter outreach groups and campaigns — Could encounter temporary uncertainty about list content (inactive vs active) and about the timing of cancellations, complicating outreach strategies and signature‑gathering calculations.
- Secretary of State — Absorbs implementation pressure to issue guidance or regulations: with the statutory anchor removed, the SOS may need to define standards and timelines administratively, a resource and political cost not specified by the bill.
Key Issues
The Core Tension
The central dilemma is tidy statutory housekeeping versus the loss of an explicit legal regime that produced consistent county practices: removing an outdated provision reduces contradiction in the code but also erases clear, litigable rules about when and how registrations become inactive or are canceled, leaving administrators to rely on system capability and administrative guidance rather than the steadiness of statute.
AB2153 is a statutory housekeeping move on its face, but the operational consequences depend on surrounding law and system capability. The repealed text did more than describe process; it set evidentiary expectations (which address feeds count), timelines (the two‑federal‑general‑elections cancellation window), and publication duties (what must appear on the official list).
Removing that statutory scaffolding creates ambiguity about whether counties may adopt more permissive or more conservative practices, and about which data sources will be treated as sufficient cause for inactivation or cancellation.
Implementation will hinge on administrative interpretation. If the Secretary of State’s systems already provide the notification and confirmation features that §2226 presumed, practical impact may be small; if not, counties could face legal exposure for either continuing to follow the repealed workflow or for adopting divergent practices.
The repeal also shifts pressure onto intergovernmental coordination: counties, the Secretary of State, and vendors must align on data‑acceptance standards, SLAs for processing address feeds, and the public messaging required when registrations are inactivated or canceled.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.