Questions, plainly answered.

Hub3 is a civic-tech outfit that shares the resources we use internally -- strategy docs, precinct and household maps, and contact-sync help -- with individual organizers and small teams working on health, wealth, and power in North Carolina. We also run the Field Targeting System, a precinct-level data and dashboard platform for NC county chairs.

Individual organizers, small teams, and grassroots civic groups working in North Carolina. We're built for people who do the work themselves. We're not a vendor and not a campaign; we're the floor, not the ceiling.

Three things, plus the Field Targeting System.

• Strategy docs. The long-cycle organizing memos and county-level priority frameworks we use internally.
• Maps. Precinct and household maps for the NC counties we cover.
• Contact sync. Help pulling your contacts, voter-file matches, and friend-of-friend lookups into one workable list -- local files, no cloud upload.

The Field Targeting System is the larger dashboard product for county chairs, sitting alongside.

For individual organizers and small NC teams, yes. We share what we already have. If your ask is large enough that we'd need to build new infrastructure, tell us what you're trying to do and we'll figure out scope together.

Yes. The Field Targeting page has a redacted county-packet request form, and we can send a sample strategy doc or map on request. Ask here.

Today it covers 11 NC counties. Adding a county is config-first; adding a state is a larger lift and on the roadmap.

Statewide public voter and voter-history files, official polling-place files, AddressNC, NC OneMap precinct boundaries, and cached Census geocoder responses for fallback. No paid APIs.

No. Local mode reads and writes local files only. No voter data is sent to any third-party map or AI service.

Yes -- that's what redacted demo mode is for. Names, addresses, NCIDs, and phone numbers are masked; exact household coordinates are jittered or aggregated; sensitive PDFs are disabled. Aggregate counts and workflow behavior stay intact so the system reads the same.

No. The dashboard is built for county and precinct chairs. The chair workflow is five steps: pick a county and precinct, review priority doors, route a shift on the map, print the playbook, check provenance.

Every build regenerates the dashboard from scratch and writes a run log. The Audit view in the dashboard shows source directories, generation timestamps, and provenance before any chair acts on an output.