Do I really need a campaign database, or can I use a spreadsheet?

For a very small campaign (say, a single precinct race where you're making a few hundred contacts) a spreadsheet might be manageable. For anything larger, a purpose-built campaign database will save significant time and produce better results. The main advantages are multi-user access without version conflicts, structured tracking of support levels and survey responses, and the ability to filter your contact list to build targeted universes instantly. The cost of most campaign database platforms is low enough that it's rarely worth the operational friction of trying to run a real campaign out of a spreadsheet.

How is a campaign database different from a regular CRM?

A general CRM (customer relationship management) tool is built for business contact management like tracking leads, deals, and customer interactions. A campaign database is built for campaigns: it's designed to import and work with voter files, track canvassing outcomes, generate walk lists, manage volunteer shifts, and produce campaign finance compliance reports. Some campaigns use general CRMs and work around the gaps, but a purpose-built campaign database will handle the workflows campaigns actually use more cleanly.

What is a support level, and how do I use it?

A support level is a number you assign to a voter contact based on what you learn about their likelihood of supporting your campaign – typically on a 1-to-5 scale, where 1 means strong support and 5 means strong opposition. Support levels come from ID conversations: when a canvasser or phone banker talks to a voter and asks who they're supporting, that response gets translated into a support score. Your GOTV universe is drawn from your 1s and 2s. Your persuasion universe is your 3s. Your 4s and 5s generally don't get more resources. The support level system only works if canvassers use it consistently, and score-creep (everyone becoming a 1 or 2) is a risk on campaigns where volunteers want to report good results.

Who should have access to the campaign database?

Most campaigns give full access to senior staff and their campaign manager, and limited access to volunteers. Most campaign database platforms support role-based permissions, so you can give a canvassing volunteer access to their walk list and the ability to log contacts without being able to see donor records or change settings. At minimum, anyone who's logging contacts should be able to do so in real time. Anyone who's building universes or generating lists should have the appropriate access to filter and export. Keep sensitive records (donor information, personal notes on specific voters) on a need-to-know basis.

How do I get a voter file?

Voter files come from a few sources depending on your state and party affiliation. Your state or county Democratic or Republican party committee often provides access to the party's voter file, though they may charge a fee or set limitations on how it can be used. State election authorities typically provide voter registration data directly, sometimes for a fee. Commercial voter data vendors sell enhanced voter files with additional modeling data. The right path depends on your party, your state, and your budget. See the voter file guide for more detail.

What happens to my campaign database after the election?

What you do with your data after the election depends on your jurisdiction's rules, your party's data agreements, and what you plan to do next. If you're running again, your data is an asset, and the support scores, interaction history, and volunteer relationships you've built are a foundation for the next campaign. If you're not running again, consider whether to transfer your data to your local party committee (who can use it to support future candidates) or to another candidate you're supporting. Check your platform's terms of service and any party data agreements before making decisions about data transfer or deletion.

How to Run for Office · Section 17 of 17

Campaign Database: How to Manage Your Voter and Supporter Data

A campaign database is the system where you store and manage every contact, conversation, and commitment your campaign collects, from voter file records and canvassing notes to volunteer sign-ups and donor history. Unlike a spreadsheet, a purpose-built campaign database lets multiple team members work simultaneously, tracks the full history of every interaction, and lets you filter your contact list to build precisely targeted universes for any phase of your campaign. This guide explains what belongs in your database, what capabilities to look for, how to set it up, and how to use it from launch through election day.

Why a spreadsheet isn't enough

Many first-time candidates start with a spreadsheet. It's free, familiar, and fine for a very small operation. But campaigns grow fast, and spreadsheets don't scale well.

The core problem is that a spreadsheet stores data – names, phone numbers, a note in a cell – but doesn't track relationships or history. When two volunteers are working from the same file, they can overwrite each other's work. When a voter moves from "unknown" to "confirmed supporter," there's no record of when that happened or who made the contact. When you need to pull a list of supporters in a specific precinct who haven't been contacted in two weeks, you're doing that manually.

A campaign database handles all of this automatically. Every contact gets a record. Every interaction gets logged with a timestamp and the name of who made it. Filters let you slice your contact list any way you need. Multiple users can work at the same time without creating conflicts. And when get-out-the-vote (GOTV) begins and you need to know exactly who has voted and who hasn't, you're not digging through a spreadsheet – you're running a filter.

Spreadsheet compared with a campaign database
Capability	Spreadsheet	Campaign database
Storing contacts	Can list names, phones, addresses	Stores full contact profiles with history, relationships, and custom fields
Logging interactions	Manual notes in a cell; no structure	Every door knock, call, and text logged with date, outcome, and who made contact
Tracking support	A number in a column; no history	Support scores with full history; filterable by score, geography, voting history
Building contact lists	Manual filtering and sorting	Filter by any combination of fields to build targeted universes instantly
Volunteer management	Separate spreadsheet (usually)	Same database: sign-ups, shifts, roles, contact history all in one place; understand overlap between volunteers/donors/voters
Email and texting	Export to a separate tool	Send directly from the database; responses logged back to contact records
Fundraising	Track in a separate spreadsheet	Donor records, donation history, and compliance reporting in one place
Multiple users	Conflict and version risk	Multiple users can work simultaneously; permissions control what each can see or edit

The transition from spreadsheet to database doesn't have to happen all at once. Many campaigns start in a spreadsheet and migrate to a proper database once they have the budget or once the complexity of their operation demands it. But the earlier you make the switch, the more valuable your data becomes – every contact logged from day one is data you'll have available in the home stretch of the campaign.

What your campaign database stores

A campaign database is built around contact records (one record per person) with everything your campaign knows about that person attached to it. Here's what those records will typically contain:

Contact information

The basics: name, address, phone, email. For voters, much of this comes from your voter file import. For supporters and volunteers who find you through your website or events, it's captured when they sign up. Contact information should be updated whenever you learn something new, like a phone number that's no longer active, a new email address, or a change of address.

Voter file data

For registered voters, the record includes the data from your voter file: party registration, voting history (which elections they voted in, not how they voted), precinct, district, and any demographic fields your state's voter file includes. This is the foundation for targeting, allowing you to identify likely voters, build persuasion universes, and prioritize GOTV contacts.

Support level

Support level is how your campaign records where a given voter stands relative to your candidate. Most campaigns use a simple scale – typically 1 through 5, where 1 means strong support and 5 means strong opposition – assigned based on what canvassers or phone bankers learn in ID conversations. Support level is what you use to build your GOTV universe (contacts scored 1 or 2) and your persuasion universe (contacts scored 3).

Support levels should be updated whenever new information comes in. A voter who was scored as a 3 (undecided) in March might be a 1 (strong supporter) after a conversation in September. That movement is useful data, telling you that your persuasion effort is working.

Survey responses and tags

Survey questions let you record specific information about a voter beyond their support level: which issues they care about, whether they've committed to volunteering, whether they've requested a yard sign, whether they've been asked for a donation. Tags are flexible labels that let you group contacts however your campaign needs – by neighborhood, by issue interest, by which events they attended.

Both are most valuable when they're used consistently. If canvassers record "interested in schools" differently on different days (sometimes tagging, sometimes writing a note, sometimes not recording it at all), you can't filter on it reliably. Decide before your first canvass what you're tracking and how, and make sure every volunteer who logs contacts follows the same approach.

Interaction history

Every contact your campaign makes with a person – every door knock, phone call, text, email, event attendance – should be logged to their record. This creates a complete picture of the relationship: when was this person last contacted, by what method, what was the outcome, and who made the contact.

Interaction history is what prevents you from calling the same person five times in a week or canvassing a door that was already canvassed yesterday. It's also what lets you identify your most-engaged supporters and treat them differently from cold contacts.

Volunteer and donor data

For people who have volunteered or donated, the record captures that history: which shifts they worked, which events they attended, how much they've given, when their last donation was. This data drives volunteer recruitment (who have been your most reliable volunteers?), fundraising (who are your consistent donors? Who made a first gift and hasn't given again?), and leadership development (who is ready for more responsibility?).

