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

CoreCNX for Referendum Coalitions and Party Organizations

CoreCNX is a CRM, meaning a shared contact database. It gives a referendum committee or a party organization one contact record per person, which is a single entry holding that person's details. Each record has a timeline, a dated history to which text replies and chatbot sign-ups are added, and door-visit results and email activity. Instead of a petition spreadsheet, a volunteer sign-up sheet, a text list and a donor list that rarely match, everyone works from one record of who each person is and every interaction they have had with the group. For organizations with several units, such as a county party with township organizations, Enterprise accounts can include sub-accounts. These are separate accounts under one main, or parent, account, so each unit has its own space.

A sign pointing to an official ballot drop box

This post explains what that looks like for the two groups that most need it: coalitions that come together for a single ballot question, and party organizations that canvass the same precincts election after election. It ends with pricing plans and worked examples.

Our political campaign CRM guide covers how a campaign CRM fits into the rest of a campaign.

Why these two groups have the same problem

A referendum coalition and a party organization look different, but they share a record-keeping problem. Many people collect information about the same voters, at different times, using different lists and programs.

  • A referendum coalition might include parents, a booster club, neighborhood associations and local business owners, all working on one question for a few months. Each brings its own list. By the time early voting opens, it is often unclear which of the 600 names on the combined sheet are actually supporters.
  • A party organization has committeepersons in every precinct, each with their own notes, plus a county or township office trying to see the whole picture. When a committeeperson moves out of the precinct, the office becomes vacant (10 ILCS 5/7-8(b)), and if their notes were kept privately, the organization loses the precinct's history when they leave.

A shared contact record addresses both problems. It gives each person one entry, and the history belongs to the organization rather than to whoever collected it.

For referendum coalitions

A person signing papers at a table

The rules that shape your data

A referendum campaign is usually run by a committee of residents, not by the public body that put the question on the ballot. Public funds may not be used to urge a vote for or against a public question, though factual information is allowed (10 ILCS 5/9-25.1). Groups that raise or spend more than $5,000 in any 12-month period for or against a public question generally must file a Statement of Organization (Form D-1) with the Illinois State Board of Elections (10 ILCS 5/9-3). Confirm your obligations with ISBE or an election attorney, and keep your financial records in the form your treasurer uses for ISBE reports.

For the April 6, 2027 election, citizen petitions for a question were due January 4, 2027, and questions are certified by January 28. Early voting opens February 25 (or March 12 where a February primary ran).

How CoreCNX helps

  • Bring every list in. Each partner saves its list as a CSV file (a simple spreadsheet format that most programs can open), and you import, or load, it into CoreCNX. CoreCNX can also export your contacts to a CSV file, so you can always take your data elsewhere.
  • One record per person. When three coalition partners each bring a list, set the rule that each person is one contact, and combine duplicate entries for the same person before volunteers begin. After that, the timeline shows each interaction, such as a text reply or a chatbot sign-up.
  • Door results on the timeline. CoreCNX is designed to work with Beacon, the canvassing app, as part of one suite. Door-visit results are among the items added to a contact's timeline, so a volunteer can see that someone was "undecided, worried about the tax bill" before calling or knocking again.
  • Text replies on the timeline. CoreCNX is likewise designed to work alongside CampaignCNX+ for texting. When a supporter replies to a text, that reply becomes part of their record as a dated event; its words stay in CampaignCNX+.
  • Chatbot sign-ups and email activity. If your coalition's website has a chatbot (an automated chat window) that collects sign-ups, those sign-ups are added as contacts (Alma sends them on its Growth plan and up), and email activity appears on the timeline.
  • Consent on the record. Keep a note of when and how each person opted in to texts, meaning they gave permission to receive them. A petition signature does not give permission to text. A sign-up sheet counts as consent only if it says so plainly and the date is recorded. The contact record is a sensible place to keep that date.

A worked example: one-question coalition

Residents talking together during a meeting

