It is a CRM, so it does not knock doors or send texts on its own. 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.
The committeeperson's real jobs
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.
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 something useful for the next person.
Each of those jobs depends on remembering things about people. That is the part a CRM is for. Our political campaign CRM guide covers the broader case; here is how it applies to a precinct.
One record per person, one timeline
The core idea in CoreCNX is simple. Each person in your precinct has one contact record. Activity from the suite lands on that record's timeline:
- Door results from Beacon, such as contacted, not home, come back later or moved, along with ratings, notes and survey answers.
- Text replies from CampaignCNX+.
- Chatbot leads and email events.
The result is a single history per person. When you open a neighbor's record before a petition walk, you see what happened at their door last spring and whether they replied to a text, in one place.
We describe the connections between Beacon, CampaignCNX+ and CoreCNX as the way the suite is designed to work together. If you need a specific workflow beyond the timeline, ask us before you rely on it.
Mapping the jobs to the record
Knowing the precinct
A committeeperson's knowledge usually lives in memory. A record per person turns it into something you can return to. When Beacon logs "moved" or "deceased" at a door, that lands on the person's timeline, so the precinct picture stays closer to current.
Petitions
Illinois candidate petitions are signed in ink on the official form with a notarized circulator statement. That part stays on paper, and CoreCNX does not change it. What the timeline gives you is context: if a canvasser recorded "signed: yes/no" as a survey answer at the door in Beacon, it sits on the same record as everything else you know about that voter.
A caution on contact: 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
Turnout is about knowing which of your party's voters are solid and which need a nudge. Survey answers from the door, such as "plans to vote: unsure," and replies to texts all live 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 lands on 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 lives in the organization's CoreCNX account, the successor starts 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. That is not a feature; it is a decision your organization makes, and it is the one that keeps precinct history from walking out the door.
Township and county parties that want a separate account per committeeperson or area can look at agency sub-accounts, which run $49 a month each ($39 a month annual) under an Enterprise parent account.
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 size by total contacts. For the canvassing side, Beacon is at beaconcnx.com, and texting runs through CampaignCNX+ at campaigncnx.com. See how CoreCNX fits political work more broadly on our political page.
What CoreCNX does not do
To set expectations plainly:
- 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 lands on the record.
Try it with your precinct
The best way to judge a CRM is to put real people in it. Start a 14-day CoreCNX trial, add the people in your precinct, and see whether having one record per neighbor changes how you plan your next walk. Start your 14-day trial.