What to look for in campaign database software

Not all contact management tools are built for campaigns. A general CRM (customer relationship management) tool can handle contacts and notes, but it won't have a voter file import, precinct-level filtering, canvassing walk list generation, or donation tracking in a way that's optimized for campaigns. When evaluating campaign database software, look for these capabilities:

Voter file import. The ability to import your state or county voter file and have that data populate contact records. Without this, you're building your database from scratch rather than starting from a foundation of registered voters.
Support levels and survey questions. Structured fields specifically designed for tracking voter contact outcomes – not just freeform notes.
Targeted list building. Filtering across any combination of fields (geography, voting history, support level, tags, last contact date) to build contact universes for canvassing, phone banking, GOTV, and other programs.
Walk list and call list generation. The ability to generate organized lists for canvassers (sorted by address for efficient routing) and phone bankers (sorted by phone number or other criteria) directly from your filtered universe.
Mobile canvassing integrations. A mobile app or mobile-optimized interface that lets canvassers log contacts and survey responses at the door, with data syncing back to the main database in real time.
Multi-user access with permissions. Multiple staff and volunteers should be able to use the database simultaneously, with permission controls that determine what each person can see or change.
Email and texting integration. The ability to send communications directly from the database (so responses and engagement data flow back to contact records) rather than exporting to separate tools and manually syncing data.
Volunteer management. Sign-up pages and tools to capture shift RSVPs in the same system that stores your donor and voter information.
Fundraising and donor management. Donor records, giving history, and concepts like per-cycle donation tracking – ideally in the same platform rather than a separate tool. Capturing donation data in compliance-friendly format will save time and worry.

