Ballot access operations

Organize petition work with clear boundaries.

CampaignOS can support signature collection planning and operational review. It does not certify legal compliance, signer eligibility, petition validity, or submission readiness.

Campaign volunteers organizing paper petition sheets, review records, and a district map
Controlled betaKeep paper petition work organized, traceable, and ready for human review.
  • Goals, sheets, records, and exports
  • Human review remains required
  • No legal certification claims

Operational support

Build a clearer campaign record around petition work.

These tools support organization and review. Official paper requirements, election authority guidance, and qualified counsel remain controlling.

Beta

Goals and safety margin

Configure the minimum, internal target, stretch target, collection window, and campaign planning buffer.

Beta

Petition sheet custody

Create and assign individual petition sheets, follow their field and return status, and preserve the paper-first chain of custody.

Beta

Signature records and review

Track line-level records, sources, collectors, zones, review states, rejection reasons, notes, and possible duplicates.

Beta

Progress, field context, and exports

Connect campaign-reported progress with field activity, events, QR sources, and operational exports without presenting official certification.

Operating boundary

Campaign software does not decide ballot eligibility.

CampaignOS is an operational system. Campaign teams remain responsible for official forms, signer requirements, filing deadlines, legal review, and submission decisions.

  • No ballot-access guarantee
  • No signer eligibility certification
  • No official petition-validity certification
  • No substitute for election officials or qualified counsel

Start with the proven path

Start with the campaign workspace.

Create the first campaign tenant, then evaluate beta ballot-access workflows against your jurisdiction and counsel.