The Political Campaign CRM Guide: One Record for Every Voter

A political campaign CRM keeps one record for every person your campaign or party organization works with: voters, volunteers, donors, committeepersons, and the local leaders whose support you want. Everything you learn about a person lands on that one record in date order, from the petition they signed to what they said at the door, how they answered a text, and the sign-up form they filled out on your website. Anyone on the team can open the record before the next contact and see the whole history, instead of piecing it together from three spreadsheets and a volunteer's phone.

Turning door, text, petition and form data into one voter record takes a few decisions more than it takes software. Treat each person as one record. Bring every list in through the same door and combine duplicates before volunteers start. Let the field tools write their results to the person. Write down consent with a date and a source. The record then lasts from one cycle to the next because the organization owns it, not whichever volunteer built the first list. This guide covers each step for candidates, campaign managers, county and township party organizations, precinct committeepersons and referendum committees, whatever your party and whichever side of a ballot question you are on.

What a campaign CRM actually does

Many CRMs are built around a sales pipeline. Campaign work has a different shape. A race has a fixed end date and touches many people once or twice, but underneath it sits a smaller group the organization deals with again and again for years. Precinct committeepersons walk the same streets every cycle. Candidates who run again go back to the same committeepersons, donors and volunteers. A campaign CRM has to serve both the short sprint and the long relationship.

It keeps one record per person

The basic unit is a person, not a list. A voter who signed your petition, answered a survey question at the door and replied to a text is one person with three events on their record. In a campaign without a CRM, that same voter is three rows in three files, often under slightly different names, and nobody can tell they are the same neighbor.

It keeps the history in order

Each record carries two kinds of information. Stable facts, such as name, address, precinct, phone and email, change rarely, and you want the current value. Events, such as a door result, a text reply or an opt-out, stay on the record in the order they happened. Keeping the two apart lets a volunteer see "not home twice, then contacted, said yes to a yard sign" rather than a bare label like "supporter" with nothing behind it.

It answers the questions that come up late in a race

In the last few weeks of a race, when time is shortest and the team is largest, the same questions come up. Who signed our petition? Who told us they are with us? Who asked us to stop contacting them? Which supporters have we not reached since the first canvass? Which committeepersons promised to circulate sheets, and did they get them? A CRM can answer those quickly because the answers sit on the people, not in someone's memory.

What it does not do

A CRM is a record, not the whole campaign. It does not replace the paper petition: every Illinois candidate petition is signed in ink on the official form with a notarized circulator statement, and the CRM holds a note about the paper, never the paper itself. It does not decide who you may text, because consent rules still apply. It is not the treasurer's ledger. And it does not knock doors or send texts on its own. Your canvassing and texting tools do that, and their results land on the record. Our political campaigns page shows how CoreCNX handles this for campaigns that run the full CNX suite.

Where a campaign's contact data comes from

Contact data arrives in streams, and each knows a different piece of the person. A petition sheet knows a name, an address and a signature. A canvassing app knows an address and a door result. A texting tool knows a phone number and what was said. Because none of those identifiers has the same shape, the same voter often ends up as several people.

Petition sheets

Petition season produces your first list of people who have actively done something for the campaign. Signers of an Illinois petition must be registered voters at the address shown next to their signature, and on a party primary petition they must be qualified primary electors of that party who live in the district (10 ILCS 5/7-10). That makes a signed sheet a useful record of engaged voters.

Note who signed, which sheet, who circulated it and roughly when. The paper stays the legal document, and once a petition is filed it cannot be modified or added to. There is no electronic option for an Illinois candidate petition, so the typed list is only ever a note about the sheets.

The most common mistake with petition data is treating a signature as permission to text. It is not. A petition sheet counts as consent to receive texts only if the sheet says so plainly and the date is recorded. Our post on keeping one voter record across petitions, doors and texts walks through how a signer's record should look, consent included.

Door results

Canvassing produces the most detailed data a campaign collects. In Beacon, the CNX suite's canvassing app, a door result can be contacted, not home, refused, moved, deceased, inaccessible, come back later or left literature, along with a 1 to 5 rating, notes and survey answers. During petition season, a survey question can record "signed: yes/no" at the door, so the canvass and the petition drive tell the same story.

Two results deserve special attention: moved and deceased. When they land on the person's record, whoever plans the next walk can see them and leave those doors off.

Text replies

Texting is where a merged record matters most, because the rules are strict and the stakes include your number and your reputation. Every reply and every opt-out belongs on the same record as that person's door results. CampaignCNX+, the suite's texting tool, handles STOP replies automatically and keeps a shared two-way inbox for your team. For contacts added through its API or by texting START, it records the consent date and source. Our sister product's guide to political texting covers the texting side in full.

