The administrative split of Maricopa County’s election infrastructure is a profound operational partitioning of a high-throughput voting system. By formalizing a binary division of labor between early voting and Election Day operations, and funding a $15 million IT decoupling, the July 2026 settlement between Recorder Justin Heap and the Board of Supervisors establishes a dual-engine governance model. This structural reallocation of power ends a year of litigation but introduces complex operational trade-offs, critical single points of failure, and long-term fiscal burdens.
Analyzing this settlement requires looking past the political theater. Instead, we must examine the physical and digital architecture of Arizona’s most populous county, which processes more than 60% of the state’s total electorate. If you found value in this post, you might want to look at: this related article.
The Legal and Jurisdictional Split
Arizona Revised Statutes (A.R.S.) divide county-level election administration between two separate, independently elected entities: the County Recorder and the Board of Supervisors. Because the statutory boundaries between these offices are notoriously fluid, Maricopa County historically relied on intergovernmental "shared services" agreements to pool staff, IT, and facilities.
The July 2026 settlement fundamentally alters this arrangement by implementing a strict temporal and functional partition of duties: For another look on this story, refer to the recent update from The Washington Post.
MARICOPA COUNTY ELECTIONS
│
┌───────────────────────┴───────────────────────┐
▼ ▼
RECORDER'S OFFICE (Justin Heap) BOARD OF SUPERVISORS (Elections Dept)
┌───────────────────────────────────────┐ ┌───────────────────────────────────────┐
│ - Voter Registration Database │ │ - Emergency Voting Operations │
│ - Signature Verification Protocols │ │ - In-Person Election Day Voting │
│ - Early Ballot Site Selection │ │ - Ballot Tabulation & Adjudication │
│ - Mail-In Ballot Mailing & Drop Boxes │ │ - Polling Place Staffing & Logistics │
└───────────────────────────────────────┘ └───────────────────────────────────────┘
The Recorder’s Pre-Election Domain
Under the new agreement, Recorder Justin Heap exercises exclusive, non-delegable authority over the entire early voting window, which represents approximately 80% of all ballots cast in typical Maricopa County elections. This domain includes:
- Voter Registration and Database Management: Maintaining the active and inactive voter rolls, processing new registrations, and managing list maintenance.
- Early Ballot Distribution: Designing, printing, and mailing early ballot packages to voters on the Active Early Voting List (AEVL).
- Signature Verification: Running the multi-tiered human and automated validation protocols that compare inbound envelope signatures against voter registration records.
- Drop Box and Early Site Logistics: Selecting, securing, and operating physical ballot drop boxes and early in-person voting locations.
The Board's Live-Event Domain
Conversely, the Board of Supervisors retains command over the physical infrastructure required for synchronous, high-volume voting on and immediately preceding Election Day. Their domain is confined to:
- Emergency and Election Day Voting: Managing the logistics of in-person vote centers on the Monday before the election (emergency voting) and Tuesday itself.
- Polling Place Staffing: Hiring, training, and deploying thousands of temporary poll workers to manage physical vote centers.
- Tabulation and Adjudication: Operating the central count tabulators, managing the duplication of damaged ballots, and running the bipartisan hand-count audits required by state law.
The Cost of Administrative Redundancy: A $21 Million Capital Reallocation
The physical separation of these offices is not cheap. Operating a split election system requires duplicating existing technical systems, staffing, and support teams. To resolve the litigation, the Board of Supervisors agreed to transfer up to $21 million in county funds to the Recorder’s Office.
The allocation of these capital expenditures reveals the structural friction of the new model:
The $15 Million Database Decoupling
Historically, the Maricopa County Elections Department (under the Board) and the Recorder's Office utilized a unified, shared database infrastructure to track voters, process early ballot requests, and verify signatures. While highly efficient, this shared system created a governance bottleneck, as both parties claimed ultimate authority over the database's administrative access, security settings, and personnel permissions.
The settlement solves this governance dispute by spending $15 million to build an entirely new, independent IT infrastructure for the Recorder’s Office. This database decoupling introduces two distinct structural risks:
- Synchronization Lag: Because voter registration (Recorder) and physical voting status (Board) must now communicate across separate networks, the risk of data synchronization latency increases. During the critical 27-day early voting window, real-time updates are essential to prevent a voter from returning a mail ballot and subsequently attempting to cast a regular ballot at an in-person vote center.
- Increased Attack Surface: Splitting a unified database into two discrete systems with custom APIs or batch-processing transfer protocols inherently doubles the entry points for external cyber threats. Each database requires independent penetration testing, credential management, and security audits.
Human Capital Duplication
The remaining $6 million of the settlement fund is earmarked for the acquisition of independent IT personnel and dedicated early voting staff for the Recorder’s Office. In previous cycles, staff could be dynamically reallocated across departments depending on the operational phase—for instance, transitioning IT specialists from registration database maintenance in October to tabulation network security in November.
By hard-coding staff allocations to specific offices, Maricopa County loses this operational agility. The county must now fund permanent, year-round salaries for dual sets of IT specialists, security personnel, and project managers who cannot easily cross jurisdictional lines during peak demand periods.
Systemic Failure Modes of the Dual-Engine Model
The primary argument for a unified election department is the reduction of handoffs. In systems engineering, every interface between two independent entities represents a potential point of failure. The Maricopa County settlement introduces three distinct operational handoffs that must be tightly managed to prevent administrative failure.
1. The Chain-of-Custody Handoff
Under the agreement, the Recorder’s Office collects early ballots from mail carriers and physical drop boxes. Once collected, these ballots must undergo signature verification by the Recorder’s staff. However, once verified, those physical ballots must be transferred to the Board of Supervisors' Elections Department for physical tabulation.
This creates a critical handoff window. Any discrepancy in the batch logs, transport containers, or electronic tracking records during the transfer from the Recorder to the Board will immediately trigger public skepticism and legal challenges.
[Early Ballots Gathered] (Recorder)
│
▼
[Signature Verification] (Recorder)
│
▼
====== TRANSFER POINT: Batch Logging & Security Verification ======
│
▼
[Physical Ballot Tabulation] (Board of Supervisors)
2. Physical Site Conficts
Because the Recorder selects and operates early voting sites, while the Board manages Election Day vote centers, there is potential for physical asset contention. Many high-volume locations—such as community centers, churches, and municipal buildings—serve as both early voting locations and Election Day vote centers.
If the Recorder’s staff and the Board’s staff operate under different rules, security procedures, or setup configurations, the transition period between the close of early voting (the Friday before the election) and the opening of Election Day polls (Tuesday morning) could suffer from severe logistical bottlenecks.
3. The Special Master Dispute Escalation Trap
The settlement acknowledges that conflict is highly likely. To mitigate this, the parties appointed Maricopa County Superior Court Judge Christopher Coury to serve as a "special master" to mediate any future disputes.
While a dedicated arbitrator prevents prolonged public litigation, relying on a judicial special master during an active election cycle is highly risky. Election operations run on minutes, not days. If a dispute arises over ballot-box retrieval times on election night, waiting even six hours for a special master's ruling can delay the reporting of results, fuel conspiracy theories, and violate statutory reporting deadlines.
Operational Risk Analysis for the 2026 Midterms
With the July 2026 primary operating under an interim plan, the November 2026 general election will serve as the first full-scale stress test of this split-architecture model. The following matrix outlines the primary operational risks, their systemic consequences, and the mitigation steps required by both offices.
| Operational Risk | Primary Owner | Systemic Consequence | Required Mitigation Strategy |
|---|---|---|---|
| Data Out-of-Sync | Joint (Recorder & Board IT) | Voters are incorrectly issued provisional ballots due to latency in updating their active voting status. | Establish a near-instantaneous API sync protocol between the new $15M Recorder database and the Board's tabulation network. |
| Tabulation Delays | Board of Supervisors | Slow reporting of early ballot results on election night, which are crucial for establishing trust. | Formalize strict, hourly batch-delivery quotas from the Recorder’s signature verification teams to the tabulation facility. |
| Signature Verification Backlogs | Recorder's Office | Delays in processing late-arriving early ballots, extending the canvas period past statutory deadlines. | Use the $6M operational fund to pre-hire and thoroughly train signature-verification staff to run parallel shifts. |
| Chain-of-Custody Discrepancies | Joint (Security Teams) | Legal challenges and public distrust arising from mismatches in batch count logs. | Implement dual-custody logbooks signed by both a Recorder representative and a Board representative at the exact moment of physical ballot transfer. |
The Strategic Play for Arizona Election Officials
To prevent the administrative split from degrading election performance, Maricopa County cannot treat the settlement as a mere legal division of territory. To execute this model successfully through the 2026 general election and beyond, both entities must adopt a unified, systems-engineering approach:
- Establish a Shared API Standard immediately: Rather than allowing the two IT departments to build isolated database silos, the county manager must enforce a strict, read-write API standard that ensures changes to voter status (e.g., ballot returned, registration updated) propagate across both networks in less than five minutes.
- Draft a Joint Chain-of-Custody Playbook: The transfer of ballots from the Recorder's verification custody to the Board's tabulation custody must be treated with the same precision as a corporate supply-chain handoff. This requires standardized batch sizes, shared tracking barcodes, and real-time electronic ledger updates.
- Conduct Dry-Run Stress Tests: Before the early voting window opens for the November general election, the county must run a series of simulated high-volume scenarios—processing tens of thousands of mock ballots through the entire chain, from early collection to final tabulation—to identify latency issues and physical bottlenecks before they impact actual voters.
