Prepare a California voter-file workspace through access review.

Activation comes before file upload

A campaign's eligibility and approved purpose are necessary but not sufficient for hosted processing. VoterFile must also preserve issuing-agency acceptance covering the disclosed processor and viewers, complete the conservative vendor notice/security handoff, and close every applicable California security-control evidence item.

Until those records are green, the California workflow stops at account, contract, application, and security setup. The product rejects preview, upload, import, browse, and export for a structured California workspace by default.

• No California voter-data upload during access review
• Written issuing-agency and viewer coverage required
• Security evidence and notice/handoff required before activation

What campaigns need from voter data

A raw voter file is not a campaign system by itself. Campaign teams need fast ways to narrow the universe, explain why a voter is in a segment, track voter-level notes, and move that list into canvassing, email, SMS, phone, or mail workflows.

VoterFile is the operational layer after a qualified campaign, committee, consultant, or approved user already has lawful access to the file.

California voter-data upload and processing are not activated yet. Before any file enters VoterFile, the issuing agency must accept the disclosed hosted workflow and viewer coverage, the required notice and security handoff must be complete, and the California security evidence checklist must be green. After that gate, California workspaces default to the campaign's authorized official fields, customer-directed lists and turf, and campaign-entered activity. Voter-level BISG, turnout-propensity, and other modeled fields require a separate documented privacy-law activation basis.

• Party, county, age, and official vote-history filters
• Turnout and BISG signals only in a model-enabled workspace
• Per-voter CRM, survey responses, and follow-up status
• Walk packets, canvass mode, outreach handoff, and CSV export

California-first by design

California campaigns have local races, multi-county districts, nonpartisan contests, ballot measures, and different file-refresh needs. The product is intentionally scoped around California compliance, California districts, and campaign workflows.

Common campaign use cases

The strongest fit is not generic data browsing. It is repeatable campaign work where the team needs to build a voter universe, review it, save it, and use it for field, mail, email, SMS, phones, or reporting.

Those decisions usually happen under time pressure, so the workflow keeps counts, filters, authorized signal context, voter notes, and export paths close together.

• Build a turnout universe for a city council or school board race
• Compare persuasion, base, and vote-by-mail follow-up lists before export
• Cut a canvassing list, assign packets, and collect survey responses
• Track voter support, notes, and follow-up status after contact
• Give consultants separated client workspaces instead of shared spreadsheets

What makes the workflow reviewable

Campaign teams should be able to explain why a voter is in a list before they spend money or volunteer time on that list. VoterFile keeps the segment logic and voter-level context visible enough for a manager, consultant, candidate, or field lead to review.

That matters most in local California races where a bad list can waste the entire weekend of field work or distort a mail budget.

• Saved universes preserve the list logic the campaign chose
• Segment counts help compare options before final export
• Any enabled BISG and turnout signals are paired with methodology context
• Per-voter CRM fields keep field feedback attached to the record

Questions