Campaign Verify is required for political texting on 10DLC, toll-free and short code numbers by candidates, parties, PACs and committees registered with an election authority, and it needs an EIN and a published election-authority filing. A candidate with no committee is not eligible, and neither is an individual committeeperson texting personally, though a county or township party committee with an EIN and a filing can be verified. If you are not sure whether your campaign has a filing yet, our explainer on when an Illinois candidate needs a campaign committee covers the $5,000 threshold and the D-1 deadlines.

Forms, sign-in sheets and your website

The last stream is the widest: volunteer sign-up forms, event sign-in sheets, emails people answer, and questions visitors ask on your website. A website chatbot such as Alma captures leads from visitors, and in CoreCNX, chatbot leads and email events are among the events that write to a contact's timeline. Paper sign-in sheets follow the same consent rule as petitions.

How the streams become one voter record

Joining the streams is mostly about doing a few things in the right order. Skip the order and you end up with a CRM full of duplicates, which is the original problem inside a new tool.

Start with your best list

Pick the most complete, most trusted list you have, often a voter list from your county party or your own cleaned-up supporter file, and import it first. Then add each other list one at a time, combining overlapping entries as you go, rather than pouring everything in at once.

Match on phone and email, never on a name alone

Two entries are the same person when they share a phone number or an email address. Phone is usually the stronger match, because shared family inboxes and addresses like info@ break the idea that one email means one person. Matching on name and street is how two different people get fused into one record. The two mistakes are not equal: a missed merge leaves a duplicate you can fix later, while a wrong merge mixes two people's histories in a way that is hard to undo. When in doubt, keep them separate. Our companion guide to the unified contact timeline goes deeper on matching, merging and why this order matters.

Keep stable facts and events apart

Decide before the first import which columns are facts about the person (name, address, precinct, phone, email) and which are events (signed a petition, a door result, a text reply, attended an event). Facts get updated. Events get added and are never overwritten, because an event you can quietly change is no longer evidence of anything. That matters most for opt-outs. The record that someone asked you to stop is the one you most need to keep.

Let the field tools write to the person

Once the base list is in, the cleanest way to keep the record current is to let the tools that do the work write their results to the person, rather than reconciling a weekly spreadsheet from each tool by hand. In the CNX suite, CoreCNX holds that record, and its unified contact timeline is the spine of the suite. Beacon for doors, CampaignCNX+ for texts and Alma for website conversations are designed to write to it.

Put consent on the record, with a date and a source

For every phone number, note where it came from and when consent was given: a sign-up form with clear texting language, a sign-in sheet that said so, or a reply in which the person asked to hear from you. Keep it on the person's record, not in a separate file someone forgets to check, and build your texting list only from people who agreed.

Note where each piece came from

Every fact and event should say where it came from: which sheet, which canvass, which form. When two sources disagree, the source and the date tell you which to trust, and when a voter asks where you got their number, you can answer plainly.

Making the record survive from cycle to cycle

A campaign that starts over every cycle from a blank spreadsheet throws away its most valuable asset. The record is worth the most in its second and third cycle, when it already knows your reliable volunteers, your friendly doors and who asked not to be contacted.

The calendar guarantees turnover

In Illinois, the people in party roles change on a schedule. 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)). In Cook County, Chicago voters elect a ward committeeperson per ward and suburban Cook voters elect a township committeeperson per township every four years, and precinct captains are volunteers organized by those ward and township organizations. Staff and volunteers turn over even faster.

The organization owns the account

Set up the CRM, the canvassing tool and the texting tool under the campaign committee or the party organization, never under a volunteer's personal email or credit card. Give at least two people administrator access. Volunteers get access to the work they do, not ownership of the list. That one decision is what keeps a precinct's history from leaving when its committeeperson does.

Plan the handoff before anyone moves

A precinct committeeperson who moves out of the precinct creates a vacancy right away. The statute says the person loses all rights and duties in the precinct 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 already lives in the organization's account, the successor starts with it. Our post on what happens when a committeeperson moves includes a handoff checklist that works on paper or in software.

Close out each election on purpose

After election day, decide whether the record carries forward to the next race, passes to a successor, or closes. Export a full copy so the data is never stuck in one tool, and keep opt-outs and "do not contact" notes with the records wherever they go. When an old list comes back in for the next cycle, give its entries their real dates. A history with invented dates misleads everyone who reads it.

