Offline behaviour, voter-file formats, TCPA handling, account hierarchy, and what it costs — answered plainly.
Sovereign Field is a multi-modal field-organizing platform for political campaigns. Volunteers canvass doors, phone-bank, and place yard signs from one Progressive Web App — switching between the three modes mid-shift. Campaigns deploy at any scale: a single city-council race, a county GOP, or a whole state-party operation. Built for ground games that actually knock doors, not for spreadsheet-only operations.
Sovereign Field runs three volunteer modes (canvassing, phone banking, sign placement) from one login — competitors generally require separate tools for each. It scales from a single race to a state-party operation with no re-tooling; county and LD sub-accounts read from the state's universe through scope filters. The phone-bank flow ships TCPA-aware cell/landline separation, reliability-gated phone imports (only L2 tiers 1 and 2 enter the dialing universe), and persistent bad-number bans that survive monthly L2 refreshes. Walk lists work fully offline; knocks queue in IndexedDB and sync when service returns. Self-hosted PMTiles basemap means zero per-tile cost as volunteer count scales.
Yes. Phone banking is one of three volunteer modes alongside canvassing and sign placement — volunteers switch between them on the fly from the chip at the top of the screen. Each phone-bank list captures a 1-to-5 support stance and survey answers on every call. Bad numbers flagged during calls (disconnected, wrong number, do-not-call) get purged with a persistent ban so the same dead line doesn't re-appear on the next monthly L2 refresh. TCPA-safe: cell and landline numbers are stored separately, SMS exports pull only mobiles, and phone-bank lists dial either.
Yes. Sovereign Field uses an account hierarchy designed for state and county party operations. A state party owns the master voter universe at the top; counties, LDs, ward-level campaigns, and individual candidates read from it through automatic scope filters (county, LD, ward, ZIP). Sibling campaigns cannot see each other's knocks or call outcomes — data is walled off by default. The master account aggregates everything with full attribution per campaign. Same software at every level, no separate tools.
L2 (standard and Custom export profiles), GOPDC (GOP Data Center), and hand-built CSVs all flow through the same import path. Confidence codes (L2 numeric 1-5, GOPDC letter H/M/L/U), partisan bands (modeled or 1-5 lean), and district names normalize automatically at import. State-specific quirks (Washington top-two primary semantics, voting-history columns by year, etc.) handled in the bucket and projection logic. Imports accept up to 300,000 voters per call.
Yes. Phone numbers are stored separately as cell or landline at import based on the source vendor's classification. SMS exports pull only mobile numbers, preserving the TCPA distinction between calling (landlines allowed) and texting (mobiles only with consent). Bad numbers flagged during phone-bank calls (disconnected, wrong number, do-not-call) get a persistent ban that survives monthly L2 refreshes — the same dead line can't re-appear in your dialing queue next month. Only high-reliability phones (L2 confidence tiers 1-2 or GOPDC H) enter the dialing universe in the first place.
Each L2 refresh auto-prunes voters L2 has stopped shipping — people who moved out of state, became deceased, deregistered, or got merged/split by L2's data team. The universe self-cleans on every import; no manual SQL, no ghost rows. The same import flow preserves your prior geocode pin corrections via a cache keyed by address, so manual fixes survive monthly refreshes (L2 sometimes re-ships the original wrong coordinates, but the cached fix wins).
Yes. The volunteer app caches the assigned turf's voter pins, household notes, and basemap tiles locally before the volunteer leaves service. Knocks logged offline queue in IndexedDB and sync to the server automatically when connectivity returns. Failed writes surface for review instead of getting lost silently. Volunteers in rural areas, apartment basements, or stadiums with congested cell service can canvass uninterrupted for hours.
Yes. Sign placement is one of three volunteer modes (alongside canvassing and phone banking). Sign placers see open requests on the map, drop a pin when the sign goes up, and snap a photo for proof of placement. Admins watch placements live on the same map as door knocks. Sign placements are tracked across the campaign with photo provenance per pin.
Yes. The Ballot Bucket feature (admin-enabled per campaign, where state law permits ballot harvesting) lets canvassers pick up sealed ballot envelopes at the door, record chain-of-custody at each transfer, capture a consent confirmation and volunteer signature, and drop ballots at official drop boxes. Every pickup is GPS and photo verified. Built-in compliance audit trail.
Volunteer access is free. Campaign-side pricing scales with universe size (active voters in your file) and active volunteer count. Most local and state-legislative campaigns fall under the small-tier price; statewide and federal campaigns scale up. Contact the team via the demo form on the homepage for a quote.
Volunteers visit svrnfield.app on their phone, tap 'Add to Home Screen' from the browser share menu, and the app installs as a Progressive Web App. No app store account, no review delay, no per-device licensing. The app launches full-screen, works offline, and updates push silently the next time the volunteer opens it. Sign-in is a single-line code issued by the campaign — no passwords, no email.