Setting up your campaign database

Getting your database set up correctly at the start of the campaign saves significant time later. The three most important steps are importing your voter file, configuring your tracking fields, and building your initial contact list.

Import your voter file

Your voter file is the foundation of your database. Once imported, every registered voter in your district has a record, pre-populated with their address, phone, voting history, party registration, and precinct. You're building on top of that, not starting from scratch.

Voter files come from different sources depending on your state and party affiliation. Your state party or county party committee is often the fastest path; state election authorities also typically provide voter registration data, sometimes for a fee. The file usually comes as a spreadsheet or CSV, which you import into your database software.

Configure your tracking fields

Before you start making contacts, decide what you're going to track and set up the fields to track it. At minimum, configure:

Support level scale (typically 1–5, with definitions for each level)
Survey questions for your ID conversations (what do you want canvassers to record at every door?)
Tags for key categories you'll want to filter on (yard sign requests, issue interests, volunteer interest)
Volunteer roles and paths
Donation tracking fields if you're using the same system for fundraising

Consistency matters more than completeness here. Better to track three things reliably than ten things inconsistently. Talk to your key staff and volunteers about what information will actually be usable before you build out an elaborate tracking system.

Worth noting: some of these fields will already be pre-configured depending on the database software you use.

Build your initial contact list

Before your first canvass, populate your database with the relationships you already have: people who have told you they support you, local leaders and allies you've identified, your personal and professional network. These become your first tagged supporters and your initial volunteer recruitment pool.

You'll also want to flag any contacts who should not be canvassed – people who have asked not to be contacted, addresses that are inaccessible, known opponents. Filtering these out from the start keeps your team from wasting time and avoids awkward situations.

Using your database throughout the campaign

A campaign database is most valuable when it's used consistently – when every contact gets logged, every update gets recorded, and every list gets built from the database rather than assembled manually. The table below shows how the database supports each phase of the campaign.

How the database supports each campaign phase
Phase	How you use your database
Setup	Import your voter file. Configure support levels, survey questions, and tags. Set up volunteer and donor paths. Add your initial contact list (supporters, known allies, existing relationships).
Launch & ID	Log canvassing and phone contacts. Record support levels from every conversation. Tag first-time contacts. Track event sign-ups and new supporter sign-ups from your website.
Persuasion	Filter to your persuasion universe. Log every contact attempt and outcome. Track movement in support scores. Identify supporters ready to be moved to a more active role.
GOTV	Build your GOTV universe from confirmed supporters. Log GOTV contacts and commitments. Track who has voted (via poll watcher reports or early vote data). Update contact priorities in real time as the day progresses.
Volunteers	Manage sign-ups and shift assignments. Track participation history to identify your most engaged volunteers. Log training completions and role assignments. Send targeted communications to active volunteers.
Fundraising	Manage donor records and giving history. Track outstanding asks and follow-ups. Segment donors for targeted asks.

The logging discipline

Key principle

The single most important habit in managing a campaign database is logging every contact. A voter who was canvassed but not logged is, from the database's perspective, a voter who was never canvassed. They'll appear on the next walk list. Your team will knock the same door again. Your support level data will be incomplete.

Build logging into your canvassing and phone banking workflow from the first shift. If you're using a mobile canvassing app, contacts get logged at the door. If you're using paper walk lists, someone needs to enter those results into the database before the next shift. The faster results get entered, the more current your data stays, and the more useful it is.

Keeping your data clean

Over the course of a campaign, your database accumulates errors: duplicate records, outdated phone numbers, contacts who have moved out of the district, merge conflicts from manual data entry. A clean database produces accurate contact lists; a messy one wastes your volunteers' time on bad contacts and distorts your picture of where your support actually stands.