Who keeps a campaign CRM, and what they use it for

The same record serves different jobs depending on who is working it.

Candidates and campaign managers

For a candidate in a partisan race, some of the most important records are not voters at all but committeepersons. On the county central committee, each precinct committeeperson has 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)), so some carry far more weight than others. They also know which doors belong to the party's primary voters, which makes them valuable circulators. Our post on why candidates court committeepersons explains what they control, and our step-by-step plan for meeting the committeepersons in your district runs from the first coffee through the primary.

Many county and township parties also slate candidates before a primary. Slating is a party practice rather than a procedure the Election Code sets out, and a slated candidate still has to file a valid petition and win the primary. Our explainer on how local parties slate candidates covers who decides and what to ask. Through all of it, every conversation, ask and commitment belongs on the committeeperson's record, so the follow-up happens when you said it would.

Precinct committeepersons

A committeeperson's work is about people they will see again: the same voters, the same volunteers, the same election judges. Most county parties ask committeepersons to recruit judges for their precinct, because the county chairs furnish the judge lists and are asked to list people who live in the precinct "insofar as possible" (10 ILCS 5/13-1). A record per neighbor turns that knowledge into something a successor can inherit. Our post on how CoreCNX supports precinct committeepersons maps each part of the role to the record, and Beacon's precinct committeeperson handbook covers the role itself, from the statute to walking the precinct.

County and township party organizations

The county central committee is made up of the party's township, precinct and ward committeepersons in the county (10 ILCS 5/7-8(d)), so a county party's strength is the sum of its precincts. With one account, the county party can see which precincts are organized, which are vacant and who said yes to serving as an election judge. Larger organizations often want separate workspaces for townships or wards, and consultants managing several campaigns need the same. Our agency page explains how an Enterprise parent account holds client sub-accounts, and our guide to running the county party's data in one CRM shows how to set it up for every committeeperson.

Referendum committees and coalitions

A referendum coalition often brings several groups together, each with its own list, for a few months on one question, so the first job is turning those lists into one record per person. Two rules shape the work. 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). And a group that raises or spends more than $5,000 in any 12-month period for or against a question generally must file a Statement of Organization with the Illinois State Board of Elections (10 ILCS 5/9-3). Our post on CoreCNX for referendum coalitions and party organizations includes worked examples. Confirm your own obligations with ISBE or an election attorney.

Running the job in CoreCNX

CoreCNX is the CRM in the CNX suite: one contact record per person, with a timeline that door results, text replies, chatbot leads and email events write to. Here is how to set it up and run a cycle in it.

1. Open the account in the organization's name. Start the trial under the committee or party organization, not a personal account, and make at least two people admins. Give your campaign manager or county office the manager role, and volunteers and committeepersons the user role.
2. Pick the plan by contact count. Starter is $49 a month for up to 5,000 contacts, Growth is $99 for 15,000, Pro is $199 for 50,000, and Enterprise is $499 for about 150,000. An Enterprise parent can hold sub-accounts for townships, wards or clients at $49 a month each. As an example, a campaign keeping 3,000 people fits Starter, while a county party bringing many precincts together should size by its total.
3. Import your best list first. Clean it in a spreadsheet, one row per person, with name, address, precinct, phone and email in their own columns, then import it as a CSV. Combine overlaps before each later import.
4. Bring in petition and sign-up lists the same way. Type up signers with sheet number and circulator, and sign-ups with their date. Fill a texting-consent column only where the sheet or form said so plainly and was dated.
5. Walk with Beacon. Beacon puts walk lists on a map, optimizes routes door to door, works offline and syncs, and includes unlimited canvassers on every plan. The suite is designed so that Beacon's door results, appointments and contact status land on the person's CoreCNX timeline.
6. Text through CampaignCNX+. Send to supporters who agreed to receive texts. CampaignCNX+ is designed to write their replies to the same timeline, beside the door results.
7. Connect your website chatbot. Leads from a chatbot such as Alma land on the timeline too, so a site visitor is not a stranger at the door.
8. Open the record before every contact. Before a callback, a second knock or a committeeperson meeting, read the person's timeline.
9. Export at the end of the cycle. CoreCNX exports to CSV, so the organization keeps a full copy and decides what carries forward.

Start with the list you already have

You do not need a perfect list to begin. Take the file you trust most, whether that is last cycle's supporters, a precinct list or a coalition partner's sign-ups, and put it in an account your organization owns. Start a 14-day CoreCNX trial, import that one list, and see how a single record per person changes the way your team plans its next walk.