This example is an illustration and not a price quote.

A coalition is supporting a school facilities question on the April 6, 2027 ballot. It has four partner groups, one committee and around 3,000 contacts once the lists are combined.

  • Plan: Starter, $49 a month for up to 5,000 contacts.
  • Months: January through April, four months.
  • Cost: 4 × $49 = $196 for the campaign.
  • Process: Partners' lists are imported as CSV files in January. Volunteers work from one shared record through the persuasion period and early voting. Afterward, the committee closes the account or keeps it for the next question.

If the coalition expects to return for a future question, keeping the records means it can begin the next campaign already knowing who its supporters are.

For party organizations

The rules that shape your data

Outside Cook County, each party elects one precinct committeeperson per precinct at the general primary every two years; the most recent was March 17, 2026. In Cook County, Chicago elects ward committeepersons and suburban Cook elects township committeepersons every four years (10 ILCS 5/7-8(b)). Committeepersons make up the county central committee, and each votes with a weight equal to the ballots cast in their precinct by the party's primary voters at the primary where they were elected (10 ILCS 5/7-8(d)). Most county parties also ask committeepersons to recruit election judges, since the county chairs furnish the judge lists and are asked to list precinct residents where possible (10 ILCS 5/13-1).

All of this work depends on knowing people, including voters, volunteers, possible election judges and candidates.

How CoreCNX helps

  • A precinct history that stays with the precinct. When the account belongs to the organization, a committeeperson's notes, and their door results, stay with the party when they move. A vacancy is filled under your party's rules, usually through the county chair, and the successor receives the existing records instead of starting with nothing.
  • Roles. Roles control what each person can see and change. Give the county or township office the admin or manager role and give committeepersons the user role, so each person has the access their job needs.
  • One view across precincts. The county or township office sees every contact and every timeline, so it can find, for example, every person in the county who said yes to serving as an election judge.
  • Sub-accounts for units. On Enterprise, the county party can be the parent account, with township organizations or regional committees as sub-accounts. Each unit manages its own contacts within the parent account.
  • The rest of the suite. Beacon, used for canvassing precincts, and CampaignCNX+, used for texting supporters who have opted in, are designed to add their results to the same contact timeline.

For a longer look at the county-party setup, see running the county party's data: one CRM for every committeeperson. For how one record carries a voter from petition season through doors and texts, see one voter record across petitions, doors and texts.

A worked example: county party with townships

A red barn and a small shed in an open field under a pink and purple sunset

This example is an illustration and not a price quote.

A county party has eight township organizations, and each one wants its own separate account.

  • Parent: Enterprise, $499 a month, sized for about 150,000 contacts.
  • Sub-accounts: 8 × $39 a month on annual billing = $312 a month (or 8 × $49 = $392 a month billed monthly).
  • Monthly total: $811 on annual sub-account billing, or $891 monthly.

A smaller township organization working on its own would more likely start on Starter ($49 a month, 5,000 contacts), then Growth ($99, 15,000) or Pro ($199, 50,000) as it adds precincts.

Plans at a glance

Plan Monthly Notes
Starter $49 Up to 5,000 contacts
Growth $99 Up to 15,000 contacts
Pro $199 Up to 50,000 contacts
Enterprise $499 About 150,000 contacts (an approximate limit); can hold client sub-accounts
Sub-account $49 ($39 annual) Each, under an Enterprise parent

Every plan has a 14-day trial. Our agency page explains how parent and sub-accounts are set up for organizations with several units.

Questions to settle before you start

  • Who owns the account? The account should belong to the committee or the party organization rather than to an individual. That decision keeps the history in place when people change roles.
  • Who can see what? Decide which volunteers work which contacts before you invite them.
  • What counts as consent? Write down your rule for text opt-ins and record the date on each contact.
  • What happens after the election? For a coalition, decide whether to keep the record for a future question. For a party, keeping the record is the main purpose, because it carries forward into the next primary.