Filed under Party organizations · Part of the political campaign software guide

How CoreCNX Supports Precinct Committeepersons

CoreCNX gives a precinct committeeperson one contact record, or entry, for each person in the precinct. Each record has a timeline, which is a dated history of activity from the other CNX products: text replies from CampaignCNX+ and chatbot sign-ups, and door-visit results from Beacon and email activity. Instead of keeping what you know about your neighbors in a binder, a phone and a few spreadsheets, you keep it together on each person's record. This matters because most of a committeeperson's work involves the same voters, volunteers and election judges, election after election.

Brick houses with lawns along a curving sidewalk

CoreCNX is a CRM, meaning a shared contact database, so it does not knock on doors or send texts by itself. This post starts with what a committeeperson actually does, then shows where a single record per person helps with each part, and where it does not.

What a committeeperson does

Outside Cook County, each party's primary voters elect one precinct committeeperson per precinct at the general primary every two years (10 ILCS 5/7-8(b)). The most recent general primary was March 17, 2026. In Cook County, Chicago elects ward committeepersons and suburban Cook elects township committeepersons every four years, and precinct captains are volunteers organized by those ward and township organizations. Our post on what a precinct is explains how Illinois draws the precincts themselves.

By statute, committeepersons make up the county central committee, and each precinct committeeperson votes with one vote for each ballot cast in the precinct by the party's primary voters at the primary where they were elected (10 ILCS 5/7-8(d)). The rest of the work is what county parties typically expect:

  • Knowing the precinct: who lives there, who has moved, who can be counted on.
  • Petitions for slated candidates: carrying the party's candidates' petitions to primary voters in the precinct.
  • Turnout: making sure the party's voters get to the polls, which also sets the weight of the committeeperson's own vote.
  • Election judge recruitment: the county chair is asked to list judges who live in the precinct "insofar as possible" (10 ILCS 5/13-1), so most county parties ask committeepersons to find them.
  • Handing the precinct on: leaving useful records for the next person.

Each of those jobs depends on remembering details about people, and keeping those details is the purpose of a CRM. Our political campaign CRM guide covers the broader case. The sections below explain how it applies to a precinct.

One record per person, one timeline

What feeds one contact record

  • BeaconDoor results, appointments and contact status from the canvass
  • CampaignCNX+Texts sent and the replies that come back
  • AlmaLeads and conversations from your website chatbot
  • Your teamNotes, tags, stage changes and follow-up dates

One record per person

Matched by phone number first, then by email address. The same event sent twice is recorded once.

Beacon, CampaignCNX+ and Alma are the other products in the CNX Suite. CampaignCNX+, Beacon and Alma (on its Growth plan and up) send their activity to CoreCNX.

In CoreCNX, each person in your precinct has one contact record. Activity from the other products in the suite is added to that record's timeline:

  • Door results from Beacon, such as contacted, not home, come back later or moved, along with appointments and contact status.
  • Text replies from CampaignCNX+.
  • Chatbot leads, meaning people who sign up through a chatbot on your website, and email activity.

The result is a single history per person. When you open a neighbor's record before a petition walk, you see whether they replied to a text and what happened at their door last spring, in one place.

The connections described here between Beacon, CampaignCNX+ and CoreCNX reflect how the suite is designed to work together. If you need a specific process beyond the timeline, ask us before you rely on it.

Mapping the jobs to the record

Knowing the precinct

A committeeperson's knowledge of the precinct is usually kept in memory. A record for each person gives you a written history you can return to. When a canvasser records "moved" or "deceased" in Beacon, that result is added to the person's timeline, so your view of the precinct stays closer to current.

Petitions

Illinois candidate petitions are signed in ink on the official form with a notarized circulator statement. That process stays on paper, and CoreCNX does not change it. The timeline adds context. For example, if a canvasser recorded "signed: yes/no" as a survey answer at the door in Beacon, that answer appears on the same record as everything else you know about that voter.

Please note that a petition sheet counts as consent to receive texts only if the sheet says so plainly and the date is recorded. Do not treat everyone who signed a petition as someone you can text.

Turnout

Voting booths and check-in tables set up in a polling place

Turnout work depends on knowing which of your party's voters are certain to vote and which need a reminder. Survey answers from the door, such as "plans to vote: unsure," and replies to texts are all kept on the record. Before the primary, the people who need a second contact are easier to find because their history is in one place.

Election judge recruitment

When someone at the door says they would consider serving as an election judge, that answer is added to their record. When your county party asks for names, you are working from what people actually said, with the date they said it, rather than from memory.

Handing the precinct on

A vacancy exists when a precinct committeeperson stops living in the precinct, and they lose all rights and duties there even before a successor is named (10 ILCS 5/7-8(b)). The vacancy is filled under your party's rules, usually through the county chair. If the precinct's history is kept in the organization's CoreCNX account, the successor can start with it. We cover this in more depth in when a committeeperson moves.

Who should own the account

For a single committeeperson trying things out, a personal account is fine. For anything meant to last, the account should belong to the party organization. This is a decision your organization makes rather than a software setting, and it is the decision that keeps the precinct's history with the party when people leave.

Township and county parties that want a separate account per committeeperson or area can look at agency sub-accounts, which are separate accounts held under one Enterprise parent account. They cost $49 a month each ($39 a month with annual billing).

Pricing

CoreCNX is priced by contact count, with a 14-day trial.

  • Starter: $49 a month, 5,000 contacts
  • Growth: $99 a month
  • Pro: $199 a month
  • Enterprise: $499 a month, 150,000 contacts

Starter's 5,000 contacts is sized for a single precinct. A county party bringing many precincts together should choose a plan based on its total number of contacts. For canvassing, Beacon is at beaconcnx.com, and texting is handled by CampaignCNX+ at campaigncnx.com. See how CoreCNX fits political work more broadly on our political page.

What CoreCNX does not do

Two hands holding a smartphone

CoreCNX has the following limits:

  • It does not replace the paper petition or the circulator's notarized statement.
  • It does not decide who you may text; consent rules still apply.
  • It does not knock doors or send texts itself; Beacon and CampaignCNX+ do that, and their activity is added to the record.