Deduplicate regularly. Most database platforms have tools to identify likely duplicates (same name and address, or same contact information). They also usually can automatically merge records with the same unique identifiers, like email or voter file ID. When it doesn't happen automatically, make sure to merge duplicates before they multiply.
Update contact info when you learn it's wrong. A canvasser who finds out a phone number is disconnected should log that immediately, not leave it for someone else to discover on the next call shift.
Review your support level distribution periodically. If your database shows an unrealistically high percentage of strong supporters, your canvassers may be entering optimistic scores rather than accurate ones. Spot-check entries and retrain if needed.
Double-check before deleting. If you find a record that looks incorrect, review it carefully before deleting it. You may need the history later.

Next steps

Choose your platform. Pick a campaign database that covers the capabilities above – voter file import, support levels, list building, mobile canvassing integration, and multi-user access – before your campaign begins.
Import your voter file. Get your voter file from your state party, county party, or local election authority and import it as soon as your platform is set up.
Configure your tracking fields. Set up support levels, survey questions, and tags before your first canvass. Decide what you're tracking and make sure everyone knows the system.
Build your initial contact list. Add your known supporters, allies, and network before you start reaching out to new voters.
Train your team on logging. Every volunteer who makes contacts should know how to log them. Build this into your onboarding process from the start.
Make data hygiene a regular habit. Set a regular cadence (weekly or biweekly) for reviewing and cleaning your data. It's much easier to maintain a clean database than to clean a messy one.

Frequently asked questions

Do I really need a campaign database, or can I use a spreadsheet?: For a very small campaign (say, a single precinct race where you're making a few hundred contacts) a spreadsheet might be manageable. For anything larger, a purpose-built campaign database will save significant time and produce better results. The main advantages are multi-user access without version conflicts, structured tracking of support levels and survey responses, and the ability to filter your contact list to build targeted universes instantly. The cost of most campaign database platforms is low enough that it's rarely worth the operational friction of trying to run a real campaign out of a spreadsheet.
How is a campaign database different from a regular CRM?: A general CRM (customer relationship management) tool is built for business contact management like tracking leads, deals, and customer interactions. A campaign database is built for campaigns: it's designed to import and work with voter files, track canvassing outcomes, generate walk lists, manage volunteer shifts, and produce campaign finance compliance reports. Some campaigns use general CRMs and work around the gaps, but a purpose-built campaign database will handle the workflows campaigns actually use more cleanly.
What is a support level, and how do I use it?: A support level is a number you assign to a voter contact based on what you learn about their likelihood of supporting your campaign – typically on a 1-to-5 scale, where 1 means strong support and 5 means strong opposition. Support levels come from ID conversations: when a canvasser or phone banker talks to a voter and asks who they're supporting, that response gets translated into a support score. Your GOTV universe is drawn from your 1s and 2s. Your persuasion universe is your 3s. Your 4s and 5s generally don't get more resources. The support level system only works if canvassers use it consistently, and score-creep (everyone becoming a 1 or 2) is a risk on campaigns where volunteers want to report good results.
Who should have access to the campaign database?: Most campaigns give full access to senior staff and their campaign manager, and limited access to volunteers. Most campaign database platforms support role-based permissions, so you can give a canvassing volunteer access to their walk list and the ability to log contacts without being able to see donor records or change settings. At minimum, anyone who's logging contacts should be able to do so in real time. Anyone who's building universes or generating lists should have the appropriate access to filter and export. Keep sensitive records (donor information, personal notes on specific voters) on a need-to-know basis.
How do I get a voter file?: Voter files come from a few sources depending on your state and party affiliation. Your state or county Democratic or Republican party committee often provides access to the party's voter file, though they may charge a fee or set limitations on how it can be used. State election authorities typically provide voter registration data directly, sometimes for a fee. Commercial voter data vendors sell enhanced voter files with additional modeling data. The right path depends on your party, your state, and your budget. See the voter file guide for more detail.
What happens to my campaign database after the election?: What you do with your data after the election depends on your jurisdiction's rules, your party's data agreements, and what you plan to do next. If you're running again, your data is an asset, and the support scores, interaction history, and volunteer relationships you've built are a foundation for the next campaign. If you're not running again, consider whether to transfer your data to your local party committee (who can use it to support future candidates) or to another candidate you're supporting. Check your platform's terms of service and any party data agreements before making decisions about data transfer or deletion.

← Back to the full course