Committeepersons

Running 100 Precincts From One Map: For Township and County Parties

A township or county party can run its precincts from one map by putting every precinct's walk list in one shared canvassing account, dividing the ground into territories that match how the organization is actually structured, and letting each committeeperson and volunteer work their own piece while the organization sees the whole picture. The software matters less than the setup: one account owned by the organization, territories drawn to match precincts, and the same result codes used everywhere.

Beacon is built for that kind of setup. It has territory management, unlimited canvassers on every plan, real-time tracking, and analytics across the account. This guide covers how to organize it, written for party organizations of any affiliation, and is plain about what software can and cannot do for you.

Why one map instead of a hundred binders

Most county parties already have the people. What they lack is a shared picture. Each committeeperson keeps their own notes, in their own format, and the organization learns what happened in a precinct only if someone remembers to report it.

That gap has real costs:

• Turnout is hard to see in advance. In the county central committee, 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)). Turnout in each precinct shapes the organization itself, yet most parties cannot see door-level progress until it is over.
• Uncovered precincts stay invisible. If a precinct has no committeeperson, or a committeeperson who has stopped walking, nobody notices until the primary.
• Judge recruitment is scattered. Election judges are appointed from certified lists furnished by the two leading parties' county chairs, and the chair is asked to list people who reside in the precinct "insofar as possible" (10 ILCS 5/13-1). Most county parties ask committeepersons to recruit those names, then chase them by phone.
• History leaves with people. When a precinct committeeperson stops living in the precinct, a vacancy exists and they lose their rights and duties there even before a successor is named (10 ILCS 5/7-8(b)). If their notes were personal, the precinct starts over.

For a fuller look at the role and its structure across Illinois, see our precinct committeeperson guide.

Structure first: who your map serves

The shape of your map depends on where you are.

Outside Cook County, each party's primary voters elect one precinct committeeperson per precinct every two years, and the county central committee is made up of those precinct committeepersons along with any township and ward committeepersons in the county (10 ILCS 5/7-8(b), 7-8(d)). A county party there typically thinks in precincts, sometimes grouped by township.

In Cook County, there are no elected precinct committeepersons. Chicago elects ward committeepersons and suburban Cook elects township committeepersons every four years. Precinct captains are volunteers organized by the ward or township organization. A ward or township organization there thinks in precincts too, but the people walking them are captains and volunteers rather than elected officers.

Either way, the map should mirror the organization people already recognize.

Setting up territories

Territory management is how you divide one large map into pieces people can own. A practical approach:

1. Make each precinct a territory. It is the unit committeepersons and captains already know.
2. Group precincts the way your organization groups them, by township, ward or region, so area leaders can see their part.
3. Decide who is responsible for each territory. Usually the committeeperson or captain, with the organization stepping in where a precinct is open.
4. Keep a list of open precincts. A precinct with nobody responsible for it is a recruiting target, not an afterthought.

Keep territories stable from cycle to cycle. The value of a shared map grows with history, and redrawing everything each spring throws some of that away.

Agreeing on what gets recorded

A shared map only works if everyone records doors the same way. Beacon's door results give you a common vocabulary out of the box: contacted, not home, refused, moved, deceased, inaccessible, come back later, and left literature. Each door can also get a 1 to 5 rating, notes, and survey answers.

The survey builder is where an organization can standardize the questions that matter county-wide. A short, consistent set might include:

• Plans to vote in the next primary: yes, no, unsure
• Interested in serving as an election judge: yes, no, maybe
• Willing to volunteer: yes, no
• For petition drives, "signed: yes/no"

Write a one-page guide for committeepersons on what each result means locally. "Come back later" should mean the same thing in every township.

A note on petitions: Illinois candidate petitions are signed in ink on the official form with a notarized circulator statement. Beacon can route circulators door to door, record which doors were visited and the result, and capture "signed: yes/no" as a survey answer. The paper process stays exactly as the law requires.

Bringing everyone onto the map

Beacon includes unlimited canvassers on every plan. For a party organization that is the deciding detail: you can add every committeeperson, captain and volunteer without counting seats, and the plan is priced by the number of contacts instead.

Field features that help when many people are walking at once:

• Walk lists on a map with route optimization, so a volunteer new to a precinct still walks it efficiently.
• Offline mode with sync, for rural precincts and spotty blocks.
• Real-time tracking, so area leaders see results as they come in.
• Live GPS and geofencing on Growth and above, for organizations that want them.
• An AI script coach as an add-on, if you want help with what volunteers say at the door.

For texting opted-in supporters, the suite's texting tool is CampaignCNX+ at campaigncnx.com.

The organization-level view

Analytics is where one map pays off for leadership. Because every precinct records results the same way, the organization can see, across the whole account, how many doors have been reached and what they said, and spot where work is moving and where it has stalled.

Questions that view helps answer:

• Which precincts have not been walked this season?
• Where are "unsure" primary voters concentrated?
• Which precincts have produced judge candidates, and which have none?
• Where did "moved" and "deceased" results pile up, suggesting the list needs attention?

None of this replaces talking to your committeepersons. It gives those conversations a starting point.

Keeping precinct history with the organization

The single most useful decision a party organization can make is that the account belongs to the organization, not to any one person. When a committeeperson moves or steps down, the vacancy is filled under your party's rules, usually through the county chair, and the incoming committeeperson inherits the precinct's door history instead of a blank sheet. For the precinct-level habits that make that history worth inheriting, see knowing every door in your precinct.

Organizations that also want one contact record per person across doors, texts and other sources can pair Beacon with CoreCNX, the suite's CRM, at corecnx.com.

Sizing the plan

Beacon is priced by contacts, with unlimited canvassers on every plan.

Starter is sized for a single precinct. An organization with many precincts should add up its contacts across all of them and choose Growth or higher on that basis.

Start with a few precincts

You do not need all 100 precincts on day one. Start a 14-day Beacon trial, set up a handful of precincts as territories, invite the committeepersons who walk them, and agree on the result codes. If the organization-level view tells you something you did not know after two weeks, add the rest. Start your 14-day trial.